Hi,
I'm starting to use god to monitor some resque workers and I'm trying
to match these constraints:
1) Not making my deploy user a sudoer
2) Being able to restart my workers as part of a cap deploy.
I looked at san_juan (which appears to not have been touched in about
2 years), but that breaks #1, which I don't think my sysadmin would
like very much.
Instead, this is what I'm doing:
1) Put all of the .god files in /etc/god and set up init scripts
(san_juan seemed to prefer them in #{rails_root}/config/god).
2) Made a god user with proper permissions.
3) (Not implemented yet) Had god watch #{rails_root}/tmp for a restart
file for the entire group (similar to how Passenger restarts).
Before I spend the time to implement 3, I just wanted to double check
that this was in line with other people's experiences/best practices.
I saw someone posted something similar to this a couple of weeks ago
(http://groups.google.com/group/god-rb/browse_thread/thread/
11ac52bdec727453), but he didn't get an answer.
Thanks,
Andrew
--
You received this message because you are subscribed to the Google Groups
"god.rb" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/god-rb?hl=en.
