Thursday, July 23, 2015
On Thu, Jul 23, 2015 at 8:22 AM, Rafa F <sephyrot@gmail.com> wrote:
Ok! Understood! :^)Thank you so much for your help.
El jueves, 23 de julio de 2015, 15:18:10 (UTC+2), Scott Ribe escribió:On Jul 23, 2015, at 7:14 AM, Rafa F <seph...@gmail.com> wrote:
>
> Ok, and if I decided to work with migrations, what is the best way deploying in a production environment?
> Run a rake db:migrate in a production platform sounds like a little dangerous...
You need to review and test your migrations before deployment ;-)
You might want a third environment, "staging", in addition to development, test, & deployment. Let the staging db server have a replica of the production db that is re-synced periodically to have the full data. After other testing, before deployment, test the migration there. Review the SQL executed by the migration.
--
Scott Ribe
scott...@elevated-dev.com
http://www.elevated-dev.com/
https://www.linkedin.com/in/scottribe/
(303) 722-0567 voice
Scott's advice is top notch, a very best practice. In addition, you should ensure you have a full suite of acceptance tests you can run against the staging server, and pull in live testers as well to give it a good shake-down as only real live humans seem able to do.
Another aspect of this is to both automate and instrument your deployment processes. Capistrano seems the leading contender still amongst the Rails community and it does a pretty thorough job of things given a standard range of deployment environments.
Definitely make sure you have a roadmap or punchlist of everything that needs to be done, and stick to it; when you find something you had to do make sure to add it to the punchlist for future deploys or file defects to fix the problems to prevent them from showing up again.
Deployment is a big deal; you've already sussed that out, but sometimes it's not at all apparent just *how* big a deal it is.
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/CAHUC_t9TyvaGs6R03VG2YtWfuexM%3DYk%2BgCP6LYnz6gNhQAy%3DJw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment