gitlab-org--gitlab-foss

History

lurdan d2f490c8f3 fix required gitlab-shell version. Under the procedure, I've warned about gitlab-shell version, which should be 2.6.12 (may be some minor revisions introduces that).		2016-04-15 12:41:26 +09: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	Move mention of git 2.1.2 to intro paragraph	2015-06-12 15:32:43 +02:00
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	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	Go back to gitlab-workhorse 0.7.1	2016-04-11 17:03:27 +02:00
README.md	Reload the schema before restoring a database backup	2016-03-21 21:16:34 -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	make cleanup optional	2016-03-07 15:39:12 +01: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

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.
MySQL installation guide contains additional information about configuring GitLab to work with a MySQL database.
Restoring from backup after a failed upgrade