summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDmitriy Zaporozhets <dzaporozhets@gitlab.com>2015-06-16 09:33:45 +0000
committerDmitriy Zaporozhets <dzaporozhets@gitlab.com>2015-06-16 09:33:45 +0000
commite840ccaf1531b604544af09b84e031eab7b4a458 (patch)
treef6355ad69ef9ee05bd28af6deaeee73e8ed3e0ca
parent698f79e8b5387c1b7cfe3abafa62ab82cad5363b (diff)
parent6000c7199e2cec97022911ea24c1a66f615f3434 (diff)
downloadgitlab-ce-e840ccaf1531b604544af09b84e031eab7b4a458.tar.gz
Merge branch 'db-dump-instructions' into 'master'
Improve DB dump instructions See merge request !1868
-rw-r--r--doc/development/db_dump.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/development/db_dump.md b/doc/development/db_dump.md
index 4ad3bd534e0..21f1b3edecd 100644
--- a/doc/development/db_dump.md
+++ b/doc/development/db_dump.md
@@ -4,6 +4,9 @@ Sometimes it is useful to import the database from a production environment
into a staging environment for testing. The procedure below assumes you have
SSH+sudo access to both the production environment and the staging VM.
+**Destroy your staging VM** when you are done with it. It is important to avoid
+data leaks.
+
On the staging VM, add the following line to `/etc/gitlab/gitlab.rb` to speed up
large database imports.
@@ -12,6 +15,8 @@ large database imports.
echo "postgresql['checkpoint_segments'] = 64" | sudo tee -a /etc/gitlab/gitlab.rb
sudo touch /etc/gitlab/skip-auto-migrations
sudo gitlab-ctl reconfigure
+sudo gitlab-ctl stop unicorn
+sudo gitlab-ctl stop sidekiq
```
Next, we let the production environment stream a compressed SQL dump to our