Capistrano deployment

Created by: netdata-be

Is it usefull to have the required capistrano deployment code commited to gitlab. We are using this to update our gitlab instance and it works PERFECT.

So I would like to make a pull request for this, what do you think?

Created by: riyad

+1 maybe you can also add some docs on how to use it then.

By Administrator on 2013-01-10T14:50:46 (imported from GitLab project)

By Administrator on 2013-01-10T14:50:46 (imported from GitLab)

Created by: kirantpatil

By Administrator on 2013-01-13T13:33:22 (imported from GitLab project)

By Administrator on 2013-01-13T13:33:22 (imported from GitLab)

Created by: mikew

only a couple of things differ from the standard capistrano deploy.rb

# adjust accordingly
set :bundle_without, %w(development test postgres sqlite)

after 'deploy:cold' do
  run "cd #{release_path} && #{rake} gitlab:app:setup RAILS_ENV=#{rails_env}"
  deploy.restart
end

to the same effect, I've never understood why Gitlab ships with a Procfile and still uses init.d scripts throughout the documentation.

By Administrator on 2013-01-23T19:28:25 (imported from GitLab project)

By Administrator on 2013-01-23T19:28:25 (imported from GitLab)

Created by: brodock

@mikew it probably is there to be used on development

By Administrator on 2013-01-23T22:03:38 (imported from GitLab project)

By Administrator on 2013-01-23T22:03:38 (imported from GitLab)

Created by: koenpunt

@mikew the Procfile is useful for development, but the Procfile in production is also possible by exported by foreman as an upstart job.

For example, I use it like this:

Procfile:

web: bundle exec unicorn_rails --env production -p $PORT -c ./config/unicorn.rb
worker: bundle exec sidekiq -q post_receive,mailer,system_hook,common,default -e production

And to setup the upstart job I run:

bundle exec foreman export upstart /etc/init -a gitlab -u gitlab -l /home/gitlab/gitlab/log/

And after that you can simple start and stop gitlab by running start gitlab and stop gitlab or service gitlab {start|stop|restart|reload}

By Administrator on 2013-01-23T23:36:19 (imported from GitLab project)

By Administrator on 2013-01-23T23:36:19 (imported from GitLab)

Created by: mikew

@koenpunt that's the point I'm trying to make. the documentation could then be the same for installation and upgrading, and silly changes like this would no longer be needed.

By Administrator on 2013-01-24T00:01:00 (imported from GitLab project)

By Administrator on 2013-01-24T00:01:00 (imported from GitLab)

Created by: riyad

@koenpunt @mikew Could you submit PRs for that? Proven/tested simplifications or improvements to the deployment are appreciated. ;)

By Administrator on 2013-01-24T15:20:57 (imported from GitLab project)

By Administrator on 2013-01-24T15:20:57 (imported from GitLab)

Created by: senny

As #3047 was merged I'm closing this one.

By Administrator on 2013-04-24T13:30:52 (imported from GitLab project)

By Administrator on 2013-04-24T13:30:52 (imported from GitLab)