Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
gitlab-ce
Commits
5d543eb1
Commit
5d543eb1
authored
Sep 08, 2014
by
Robert Schilling
Browse files
Options
Browse Files
Download
Plain Diff
Merge pull request #7668 from bbodenmiller/patch-15
add cleanup section to 5.0 upgrade guide
parents
de6f4c31
9a1dcf8d
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
40 additions
and
5 deletions
+40
-5
doc/update/4.2-to-5.0.md
doc/update/4.2-to-5.0.md
+40
-5
No files found.
doc/update/4.2-to-5.0.md
View file @
5d543eb1
...
...
@@ -10,7 +10,7 @@ GitLab 5.0 is affected by critical security vulnerability CVE-2013-4490.
-
Self signed SSL certificates are not supported until GitLab 5.1
-
**requires ruby1.9.3**
## 0. Stop
gitl
ab
## 0. Stop
GitL
ab
sudo service gitlab stop
...
...
@@ -41,7 +41,7 @@ git checkout v1.1.0
# copy config
cp
config.yml.example config.yml
# change url to
gitl
ab instance
# change url to
GitL
ab instance
# ! make sure url end with '/' like 'https://gitlab.example/'
vim config.yml
...
...
@@ -49,14 +49,14 @@ vim config.yml
./support/rewrite-hooks.sh
# check ruby version for git user ( 1.9 required!! )
#
gitl
ab shell requires system ruby 1.9
#
GitL
ab shell requires system ruby 1.9
ruby
-v
# exit from git user
exit
```
## 4. Copy
gitl
ab instance to git user
## 4. Copy
GitL
ab instance to git user
```
bash
sudo cp
-R
/home/gitlab/gitlab /home/git/gitlab
...
...
@@ -162,8 +162,43 @@ sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production
```
**P.S. If everything works as expected you can remove gitlab user from system**
## 9. Cleanup
**If everything works as expected you can cleanup some old things**
Recommend you wait a bit and do a backup before completing the following.
```
bash
# remove GitLab user from system
sudo
userdel
-r
gitlab
cd
/home/git
# cleanup .profile
## remove text from .profile added during gitolite installation:
## PATH=\$PATH:/home/git/bin
## export PATH
## to see what a clean .profile for new users on your system would look like see /etc/skel/.profile
sudo
-u
git
-H
vim .profile
# remove gitolite
sudo rm
-R
bin
sudo rm
-Rf
gitolite
sudo rm
-R
.gitolite
sudo rm
.gitolite.rc
sudo rm
-f
gitlab.pub
sudo rm
projects.list
# reset tmp folders
sudo
service gitlab stop
cd
/home/git/gitlab
sudo rm
-R
tmp
sudo
-u
git
-H
mkdir
tmp
sudo chmod
-R
u+rwX tmp/
# reboot system
sudo
reboot
# login, check that GitLab is running fine
cd
/home/git/gitlab
sudo
-u
git
-H
bundle
exec
rake gitlab:check
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