This is yet another good reason to use capistrano. capistrano recipes allow to define comands to be performed on the target server, so it's easy to add a mysqldump command for backup and a a rake task to perform the migration. And, usually I warn my customers before upgrading them and agree a 'service window'. That's good practice anway. Finally, a lot depends on your customer relationship. If your customer doesn' trust you you need to go with a different solution.
Am Mittwoch, 4. Februar 2015 20:04:37 UTC+1 schrieb Ruby-Forum.com User: > > Thanks for the answers. > @ Vivek Sampara how do you deal with migration? because customer have > existing data that can't be lost. > > -- > Posted via http://www.ruby-forum.com/. > -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/d7812a87-82da-4262-85bc-117db18b7965%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
