Commit 4f07a6a9 authored by Sytse Sijbrandij's avatar Sytse Sijbrandij

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

parents 79bea312 121f20d2
# From 5.4 to 6.0 # From 5.4 to 6.0
### 0. Backup ### Deprecations
It's useful to make a backup just in case things go south: #### Global projects
(With MySQL, this may require granting "LOCK TABLES" privileges to the GitLab user on the database version)
We deprecated root(global) namespace for projects.
```bash 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.
cd /home/git/gitlab
sudo -u git -H RAILS_ENV=production bundle exec rake gitlab:backup:create #### Teams
```
We drop teams support as separate entity for 6.0 in favor of group membership.
### 1. Stop server So now you will be able to manage group members in order to provide access to corresponding projects.
sudo service gitlab stop
### 0. Backup
### 2. Get latest code
It's useful to make a backup just in case things go south:
```bash (With MySQL, this may require granting "LOCK TABLES" privileges to the GitLab user on the database version)
cd /home/git/gitlab
sudo -u git -H git fetch ```bash
sudo -u git -H git checkout 6-0-dev cd /home/git/gitlab
``` sudo -u git -H RAILS_ENV=production bundle exec rake gitlab:backup:create
```
### 3. Install libs, migrations, etc.
### 1. Stop server
```bash
cd /home/git/gitlab sudo service gitlab stop
# MySQL ### 2. Get latest code
sudo -u git -H bundle install --without development test postgres --deployment
```bash
#PostgreSQL cd /home/git/gitlab
sudo -u git -H bundle install --without development test mysql --deployment sudo -u git -H git fetch
sudo -u git -H git checkout 6-0-dev
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production ```
sudo -u git -H bundle exec rake migrate_groups RAILS_ENV=production
sudo -u git -H bundle exec rake migrate_global_projects RAILS_ENV=production ### 3. Install libs, migrations, etc.
sudo -u git -H bundle exec rake migrate_keys RAILS_ENV=production
```bash
``` cd /home/git/gitlab
### 4. Update config files # MySQL
sudo -u git -H bundle install --without development test postgres --deployment
* 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.
* 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. #PostgreSQL
sudo -u git -H bundle install --without development test mysql --deployment
### 5. Update Init script
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
```bash sudo -u git -H bundle exec rake migrate_groups RAILS_ENV=production
sudo rm /etc/init.d/gitlab sudo -u git -H bundle exec rake migrate_global_projects RAILS_ENV=production
sudo curl --output /etc/init.d/gitlab https://raw.github.com/gitlabhq/gitlabhq/5-3-stable/lib/support/init.d/gitlab sudo -u git -H bundle exec rake migrate_keys RAILS_ENV=production
sudo chmod +x /etc/init.d/gitlab
``` ```
### 6. Start application ### 4. Update config files
sudo service gitlab start * 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.
sudo service nginx restart * 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.
### 7. Check application status ### 5. Update Init script
Check if GitLab and its environment are configured correctly: ```bash
sudo rm /etc/init.d/gitlab
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production sudo curl --output /etc/init.d/gitlab https://raw.github.com/gitlabhq/gitlabhq/5-3-stable/lib/support/init.d/gitlab
sudo chmod +x /etc/init.d/gitlab
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 ### 6. Start application
If all items are green, then congratulations upgrade complete! sudo service gitlab start
sudo service nginx restart
### 7. Check application status
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!
\ No newline at end of file
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment