5.1-to-5.2.md 2.6 KB
Edit Raw Blame History Permalink


From 5.1 to 5.2
Warning
GitLab 5.2 is affected by critical security vulnerabilities CVE-2013-4490 and CVE-2013-4489. Please update to GitLab 5.4 directly.
0. Backup
It's useful to make a backup just in case things go south:
(With MySQL, this may require granting "LOCK TABLES" privileges to the GitLab user on the database version)


    cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production

  
1. Stop server

  
    sudo service gitlab stop

  
2. Get latest code

  
    cd /home/git/gitlab
sudo -u git -H git fetch
sudo -u git -H git checkout 5-2-stable

  
3. Update gitlab-shell

  
    cd /home/git/gitlab-shell
sudo -u git -H git fetch
sudo -u git -H git checkout v1.4.0

  
4. Install libs, migrations, etc.

  
    cd /home/git/gitlab

# MySQL
sudo -u git -H bundle install --without development test postgres --deployment

#PostgreSQL
sudo -u git -H bundle install --without development test mysql --deployment

sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production

sudo -u git -H bundle exec rake assets:precompile RAILS_ENV=production

  
5. Update config files

Make /home/git/gitlab/config/gitlab.yml same as https://github.com/gitlabhq/gitlabhq/blob/5-2-stable/config/gitlab.yml.example but with your settings.
Make /home/git/gitlab/config/puma.rb same as https://github.com/gitlabhq/gitlabhq/blob/5-2-stable/config/puma.rb.example but with your settings.

6. Update Init script

  
    cd /home/git/gitlab
sudo rm /etc/init.d/gitlab
sudo cp lib/support/init.d/gitlab /etc/init.d/gitlab 
sudo chmod +x /etc/init.d/gitlab

  
7. Create uploads directory

  
    cd /home/git/gitlab
sudo -u git -H mkdir public/uploads
sudo chmod -R u+rwX  public/uploads

  
8. Start application

  
    sudo service gitlab start
sudo service nginx restart

  
9. Check application status
Check if GitLab and its environment are configured correctly:


    sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production

  
To make sure you didn't miss anything run a more thorough check with:


    sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production

  
If all items are green, then congratulations upgrade complete!
Things went south? Revert to previous version (5.1)
1. Revert the code to the previous version
Follow the <code>upgrade guide from 5.0 to 5.1</code>, except for the database migration 
(The backup is already migrated to the previous version)
2. Restore from the backup:

  
    cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production