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.
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
* 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: