Commit 6000c719 authored by Jacob Vosmaer's avatar Jacob Vosmaer

Improve DB dump instructions

parent c14de4fd
...@@ -4,6 +4,9 @@ Sometimes it is useful to import the database from a production environment ...@@ -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 into a staging environment for testing. The procedure below assumes you have
SSH+sudo access to both the production environment and the staging VM. 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 On the staging VM, add the following line to `/etc/gitlab/gitlab.rb` to speed up
large database imports. large database imports.
...@@ -12,6 +15,8 @@ large database imports. ...@@ -12,6 +15,8 @@ large database imports.
echo "postgresql['checkpoint_segments'] = 64" | sudo tee -a /etc/gitlab/gitlab.rb echo "postgresql['checkpoint_segments'] = 64" | sudo tee -a /etc/gitlab/gitlab.rb
sudo touch /etc/gitlab/skip-auto-migrations sudo touch /etc/gitlab/skip-auto-migrations
sudo gitlab-ctl reconfigure 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 Next, we let the production environment stream a compressed SQL dump to our
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment