diff options
| author | Evan Read <eread@gitlab.com> | 2018-11-13 10:39:21 +1000 |
|---|---|---|
| committer | Evan Read <eread@gitlab.com> | 2018-11-13 10:53:38 +1000 |
| commit | 20146580a0618e7c9a726c6d53e51d3ca60b63e8 (patch) | |
| tree | 5d70d8989f3897f84468dde83ca9521d759fc12c /doc/development/post_deployment_migrations.md | |
| parent | dbb342d4d95d24a1313c64be4a923ea5f759d3fa (diff) | |
| download | gitlab-ce-20146580a0618e7c9a726c6d53e51d3ca60b63e8.tar.gz | |
Resolve Markdown ordered lists not conforming to styleguidedocs/fix-ordered-list-item-prefix
Diffstat (limited to 'doc/development/post_deployment_migrations.md')
| -rw-r--r-- | doc/development/post_deployment_migrations.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/development/post_deployment_migrations.md b/doc/development/post_deployment_migrations.md index cfc91539bee..5986efa9974 100644 --- a/doc/development/post_deployment_migrations.md +++ b/doc/development/post_deployment_migrations.md @@ -57,13 +57,13 @@ depends on this column being present while it's running. Normally you'd follow these steps in such a case: 1. Stop the GitLab instance -2. Run the migration removing the column -3. Start the GitLab instance again +1. Run the migration removing the column +1. Start the GitLab instance again Using post deployment migrations we can instead follow these steps: 1. Deploy a new version of GitLab while ignoring post deployment migrations -2. Re-run `rake db:migrate` but without the environment variable set +1. Re-run `rake db:migrate` but without the environment variable set Here we don't need any downtime as the migration takes place _after_ a new version (which doesn't depend on the column anymore) has been deployed. |