Re: [Rails] Re: Reducing downtime

On 4 July 2013 12:08, Jordon Bedwell <envygeeks@gmail.com> wrote:

You really only have two options here if you ask me, learn to do live

snap-shots so you can roll-back or learn to deploy early and often
with small changes that will not drastically break anything and can be
easily rolled back if something bad happens.

Deploying is not the problem. It's things like the file system becoming corrupted, which can happen at any time. In fact this is what prompted this post in the first place, the file system on a vm became corrupt and we had to wipe and rebuild.

"Live with it" is not acceptable either. There is something better than the current situation. Even if it is not perfect it can be better.

Logging the changes from ActiveRecord by using the before_* and after_* hooks might provide an ad hoc transaction journal that could be replayed against a backup to bring things up to date. At least for databases that experience a low level of activity.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CALxYQy6AOBbhGrcE5ZjQ4DTsk30%3DRw2yt8nvQFfxSR1XcmDLrQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.