kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/doc/update/5.2-to-5.3.md

86 lines
2.3 KiB
Markdown
Raw Normal View History

Update docs from 5.2 to 5.3
2013-06-20 02:51:09 -04:00
# From 5.2 to 5.3
Add security warnings to update docs
2013-11-02 11:49:26 -04:00
## Warning
Update docs to markdown style guide.
2014-04-24 18:48:22 -04:00
We should only specify unsafe version, never give advise since it it perishable.
2014-03-24 10:17:43 -04:00
GitLab 5.3 is affected by critical security vulnerabilities CVE-2013-4490 and CVE-2013-4489.
Add security warnings to update docs
2013-11-02 11:49:26 -04:00
Update docs to markdown style guide.
2014-04-24 18:48:22 -04:00
## 0. Backup
Update docs from 5.2 to 5.3
2013-06-20 02:51:09 -04:00
Update docs to markdown style guide.
2014-04-24 18:48:22 -04:00
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):
Update docs from 5.2 to 5.3
2013-06-20 02:51:09 -04:00
```bash
cd /home/git/gitlab
Fix sudo commands in update guides
2013-10-07 08:16:04 -04:00
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
Update docs from 5.2 to 5.3
2013-06-20 02:51:09 -04:00
```
Update docs to markdown style guide.
2014-04-24 18:48:22 -04:00
## 1. Stop server
Update docs from 5.2 to 5.3
2013-06-20 02:51:09 -04:00
sudo service gitlab stop
Update docs to markdown style guide.
2014-04-24 18:48:22 -04:00
## 2. Get latest code
Update docs from 5.2 to 5.3
2013-06-20 02:51:09 -04:00
```bash
cd /home/git/gitlab
sudo -u git -H git fetch
sudo -u git -H git checkout 5-3-stable
```
Update docs to markdown style guide.
2014-04-24 18:48:22 -04:00
## 3. Install libs, migrations, etc.
Update docs from 5.2 to 5.3
2013-06-20 02:51:09 -04:00
```bash
cd /home/git/gitlab
# MySQL
sudo -u git -H bundle install --without development test postgres --deployment
#PostgreSQL
sudo -u git -H bundle install --without development test mysql --deployment
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
Add assets precompile step for fixing activities lost and some UI style issues
2013-07-20 07:20:21 -04:00
sudo -u git -H bundle exec rake assets:precompile RAILS_ENV=production
Update docs from 5.2 to 5.3
2013-06-20 02:51:09 -04:00
```
Update docs to markdown style guide.
2014-04-24 18:48:22 -04:00
## 4. Update config files
Update docs from 5.2 to 5.3
2013-06-20 02:51:09 -04:00
Update docs to markdown style guide.
2014-04-24 18:48:22 -04:00
- Make `/home/git/gitlab/config/gitlab.yml` same as https://gitlab.com/gitlab-org/gitlab-ce/blob/5-3-stable/config/gitlab.yml.example but with your settings.
- Make `/home/git/gitlab/config/puma.rb` same as https://gitlab.com/gitlab-org/gitlab-ce/blob/5-3-stable/config/puma.rb.example but with your settings.
Update docs from 5.2 to 5.3
2013-06-20 02:51:09 -04:00
Update docs to markdown style guide.
2014-04-24 18:48:22 -04:00
## 5. Update Init script
Update docs from 5.2 to 5.3
2013-06-20 02:51:09 -04:00
```bash
sudo rm /etc/init.d/gitlab
follow curl redirects Update `curl` commands to follow redirects (see http://curl.haxx.se/docs/manpage.html#-L). Current `curl` commands will return unexpected results if the requested content has been moved and is returning information about where it has been moved to. Including the `-L` option tells `curl` to follow the redirect so the file can be correctly acquired.
2014-08-12 01:01:37 -04:00
sudo curl -L --output /etc/init.d/gitlab https://raw.github.com/gitlabhq/gitlabhq/5-3-stable/lib/support/init.d/gitlab
Update docs from 5.2 to 5.3
2013-06-20 02:51:09 -04:00
sudo chmod +x /etc/init.d/gitlab
```
Update docs to markdown style guide.
2014-04-24 18:48:22 -04:00
## 6. Start application
Update docs from 5.2 to 5.3
2013-06-20 02:51:09 -04:00
sudo service gitlab start
sudo service nginx restart
Update docs to markdown style guide.
2014-04-24 18:48:22 -04:00
## 7. Check application status
Update docs from 5.2 to 5.3
2013-06-20 02:51:09 -04:00
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!
## Things went south? Revert to previous version (5.2)
### 1. Revert the code to the previous version
Update docs to markdown style guide.
2014-04-24 18:48:22 -04:00
Remove backticks in markdown links that cause ugly code blocks in GitLab.
2014-08-21 11:25:14 -04:00
Follow the [upgrade guide from 5.1 to 5.2](5.1-to-5.2.md), except for the database migration (the backup is already migrated to the previous version).
Update docs from 5.2 to 5.3
2013-06-20 02:51:09 -04:00
### 2. Restore from the backup:
```bash
cd /home/git/gitlab
Fix sudo commands in update guides
2013-10-07 08:16:04 -04:00
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
Update docs from 5.2 to 5.3
2013-06-20 02:51:09 -04:00
```
Copy permalink