From 612a849a6cba1765bc41d30d4e931195dcdf64cf Mon Sep 17 00:00:00 2001 From: GitLab Bot Date: Tue, 3 Mar 2020 03:08:31 +0000 Subject: Add latest changes from gitlab-org/gitlab@master --- doc/raketasks/user_management.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'doc/raketasks/user_management.md') 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 `` 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 -- cgit v1.2.1