2014-09-17 12:27:23 -04:00
# From 6.0 to 7.3
# GitLab 7.3 has not been released yet!
2014-08-19 08:24:02 -04:00
## Global issue numbers
As of 6.1 issue numbers are project specific. This means all issues are renumbered and get a new number in their URL. If you use an old issue number URL and the issue number does not exist yet you are redirected to the new one. This conversion does not trigger if the old number already exists for this project, this is unlikely but will happen with old issues and large projects.
2014-08-20 03:54:47 -04:00
## Editable labels
In GitLab 7.2 we replace Issue and Merge Request tags with labels, making it
2014-09-21 07:28:47 -04:00
possible to edit the label text and color. The characters `?` , `&` and `,` are
2014-08-20 03:54:47 -04:00
no longer allowed however so those will be removed from your tags during the
database migrations for GitLab 7.2.
2014-08-19 08:24:02 -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
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
## 1. Stop server
sudo service gitlab stop
2014-08-20 23:05:17 -04:00
## 2. Update Ruby
If you are still using Ruby 1.9.3 or below, you will need to update Ruby.
You can check which version you are running with `ruby -v` .
If you are you running Ruby 2.0.x, you do not need to upgrade ruby, but can consider doing so for performance reasons.
If you are running Ruby 2.1.1 consider upgrading to 2.1.2, because of the high memory usage of Ruby 2.1.1.
Install, update dependencies:
```bash
sudo apt-get install build-essential zlib1g-dev libyaml-dev libssl-dev libgdbm-dev libreadline-dev libncurses5-dev libffi-dev curl
```
Download and compile Ruby:
```bash
mkdir /tmp/ruby & & cd /tmp/ruby
curl --progress ftp://ftp.ruby-lang.org/pub/ruby/2.1/ruby-2.1.2.tar.gz | tar xz
cd ruby-2.1.2
./configure --disable-install-rdoc
make
sudo make install
```
Install Bundler:
```bash
sudo gem install bundler --no-ri --no-rdoc
```
## 3. Get latest code
2014-08-19 08:24:02 -04:00
```bash
cd /home/git/gitlab
sudo -u git -H git fetch --all
```
For GitLab Community Edition:
```bash
2014-09-17 12:27:23 -04:00
sudo -u git -H git checkout 7-3-stable
2014-08-19 08:24:02 -04:00
```
OR
For GitLab Enterprise Edition:
```bash
2014-09-17 12:27:23 -04:00
sudo -u git -H git checkout 7-3-stable-ee
2014-08-19 08:24:02 -04:00
```
2014-08-20 23:05:17 -04:00
## 4. Install additional packages
2014-08-19 08:24:02 -04:00
```bash
# Add support for lograte for better log file handling
sudo apt-get install logrotate
2014-08-21 07:59:04 -04:00
2014-08-26 00:10:53 -04:00
# Install pkg-config and cmake, which is needed for the latest versions of rugged
sudo apt-get install pkg-config cmake
2014-08-19 08:24:02 -04:00
```
2014-09-17 12:27:23 -04:00
## 5. Configure Redis to use sockets
# Configure redis to use sockets
sudo cp /etc/redis/redis.conf /etc/redis/redis.conf.orig
2014-09-21 08:05:48 -04:00
# Disable Redis listening on TCP by setting 'port' to 0
sed 's/^port .*/port 0/' /etc/redis/redis.conf.orig | sudo tee /etc/redis/redis.conf
# Enable Redis socket for default Debian / Ubuntu path
echo 'unixsocket /var/run/redis/redis.sock' | sudo tee -a /etc/redis/redis.conf
2014-09-17 12:27:23 -04:00
# Activate the changes to redis.conf
sudo service redis-server restart
# Add git to the redis group
sudo usermod -aG redis git
# Configure Redis connection settings
sudo -u git -H cp config/resque.yml.example config/resque.yml
2014-09-21 08:05:48 -04:00
# Change the Redis socket path if you are not using the default Debian / Ubuntu configuration
2014-09-17 12:27:23 -04:00
sudo -u git -H editor config/resque.yml
# Configure gitlab-shell to use Redis sockets
2014-09-21 08:05:48 -04:00
sudo -u git -H sed -i 's|^ # socket.*| socket: /var/run/redis/redis.sock|' /home/git/gitlab-shell/config.yml
2014-09-17 12:27:23 -04:00
## 6. Update gitlab-shell
2014-08-19 08:24:02 -04:00
```bash
cd /home/git/gitlab-shell
sudo -u git -H git fetch
2014-09-17 12:27:23 -04:00
sudo -u git -H git checkout v2.0.0
2014-08-19 08:24:02 -04:00
```
2014-09-17 12:27:23 -04:00
## 7. Install libs, migrations, etc.
2014-08-19 08:24:02 -04:00
```bash
cd /home/git/gitlab
# MySQL installations (note: the line below states '--without ... postgres')
sudo -u git -H bundle install --without development test postgres --deployment
# PostgreSQL installations (note: the line below states '--without ... mysql')
sudo -u git -H bundle install --without development test mysql --deployment
# Run database migrations
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
# Enable internal issue IDs (introduced in GitLab 6.1)
sudo -u git -H bundle exec rake migrate_iids RAILS_ENV=production
# Clean up assets and cache
sudo -u git -H bundle exec rake assets:clean assets:precompile cache:clear RAILS_ENV=production
# Close access to gitlab-satellites for others
sudo chmod u+rwx,g+rx,o-rwx /home/git/gitlab-satellites
2014-09-01 19:41:37 -04:00
# Update init.d script
sudo cp lib/support/init.d/gitlab /etc/init.d/gitlab
2014-08-19 08:24:02 -04:00
```
2014-09-17 12:27:23 -04:00
## 8. Update config files
2014-08-19 08:24:02 -04:00
2014-09-21 07:28:47 -04:00
TIP: to see what changed in `gitlab.yml.example` in this release use next command:
2014-08-19 08:24:02 -04:00
```
2014-09-17 12:27:23 -04:00
git diff 6-0-stable:config/gitlab.yml.example 7-3-stable:config/gitlab.yml.example
2014-08-19 08:24:02 -04:00
```
2014-09-17 12:27:23 -04:00
* Make `/home/git/gitlab/config/gitlab.yml` the same as https://gitlab.com/gitlab-org/gitlab-ce/blob/7-3-stable/config/gitlab.yml.example but with your settings.
* Make `/home/git/gitlab/config/unicorn.rb` the same as https://gitlab.com/gitlab-org/gitlab-ce/blob/7-3-stable/config/unicorn.rb.example but with your settings.
* Make `/home/git/gitlab-shell/config.yml` the same as https://gitlab.com/gitlab-org/gitlab-shell/blob/v2.0.0/config.yml.example but with your settings.
* HTTP setups: Make `/etc/nginx/sites-available/nginx` the same as https://gitlab.com/gitlab-org/gitlab-ce/blob/7-3-stable/lib/support/nginx/gitlab but with your settings.
* HTTPS setups: Make `/etc/nginx/sites-available/nginx-ssl` the same as https://gitlab.com/gitlab-org/gitlab-ce/blob/7-3-stable/lib/support/nginx/gitlab-ssl but with your settings.
2014-08-19 08:24:02 -04:00
* Copy rack attack middleware config
```bash
sudo -u git -H cp config/initializers/rack_attack.rb.example config/initializers/rack_attack.rb
```
* Set up logrotate
```bash
sudo cp lib/support/logrotate/gitlab /etc/logrotate.d/gitlab
```
2014-09-17 12:27:23 -04:00
## 9. Start application
2014-08-19 08:24:02 -04:00
sudo service gitlab start
sudo service nginx restart
2014-09-17 12:27:23 -04:00
## 10. Check application status
2014-08-19 08:24:02 -04:00
Check if GitLab and its environment are configured correctly:
cd /home/git/gitlab
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!
2014-09-17 12:27:23 -04:00
## 11. Update OmniAuth configuration
2014-08-19 08:53:37 -04:00
When using Google omniauth login, changes of the Google account required.
Ensure that `Contacts API` and the `Google+ API` are enabled in the [Google Developers Console ](https://console.developers.google.com/ ).
More details can be found at the [integration documentation ](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/integration/google.md ).
2014-08-19 08:24:02 -04:00
## Things went south? Revert to previous version (6.0)
### 1. Revert the code to the previous version
2014-08-21 11:25:14 -04:00
Follow the [upgrade guide from 5.4 to 6.0 ](5.4-to-6.0.md ), except for the database migration (the backup is already migrated to the previous version).
2014-08-19 08:24:02 -04:00
### 2. Restore from the backup:
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
```
## Login issues after upgrade?
2014-08-19 08:53:37 -04:00
If running in HTTPS mode, be sure to read [Can't Verify CSRF token authenticity ](https://github.com/gitlabhq/gitlab-public-wiki/wiki/Trouble-Shooting-Guide#cant-verify-csrf-token-authenticitycant-get-past-login-pageredirected-to-login-page )