Database Setup in Develop Mode

Database Setup is an optional step in Develop Mode that runs after code generation. The AI agent reads your generated codebase, identifies models and migration files, and executes the schema against your real database — optionally populating it with seed data for testing.

Prerequisites

Database Setup unlocks only after the Development step (code generation via Task Queue or Task Plans) has been completed for the project. If the step appears locked, finish development first.

How it works

1. You provide a database connection string.
2. Ileen’s agent clones the repository (already in its workspace), reads model definitions, ORM configs, and migration scripts.
3. The agent creates tables / collections, runs migrations, and optionally seeds data.
4. A structured result is returned: tables created, indexes created, seed status, and any warnings.

If the agent finds no database code (e.g., a pure API proxy or a static site), it returns a No Database Needed result rather than failing — no action is taken.

Supported databases

Type	Examples
PostgreSQL	PostgreSQL, CockroachDB
MySQL	MySQL, MariaDB
MongoDB	MongoDB, DocumentDB
SQLite	SQLite (local file)

Select Auto-detect to let the agent infer the type from your connection string and codebase.

Step 1 — Enter your connection string

In the Database Connection section:

1. Paste your full connection URI into the Connection String field.
   Example: postgresql://user:secret@db.myhost.com:5432/myapp
2. Use the eye icon to toggle visibility of the credential.
3. Select the Database Type (or leave it as Auto-detect).
4. Optionally enable Include seed data to populate tables with realistic mock data.

Click Save Credentials to persist the connection string securely. A preview of the saved string (masked) appears below the form.

Security

Connection strings are stored encrypted. Never paste credentials into plain text files or share them in the Discussion chat.

Step 2 — Run setup

Click Setup Database. The view transitions to a three-step progress tracker:

Step	What happens
Reading credentials	Agent retrieves the saved connection string
Agent analyzing codebase & executing setup	Agent reads models, runs migrations, creates schema
Verifying results	Agent confirms tables exist and are accessible

A progress bar tracks overall completion.

Understanding the results

Success

The Database Setup Complete card shows:

• Tables / Collections Created — list of all created entities
• Indexes Created — performance indexes applied
• Seed data inserted — confirmation if you enabled seeding
• Warnings — non-fatal issues (e.g., a table already existed)

No database needed

If the agent determines your project has no database layer, it returns a friendly message explaining its reasoning. You can safely proceed to the Deploy step.

Failure

If the setup fails:

• An error banner appears with the agent’s error message.
• The form returns to the Credentials phase.
• Fix the issue (wrong connection string, wrong DB type, network access) and retry.

Troubleshooting

Symptom	Likely cause	Fix
Connection refused	Database not reachable from Ileen’s cloud	Allow egress from Ileen’s IP range or use a publicly accessible host
Authentication failed	Wrong username/password	Re-enter credentials and click Save before running
No database code found	Agent result is “No DB needed” even though you have a DB	Check that model files / migration scripts are present in the committed code
Seed data not inserted	Seeding disabled or no seed scripts found	Enable the checkbox and ensure seed fixtures exist in the codebase

Running setup again

Click Run Again at the bottom of any result card to return to the credentials form and re-run. This is safe to do multiple times — the agent checks for existing tables and skips or updates as appropriate, depending on your ORM/migration setup.