From 0d6bbb942d5cd3cc5b6e9dcae8076f2d5547d745 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marc-Andr=C3=A9=20Bombeck?= Date: Thu, 15 Oct 2026 19:08:17 +0200 Subject: [PATCH] docs(self-hosting): take the dump before pulling, not after the pending-migrations line --- docs/self-hosting/getting-started.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/self-hosting/getting-started.md b/docs/self-hosting/getting-started.md index 983a8267f..fac39c9b6 100644 --- a/docs/self-hosting/getting-started.md +++ b/docs/self-hosting/getting-started.md @@ -394,9 +394,9 @@ HealthLog: Running database migrations... ``` or `HealthLog: Database schema is up to date.` when the image brings none. -The line is a notice and does not pause the start. If you see a count and -have no dump yet, stop the container (`docker compose stop app`), take the -dump, and start it again; the migrations run on that start. +The line is a notice and does not pause the start: the migrations run right +after it. So the dump belongs before step 2, not after you see the line; by +then the database is already being migrated. For the ordering on a host where you want the migration result before the new container takes traffic, see [`docs/ops/deploy.md`](../ops/deploy.md).