mirror of
https://github.com/wahyd4/gitlabhq.git
synced 2026-08-10 13:16:09 +10:00
Hannes Rosenögger
cde076c525
don't set LATEST_TAG automatically in patch update guide As discussed in https://gitlab.com/gitlab-org/gitlab-ce/issues/2607, this removes the automatic setting of the LATEST_TAG variable in the update guide, because it could get set to rc versions. Instead, a command was added to list all tags, with the most recent one being on the end of the list. Also a note was added to prevent users from updating to new minor/major versions because the tag list includes all tags. [ci skip] See merge request !1510
Depending on the installation method and your GitLab version, there are multiple update guides. Choose one that fits your needs.
Omnibus Packages
- Omnibus update guide contains the steps needed to update a GitLab package.
Installation from source
- The individual upgrade guides are for those who have installed GitLab from source.
- 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 installations from source.
- Patch versions guide includes the steps needed for a patch version, eg. 6.2.0 to 6.2.1.
Miscellaneous
- MySQL to PostgreSQL guides you through migrating your database from MySQL to PostgreSQL.