Skip to content

docs: Clarify how migrations are applied with serverpod start#599

Open
Zfinix wants to merge 1 commit into
mainfrom
chore/replace-dart-run-main-references
Open

docs: Clarify how migrations are applied with serverpod start#599
Zfinix wants to merge 1 commit into
mainfrom
chore/replace-dart-run-main-references

Conversation

@Zfinix

@Zfinix Zfinix commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

Summary

Notes that serverpod start applies migrations during local development (on first boot, or by pressing A in the terminal UI). The explicit --apply-migrations runtime command stays documented for production and automated pipelines.

The remaining dart run bin/main.dart mentions are intentional: the --role maintenance and production invocations are runtime calls that serverpod start should not replace (it is a development tool and always applies migrations).

Part of #565

## Apply migrations

Migrations are applied using the server runtime. To apply migrations, navigate to your project's `server` package directory, then start the server with the `--apply-migrations` flag. Migrations are applied as part of the startup sequence and the framework asserts that each migration is only applied once to the database.
During local development, `serverpod start` applies your migrations for you: pending migrations run on the first boot, and you can apply new ones at any time by pressing **A** in the terminal UI.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: Users scan documentation real quick. When scanning quickly, the text "pressing A" disappears and what stands out is the "dart run bin/main.dart...". Consider following the pattern in the "Build your first app", where Press R stands out by using a bullet.

Image

The same goes for "production and automated pipeline" which disappears in text. Consider if this should be a heading, to catch the attention of users searching for those particular use cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants