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
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
b7d095cf
Commit
b7d095cf
authored
Jun 20, 2014
by
Dmitriy Zaporozhets
Browse files
Options
Browse Files
Download
Plain Diff
Merge branch '7.0-ce-to-ee' into 'master'
Add 7.0 ce to ee guide
parents
e677ef34
88200cfb
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
87 additions
and
0 deletions
+87
-0
doc/update/7.0-ce-to-ee.md
doc/update/7.0-ce-to-ee.md
+87
-0
No files found.
doc/update/7.0-ce-to-ee.md
0 → 100644
View file @
b7d095cf
# From Community Edition 7.0 to Enterprise Edition 7.0
This guide assumes you have a correctly configured and tested installation of GitLab Community Edition 7.0.
If you run into any trouble or if you have any questions please contact us at support@gitlab.com.
### 0. Backup
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)
```
bash
cd
/home/git/gitlab
sudo
-u
git
-H
bundle
exec
rake gitlab:backup:create
RAILS_ENV
=
production
```
### 1. Stop server
sudo service gitlab stop
### 2. Get the EE code
```
bash
cd
/home/git/gitlab
sudo
-u
git
-H
git remote add ee https://gitlab.com/subscribers/gitlab-ee.git
sudo
-u
git
-H
git fetch
--all
sudo
-u
git
-H
git checkout 7-0-stable-ee
```
### 3. Update config files
*
Make
`/home/git/gitlab/config/gitlab.yml`
same as /home/git/gitlab/config/gitlab.yml.example but with your settings.
Note: Under LDAP settings fill in the
`group_base`
setting.
*
Make
`/home/git/gitlab/config/unicorn.rb`
same as /home/git/gitlab/config/unicorn.rb.example but with your settings.
### 4. Install libs, migrations, etc.
```
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
sudo
-u
git
-H
bundle
exec
rake assets:clean assets:precompile cache:clear
RAILS_ENV
=
production
```
### 5. Update Init script
```
bash
sudo cp
lib/support/init.d/gitlab /etc/init.d/gitlab
sudo chmod
+x /etc/init.d/gitlab
```
### 6. Start application
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!
## Things went wrong? Revert to previous version (Community Edition 7.0)
### 1. Revert the code to the previous version
```
bash
cd
/home/git/gitlab
sudo
-u
git
-H
git checkout 7-0-stable
```
### 2. Restore from the backup:
```
bash
cd
/home/git/gitlab
sudo
-u
git
-H
bundle
exec
rake gitlab:backup:restore
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