app:dev:setup¶

Bootstrap the development environment: run migrations, generate OAuth keys, seed OAuth clients, and create dev users. This is a dev-only command that orchestrates the other setup commands as isolated subprocesses.

The development lifecycle runs this only when initializing an empty instance. make exec below targets the current worktree's preview. Do not rerun setup with --fresh as a lifecycle or adoption step.

Quick start¶

make exec cmd="php bin/console app:dev:setup"

Start from a clean database:

make exec cmd="php bin/console app:dev:setup --fresh"

Options¶

Details¶

The command runs these steps in order, each as a separate php bin/console subprocess:

1. If --fresh: doctrine:schema:drop --force --full-database, then the cache directory is removed.
2. doctrine:migrations:migrate --no-interaction
3. Unless --skip-keys or a matching existing key pair is found: app:oauth:generate-keys --no-interaction
4. app:auth:setup-clients --origin=<instance-origin> --no-interaction
5. app:dev:create-users --no-interaction

Unless --skip-keys is supplied, existing OAuth keys are checked as a pair before migrations. A valid matching pair is retained; partial or mismatched keys cause failure rather than replacement. The origin is passed to OAuth client setup for new clients. Existing client identity is retained.

Subprocesses boot a fresh kernel, so they survive the cache clear performed by --fresh (which deletes compiled container classes the parent process has already loaded). A failed subprocess prints its error output, stops setup before later steps, and returns a failure exit code.

On success the command prints the dev account credentials (admin@baander.test / admin, user@baander.test / user).

Tips¶

• Use --fresh only when you want a completely clean database — it drops every table.
• Pass --skip-keys if you already have OAuth keys and don't want them regenerated.
• Never run this in production.