Okay, I'll bite and give my $0.02. Method #1 Pros and Cons:
Con: I don't like the application code to be responsible for log rotations. It "feels" like this should be a system administrative task. Pro: Easy to set up and no need to drop a logrotate config in /etc on deployment Method #2 Con: Deployment requires another "external" step (configuration external to the application code itself) Pro: From a sysadmin point of view, I keep all my "log rotation" configuration in one place (as it ought to be). My Preference Method #2: use capistrano or other scripted/automated deployment tool to drop (or update) a logrotate config in your /etc/logrotate.d/ directory to overcome the downside of this method and you're golden. That's just my opinion. I'd also be interested in other points of view and better ideas. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en.
