kotovalexarian-likes-gitlab
/
gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Whitespace

This commit is contained in:
Robert Speicher 2015-09-21 18:02:50 -04:00
parent 12969a14dd
commit 7fa0c793d2
1 changed files with 14 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
doc/migrate_ci_to_ce/README.md
View File

@ -31,10 +31,10 @@ The migration is divided into three parts and covers manual and omnibus installa
# Manual installation # Manual installation
sudo service gitlab_ci stop sudo service gitlab_ci stop
# Omnibus installation # Omnibus installation
sudo gitlab-ctl stop ci-unicorn ci-sidekiq sudo gitlab-ctl stop ci-unicorn ci-sidekiq
#### 2. Create a backup #### 2. Create a backup
The migration procedure modifies the structure of the CI database. If something The migration procedure modifies the structure of the CI database. If something
@ -59,20 +59,20 @@ database configuration files:
# Manual installation # Manual installation
cd /home/gitlab_ci/gitlab-ci cd /home/gitlab_ci/gitlab-ci
sudo -u gitlab_ci -H bundle exec backup:create RAILS_ENV=production sudo -u gitlab_ci -H bundle exec backup:create RAILS_ENV=production
# Omnibus installation # Omnibus installation
sudo gitlab-ci-rake backup:create sudo gitlab-ci-rake backup:create
- If CI uses MySQL, and CE (or EE) uses PostgreSQL, create the backup with this - If CI uses MySQL, and CE (or EE) uses PostgreSQL, create the backup with this
command (note the `MYSQL_TO_POSTGRESQL` flag): command (note the `MYSQL_TO_POSTGRESQL` flag):
# Manual installation # Manual installation
cd /home/gitlab_ci/gitlab-ci cd /home/gitlab_ci/gitlab-ci
sudo -u gitlab_ci -H bundle exec backup:create RAILS_ENV=production MYSQL_TO_POSTGRESQL=1 sudo -u gitlab_ci -H bundle exec backup:create RAILS_ENV=production MYSQL_TO_POSTGRESQL=1
# Omnibus installation # Omnibus installation
sudo gitlab-ci-rake backup:create MYSQL_TO_POSTGRESQL=1 sudo gitlab-ci-rake backup:create MYSQL_TO_POSTGRESQL=1
#### 3. Remove cronjob (manual installation) #### 3. Remove cronjob (manual installation)
# Manual installation # Manual installation
@ -101,7 +101,7 @@ Before you can migrate data you need to stop the GitLab service first:
# Manual installation # Manual installation
sudo service gitlab stop sudo service gitlab stop
# Omnibus installation # Omnibus installation
sudo gitlab-ctl stop unicorn sidekiq sudo gitlab-ctl stop unicorn sidekiq
@ -113,16 +113,16 @@ installation. Create a backup before proceeding:
# Manual installation # Manual installation
cd /home/git/gitlab cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
# Omnibus installation # Omnibus installation
sudo gitlab-rake gitlab:backup:create sudo gitlab-rake gitlab:backup:create
It's possible to speedup backup creation. To do that you can skip repositories and uploads. It's possible to speedup backup creation. To do that you can skip repositories and uploads.
# Manual installation # Manual installation
cd /home/git/gitlab cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production SKIP=repositories,uploads sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production SKIP=repositories,uploads
# Omnibus installation # Omnibus installation
sudo gitlab-rake gitlab:backup:create SKIP=repositories,uploads sudo gitlab-rake gitlab:backup:create SKIP=repositories,uploads
@ -158,7 +158,7 @@ The new options include configuration settings for GitLab CI.
# Manual installation # Manual installation
sudo cp -v /home/gitlab_ci/gitlab-ci/tmp/backups/*_gitlab_ci_backup.tar /home/git/gitlab/tmp/backups sudo cp -v /home/gitlab_ci/gitlab-ci/tmp/backups/*_gitlab_ci_backup.tar /home/git/gitlab/tmp/backups
sudo chown git:git /home/git/gitlab/tmp/backups/*_gitlab_ci_backup.tar sudo chown git:git /home/git/gitlab/tmp/backups/*_gitlab_ci_backup.tar
# Omnibus installation # Omnibus installation
sudo cp -v /var/opt/gitlab/ci-backups/*_gitlab_ci_backup.tar /var/opt/gitlab/backups/ sudo cp -v /var/opt/gitlab/ci-backups/*_gitlab_ci_backup.tar /var/opt/gitlab/backups/
sudo chown git:git /var/opt/gitlab/backups/*_gitlab_ci_backup.tar sudo chown git:git /var/opt/gitlab/backups/*_gitlab_ci_backup.tar
@ -169,7 +169,7 @@ You can try to use ssh-agent from your local machine to have that: login to your
# Manual installation # Manual installation
scp /home/gitlab_ci/gitlab-ci/tmp/backups/*_gitlab_ci_backup.tar root@gitlab.example.com:/home/git/gitlab/tmp/backup scp /home/gitlab_ci/gitlab-ci/tmp/backups/*_gitlab_ci_backup.tar root@gitlab.example.com:/home/git/gitlab/tmp/backup
# Omnibus installation # Omnibus installation
scp /var/opt/gitlab/ci-backups/*_gitlab_ci_backup.tar root@gitlab.example.com:/var/opt/gitlab/backups/ scp /var/opt/gitlab/ci-backups/*_gitlab_ci_backup.tar root@gitlab.example.com:/var/opt/gitlab/backups/
@ -180,7 +180,7 @@ GitLab CE or EE database:
# Manual installation # Manual installation
sudo -u git -H bundle exec rake ci:migrate RAILS_ENV=production sudo -u git -H bundle exec rake ci:migrate RAILS_ENV=production
# Omnibus installation # Omnibus installation
sudo gitlab-rake ci:migrate sudo gitlab-rake ci:migrate
@ -192,7 +192,7 @@ You can start GitLab CE (or EE) now and see if everything is working:
# Manual installation # Manual installation
sudo service gitlab start sudo service gitlab start
# Omnibus installation # Omnibus installation
sudo gitlab-ctl restart unicorn sidekiq sudo gitlab-ctl restart unicorn sidekiq