5.0-to-5.1.md 2.55 KB
Newer Older
Yves Senn's avatar
Yves Senn committed
1
# From 5.0 to 5.1
2
*Make sure you view this [upgrade guide from the `master` branch](https://gitlab.com/gitlab-org/gitlab-ce/tree/master/doc/update/5.0-to-5.1.md) for the most up to date instructions.*
Yves Senn's avatar
Yves Senn committed
3

4
## Warning
5

6
GitLab 5.1 is affected by critical security vulnerability CVE-2013-4490.
7

8
## Release notes
9

10 11
- `unicorn` replaced with `puma`
- merge request cached diff will be truncated
12

13
## 1. Stop server
14 15 16

    sudo service gitlab stop

17
## 2. Get latest code
18

19 20
```bash
cd /home/git/gitlab
21 22 23 24
sudo -u git -H git fetch
sudo -u git -H git checkout 5-1-stable
```

25
## 3. Update gitlab-shell
26

27 28 29 30
```bash
cd /home/git/gitlab-shell
sudo -u git -H git fetch
sudo -u git -H git checkout v1.3.0
31 32 33 34 35
# replace your old config with the new one
sudo -u git -H mv config.yml config.yml.old
sudo -u git -H cp config.yml.example config.yml
# edit options to match old config
sudo -u git -H vi config.yml
36 37
```

38
## 4. Install libs, migrations etc
Grégoire Paris's avatar
Grégoire Paris committed
39

40 41 42 43
```bash
cd /home/git/gitlab
sudo rm tmp/sockets/gitlab.socket
sudo -u git -H cp config/puma.rb.example config/puma.rb
Grégoire Paris's avatar
Grégoire Paris committed
44

45 46 47 48 49 50 51 52 53
# 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

# 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)
54
sudo -u git -H bundle install --without development test postgres --deployment
55

56 57
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
sudo -u git -H bundle exec rake migrate_merge_requests RAILS_ENV=production
58
sudo -u git -H bundle exec rake assets:precompile RAILS_ENV=production
59 60
```

61
## 5. Update init.d script with a new one
62 63 64 65

```bash
# init.d
sudo rm /etc/init.d/gitlab
66
sudo curl --location --output /etc/init.d/gitlab https://raw.github.com/gitlabhq/gitlab-recipes/5-1-stable/init.d/gitlab
67 68 69
sudo chmod +x /etc/init.d/gitlab
```

70
## 6. MySQL grant privileges
71

72
Only if you are using MySQL:
73 74 75 76 77 78 79

```bash
mysql -u root -p
mysql> GRANT LOCK TABLES ON `gitlabhq_production`.* TO 'gitlab'@'localhost';
mysql> \q
```

80
## 7. Start application
81 82

    sudo service gitlab start
83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101

## 8. Check installation


```bash
# In 5-10 seconds lets check gitlab-shell
sudo -u git -H /home/git/gitlab-shell/bin/check

# Example of success output
# Check GitLab API access: OK
# Check directories and files:
#         /home/git/repositories: OK
#         /home/git/.ssh/authorized_keys: OK


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

```