summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCindy Pallares <cindy@gitlab.com>2017-04-17 23:18:03 +0000
committerCindy Pallares <cindy@gitlab.com>2017-04-20 13:36:25 -0500
commit21eecf4dda85b270749284d1c537c9d2a07b09af (patch)
treef66f468b7b2c0e096243be904dd109c5cca835aa
parent85d37c091c69b23a4395f43f6894b59245ae7e7c (diff)
downloadgitlab-ce-21eecf4dda85b270749284d1c537c9d2a07b09af.tar.gz
Reword backup & restore secrets descriptionbackup-restore-docs-update
The new description will make it more clear that there are 3 separate things being affected and not just 2FA.
-rw-r--r--doc/raketasks/backup_restore.md10
1 files changed, 6 insertions, 4 deletions
diff --git a/doc/raketasks/backup_restore.md b/doc/raketasks/backup_restore.md
index 65fcfc77ab1..e680a560888 100644
--- a/doc/raketasks/backup_restore.md
+++ b/doc/raketasks/backup_restore.md
@@ -18,10 +18,12 @@ another is through backup restore.
To restore a backup, you will also need to restore `/etc/gitlab/gitlab-secrets.json`
(for omnibus packages) or `/home/git/gitlab/.secret` (for installations
-from source). This file contains the database encryption key and CI secret
-variables used for two-factor authentication. If you fail to restore this
-encryption key file along with the application data backup, users with two-factor
-authentication enabled will lose access to your GitLab server.
+from source). This file contains the database encryption key,
+[CI secret variables](../ci/variables/README.md#secret-variables), and
+secret variables used for [two-factor authentication](../security/two_factor_authentication.md).
+If you fail to restore this encryption key file along with the application data
+backup, users with two-factor authentication enabled and GitLab Runners will
+lose access to your GitLab server.
## Create a backup of the GitLab system