God leaks memory pretty badly so I chose Monit for my VPS. Monit runs at about 2MB of RAM constantly, whereas my god install running on Ruby 1.8.6 leaked out to about 60MB of RAM in about 36 hours. I didn't want to monitor my system monitoring tool so I scrapped God and went over to Monit and have had absolutely no problems.
Both solutions are good, and there are some pros and cons for both of them.
God config file is written in Ruby, so you can do basically everything Ruby allows you to do, and it's a lot of stuff. Monit has to be configured using its own syntax, it's usually OK but more restrictive. Anyway, you can also generate monit config with Ruby (as a part of your deployment strategy).
Also, monit uses less resources, so if you're on VPS or just don't have any spare memory, monit could be a better choice. Personally, I prefer god, as it's more configurable.
Here's a very good screencast on god. There's also a lot of feedback in comments to this screencast.
The only real problem with monit (if its a problem) is that the configuration files can get a bit verbose if you're running large clusters, but this could be solved with a templating system.
即使让 God 在我的专用 Ubuntu 服务器上运行，我也遇到了很多问题。 我最终只是放弃了。 Monit 可能不是 Ruby，但它基本上没有麻烦。
I had a ton of problems even getting God to run at all on my dedicated Ubuntu server. I eventually just gave up. Monit may not be Ruby, but it's largely hassle-free.
To anyone finding this post going forward, you might also consider bluepill as an alternative to God. While I'd hope that God has addresses its memory issues in the past two years, I know bluepill was set out from the beginning to run on a small footprint. While still not as small as monit, bluepill's footprint is very reasonable (~16 MB VIRT, 13 MB RES for me).
If you have multiple levels of dependencies it starts up top level apps when lower level dependencies are started. This might be great for some use-cases, but its not particularly flexible.
At the moment I find it pretty annoying. Fortunately you can kinda kludge your way through the dependencies with their 'groups' feature, but its not particularly satisfying. Anyway, thats my take on v5.1.1
发布评论
评论（6）
上帝会严重泄漏内存，所以我选择 Monit 作为我的 VPS。 Monit 始终以大约 2MB 的 RAM 运行，而我的上帝安装在 Ruby 1.8.6 上运行，在大约 36 小时内泄漏到大约 60MB 的 RAM。 我不想监控我的系统监控工具，所以我放弃了 God，转而使用 Monit，并且绝对没有任何问题。
God leaks memory pretty badly so I chose Monit for my VPS. Monit runs at about 2MB of RAM constantly, whereas my god install running on Ruby 1.8.6 leaked out to about 60MB of RAM in about 36 hours. I didn't want to monitor my system monitoring tool so I scrapped God and went over to Monit and have had absolutely no problems.
两种解决方案都很好，并且都有一些优点和缺点。
God 配置文件是用 Ruby 编写的，因此您基本上可以完成 Ruby 允许您做的所有事情，而且内容很多。 Monit 必须使用它自己的语法进行配置，通常没问题，但限制更多。 无论如何，您还可以使用 Ruby 生成 monit 配置（作为部署策略的一部分）。
此外，monit 使用的资源较少，因此如果您使用的是 VPS 或者只是没有任何空闲内存，monit 可能是更好的选择。 就我个人而言，我更喜欢 God，因为它更可配置。
这是一个非常好的关于上帝的截屏视频。 对此截屏视频的评论中也有很多反馈。
Both solutions are good, and there are some pros and cons for both of them.
God config file is written in Ruby, so you can do basically everything Ruby allows you to do, and it's a lot of stuff. Monit has to be configured using its own syntax, it's usually OK but more restrictive. Anyway, you can also generate monit config with Ruby (as a part of your deployment strategy).
Also, monit uses less resources, so if you're on VPS or just don't have any spare memory, monit could be a better choice. Personally, I prefer god, as it's more configurable.
Here's a very good screencast on god. There's also a lot of feedback in comments to this screencast.
上帝有很多问题，包括：
我在 http://blog.bradgessler.com/use-monit-with-rails-not-god
唯一真正的问题与 monit （如果它是一个问题）的一个问题是，如果您运行大型集群，配置文件可能会变得有点冗长，但这可以通过模板系统来解决。
God has a lot of problems including:
I did a write-up about it at http://blog.bradgessler.com/use-monit-with-rails-not-god
The only real problem with monit (if its a problem) is that the configuration files can get a bit verbose if you're running large clusters, but this could be solved with a templating system.
即使让 God 在我的专用 Ubuntu 服务器上运行，我也遇到了很多问题。 我最终只是放弃了。 Monit 可能不是 Ruby，但它基本上没有麻烦。
I had a ton of problems even getting God to run at all on my dedicated Ubuntu server. I eventually just gave up. Monit may not be Ruby, but it's largely hassle-free.
对于任何发现这篇文章的人，您也可以考虑将 bluepill 作为上帝的替代品。 虽然我希望上帝在过去两年里解决了它的内存问题，但我知道 bluepill 从一开始就注定要在很小的足迹上运行。 虽然仍然不像 monit 那么小，但 bluepill 的占用空间非常合理（对我来说大约 16 MB VIRT，13 MB RES）。
To anyone finding this post going forward, you might also consider bluepill as an alternative to God. While I'd hope that God has addresses its memory issues in the past two years, I know bluepill was set out from the beginning to run on a small footprint. While still not as small as monit, bluepill's footprint is very reasonable (~16 MB VIRT, 13 MB RES for me).
Monit 有其自身的问题：
目前我觉得这很烦人。 幸运的是，您可以通过“组”功能来解决依赖关系，但这并不是特别令人满意。 无论如何，这就是我对 v5.1.1 的看法
Monit has its own issues:
At the moment I find it pretty annoying. Fortunately you can kinda kludge your way through the dependencies with their 'groups' feature, but its not particularly satisfying. Anyway, thats my take on v5.1.1