Download as
Browse Code »

Commit 4f07a6a99cab8f8ae3ad0a786a6cc9a837955c08

Authored by Sytse Sijbrandij
2 parents 79bea312 121f20d2
Exists in master and in 4 other branches 6-8-stable, 7-0-stable, 7-0-stable-spb, spb-stable

Merge branch 'improve/6-0-update-docs' of /home/git/repositories/gitlab/gitlabhq

Showing 1 changed file with 84 additions and 71 deletions   Show diff stats
doc/update/5.4-to-6.0.md
  Diff comments   View file @4f07a6a
1   -# From 5.4 to 6.0
2   -
3   -### 0. Backup
4   -
5   -It's useful to make a backup just in case things go south:
6   -(With MySQL, this may require granting "LOCK TABLES" privileges to the GitLab user on the database version)
7   -
8   -```bash
9   -cd /home/git/gitlab
10   -sudo -u git -H RAILS_ENV=production bundle exec rake gitlab:backup:create
11   -```
12   -
13   -### 1. Stop server
14   -
15   - sudo service gitlab stop
16   -
17   -### 2. Get latest code
18   -
19   -```bash
20   -cd /home/git/gitlab
21   -sudo -u git -H git fetch
22   -sudo -u git -H git checkout 6-0-dev
23   -```
24   -
25   -### 3. Install libs, migrations, etc.
26   -
27   -```bash
28   -cd /home/git/gitlab
29   -
30   -# MySQL
31   -sudo -u git -H bundle install --without development test postgres --deployment
32   -
33   -#PostgreSQL
34   -sudo -u git -H bundle install --without development test mysql --deployment
35   -
36   -sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
37   -sudo -u git -H bundle exec rake migrate_groups RAILS_ENV=production
38   -sudo -u git -H bundle exec rake migrate_global_projects RAILS_ENV=production
39   -sudo -u git -H bundle exec rake migrate_keys RAILS_ENV=production
40   -
41   -```
42   -
43   -### 4. Update config files
44   -
45   -* Make `/home/git/gitlab/config/gitlab.yml` same as https://github.com/gitlabhq/gitlabhq/blob/5-3-stable/config/gitlab.yml.example but with your settings.
46   -* Make `/home/git/gitlab/config/puma.rb` same as https://github.com/gitlabhq/gitlabhq/blob/5-3-stable/config/puma.rb.example but with your settings.
47   -
48   -### 5. Update Init script
49   -
50   -```bash
51   -sudo rm /etc/init.d/gitlab
52   -sudo curl --output /etc/init.d/gitlab https://raw.github.com/gitlabhq/gitlabhq/5-3-stable/lib/support/init.d/gitlab
53   -sudo chmod +x /etc/init.d/gitlab
54   -```
55   -
56   -### 6. Start application
57   -
58   - sudo service gitlab start
59   - sudo service nginx restart
60   -
61   -### 7. Check application status
62   -
63   -Check if GitLab and its environment are configured correctly:
64   -
65   - sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
66   -
67   -To make sure you didn't miss anything run a more thorough check with:
68   -
69   - sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production
70   -
71   -If all items are green, then congratulations upgrade complete!
  1 +# From 5.4 to 6.0
  2 +
  3 +### Deprecations
  4 +
  5 +#### Global projects
  6 +
  7 +We deprecated root(global) namespace for projects.
  8 +So you need to move all your global projects under group/users manually before update or it will be moved automatically to owner namespace during update.
  9 +
  10 +#### Teams
  11 +
  12 +We drop teams support as separate entity for 6.0 in favor of group membership.
  13 +So now you will be able to manage group members in order to provide access to corresponding projects.
  14 +
  15 +
  16 +### 0. Backup
  17 +
  18 +It's useful to make a backup just in case things go south:
  19 +(With MySQL, this may require granting "LOCK TABLES" privileges to the GitLab user on the database version)
  20 +
  21 +```bash
  22 +cd /home/git/gitlab
  23 +sudo -u git -H RAILS_ENV=production bundle exec rake gitlab:backup:create
  24 +```
  25 +
  26 +### 1. Stop server
  27 +
  28 + sudo service gitlab stop
  29 +
  30 +### 2. Get latest code
  31 +
  32 +```bash
  33 +cd /home/git/gitlab
  34 +sudo -u git -H git fetch
  35 +sudo -u git -H git checkout 6-0-dev
  36 +```
  37 +
  38 +### 3. Install libs, migrations, etc.
  39 +
  40 +```bash
  41 +cd /home/git/gitlab
  42 +
  43 +# MySQL
  44 +sudo -u git -H bundle install --without development test postgres --deployment
  45 +
  46 +#PostgreSQL
  47 +sudo -u git -H bundle install --without development test mysql --deployment
  48 +
  49 +sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
  50 +sudo -u git -H bundle exec rake migrate_groups RAILS_ENV=production
  51 +sudo -u git -H bundle exec rake migrate_global_projects RAILS_ENV=production
  52 +sudo -u git -H bundle exec rake migrate_keys RAILS_ENV=production
  53 +
  54 +```
  55 +
  56 +### 4. Update config files
  57 +
  58 +* Make `/home/git/gitlab/config/gitlab.yml` same as https://github.com/gitlabhq/gitlabhq/blob/5-3-stable/config/gitlab.yml.example but with your settings.
  59 +* Make `/home/git/gitlab/config/puma.rb` same as https://github.com/gitlabhq/gitlabhq/blob/5-3-stable/config/puma.rb.example but with your settings.
  60 +
  61 +### 5. Update Init script
  62 +
  63 +```bash
  64 +sudo rm /etc/init.d/gitlab
  65 +sudo curl --output /etc/init.d/gitlab https://raw.github.com/gitlabhq/gitlabhq/5-3-stable/lib/support/init.d/gitlab
  66 +sudo chmod +x /etc/init.d/gitlab
  67 +```
  68 +
  69 +### 6. Start application
  70 +
  71 + sudo service gitlab start
  72 + sudo service nginx restart
  73 +
  74 +### 7. Check application status
  75 +
  76 +Check if GitLab and its environment are configured correctly:
  77 +
  78 + sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
  79 +
  80 +To make sure you didn't miss anything run a more thorough check with:
  81 +
  82 + sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production
  83 +
  84 +If all items are green, then congratulations upgrade complete!
72 85 \ No newline at end of file
... ...