gitlab-org--gitlab-foss/doc/update/6.1-to-6.2.md

123 lines
3.5 KiB
Markdown
Raw Normal View History

2013-10-01 04:05:58 -04:00
# From 6.1 to 6.2
*Make sure you view this [upgrade guide from the `master` branch](../../../master/doc/update/6.1-to-6.2.md) for the most up to date instructions.*
2013-10-01 04:05:58 -04:00
2014-04-24 18:48:22 -04:00
**You should update to 6.1 before installing 6.2 so all the necessary conversions are run.**
2013-10-01 04:05:58 -04:00
2014-04-24 18:48:22 -04:00
## 0. Backup
2013-10-01 04:05:58 -04:00
2014-04-24 18:48:22 -04:00
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).
2013-10-01 04:05:58 -04:00
```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
2013-10-01 04:05:58 -04:00
```
2014-04-24 18:48:22 -04:00
## 1. Stop server
2013-10-01 04:05:58 -04:00
sudo service gitlab stop
2014-04-24 18:48:22 -04:00
## 2. Get latest code
2013-10-01 04:05:58 -04:00
```bash
cd /home/git/gitlab
sudo -u git -H git fetch --all
2013-11-02 12:05:06 -04:00
sudo -u git -H git checkout 6-2-stable # Latest version of 6-2-stable addresses CVE-2013-4489
# For GitLab Enterprise Edition: sudo -u git -H git checkout 6-2-stable-ee
2013-10-01 04:05:58 -04:00
```
2014-04-24 18:48:22 -04:00
## 3. Update gitlab-shell
2013-11-02 12:05:06 -04:00
```bash
cd /home/git/gitlab-shell
sudo -u git -H git fetch
sudo -u git -H git checkout v1.7.9 # Addresses multiple critical security vulnerabilities
2013-11-02 12:05:06 -04:00
```
2014-04-24 18:48:22 -04:00
## 4. Install additional packages
2013-10-18 09:22:23 -04:00
```bash
# Add support for logrotate for better log file handling
2013-10-18 09:22:23 -04:00
sudo apt-get install logrotate
```
2014-04-24 18:48:22 -04:00
## 5. Install libs, migrations, etc.
2013-10-01 04:05:58 -04:00
```bash
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:clean RAILS_ENV=production
sudo -u git -H bundle exec rake assets:precompile RAILS_ENV=production
sudo -u git -H bundle exec rake cache:clear RAILS_ENV=production
```
2014-04-24 18:48:22 -04:00
## 6. Update config files
2013-10-01 04:05:58 -04:00
2014-04-24 18:48:22 -04:00
TIP: to see what changed in `gitlab.yml.example` in this release use next command:
```
git diff 6-1-stable:config/gitlab.yml.example 6-2-stable:config/gitlab.yml.example
```
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/6-2-stable/config/gitlab.yml.example but with your settings.
2014-04-24 18:48:22 -04:00
- Make `/home/git/gitlab/config/unicorn.rb` same as https://gitlab.com/gitlab-org/gitlab-ce/blob/6-2-stable/config/unicorn.rb.example but with your settings.
- Copy rack attack middleware config:
```bash
sudo -u git -H cp config/initializers/rack_attack.rb.example config/initializers/rack_attack.rb
```
- Uncomment `config.middleware.use Rack::Attack` in `/home/git/gitlab/config/application.rb`
- Set up logrotate.
2013-10-18 09:22:23 -04:00
```bash
sudo cp lib/support/logrotate/gitlab /etc/logrotate.d/gitlab
```
2013-10-01 04:05:58 -04:00
2014-04-24 18:48:22 -04:00
## 7. Update Init script
2013-10-01 04:05:58 -04:00
```bash
sudo rm /etc/init.d/gitlab
sudo cp lib/support/init.d/gitlab /etc/init.d/gitlab
2013-10-01 04:05:58 -04:00
```
2014-04-24 18:48:22 -04:00
## 8. Start application
2013-10-01 04:05:58 -04:00
sudo service gitlab start
sudo service nginx restart
2014-04-24 18:48:22 -04:00
## 9. Check application status
2013-10-01 04:05:58 -04:00
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 (6.1)
### 1. Revert the code to the previous version
2014-04-24 18:48:22 -04:00
Follow the [upgrade guide from 6.0 to 6.1](6.0-to-6.1.md), except for the database migration (the backup is already migrated to the previous version).
2013-10-01 04:05:58 -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
2013-10-01 04:05:58 -04:00
```