summaryrefslogtreecommitdiff
path: root/doc/development/post_deployment_migrations.md
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2020-01-30 15:09:15 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2020-01-30 15:09:15 +0000
commit536aa3a1f4b96abc4ca34489bf2cbe503afcded7 (patch)
tree88d08f7dfa29a32d6526773c4fe0fefd9f2bc7d1 /doc/development/post_deployment_migrations.md
parent50ae4065530c4eafbeb7c5ff2c462c48c02947ca (diff)
downloadgitlab-ce-536aa3a1f4b96abc4ca34489bf2cbe503afcded7.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/post_deployment_migrations.md')
-rw-r--r--doc/development/post_deployment_migrations.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/development/post_deployment_migrations.md b/doc/development/post_deployment_migrations.md
index a41096aa3eb..4d523178a21 100644
--- a/doc/development/post_deployment_migrations.md
+++ b/doc/development/post_deployment_migrations.md
@@ -9,13 +9,13 @@ when running `rake db:migrate`.
For example, this would run all migrations including any post deployment
migrations:
-```bash
+```shell
bundle exec rake db:migrate
```
This however will skip post deployment migrations:
-```bash
+```shell
SKIP_POST_DEPLOYMENT_MIGRATIONS=true bundle exec rake db:migrate
```
@@ -26,7 +26,7 @@ post deployment migrations after deploying a new version. Let's assume you
normally use the command `chef-client` to do so. To make use of this feature
you'd have to run this command as follows:
-```bash
+```shell
SKIP_POST_DEPLOYMENT_MIGRATIONS=true sudo chef-client
```
@@ -41,7 +41,7 @@ server but with the variable _unset_.
To create a post deployment migration you can use the following Rails generator:
-```bash
+```shell
bundle exec rails g post_deployment_migration migration_name_here
```