a few questions about moonshine god

[Josh Sharpe]

1)  I don't fully understand how god:restart works.  I checked out the task and it calls 'god quit', and then upstart(?) is suppose to respawn it, but in my experience this doesn't happen.  When god:restart is triggered after deploy, or manually I get this:

  * executing `god:restart'

  * executing "sudo -p 'sudo password: ' god quit"

    servers: ["app1"]

    [app1] executing command

 ** [out :: app1] The server is not available (or you do not have permissions to access it)

 ** [out :: app1] 

    command finished

failed: "sh -c 'sudo -p '\\''sudo password: '\\'' god quit'" on app1

So I guess 'god quit' is blowing up because god isn't running in the first place.  Wouldn't this break subsequent after deploy callbacks (if they existed?)

Also, whatever upstart is supposed to be it's not correctly respawning god. What logs should I be checking see what's going on?

2) This might be a god question and not specifically related to moonshine, but i'll give it a shot.

When I manually start god with this:

 god -c config/god/order_approval.god -D

It tries to start my order approval daemon but fails with an exit status of 1 and continues to try to restart it.  However, if I try starting the daemon with the same command god is supposidly using the daemon starts up fine.  Check out this pastie for details:

http://www.pastie.org/651089

Thanks!

[delooks]

I think you have the wrong or no configuration in your application
manifest.

God cannot create the logfile in the standard path '/var/log/god.log'
so the restart fails.

There is also an error in the documentation of the plugin, be care of
the #{} in:
configure(
:god => {
:log_level => 'info',
:log_file => "#{configuration[:deploy_to]}/shared/log/god.log"
}
)

Hope I could help you.