From 34e31cb2aa44d799e74fc2b5e2d5e8947dd50b58 Mon Sep 17 00:00:00 2001 From: mibali <111276665+mibali@users.noreply.github.com> Date: Fri, 28 Feb 2025 14:57:34 +0000 Subject: [PATCH] Update upgrade.mdx Removed a Typo --- docs/admin/deploy/docker-compose/upgrade.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/admin/deploy/docker-compose/upgrade.mdx b/docs/admin/deploy/docker-compose/upgrade.mdx index 19f454d66..d951d65a4 100644 --- a/docs/admin/deploy/docker-compose/upgrade.mdx +++ b/docs/admin/deploy/docker-compose/upgrade.mdx @@ -93,7 +93,7 @@ To perform a multi-version upgrade via migrators [upgrade](/admin/updates/migrat > *Note: you may add the `--dry-run` flag to the `command:` to test things out before altering the dbs* 3. Run migrator with `docker-compose up migrator` - - Migrator `depends_on:` will ensure the databases are ready before attempting to run the migrator. Ensuring that database entry point scripts are run before the migrator attempts to connect to the databases. For users upgrading from a version earlier than `5.10.0`, a PostgreSQL version is required and will be performed automatically here. For more details, see [Upgradeing PostgreSQL](/admin/postgresql#upgrading-postgresql). + - Migrator `depends_on:` will ensure the databases are ready before attempting to run the migrator. Ensuring that database entry point scripts are run before the migrator attempts to connect to the databases. For users upgrading from a version earlier than `5.10.0`, a PostgreSQL version is required and will be performed automatically here. For more details, see [Upgrading PostgreSQL](/admin/postgresql#upgrading-postgresql). **Example:** ```sh