Skip to content

Latest commit

 

History

History
 
 

update

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
2.6-to-3.0.md
2.6-to-3.0.md
 
 
2.9-to-3.0.md
2.9-to-3.0.md
 
 
3.0-to-3.1.md
3.0-to-3.1.md
 
 
3.1-to-4.0.md
3.1-to-4.0.md
 
 
4.0-to-4.1.md
4.0-to-4.1.md
 
 
4.1-to-4.2.md
4.1-to-4.2.md
 
 
4.2-to-5.0.md
4.2-to-5.0.md
 
 
5.0-to-5.1.md
5.0-to-5.1.md
 
 
5.1-to-5.2.md
5.1-to-5.2.md
 
 
5.1-to-5.4.md
5.1-to-5.4.md
 
 
5.1-to-6.0.md
5.1-to-6.0.md
 
 
5.2-to-5.3.md
5.2-to-5.3.md
 
 
5.3-to-5.4.md
5.3-to-5.4.md
 
 
5.4-to-6.0.md
5.4-to-6.0.md
 
 
6.0-to-6.1.md
6.0-to-6.1.md
 
 
6.1-to-6.2.md
6.1-to-6.2.md
 
 
6.2-to-6.3.md
6.2-to-6.3.md
 
 
6.3-to-6.4.md
6.3-to-6.4.md
 
 
6.4-to-6.5.md
6.4-to-6.5.md
 
 
6.5-to-6.6.md
6.5-to-6.6.md
 
 
6.6-to-6.7.md
6.6-to-6.7.md
 
 
6.7-to-6.8.md
6.7-to-6.8.md
 
 
6.8-to-6.9.md
6.8-to-6.9.md
 
 
6.9-to-7.0.md
6.9-to-7.0.md
 
 
6.x-or-7.x-to-7.3.md
6.x-or-7.x-to-7.3.md
 
 
7.0-to-7.1.md
7.0-to-7.1.md
 
 
7.1-to-7.2.md
7.1-to-7.2.md
 
 
7.2-to-7.3.md
7.2-to-7.3.md
 
 
README.md
README.md
 
 
mysql_to_postgresql.md
mysql_to_postgresql.md
 
 
patch_versions.md
patch_versions.md
 
 
upgrader.md
upgrader.md
 
 

README.md

Depending on the installation method and your GitLab version, there are multiple update guides. Choose one that fits your needs.

Omnibus Packages

Manual Installation

  • The individual upgrade guides are for those who have installed GitLab manually.
  • The CE to EE update guides are for subscribers of the Enterprise Edition only. The steps are very similar to a version upgrade: stop the server, get the code, update config files for the new functionality, install libs and do migrations, update the init script, start the application and check the application status.
  • Upgrader is an automatic ruby script that performs the update for manual installations.
  • Patch versions guide includes the steps needed for a patch version, eg. 6.2.0 to 6.2.1.

Miscellaneous