kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/doc/update
History
Yorick Peterse b5464726aa
Added 8.9 install/update guides 
[ci skip]
2016-06-07 15:20:40 +02:00
..
2.6-to-3.0.md
2.9-to-3.0.md
3.0-to-3.1.md
3.1-to-4.0.md
4.0-to-4.1.md
4.1-to-4.2.md
4.2-to-5.0.md
5.0-to-5.1.md
5.1-to-5.2.md
5.1-to-5.4.md
5.1-to-6.0.md
5.2-to-5.3.md
5.3-to-5.4.md
5.4-to-6.0.md
6.0-to-6.1.md
6.1-to-6.2.md
6.2-to-6.3.md
6.3-to-6.4.md
6.4-to-6.5.md
6.5-to-6.6.md
6.6-to-6.7.md
6.7-to-6.8.md
6.8-to-6.9.md
6.9-to-7.0.md
6.x-or-7.x-to-7.14.md Added note: working copy changes (e.g., deleted vendor folder) should be stashed before beginning the update process. We should probably include this notice on all update guides. 2016-02-01 17:11:25 +01:00
7.0-to-7.1.md
7.1-to-7.2.md
7.2-to-7.3.md
7.3-to-7.4.md
7.4-to-7.5.md
7.5-to-7.6.md
7.6-to-7.7.md
7.7-to-7.8.md
7.8-to-7.9.md
7.9-to-7.10.md
7.10-to-7.11.md
7.11-to-7.12.md
7.12-to-7.13.md
7.13-to-7.14.md
7.14-to-8.0.md
8.0-to-8.1.md
8.1-to-8.2.md Rename mention of gitlab-git-http-server to gitlab-workhorse 2015-12-14 00:18:47 -08:00
8.2-to-8.3.md Merge branch 'master' into docs_select_version_to_install 2016-03-18 14:31:33 +02:00
8.3-to-8.4.md Add note in rest of update guides 2016-03-18 14:35:04 +02:00
8.4-to-8.5.md Add note in rest of update guides 2016-03-18 14:35:04 +02:00
8.5-to-8.6.md fix required gitlab-shell version. 2016-04-15 12:41:26 +09:00
8.6-to-8.7.md Fix 18009: add missing steps in update docs 2016-05-30 17:46:54 +02:00
8.7-to-8.8.md Fix 18009: add missing steps in update docs 2016-05-30 17:46:54 +02:00
8.8-to-8.9.md Added 8.9 install/update guides 2016-06-07 15:20:40 +02:00
mysql_to_postgresql.md
patch_versions.md Revert "Merge branch 'doc-fix-db-gem-install-instructions' into 'master' " 2016-05-13 18:39:32 +02:00
README.md Change all occurrences of doc.gitlab.com to docs.gitlab.com 2016-05-13 16:26:56 -05:00
restore_after_failure.md Reload the schema before restoring a database backup 2016-03-21 21:16:34 -05:00
upgrader.md Fix URL to upgrader guide 2016-03-09 08:26:39 +01:00

README.md

Updating GitLab

Depending on the installation method and your GitLab version, there are multiple update guides.

There are currently 3 official ways to install GitLab:

  • Omnibus packages
  • Source installation
  • Docker installation

Based on your installation, choose a section below that fits your needs.

Table of Contents generated with DocToc

Omnibus Packages

Installation from source

Installation using Docker

GitLab provides official Docker images for both Community and Enterprise editions. They are based on the Omnibus package and instructions on how to update them are in a separate document.

Upgrading between editions

GitLab comes in two flavors: Community Edition which is MIT licensed, and Enterprise Edition which builds on top of the Community Edition and includes extra features mainly aimed at organizations with more than 100 users.

Below you can find some guides to help you change editions easily.

Community to Enterprise Edition

Note: The following guides are for subscribers of the Enterprise Edition only.

If you wish to upgrade your GitLab installation from Community to Enterprise Edition, follow the guides below based on the installation method:

  • Source CE to EE update guides - Find your version, and follow the -ce-to-ee.md guide. The steps are very similar to a version upgrade: stop the server, get the code, update config files for the new functionality, install libraries and do migrations, update the init script, start the application and check its status.
  • Omnibus CE to EE - Follow this guide to update your Omnibus GitLab Community Edition to the Enterprise Edition.

Enterprise to Community Edition

If you need to downgrade your Enterprise Edition installation back to Community Edition, you can follow this guide to make the process as smooth as possible.

Miscellaneous