Thursday, July 23, 2015
Ok! Understood! :^)
-- Thank you so much for your help.
El jueves, 23 de julio de 2015, 15:18:10 (UTC+2), Scott Ribe escribió:
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
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/fe1ab610-0f04-4d3f-909b-b3c9ce706ed7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment