diff options
| -rw-r--r-- | doc/update/4.2-to-5.0.md | 1 | ||||
| -rw-r--r-- | doc/update/5.1-to-6.0.md | 6 |
2 files changed, 7 insertions, 0 deletions
diff --git a/doc/update/4.2-to-5.0.md b/doc/update/4.2-to-5.0.md index d4f49f06840..30b25a2d2d5 100644 --- a/doc/update/4.2-to-5.0.md +++ b/doc/update/4.2-to-5.0.md @@ -7,6 +7,7 @@ GitLab 5.0 is affected by critical security vulnerability CVE-2013-4490. ## Important changes - We don't use `gitlab` user any more. Everything will be moved to `git` user +- Self signed SSL certificates are not supported until GitLab 5.1 - **requires ruby1.9.3** ## 0. Stop gitlab diff --git a/doc/update/5.1-to-6.0.md b/doc/update/5.1-to-6.0.md index d8484b2c650..123b3326ead 100644 --- a/doc/update/5.1-to-6.0.md +++ b/doc/update/5.1-to-6.0.md @@ -149,6 +149,12 @@ sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production The migrations in this update are very sensitive to incomplete or inconsistent data. If you have a long-running GitLab installation and some of the previous upgrades did not work out 100% correct this may bite you now. The following commands can be run in the rails console to look for 'bad' data. +Start rails console: + +``` +sudo -u git -H rails console production +``` + All project owners should have an owner: ``` |