| .. | ||
| 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 | ||
| 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 | ||
| 8.2-to-8.3.md | ||
| 8.3-to-8.4.md | ||
| 8.4-to-8.5.md | ||
| 8.5-to-8.6.md | ||
| 8.6-to-8.7.md | ||
| 8.7-to-8.8.md | ||
| 8.8-to-8.9.md | ||
| 8.9-to-8.10.md | ||
| 8.10-to-8.11.md | ||
| 8.11-to-8.12.md | ||
| 8.12-to-8.13.md | ||
| 8.13-to-8.14.md | ||
| 8.14-to-8.15.md | ||
| 8.15-to-8.16.md | ||
| 8.16-to-8.17.md | ||
| mysql_to_postgresql.md | ||
| patch_versions.md | ||
| README.md | ||
| restore_after_failure.md | ||
| upgrader.md | ||
| upgrading_postgresql_using_slony.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
- Upgrading between editions
- Miscellaneous
Omnibus Packages
- The Omnibus update guide contains the steps needed to update an Omnibus GitLab package.
Installation from source
- Upgrading Community Edition from source - The individual upgrade guides are for those who have installed GitLab CE from source.
- Upgrading Enterprise Edition from source - The individual upgrade guides are for those who have installed GitLab EE from source.
- Patch versions guide includes the steps needed for a patch version, eg. 6.2.0 to 6.2.1, and apply to both Community and Enterprise Editions.
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.mdguide. 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
- MySQL to PostgreSQL guides you through migrating your database from MySQL to PostgreSQL.
- MySQL installation guide contains additional information about configuring GitLab to work with a MySQL database.
- Restoring from backup after a failed upgrade
- Upgrading PostgreSQL Using Slony, for upgrading a PostgreSQL database with minimal downtime.