Thank you Hassan for your input. I image the old site would remain up for a few days as current users my still have old DNS caches pointing to it. I have not decided between MySQL or Postgres. It sounds like DB Replication is a must in developing a good practice for a safe migration to new servers?
-Jim On Oct 12, 2:37 pm, Hassan Schroeder <[email protected]> wrote: > On Mon, Oct 12, 2009 at 11:24 AM, JimCifarelli <[email protected]> wrote: > > In the spirit of being agile with your Rails deployment and scaling, > > can you recommend a process for moving your application to another > > hosting provider where a new IP address will be assigned? > > I'm in search of a solution that provides: > > 1. Little to no downtime to customers. > > 2. Considers Internet DNS propogation time for finding the new host > > IP. > > 3. Considers database migration. > > I'd think #3 is the only question -- you can certainly have both sites > running simultaneously, providing zero apparent downtime. > > How you handle replication of *data* depends on the details of your > app, what DB you're using, etc. > > FWIW, > -- > Hassan Schroeder ------------------------ [email protected] > twitter: @hassan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
