Commit f7b922c687dde96759b119dfaf0a5dd89eb4b9b8
1 parent
f2b37438
Exists in
master
and in
4 other branches
Unix line endings.
Showing
1 changed file
with
96 additions
and
96 deletions
Show diff stats
doc/update/5.4-to-6.0.md
| 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 deprecate teams as separate entity in 6.0 in favor of group membership. | ||
| 13 | -The old combination of groups and teams was confusing for a lot of people. | ||
| 14 | -And when the members of a team where changed this wasn't reflected in the project permissions. | ||
| 15 | -In GitLab 6.0 you will be able to add members to a group with a permission level for each member. | ||
| 16 | -These group members will have access to the projects in that group. | ||
| 17 | -Any changes to group members will immediately be reflected in the project permissions. | ||
| 18 | -You can even have multiple owners for a group, greatly simplifying administration. | ||
| 19 | - | ||
| 20 | -### 0. Backup | ||
| 21 | - | ||
| 22 | -It's useful to make a backup just in case things go south: | ||
| 23 | -(With MySQL, this may require granting "LOCK TABLES" privileges to the GitLab user on the database version) | ||
| 24 | - | ||
| 25 | -```bash | ||
| 26 | -cd /home/git/gitlab | ||
| 27 | -sudo -u git -H RAILS_ENV=production bundle exec rake gitlab:backup:create | ||
| 28 | -``` | ||
| 29 | - | ||
| 30 | -### 1. Stop server | ||
| 31 | - | ||
| 32 | - sudo service gitlab stop | ||
| 33 | - | ||
| 34 | -### 2. Get latest code | ||
| 35 | - | ||
| 36 | -```bash | ||
| 37 | -cd /home/git/gitlab | ||
| 38 | -sudo -u git -H git fetch | ||
| 39 | -sudo -u git -H git checkout 6-0-dev | ||
| 40 | -``` | ||
| 41 | - | ||
| 42 | -### 3. Install additional packages | ||
| 43 | - | ||
| 44 | -```bash | ||
| 45 | -# For reStructuredText markup language support install required package: | ||
| 46 | -sudo apt-get install python-docutils | ||
| 47 | -``` | ||
| 48 | - | ||
| 49 | -### 4. Install libs, migrations, etc. | ||
| 50 | - | ||
| 51 | -```bash | ||
| 52 | -cd /home/git/gitlab | ||
| 53 | - | ||
| 54 | -# MySQL | ||
| 55 | -sudo -u git -H bundle install --without development test postgres --deployment | ||
| 56 | - | ||
| 57 | -#PostgreSQL | ||
| 58 | -sudo -u git -H bundle install --without development test mysql --deployment | ||
| 59 | - | ||
| 60 | -sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production | ||
| 61 | -sudo -u git -H bundle exec rake migrate_groups RAILS_ENV=production | ||
| 62 | -sudo -u git -H bundle exec rake migrate_global_projects RAILS_ENV=production | ||
| 63 | -sudo -u git -H bundle exec rake migrate_keys RAILS_ENV=production | ||
| 64 | -sudo -u git -H bundle exec rake migrate_inline_notes RAILS_ENV=production | ||
| 65 | - | ||
| 66 | -``` | ||
| 67 | - | ||
| 68 | -### 5. Update config files | ||
| 69 | - | ||
| 70 | -* 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. | ||
| 71 | -* 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. | ||
| 72 | - | ||
| 73 | -### 6. Update Init script | ||
| 74 | - | ||
| 75 | -```bash | ||
| 76 | -sudo rm /etc/init.d/gitlab | ||
| 77 | -sudo curl --output /etc/init.d/gitlab https://raw.github.com/gitlabhq/gitlabhq/5-3-stable/lib/support/init.d/gitlab | ||
| 78 | -sudo chmod +x /etc/init.d/gitlab | ||
| 79 | -``` | ||
| 80 | - | ||
| 81 | -### 7. Start application | ||
| 82 | - | ||
| 83 | - sudo service gitlab start | ||
| 84 | - sudo service nginx restart | ||
| 85 | - | ||
| 86 | -### 8. Check application status | ||
| 87 | - | ||
| 88 | -Check if GitLab and its environment are configured correctly: | ||
| 89 | - | ||
| 90 | - sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production | ||
| 91 | - | ||
| 92 | -To make sure you didn't miss anything run a more thorough check with: | ||
| 93 | - | ||
| 94 | - sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production | ||
| 95 | - | ||
| 96 | -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 deprecate teams as separate entity in 6.0 in favor of group membership. | ||
| 13 | +The old combination of groups and teams was confusing for a lot of people. | ||
| 14 | +And when the members of a team where changed this wasn't reflected in the project permissions. | ||
| 15 | +In GitLab 6.0 you will be able to add members to a group with a permission level for each member. | ||
| 16 | +These group members will have access to the projects in that group. | ||
| 17 | +Any changes to group members will immediately be reflected in the project permissions. | ||
| 18 | +You can even have multiple owners for a group, greatly simplifying administration. | ||
| 19 | + | ||
| 20 | +### 0. Backup | ||
| 21 | + | ||
| 22 | +It's useful to make a backup just in case things go south: | ||
| 23 | +(With MySQL, this may require granting "LOCK TABLES" privileges to the GitLab user on the database version) | ||
| 24 | + | ||
| 25 | +```bash | ||
| 26 | +cd /home/git/gitlab | ||
| 27 | +sudo -u git -H RAILS_ENV=production bundle exec rake gitlab:backup:create | ||
| 28 | +``` | ||
| 29 | + | ||
| 30 | +### 1. Stop server | ||
| 31 | + | ||
| 32 | + sudo service gitlab stop | ||
| 33 | + | ||
| 34 | +### 2. Get latest code | ||
| 35 | + | ||
| 36 | +```bash | ||
| 37 | +cd /home/git/gitlab | ||
| 38 | +sudo -u git -H git fetch | ||
| 39 | +sudo -u git -H git checkout 6-0-dev | ||
| 40 | +``` | ||
| 41 | + | ||
| 42 | +### 3. Install additional packages | ||
| 43 | + | ||
| 44 | +```bash | ||
| 45 | +# For reStructuredText markup language support install required package: | ||
| 46 | +sudo apt-get install python-docutils | ||
| 47 | +``` | ||
| 48 | + | ||
| 49 | +### 4. Install libs, migrations, etc. | ||
| 50 | + | ||
| 51 | +```bash | ||
| 52 | +cd /home/git/gitlab | ||
| 53 | + | ||
| 54 | +# MySQL | ||
| 55 | +sudo -u git -H bundle install --without development test postgres --deployment | ||
| 56 | + | ||
| 57 | +#PostgreSQL | ||
| 58 | +sudo -u git -H bundle install --without development test mysql --deployment | ||
| 59 | + | ||
| 60 | +sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production | ||
| 61 | +sudo -u git -H bundle exec rake migrate_groups RAILS_ENV=production | ||
| 62 | +sudo -u git -H bundle exec rake migrate_global_projects RAILS_ENV=production | ||
| 63 | +sudo -u git -H bundle exec rake migrate_keys RAILS_ENV=production | ||
| 64 | +sudo -u git -H bundle exec rake migrate_inline_notes RAILS_ENV=production | ||
| 65 | + | ||
| 66 | +``` | ||
| 67 | + | ||
| 68 | +### 5. Update config files | ||
| 69 | + | ||
| 70 | +* 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. | ||
| 71 | +* 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. | ||
| 72 | + | ||
| 73 | +### 6. Update Init script | ||
| 74 | + | ||
| 75 | +```bash | ||
| 76 | +sudo rm /etc/init.d/gitlab | ||
| 77 | +sudo curl --output /etc/init.d/gitlab https://raw.github.com/gitlabhq/gitlabhq/5-3-stable/lib/support/init.d/gitlab | ||
| 78 | +sudo chmod +x /etc/init.d/gitlab | ||
| 79 | +``` | ||
| 80 | + | ||
| 81 | +### 7. Start application | ||
| 82 | + | ||
| 83 | + sudo service gitlab start | ||
| 84 | + sudo service nginx restart | ||
| 85 | + | ||
| 86 | +### 8. Check application status | ||
| 87 | + | ||
| 88 | +Check if GitLab and its environment are configured correctly: | ||
| 89 | + | ||
| 90 | + sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production | ||
| 91 | + | ||
| 92 | +To make sure you didn't miss anything run a more thorough check with: | ||
| 93 | + | ||
| 94 | + sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production | ||
| 95 | + | ||
| 96 | +If all items are green, then congratulations upgrade complete! |