2017-11-01 15:56:40 +00:00
---
comments: false
---
2013-11-20 10:44:46 +00:00
# From 6.2 to 6.3
2017-02-06 14:46:58 +00:00
*Make sure you view this [upgrade guide from the `master` branch ](https://gitlab.com/gitlab-org/gitlab-ce/tree/master/doc/update/6.2-to-6.3.md ) for the most up to date instructions.*
2013-11-20 10:44:46 +00:00
2014-04-24 22:48:22 +00:00
**Requires version: 6.1 or 6.2.**
2013-11-20 10:44:46 +00:00
2014-04-24 22:48:22 +00:00
## 0. Backup
2013-11-20 10:44:46 +00:00
2014-04-24 22:48:22 +00: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-11-20 10:44:46 +00:00
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
2014-04-24 22:48:22 +00:00
## 1. Stop server
2013-11-20 10:44:46 +00:00
sudo service gitlab stop
2014-04-24 22:48:22 +00:00
## 2. Get latest code
2013-11-20 10:44:46 +00:00
```bash
cd /home/git/gitlab
2014-01-20 09:38:16 +00:00
sudo -u git -H git fetch --all
2013-11-22 13:18:47 +00:00
sudo -u git -H git checkout 6-3-stable
2014-01-20 09:38:16 +00:00
# For GitLab Enterprise Edition: sudo -u git -H git checkout 6-3-stable-ee
2013-11-20 10:44:46 +00:00
```
2014-04-24 22:48:22 +00:00
## 3. Update gitlab-shell (and its config)
2013-11-20 10:44:46 +00: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
```
2014-08-04 20:32:41 +00:00
The gitlab-shell config changed recently, so check for config file changes and make `/home/git/gitlab-shell/config.yml` the same as < https: // github . com / gitlabhq / gitlab-shell / blob / master / config . yml . example >
2013-11-24 05:09:55 +00:00
2014-04-24 22:48:22 +00:00
## 4. Install libs, migrations, etc.
2013-11-20 10:44:46 +00:00
```bash
cd /home/git/gitlab
2016-06-01 15:01:14 +00:00
# The Modernizr gem was yanked from RubyGems. It is required for GitLab >= 2.8.0
# Edit `Gemfile` and change `gem "modernizr", "2.5.3"` to
# `gem "modernizr-rails", "2.7.1"``
sudo -u git -H vim Gemfile
2013-11-20 10:44:46 +00:00
# MySQL
2016-06-01 15:01:14 +00:00
# Run a bundle install without deployment to generate the new Gemfile
sudo -u git -H bundle install --without development test postgres --no-deployment
# Install libs (with deployment this time)
2013-11-20 10:44:46 +00:00
sudo -u git -H bundle install --without development test postgres --deployment
2013-11-26 09:30:56 +00:00
# PostgreSQL
2013-11-20 10:44:46 +00:00
2016-06-01 15:01:14 +00:00
# Run a bundle install without deployment to generate the new Gemfile
sudo -u git -H bundle install --without development test mysql --no-deployment
# Install libs (with deployment this time)
sudo -u git -H bundle install --without development test mysql --deployment
2013-11-20 10:44:46 +00:00
2016-06-01 15:01:14 +00:00
# Both MySQL and PostgreSQL
2013-11-26 09:31:02 +00:00
# Run database migrations
2013-11-20 10:44:46 +00:00
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
2013-11-26 09:31:02 +00:00
# Clean up assets and cache
sudo -u git -H bundle exec rake assets:clean assets:precompile cache:clear RAILS_ENV=production
2013-11-20 10:44:46 +00:00
```
2014-04-24 22:48:22 +00:00
## 5. Update config files
2013-11-20 10:44:46 +00:00
2014-08-04 20:32:41 +00:00
TIP: to see what changed in gitlab.yml.example in this release use next command:
2013-11-20 10:44:46 +00:00
```
2013-11-22 13:58:27 +00:00
git diff 6-2-stable:config/gitlab.yml.example 6-3-stable:config/gitlab.yml.example
2013-11-20 10:44:46 +00:00
```
2019-01-24 06:52:33 +00:00
- Make `/home/git/gitlab/config/gitlab.yml` same as < https: // gitlab . com / gitlab-org / gitlab-ce / blob / 6-3-stable / config / gitlab . yml . example > but with your settings.
- Make `/home/git/gitlab/config/unicorn.rb` same as < https: // gitlab . com / gitlab-org / gitlab-ce / blob / 6-3-stable / config / unicorn . rb . example > but with your settings.
2013-12-08 16:45:56 +00:00
```bash
# Copy rack attack middleware config
cd /home/git/gitlab
sudo -u git -H cp config/initializers/rack_attack.rb.example config/initializers/rack_attack.rb
```
2013-11-20 10:44:46 +00:00
2014-04-24 22:48:22 +00:00
## 6. Update Init script
2013-11-20 10:44:46 +00:00
```bash
2013-11-26 09:22:23 +00:00
sudo cp lib/support/init.d/gitlab /etc/init.d/gitlab
2013-11-20 10:44:46 +00:00
```
2014-04-24 22:48:22 +00:00
## 7. Start application
2013-11-20 10:44:46 +00:00
sudo service gitlab start
sudo service nginx restart
2014-04-24 22:48:22 +00:00
## 8. Check application status
2013-11-20 10:44:46 +00: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.2)
### 1. Revert the code to the previous version
2014-04-24 22:48:22 +00:00
2014-08-21 15:25:14 +00:00
Follow the [upgrade guide from 6.1 to 6.2 ](6.1-to-6.2.md ), except for the database migration (the backup is already migrated to the previous version).
2013-11-20 10:44:46 +00:00
### 2. Restore from the backup:
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
```