itamae recipe for god process monitoring framework
Add this line to your application's Gemfile:
gem 'itamae-plugin-recipe-god'And then execute:
$ bundle
Or install it yourself as:
$ gem install itamae-plugin-recipe-god
Include this recpie as:
include_recipe 'god'
This recipe will install god and generate the following files.
-
/etc/god/master.conf
This is the master file for god configuration. It loads all cofiguration files with extension .god under the directory /etc/god/
-
/etc/logrotate.d/god
god writes logfile to /var/log/god.log. This recipe generages logrotation config file to rotate it on daily basis.
-
/etc/init.d/god
service script for SysV init.
If the system does not use systemd such as CentOS6, configure for SysV init. -
/etc/systemd/system/god.service
Systemd Unit File.
If CentOS7, configure for systemd.
By default, this recipe will install "god" gem from rubygems.org. You can install another god by specifying "ALTERNATIVE_GOD" environment variables.
ALTERNATIVE_GOD="gem name"
ALTERNATIVE_GOD="path/to/gemfile"
When you specify gem name as "ALTERNATIVE_GOD" environment variables, then you can specify the version as "ALTERNATIVE_GOD_VERSION" environment varialbes.
After checking out the repo, run bin/setup to install dependencies. You can also run bin/console for an interactive prompt that will allow you to experiment.
To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release, which will create a git tag for the version, push git commits and tags, and push the .gem file to rubygems.org.
Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/itamae-plugin-recipe-god. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.
The gem is available as open source under the terms of the MIT License.
Everyone interacting in the Itamae::Plugin::Recipe::God project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.