Re:Salt: Like Puppet, Except It Doesn’t Suck
by danudey on Monday June 24, 2013 @01:00PM
(#5934182)
> Consider logrotate. Here is the only documentation I can find on the topic [1].
Using Salt's logrotate module might be more than you need. You can always just have salt manage a file in /etc/logrotate.d/ and keep it up to date, which would be a lot easier.
The salt module is meant for more complex, fine-grained tuning of logrotate files, but I'm not really sure why I would use it.
> My uswgi + nginx configuration - translating that into salt - I don't know where to begin.
The approach that I use: check your entire nginx configuration into git (e.g. your whole /etc/nginx directory) and then you can configure salt to check it out and keep it updated.
Also, if you're custom-compiling nginx into /opt/local/nginx or something, you can actually have salt recursively copy the entire directory to your slaves.
Using Salt's logrotate module might be more than you need. You can always just have salt manage a file in /etc/logrotate.d/ and keep it up to date, which would be a lot easier.
The salt module is meant for more complex, fine-grained tuning of logrotate files, but I'm not really sure why I would use it.
> My uswgi + nginx configuration - translating that into salt - I don't know where to begin.
The approach that I use: check your entire nginx configuration into git (e.g. your whole /etc/nginx directory) and then you can configure salt to check it out and keep it updated.
Also, if you're custom-compiling nginx into /opt/local/nginx or something, you can actually have salt recursively copy the entire directory to your slaves.