CentOS 6.4 install GitLab 6 0 stable ssh Auth fail

Created by: blackmanbachen

CentOS 6.4 install GitLab 6 0 stable ssh Auth fail. but i am already add ssh key in GitLab SSH public keys

doc/update/5.4-to-6.0.md

@@ -4,7 +4,7 @@
 #### Global projects
-We deprecated root(global) namespace for projects. 
+We deprecated root(global) namespace for projects.
 So you need to move all your global projects under group/users manually before update or they will be automatically moved to the owner namespace during the update.
 #### Teams
@@ -36,17 +36,25 @@ sudo -u git -H RAILS_ENV=production bundle exec rake gitlab:backup:create
 ```bash
 cd /home/git/gitlab
 sudo -u git -H git fetch
-sudo -u git -H git checkout 6-0-dev
+sudo -u git -H git checkout 6-0-stable
 ```
-### 3. Install additional packages
+### 3. Update gitlab-shell
+
+```bash
+cd /home/git/gitlab-shell
+sudo -u git -H git fetch
+sudo -u git -H git checkout v1.7.0
+```
+
+### 4. Install additional packages
 ```bash
 # For reStructuredText markup language support install required package:
 sudo apt-get install python-docutils
 ```
-### 4. Install libs, migrations, etc.
+### 5. Install libs, migrations, etc.
 ```bash
 cd /home/git/gitlab
@@ -54,7 +62,7 @@ cd /home/git/gitlab
 # MySQL
 sudo -u git -H bundle install --without development test postgres --deployment
-#PostgreSQL
+# PostgreSQL
 sudo -u git -H bundle install --without development test mysql --deployment
 sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
@@ -63,29 +71,35 @@ sudo -u git -H bundle exec rake migrate_global_projects RAILS_ENV=production
 sudo -u git -H bundle exec rake migrate_keys RAILS_ENV=production
 sudo -u git -H bundle exec rake migrate_inline_notes RAILS_ENV=production
+# Clear redis cache
+sudo -u git -H bundle exec rake cache:clear RAILS_ENV=production
+
+# Clear and precompile assets
+sudo -u git -H bundle exec rake assets:clean RAILS_ENV=production
+sudo -u git -H bundle exec rake assets:precompile RAILS_ENV=production
 ```
-### 5. Update config files
+### 6. Update config files
 Note: We switched from Puma in GitLab 5.4 to unicorn in GitLab 6.0.
 * Make `/home/git/gitlab/config/gitlab.yml` the same as https://github.com/gitlabhq/gitlabhq/blob/master/config/gitlab.yml.example but with your settings.
 * Make `/home/git/gitlab/config/unicorn.rb` the same as https://github.com/gitlabhq/gitlabhq/blob/master/config/unicorn.rb.example but with your settings.
-### 6. Update Init script
+### 7. Update Init script
 ```bash
 sudo rm /etc/init.d/gitlab
-sudo curl --output /etc/init.d/gitlab https://raw.github.com/gitlabhq/gitlabhq/master/lib/support/init.d/gitlab
+sudo curl --output /etc/init.d/gitlab https://raw.github.com/gitlabhq/gitlabhq/6-0-stable/lib/support/init.d/gitlab
 sudo chmod +x /etc/init.d/gitlab
 ```
-### 7. Start application
+### 8. Start application
     sudo service gitlab start
     sudo service nginx restart
-### 8. Check application status
+### 9. Check application status
 Check if GitLab and its environment are configured correctly: