drop it in recipes/ and capistrano will autoload it. hot, eh?

Hello, In this morning when I tested a new feature in staging a experienced some problems with god after each deploy.

The problem happens because the default restart recipe call a god stop and this task only reload the god proccess and not his watched proccess. To fix this problem what I did was change the recipe to:

task :restart do
sudo 'god terminate'
sudo 'start god'
sleep 5
end

After that everything works.

I get this error:

Uncaught exception: Puppet::Error: Parameter alias failed: /etc/logrotate.d/varloggodlog.conf can not create alias logrotate_varloggodlog: object already exists

I am only able to resolve it by removing the logrotate command from the moonshine_god recipe (not needed in my case because I put ithe logs under shared/log)

Ubuntu >= 9.04 uses /etc/init instead of /etc/event.d for upstart config files, as well as slightly different format. Not sure how best to fix the plugin to do the right thing depending on the version (potentially, both files could be written), but I see someone forked and made a version that works only on 9.04 and up. Logging this just in case someone else encounters the same issue - the fork is varyform/moonshine_god.

The first deploy needs to ensure that god is actually running, or else other cap tasks, like the restarting of god, will fail. Basically, it's just this:

service 'god', :ensure => :running, :require => [list_of_required_stuff]

It actually looks like god is manually restarted on this line, but it must not be working effectively. Consider replacing this zanyness with the plain old service call.