diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-03 03:08:31 +0000 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-03 03:08:31 +0000 |
commit | 612a849a6cba1765bc41d30d4e931195dcdf64cf (patch) | |
tree | e4062e4c9852496b731a7de9016553b64a7a433d /doc/raketasks/user_management.md | |
parent | bd8fb5668ae739a83d55ec5ca4a04344eef2167e (diff) | |
download | gitlab-ce-612a849a6cba1765bc41d30d4e931195dcdf64cf.tar.gz |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/raketasks/user_management.md')
-rw-r--r-- | doc/raketasks/user_management.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/raketasks/user_management.md b/doc/raketasks/user_management.md index 04f8ad59153..637f3604d98 100644 --- a/doc/raketasks/user_management.md +++ b/doc/raketasks/user_management.md @@ -91,7 +91,7 @@ production: Next, generate a new secret: -``` +```shell # omnibus-gitlab sudo gitlab-rake secret @@ -102,7 +102,7 @@ bundle exec rake secret RAILS_ENV=production Now you need to stop the GitLab server, back up the existing secrets file and update the database: -``` +```shell # omnibus-gitlab sudo gitlab-ctl stop sudo cp config/secrets.yml config/secrets.yml.bak @@ -122,7 +122,7 @@ error. Finally, change `config/secrets.yml` to set `otp_key_base` to `<new key>` and restart. Again, make sure you're operating in the **production** section. -``` +```shell # omnibus-gitlab sudo gitlab-ctl start @@ -133,7 +133,7 @@ sudo /etc/init.d/gitlab start If there are any problems (perhaps using the wrong value for `old_key`), you can restore your backup of `config/secrets.yml` and rollback the changes: -``` +```shell # omnibus-gitlab sudo gitlab-ctl stop sudo gitlab-rake gitlab:two_factor:rotate_key:rollback filename=backup.csv |