Skip to content

G
gitlab-ce
Commit 0555d751 authored by Marin Jankovski's avatar Marin Jankovski
Browse files
Options

Merge branch 'docs/refactor-update-guides-ee' into 'master' 

EE: Refactor the upgrading from source docs

Closes gitlab-org/release/framework#190

See merge request gitlab-org/gitlab-ee!9519
parents 28ec88f6 ec8963a0
Expand all Hide whitespace changes
Inline Side-by-side
Showing with 978 additions and 23330 deletions
doc/administration/integration/terminal.md
View file @ 0555d751
......@@ -64,8 +64,9 @@ narrower set of rules, you can restrict it to URLs ending with `/terminal.ws`
(although this may still have a few false positives).
If you installed from source, or have made any configuration changes to your
Omnibus installation before upgrading to 8.15, you may need to make some
changes to your configuration. See the [8.14 to 8.15 upgrade](../../update/8.14-to-8.15.md#nginx-configuration)
Omnibus installation before upgrading to 8.15, you may need to make some changes
to your configuration. See the [Upgrading Community Edition and Enterprise
Edition from source](../../update/upgrading_from_source.md#nginx-configuration)
document for more details.
If you'd like to disable web terminal support in GitLab, just stop passing
......
doc/development/contributing/merge_request_workflow.md
View file @ 0555d751
......@@ -89,6 +89,11 @@ request is as follows:
1. If your merge request introduces changes that require additional steps when
installing GitLab from source, add them to `doc/install/installation.md` in
the same merge request.
1. If your merge request introduces changes that require additional steps when
upgrading GitLab from source, add them to
`doc/update/upgrading_from_source.md` in the same merge request. If these
instructions are specific to a version, add them to the "Version specific
upgrading instructions" section.
Please keep the change in a single MR **as small as possible**. If you want to
contribute a large feature think very hard what the minimum viable change is.
......
doc/update/10.0-ce-to-ee.md
View file @ 0555d751
# From Community Edition 10.0 to Enterprise Edition 10.0
---
redirect_to: upgrading_from_ce_to_ee.md
---
This guide assumes you have a correctly configured and tested installation of
GitLab Community Edition 10.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 something goes wrong:
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
For installations using MySQL, this may require granting "LOCK TABLES"
privileges to the GitLab user on the database version.
### 1. Stop server
```bash
sudo service gitlab stop
```
### 2. Get the EE code
```bash
cd /home/git/gitlab
sudo -u git -H git remote add -f ee https://gitlab.com/gitlab-org/gitlab-ee.git
sudo -u git -H git checkout 10-0-stable-ee
```
### 3. Install libs, migrations, etc.
```bash
cd /home/git/gitlab
# MySQL installations (note: the line below states '--without postgres')
sudo -u git -H bundle install --without postgres development test --deployment
# PostgreSQL installations (note: the line below states '--without mysql')
sudo -u git -H bundle install --without mysql development test --deployment
# Run database migrations
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
# Clean up assets and cache
sudo -u git -H bundle exec rake assets:clean assets:precompile cache:clear RAILS_ENV=production
```
### 4. Start application
```bash
sudo service gitlab start
sudo service nginx restart
```
### 5. Check application status
Check if GitLab and its environment are configured correctly:
```bash
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:
```bash
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 (Community Edition 10.0)
### 1. Revert the code to the previous version
```bash
cd /home/git/gitlab
sudo -u git -H git checkout 10-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
```
[support@gitlab.com]: mailto:support@gitlab.com
This document was moved to [another location](upgrading_from_ce_to_ee.md).
doc/update/10.0-to-10.1.md
View file @ 0555d751
This diff is collapsed.
doc/update/10.1-ce-to-ee.md
View file @ 0555d751
# From Community Edition 10.1 to Enterprise Edition 10.1
---
redirect_to: upgrading_from_ce_to_ee.md
---
This guide assumes you have a correctly configured and tested installation of
GitLab Community Edition 10.1. 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 something goes wrong:
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
For installations using MySQL, this may require granting "LOCK TABLES"
privileges to the GitLab user on the database version.
### 1. Stop server
```bash
sudo service gitlab stop
```
### 2. Get the EE code
```bash
cd /home/git/gitlab
sudo -u git -H git remote add -f ee https://gitlab.com/gitlab-org/gitlab-ee.git
sudo -u git -H git checkout 10-1-stable-ee
```
### 3. Install libs, migrations, etc.
```bash
cd /home/git/gitlab
# MySQL installations (note: the line below states '--without postgres')
sudo -u git -H bundle install --without postgres development test --deployment
# PostgreSQL installations (note: the line below states '--without mysql')
sudo -u git -H bundle install --without mysql development test --deployment
# Run database migrations
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
# Clean up assets and cache
sudo -u git -H bundle exec rake assets:clean assets:precompile cache:clear RAILS_ENV=production
```
### 4. Start application
```bash
sudo service gitlab start
sudo service nginx restart
```
### 5. Check application status
Check if GitLab and its environment are configured correctly:
```bash
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:
```bash
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 (Community Edition 10.1)
### 1. Revert the code to the previous version
```bash
cd /home/git/gitlab
sudo -u git -H git checkout 10-1-stable
```
### 2. Restore from the backup
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
```
[support@gitlab.com]: mailto:support@gitlab.com
This document was moved to [another location](upgrading_from_ce_to_ee.md).
doc/update/10.1-to-10.2.md
View file @ 0555d751
This diff is collapsed.
doc/update/10.2-ce-to-ee.md
View file @ 0555d751
# From Community Edition 10.2 to Enterprise Edition 10.2
---
redirect_to: upgrading_from_ce_to_ee.md
---
This guide assumes you have a correctly configured and tested installation of
GitLab Community Edition 10.2. 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 something goes wrong:
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
For installations using MySQL, this may require granting "LOCK TABLES"
privileges to the GitLab user on the database version.
### 1. Stop server
```bash
sudo service gitlab stop
```
### 2. Get the EE code
```bash
cd /home/git/gitlab
sudo -u git -H git remote add -f ee https://gitlab.com/gitlab-org/gitlab-ee.git
sudo -u git -H git checkout 10-2-stable-ee
```
### 3. Install libs, migrations, etc.
```bash
cd /home/git/gitlab
# MySQL installations (note: the line below states '--without postgres')
sudo -u git -H bundle install --without postgres development test --deployment
# PostgreSQL installations (note: the line below states '--without mysql')
sudo -u git -H bundle install --without mysql development test --deployment
# Run database migrations
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
# Clean up assets and cache
sudo -u git -H bundle exec rake assets:clean assets:precompile cache:clear RAILS_ENV=production
```
### 4. Start application
```bash
sudo service gitlab start
sudo service nginx restart
```
### 5. Check application status
Check if GitLab and its environment are configured correctly:
```bash
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:
```bash
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 (Community Edition 10.2)
### 1. Revert the code to the previous version
```bash
cd /home/git/gitlab
sudo -u git -H git checkout 10-2-stable
```
### 2. Restore from the backup
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
```
[support@gitlab.com]: mailto:support@gitlab.com
This document was moved to [another location](upgrading_from_ce_to_ee.md).
doc/update/10.2-to-10.3.md
View file @ 0555d751
This diff is collapsed.
doc/update/10.3-ce-to-ee.md
View file @ 0555d751
# From Community Edition 10.3 to Enterprise Edition 10.3
---
redirect_to: upgrading_from_ce_to_ee.md
---
This guide assumes you have a correctly configured and tested installation of
GitLab Community Edition 10.3. 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 something goes wrong:
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
For installations using MySQL, this may require granting "LOCK TABLES"
privileges to the GitLab user on the database version.
### 1. Stop server
```bash
sudo service gitlab stop
```
### 2. Get the EE code
```bash
cd /home/git/gitlab
sudo -u git -H git remote add -f ee https://gitlab.com/gitlab-org/gitlab-ee.git
sudo -u git -H git checkout 10-3-stable-ee
```
### 3. Install libs, migrations, etc.
```bash
cd /home/git/gitlab
# MySQL installations (note: the line below states '--without postgres')
sudo -u git -H bundle install --without postgres development test --deployment
# PostgreSQL installations (note: the line below states '--without mysql')
sudo -u git -H bundle install --without mysql development test --deployment
# Run database migrations
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
# Clean up assets and cache
sudo -u git -H bundle exec rake assets:clean assets:precompile cache:clear RAILS_ENV=production
```
### 4. Start application
```bash
sudo service gitlab start
sudo service nginx restart
```
### 5. Check application status
Check if GitLab and its environment are configured correctly:
```bash
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:
```bash
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 (Community Edition 10.3)
### 1. Revert the code to the previous version
```bash
cd /home/git/gitlab
sudo -u git -H git checkout 10-3-stable
```
### 2. Restore from the backup
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
```
[support@gitlab.com]: mailto:support@gitlab.com
This document was moved to [another location](upgrading_from_ce_to_ee.md).
doc/update/10.3-to-10.4.md
View file @ 0555d751
This diff is collapsed.
doc/update/10.4-ce-to-ee.md
View file @ 0555d751
# From Community Edition 10.4 to Enterprise Edition 10.4
---
redirect_to: upgrading_from_ce_to_ee.md
---
This guide assumes you have a correctly configured and tested installation of
GitLab Community Edition 10.4. 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 something goes wrong:
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
For installations using MySQL, this may require granting "LOCK TABLES"
privileges to the GitLab user on the database version.
### 1. Stop server
```bash
sudo service gitlab stop
```
### 2. Get the EE code
```bash
cd /home/git/gitlab
sudo -u git -H git remote add -f ee https://gitlab.com/gitlab-org/gitlab-ee.git
sudo -u git -H git checkout 10-4-stable-ee
```
### 3. Install libs, migrations, etc.
```bash
cd /home/git/gitlab
# MySQL installations (note: the line below states '--without postgres')
sudo -u git -H bundle install --without postgres development test --deployment
# PostgreSQL installations (note: the line below states '--without mysql')
sudo -u git -H bundle install --without mysql development test --deployment
# Run database migrations
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
# Clean up assets and cache
sudo -u git -H bundle exec rake assets:clean assets:precompile cache:clear RAILS_ENV=production
```
### 4. Start application
```bash
sudo service gitlab start
sudo service nginx restart
```
### 5. Check application status
Check if GitLab and its environment are configured correctly:
```bash
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:
```bash
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 (Community Edition 10.4)
### 1. Revert the code to the previous version
```bash
cd /home/git/gitlab
sudo -u git -H git checkout 10-4-stable
```
### 2. Restore from the backup
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
```
[support@gitlab.com]: mailto:support@gitlab.com
This document was moved to [another location](upgrading_from_ce_to_ee.md).
doc/update/10.4-to-10.5.md
View file @ 0555d751
This diff is collapsed.
doc/update/10.5-ce-to-ee.md
View file @ 0555d751
# From Community Edition 10.5 to Enterprise Edition 10.5
---
redirect_to: upgrading_from_ce_to_ee.md
---
This guide assumes you have a correctly configured and tested installation of
GitLab Community Edition 10.5. 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 something goes wrong:
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
For installations using MySQL, this may require granting "LOCK TABLES"
privileges to the GitLab user on the database version.
### 1. Stop server
```bash
sudo service gitlab stop
```
### 2. Get the EE code
```bash
cd /home/git/gitlab
sudo -u git -H git remote add -f ee https://gitlab.com/gitlab-org/gitlab-ee.git
sudo -u git -H git checkout 10-5-stable-ee
```
### 3. Install libs, migrations, etc.
```bash
cd /home/git/gitlab
# MySQL installations (note: the line below states '--without postgres')
sudo -u git -H bundle install --without postgres development test --deployment
# PostgreSQL installations (note: the line below states '--without mysql')
sudo -u git -H bundle install --without mysql development test --deployment
# Run database migrations
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
# Clean up assets and cache
sudo -u git -H bundle exec rake assets:clean assets:precompile cache:clear RAILS_ENV=production
```
### 4. Start application
```bash
sudo service gitlab start
sudo service nginx restart
```
### 5. Check application status
Check if GitLab and its environment are configured correctly:
```bash
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:
```bash
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 (Community Edition 10.5)
### 1. Revert the code to the previous version
```bash
cd /home/git/gitlab
sudo -u git -H git checkout 10-5-stable
```
### 2. Restore from the backup
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
```
[support@gitlab.com]: mailto:support@gitlab.com
This document was moved to [another location](upgrading_from_ce_to_ee.md).
doc/update/10.5-to-10.6.md
View file @ 0555d751
This diff is collapsed.
doc/update/10.6-ce-to-ee.md
View file @ 0555d751
# From Community Edition 10.6 to Enterprise Edition 10.6
---
redirect_to: upgrading_from_ce_to_ee.md
---
This guide assumes you have a correctly configured and tested installation of
GitLab Community Edition 10.6. 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 something goes wrong:
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
For installations using MySQL, this may require granting "LOCK TABLES"
privileges to the GitLab user on the database version.
### 1. Stop server
```bash
sudo service gitlab stop
```
### 2. Get the EE code
```bash
cd /home/git/gitlab
sudo -u git -H git remote add -f ee https://gitlab.com/gitlab-org/gitlab-ee.git
sudo -u git -H git checkout 10-6-stable-ee
```
### 3. Install libs, migrations, etc.
```bash
cd /home/git/gitlab
# MySQL installations (note: the line below states '--without postgres')
sudo -u git -H bundle install --without postgres development test --deployment
# PostgreSQL installations (note: the line below states '--without mysql')
sudo -u git -H bundle install --without mysql development test --deployment
# Run database migrations
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
# Clean up assets and cache
sudo -u git -H bundle exec rake assets:clean assets:precompile cache:clear RAILS_ENV=production
```
### 4. Start application
```bash
sudo service gitlab start
sudo service nginx restart
```
### 5. Check application status
Check if GitLab and its environment are configured correctly:
```bash
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:
```bash
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 (Community Edition 10.6)
### 1. Revert the code to the previous version
```bash
cd /home/git/gitlab
sudo -u git -H git checkout 10-6-stable
```
### 2. Restore from the backup
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
```
[support@gitlab.com]: mailto:support@gitlab.com
This document was moved to [another location](upgrading_from_ce_to_ee.md).
doc/update/10.6-to-10.7.md
View file @ 0555d751
This diff is collapsed.
doc/update/10.7-ce-to-ee.md
View file @ 0555d751
# From Community Edition 10.7 to Enterprise Edition 10.7
---
redirect_to: upgrading_from_ce_to_ee.md
---
This guide assumes you have a correctly configured and tested installation of
GitLab Community Edition 10.7. 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 something goes wrong:
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
For installations using MySQL, this may require granting "LOCK TABLES"
privileges to the GitLab user on the database version.
### 1. Stop server
```bash
sudo service gitlab stop
```
### 2. Get the EE code
```bash
cd /home/git/gitlab
sudo -u git -H git remote add -f ee https://gitlab.com/gitlab-org/gitlab-ee.git
sudo -u git -H git checkout 10-7-stable-ee
```
### 3. Install libs, migrations, etc.
```bash
cd /home/git/gitlab
# MySQL installations (note: the line below states '--without postgres')
sudo -u git -H bundle install --without postgres development test --deployment
# PostgreSQL installations (note: the line below states '--without mysql')
sudo -u git -H bundle install --without mysql development test --deployment
# Run database migrations
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
# Clean up assets and cache
sudo -u git -H bundle exec rake assets:clean assets:precompile cache:clear RAILS_ENV=production
```
### 4. Start application
```bash
sudo service gitlab start
sudo service nginx restart
```
### 5. Check application status
Check if GitLab and its environment are configured correctly:
```bash
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:
```bash
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 (Community Edition 10.7)
### 1. Revert the code to the previous version
```bash
cd /home/git/gitlab
sudo -u git -H git checkout 10-7-stable
```
### 2. Restore from the backup
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
```
[support@gitlab.com]: mailto:support@gitlab.com
This document was moved to [another location](upgrading_from_ce_to_ee.md).
doc/update/10.7-to-10.8.md
View file @ 0555d751
This diff is collapsed.
doc/update/10.8-ce-to-ee.md
View file @ 0555d751
# From Community Edition 10.8 to Enterprise Edition 10.8
---
redirect_to: upgrading_from_ce_to_ee.md
---
This guide assumes you have a correctly configured and tested installation of
GitLab Community Edition 10.8. 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 something goes wrong:
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
For installations using MySQL, this may require granting "LOCK TABLES"
privileges to the GitLab user on the database version.
### 1. Stop server
```bash
sudo service gitlab stop
```
### 2. Get the EE code
```bash
cd /home/git/gitlab
sudo -u git -H git remote add -f ee https://gitlab.com/gitlab-org/gitlab-ee.git
sudo -u git -H git checkout 10-8-stable-ee
```
### 3. Install libs, migrations, etc.
```bash
cd /home/git/gitlab
# MySQL installations (note: the line below states '--without postgres')
sudo -u git -H bundle install --without postgres development test --deployment
# PostgreSQL installations (note: the line below states '--without mysql')
sudo -u git -H bundle install --without mysql development test --deployment
# Run database migrations
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
# Clean up assets and cache
sudo -u git -H bundle exec rake assets:clean assets:precompile cache:clear RAILS_ENV=production
```
### 4. Start application
```bash
sudo service gitlab start
sudo service nginx restart
```
### 5. Check application status
Check if GitLab and its environment are configured correctly:
```bash
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:
```bash
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 (Community Edition 10.8)
### 1. Revert the code to the previous version
```bash
cd /home/git/gitlab
sudo -u git -H git checkout 10-8-stable
```
### 2. Restore from the backup
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
```
[support@gitlab.com]: mailto:support@gitlab.com
This document was moved to [another location](upgrading_from_ce_to_ee.md).
doc/update/10.8-to-11.0.md
View file @ 0555d751
This diff is collapsed.
doc/update/11.0-ce-to-ee.md
View file @ 0555d751
# From Community Edition 11.0 to Enterprise Edition 11.0
---
redirect_to: upgrading_from_ce_to_ee.md
---
This guide assumes you have a correctly configured and tested installation of
GitLab Community Edition 11.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 something goes wrong:
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
For installations using MySQL, this may require granting "LOCK TABLES"
privileges to the GitLab user on the database version.
### 1. Stop server
```bash
sudo service gitlab stop
```
### 2. Get the EE code
```bash
cd /home/git/gitlab
sudo -u git -H git remote add -f ee https://gitlab.com/gitlab-org/gitlab-ee.git
sudo -u git -H git checkout 11-0-stable-ee
```
### 3. Install libs, migrations, etc.
```bash
cd /home/git/gitlab
# MySQL installations (note: the line below states '--without postgres')
sudo -u git -H bundle install --without postgres development test --deployment
# PostgreSQL installations (note: the line below states '--without mysql')
sudo -u git -H bundle install --without mysql development test --deployment
# Run database migrations
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
# Clean up assets and cache
sudo -u git -H bundle exec rake assets:clean assets:precompile cache:clear RAILS_ENV=production
```
### 4. Start application
```bash
sudo service gitlab start
sudo service nginx restart
```
### 5. Check application status
Check if GitLab and its environment are configured correctly:
```bash
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:
```bash
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 (Community Edition 11.0)
### 1. Revert the code to the previous version
```bash
cd /home/git/gitlab
sudo -u git -H git checkout 11-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
```
[support@gitlab.com]: mailto:support@gitlab.com
This document was moved to [another location](upgrading_from_ce_to_ee.md).
doc/update/11.0-to-11.1.md
View file @ 0555d751
This diff is collapsed.
doc/update/11.1-ce-to-ee.md
View file @ 0555d751
# From Community Edition 11.1 to Enterprise Edition 11.1
---
redirect_to: upgrading_from_ce_to_ee.md
---
This guide assumes you have a correctly configured and tested installation of
GitLab Community Edition 11.1. 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 something goes wrong:
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
For installations using MySQL, this may require granting "LOCK TABLES"
privileges to the GitLab user on the database version.
### 1. Stop server
```bash
sudo service gitlab stop
```
### 2. Get the EE code
```bash
cd /home/git/gitlab
sudo -u git -H git remote add -f ee https://gitlab.com/gitlab-org/gitlab-ee.git
sudo -u git -H git checkout 11-1-stable-ee
```
### 3. Install libs, migrations, etc.
```bash
cd /home/git/gitlab
# MySQL installations (note: the line below states '--without postgres')
sudo -u git -H bundle install --without postgres development test --deployment
# PostgreSQL installations (note: the line below states '--without mysql')
sudo -u git -H bundle install --without mysql development test --deployment
# Run database migrations
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
# Clean up assets and cache
sudo -u git -H bundle exec rake assets:clean assets:precompile cache:clear RAILS_ENV=production
```
### 4. Start application
```bash
sudo service gitlab start
sudo service nginx restart
```
### 5. Check application status
Check if GitLab and its environment are configured correctly:
```bash
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:
```bash
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 (Community Edition 11.1)
### 1. Revert the code to the previous version
```bash
cd /home/git/gitlab
sudo -u git -H git checkout 11-1-stable
```
### 2. Restore from the backup
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
```
[support@gitlab.com]: mailto:support@gitlab.com
This document was moved to [another location](upgrading_from_ce_to_ee.md).
doc/update/11.1-to-11.2.md
View file @ 0555d751
This diff is collapsed.
doc/update/11.2-ce-to-ee.md
View file @ 0555d751
# From Community Edition 11.2 to Enterprise Edition 11.2
---
redirect_to: upgrading_from_ce_to_ee.md
---
This guide assumes you have a correctly configured and tested installation of
GitLab Community Edition 11.2. 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 something goes wrong:
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
For installations using MySQL, this may require granting "LOCK TABLES"
privileges to the GitLab user on the database version.
### 1. Stop server
```bash
sudo service gitlab stop
```
### 2. Get the EE code
```bash
cd /home/git/gitlab
sudo -u git -H git remote add -f ee https://gitlab.com/gitlab-org/gitlab-ee.git
sudo -u git -H git checkout 11-2-stable-ee
```
### 3. Install libs, migrations, etc.
```bash
cd /home/git/gitlab
# MySQL installations (note: the line below states '--without postgres')
sudo -u git -H bundle install --without postgres development test --deployment
# PostgreSQL installations (note: the line below states '--without mysql')
sudo -u git -H bundle install --without mysql development test --deployment
# Run database migrations
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
# Clean up assets and cache
sudo -u git -H bundle exec rake assets:clean assets:precompile cache:clear RAILS_ENV=production
```
### 4. Start application
```bash
sudo service gitlab start
sudo service nginx restart
```
### 5. Check application status
Check if GitLab and its environment are configured correctly:
```bash
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:
```bash
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 (Community Edition 11.1)
### 1. Revert the code to the previous version
```bash
cd /home/git/gitlab
sudo -u git -H git checkout 11-2-stable
```
### 2. Restore from the backup
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
```
[support@gitlab.com]: mailto:support@gitlab.com
This document was moved to [another location](upgrading_from_ce_to_ee.md).
doc/update/11.2-to-11.3.md
View file @ 0555d751
This diff is collapsed.
doc/update/11.3-ce-to-ee.md
View file @ 0555d751
# From Community Edition 11.3 to Enterprise Edition 11.3
---
redirect_to: upgrading_from_ce_to_ee.md
---
This guide assumes you have a correctly configured and tested installation of
GitLab Community Edition 11.3. 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 something goes wrong:
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
For installations using MySQL, this may require granting "LOCK TABLES"
privileges to the GitLab user on the database version.
### 1. Stop server
```bash
sudo service gitlab stop
```
### 2. Get the EE code
```bash
cd /home/git/gitlab
sudo -u git -H git remote add -f ee https://gitlab.com/gitlab-org/gitlab-ee.git
sudo -u git -H git checkout 11-3-stable-ee
```
### 3. Install libs, migrations, etc.
```bash
cd /home/git/gitlab
# MySQL installations (note: the line below states '--without postgres')
sudo -u git -H bundle install --without postgres development test --deployment
# PostgreSQL installations (note: the line below states '--without mysql')
sudo -u git -H bundle install --without mysql development test --deployment
# Run database migrations
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
# Compile GetText PO files
bundle exec rake gettext:compile RAILS_ENV=production
# Update node dependencies and recompile assets
sudo -u git -H bundle exec rake yarn:install gitlab:assets:clean gitlab:assets:compile RAILS_ENV=production NODE_ENV=production
```
### 4. Install `gitlab-elasticsearch-indexer` (optional) **[STARTER ONLY]**
If you're interested in using GitLab's new [elasticsearch repository indexer](../integration/elasticsearch.md#elasticsearch-repository-indexer-beta) (currently in beta)
please follow the instructions on the document linked above and enable the
indexer usage in the GitLab admin settings.
### 5. Start application
```bash
sudo service gitlab start
sudo service nginx restart
```
### 6. Check application status
Check if GitLab and its environment are configured correctly:
```bash
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:
```bash
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 (Community Edition 11.2)
### 1. Revert the code to the previous version
```bash
cd /home/git/gitlab
sudo -u git -H git checkout 11-3-stable
```
### 2. Restore from the backup
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
```
[support@gitlab.com]: mailto:support@gitlab.com
This document was moved to [another location](upgrading_from_ce_to_ee.md).
doc/update/11.3-to-11.4.md
View file @ 0555d751
This diff is collapsed.
doc/update/11.4-ce-to-ee.md
View file @ 0555d751
# From Community Edition 11.4 to Enterprise Edition 11.4
---
redirect_to: upgrading_from_ce_to_ee.md
---
This guide assumes you have a correctly configured and tested installation of
GitLab Community Edition 11.4. 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 something goes wrong:
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
For installations using MySQL, this may require granting "LOCK TABLES"
privileges to the GitLab user on the database version.
### 1. Stop server
```bash
sudo service gitlab stop
```
### 2. Get the EE code
```bash
cd /home/git/gitlab
sudo -u git -H git remote add -f ee https://gitlab.com/gitlab-org/gitlab-ee.git
sudo -u git -H git checkout 11-4-stable-ee
```
### 3. Install libs, migrations, etc.
```bash
cd /home/git/gitlab
# MySQL installations (note: the line below states '--without postgres')
sudo -u git -H bundle install --without postgres development test --deployment
# PostgreSQL installations (note: the line below states '--without mysql')
sudo -u git -H bundle install --without mysql development test --deployment
# Run database migrations
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
# Clean up assets and cache
sudo -u git -H bundle exec rake assets:clean assets:precompile cache:clear RAILS_ENV=production
```
### 4. Install `gitlab-elasticsearch-indexer` (optional) **[STARTER ONLY]**
If you're interested in using GitLab's new [elasticsearch repository indexer](../integration/elasticsearch.md#elasticsearch-repository-indexer-beta) (currently in beta)
please follow the instructions on the document linked above and enable the
indexer usage in the GitLab admin settings.
### 5. Start application
```bash
sudo service gitlab start
sudo service nginx restart
```
### 6. Check application status
Check if GitLab and its environment are configured correctly:
```bash
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:
```bash
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 (Community Edition 11.3)
### 1. Revert the code to the previous version
```bash
cd /home/git/gitlab
sudo -u git -H git checkout 11-4-stable
```
### 2. Restore from the backup
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
```
[support@gitlab.com]: mailto:support@gitlab.com
This document was moved to [another location](upgrading_from_ce_to_ee.md).
doc/update/11.4-to-11.5.md
View file @ 0555d751
This diff is collapsed.
doc/update/11.5-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/11.5-to-11.6.md
View file @ 0555d751
This diff is collapsed.
doc/update/11.6-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/11.6-to-11.7.md
View file @ 0555d751
This diff is collapsed.
doc/update/11.7-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/11.7-to-11.8.md
View file @ 0555d751
This diff is collapsed.
doc/update/11.8-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/2.6-to-3.0.md
View file @ 0555d751
This diff is collapsed.
doc/update/2.9-to-3.0.md
View file @ 0555d751
This diff is collapsed.
doc/update/3.0-to-3.1.md
View file @ 0555d751
This diff is collapsed.
doc/update/3.1-to-4.0.md
View file @ 0555d751
This diff is collapsed.
doc/update/4.0-to-4.1.md
View file @ 0555d751
This diff is collapsed.
doc/update/4.1-to-4.2.md
View file @ 0555d751
This diff is collapsed.
doc/update/4.2-to-5.0.md
View file @ 0555d751
This diff is collapsed.
doc/update/5.0-to-5.1.md
View file @ 0555d751
This diff is collapsed.
doc/update/5.1-to-5.2.md
View file @ 0555d751
This diff is collapsed.
doc/update/5.1-to-5.4.md
View file @ 0555d751
This diff is collapsed.
doc/update/5.1-to-6.0.md
View file @ 0555d751
This diff is collapsed.
doc/update/5.2-to-5.3.md
View file @ 0555d751
This diff is collapsed.
doc/update/5.3-to-5.4.md
View file @ 0555d751
This diff is collapsed.
doc/update/5.4-to-6.0.md
View file @ 0555d751
This diff is collapsed.
doc/update/6.0-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/6.0-to-6.1.md
View file @ 0555d751
This diff is collapsed.
doc/update/6.0-to-6.2.md
View file @ 0555d751
This diff is collapsed.
doc/update/6.1-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/6.1-to-6.2.md
View file @ 0555d751
This diff is collapsed.
doc/update/6.2-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/6.2-to-6.3.md
View file @ 0555d751
This diff is collapsed.
doc/update/6.3-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/6.3-to-6.4.md
View file @ 0555d751
This diff is collapsed.
doc/update/6.4-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/6.4-to-6.5.md
View file @ 0555d751
This diff is collapsed.
doc/update/6.5-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/6.5-to-6.6.md
View file @ 0555d751
This diff is collapsed.
doc/update/6.6-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/6.6-to-6.7.md
View file @ 0555d751
This diff is collapsed.
doc/update/6.7-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/6.7-to-6.8.md
View file @ 0555d751
This diff is collapsed.
doc/update/6.8-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/6.8-to-6.9.md
View file @ 0555d751
This diff is collapsed.
doc/update/6.9-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/6.9-to-7.0.md
View file @ 0555d751
This diff is collapsed.
doc/update/6.x-or-7.x-to-7.14.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.0-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.0-to-7.1.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.1-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.1-to-7.2.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.10-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.10-to-7.11.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.11-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.11-to-7.12.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.12-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.12-to-7.13.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.13-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.13-to-7.14.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.14-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.14-to-8.0.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.2-to-7.3.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.3-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.3-to-7.4.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.4-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.4-to-7.5.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.5-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.5-to-7.6.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.6-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.6-to-7.7.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.7-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.7-to-7.8.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.8-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.8-to-7.9.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.9-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/7.9-to-7.10.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.0-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.0-to-8.1.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.1-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.1-to-8.2.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.10-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.10-to-8.11.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.11-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.11-to-8.12.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.12-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.12-to-8.13.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.13-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.13-to-8.14.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.14-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.14-to-8.15.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.15-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.15-to-8.16.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.16-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.16-to-8.17.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.17-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.17-to-9.0.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.2-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.2-to-8.3.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.3-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.3-to-8.4.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.4-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.4-to-8.5.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.5-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.5-to-8.6.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.6-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.6-to-8.7.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.7-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.7-to-8.8.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.8-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.8-to-8.9.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.9-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/8.9-to-8.10.md
View file @ 0555d751
This diff is collapsed.
doc/update/9.0-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/9.0-to-9.1.md
View file @ 0555d751
This diff is collapsed.
doc/update/9.1-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/9.1-to-9.2.md
View file @ 0555d751
This diff is collapsed.
doc/update/9.2-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/9.2-to-9.3.md
View file @ 0555d751
This diff is collapsed.
doc/update/9.3-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/9.3-to-9.4.md
View file @ 0555d751
This diff is collapsed.
doc/update/9.4-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/9.4-to-9.5.md
View file @ 0555d751
This diff is collapsed.
doc/update/9.5-ce-to-ee.md
View file @ 0555d751
This diff is collapsed.
doc/update/9.5-to-10.0.md
View file @ 0555d751
This diff is collapsed.
doc/update/README.md
View file @ 0555d751
This diff is collapsed.
doc/update/upgrading_from_ce_to_ee.md 0 → 100644
View file @ 0555d751
This diff is collapsed.
doc/update/upgrading_from_source.md 0 → 100644
View file @ 0555d751
This diff is collapsed.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7