Files
gitlabhq/doc/update
Dmitriy Zaporozhets 3bd66989de Merge branch 'master' into ee-master
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Conflicts:
	Gemfile
	Gemfile.lock
	VERSION
	app/models/project.rb
	app/models/user.rb
	db/schema.rb
	doc/install/installation.md
	doc/update/6.x-or-7.x-to-7.5.md
	doc/update/7.4-to-7.5.md
	lib/gitlab/git_access.rb
	spec/factories.rb
	spec/lib/gitlab/git_access_spec.rb
2014-12-05 13:28:32 +02:00
..
2014-08-11 22:01:37 -07:00
2014-10-14 23:53:01 -07:00
2014-08-30 17:04:45 -07:00
2014-09-01 16:39:56 -07:00
2014-09-01 16:39:56 -07:00
2014-09-01 16:39:56 -07:00
2013-12-02 14:40:08 +01:00
2014-01-28 18:25:46 +01:00
2014-04-02 10:38:15 +02:00
2014-09-01 16:39:56 -07:00
2014-06-11 10:33:06 +02:00
2014-09-07 15:31:13 -07:00
2014-06-20 08:21:10 +02:00
2014-09-01 16:39:56 -07:00
2014-10-17 14:14:35 +03:00

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

CE to EE

  • The CE to EE update guides (subscribers 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.

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