BigW Consortium Gitlab
Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
G
gitlab-ce
Project
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
Forest Godfrey
gitlab-ce
Commits
ca907e4f
Commit
ca907e4f
authored
May 28, 2014
by
dosire
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Make it more obvious that GitLab Shell should be upgraded.
parent
6bd114a7
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
8 deletions
+6
-8
upgrader.md
doc/update/upgrader.md
+6
-8
No files found.
doc/update/upgrader.md
View file @
ca907e4f
...
...
@@ -31,19 +31,16 @@ __GitLab Upgrader is available only for GitLab version 6.4.2 or higher__
### 4. 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:
Check if GitLab and its dependencies are configured correctly:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production
If all items are green, then congratulations upgrade is complete!
###
(optional) 5. Application status check fails
###
5. Upgrade GitLab Shell (if needed)
If the
`gitlab:check`
task reports an old version of gitlab-shell and recommends upgrading, upgrade gitlab-shell by running:
If the
`gitlab:check`
task reports an outdated version of gitlab-shell you should upgrade it.
Upgrade it by running the commands below after replacing 1.9.4 with the correct version number:
```
cd /home/git/gitlab-shell
...
...
@@ -53,7 +50,8 @@ sudo -u git -H git checkout v1.9.4
### One line upgrade command
You've read through the entire guide, and probably did all the steps manually. Here is a one liner for convenience, the next time you upgrade:
You've read through the entire guide and probably already did all the steps one by one.
Here is a one line command with step 1 to 4 for the next time you upgrade:
```
bash
cd
/home/git/gitlab
;
sudo
-u
git
-H
bundle
exec
rake gitlab:backup:create
RAILS_ENV
=
production
;
\
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment