Ruby on Rails

On Thu, Jul 4, 2013 at 5:43 AM, Peter Hickman
<peterhickman386@googlemail.com> wrote:
> We tried that, we use PostgreSQL and londiste, but when it decided to break
> it stayed broken. I spent weeks trying to get things to work again once it
> failed. That was only 2 databases, what would happen for the >25 databases
> that we have?
>
> Unless someone dumps a large amount of cash in my lap I have to improve the
> situation we are in with what we have to hand rather than throwing money
> around.

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. The latter is what some
companies do, the former is a complicated mixture of how do you want
to go about it, and are we doing it right.

--
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/CAM5XQnz0_BMaD6WvAjQugt83mf38HV1i00PGQ4V%3D9rLphWpBBw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.