If like me you didn’t know, you can do that with Capistrano:
1 2 |
$ cap HOSTS=web0.myapp.com deploy:update_code cap ROLES=web,app deploy |
Not terribly useful for the tasks demonstrated above, but what about this ?
1 |
$ cap ROLES=app monit:summary |
Incidentally, where are these documented ? I dimly remembered reading this somewhere once, and tried it. Works like a charm!
Even though Capistrano “tags” each release by creating a new folder on the production server(s), it might be interesting to have a historical perspective in your repository anyway.
This makes it easier to know exactly what went up for a release.
I would like to share the following Capistrano recipe for your pleasure:
1 2 3 4 5 6 7 8 |
require 'uri' task :after_deploy do source = repository dest = URI.parse(repository).merge("../releases/#{File.basename(release_path)}") cmd = "svn copy --revision=#{revision} --quiet --message \"Auto tagging release #{release_path}\" #{source} #{dest}" puts cmd `#{cmd}` end |
First, we start by requiring uri, because Subversion does not like relative URLs.
Next, we find the location into which to tag the release, and finally, we just do it.
Simple, effective.
Enjoy !
I am François Beausoleil, a Ruby on Rails coder. During the day, I work on XLsuite. At night, I am interested many things. Read my biography