This seems to be a common enough thing with Rails apps nowadays, so it’s in.
Testing is one of the very first things covered, the first of course being Ruby itself and then Git.
Paperclip, authlogic, cancan, aasm / statemachine / workflow (still deciding) will all get a play.
Tools and best practices for monitoring a Rails 3 app in production7 votes
I think this is an absolutely essential part of any Rails book. You have to be monitoring the exceptions that will happen, even if you are doing testing.
Then you also have to be monitoring for when the server / something else blows up.
How to set Time.zone, and how to "not worry" about times in Rails.1 vote
Plan on covering this in the Authentication chapter when the user edits their profile details.
DJ, Reseque, things with redis possibly.
How/what/why to move to background processing.8 votes
Planned to be covered, perhaps resque for this.
An obvious topic, but I think an important one for a Rails 3 book.5 votes
When changed-from-Rails-2 things are mentioned I was thinking of having like a footnote, or a reference number next to these things and an appendix at the end listing the changes.
ideas for backing up an app database...S3, good hosts, etc...1 vote
Git is of course a great way to back up your code, but backing up the data in your application is also important. Great idea.
- Don't see your idea?