gitlab-org--gitlab-foss/doc/update/5.1-to-5.2.md

105 lines
2.7 KiB
Markdown
Raw Normal View History

2013-05-18 02:46:14 -04:00
# From 5.1 to 5.2
*Make sure you view this [upgrade guide from the `master` branch](../../../master/doc/update/5.1-to-5.2.md) for the most up to date instructions.*
2013-05-18 02:46:14 -04:00
2013-11-02 11:49:26 -04:00
## Warning
2014-04-24 18:48:22 -04:00
GitLab 5.2 is affected by critical security vulnerabilities CVE-2013-4490 and CVE-2013-4489.
2013-11-02 11:49:26 -04:00
2014-04-24 18:48:22 -04:00
## 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)
```bash
cd /home/git/gitlab
2013-10-07 08:16:04 -04:00
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
2014-04-24 18:48:22 -04:00
## 1. Stop server
2013-05-18 02:46:14 -04:00
sudo service gitlab stop
2014-04-24 18:48:22 -04:00
## 2. Get latest code
2013-05-18 02:46:14 -04:00
```bash
cd /home/git/gitlab
sudo -u git -H git fetch
sudo -u git -H git checkout 5-2-stable
```
2014-04-24 18:48:22 -04:00
## 3. Update gitlab-shell
2013-05-18 02:46:14 -04:00
```bash
cd /home/git/gitlab-shell
sudo -u git -H git fetch
sudo -u git -H git checkout v1.4.0
```
2014-04-24 18:48:22 -04:00
## 4. Install libs, migrations, etc.
2013-05-18 02:46:14 -04:00
```bash
cd /home/git/gitlab
# MySQL
2013-05-18 02:46:14 -04:00
sudo -u git -H bundle install --without development test postgres --deployment
#PostgreSQL
sudo -u git -H bundle install --without development test mysql --deployment
2013-05-18 02:46:14 -04:00
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
sudo -u git -H bundle exec rake assets:precompile RAILS_ENV=production
2013-05-18 02:46:14 -04:00
```
2014-04-24 18:48:22 -04:00
## 5. Update config files
2014-04-24 18:48:22 -04:00
- Make `/home/git/gitlab/config/gitlab.yml` same as https://gitlab.com/gitlab-org/gitlab-ce/blob/5-2-stable/config/gitlab.yml.example but with your settings.
- Make `/home/git/gitlab/config/puma.rb` same as https://gitlab.com/gitlab-org/gitlab-ce/blob/5-2-stable/config/puma.rb.example but with your settings.
2014-04-24 18:48:22 -04:00
## 6. Update Init script
```bash
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
```
2014-04-24 18:48:22 -04:00
## 7. Create uploads directory
```bash
cd /home/git/gitlab
sudo -u git -H mkdir public/uploads
sudo chmod -R u+rwX public/uploads
```
2014-04-24 18:48:22 -04:00
## 8. Start application
2013-05-18 02:46:14 -04:00
sudo service gitlab start
sudo service nginx restart
2014-04-24 18:48:22 -04:00
## 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 [upgrade guide from 5.0 to 5.1](5.0-to-5.1.md), except for the database migration (the backup is already migrated to the previous version).
2014-04-24 18:48:22 -04:00
### 2. Restore from the backup
```bash
cd /home/git/gitlab
2013-10-07 08:16:04 -04:00
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
```