gitlab-org--gitlab-foss/doc/update
Rémy Coutable 19a3d42cb3 Re-add section about NGINX config and init script updates in 8.4->8.5 update doc
These sections were removed but:
- even if the NGINX config wasn't
modified, it might be in future updates so it's better to always have it
instead of having to remember to add it depending on the changes
- the init script update section must be there since it's a safe command
  line that should be run on every update

[ci skip]
2016-02-15 12:06:46 +01: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 create update guides for 7.13 2015-07-14 11:49:53 +02:00
7.13-to-7.14.md Bump gitlab-shell to v2.6.5 2015-09-08 13:34:07 -04:00
7.14-to-8.0.md Track compatible gitlab-git-http-server version 2015-10-15 13:22:28 +02:00
8.0-to-8.1.md Merge branch 'rs-8-1-update-guide-changes' into 'master' 2015-10-20 18:11:38 +02:00
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 Use gitlab-workhorse 0.5.4 2016-01-12 15:18:17 +01:00
8.3-to-8.4.md Update gitlab-workhorse versions in documentation 2016-01-27 18:30:36 -05:00
8.4-to-8.5.md Re-add section about NGINX config and init script updates in 8.4->8.5 update doc 2016-02-15 12:06:46 +01:00
README.md Update MySQL docs 2016-01-18 16:54:29 -05:00
mysql_to_postgresql.md Changed documentation of converting a MySQL-Database with Gitlab to a Postgresdatatabase. The instructions were missleading. See -> https://gitlab.com/gitlab-org/gitlab-ce/issues/2904 2015-11-04 08:30:30 +01:00
patch_versions.md added make command to docs 2016-01-04 00:29:30 +01:00
upgrader.md Add better deprecation notice for the upgrader. Too easy to miss otherwise https://twitter.com/0x663030623472/status/646262552796594176 2015-09-22 19:56:51 +00:00

README.md

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

Omnibus Packages

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