Thursday, July 23, 2015
Thanks for your fast answer! :^)
El jueves, 23 de julio de 2015, 14:55:31 (UTC+2), Scott Ribe escribió:
-- 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...
Thanks again!
El jueves, 23 de julio de 2015, 14:55:31 (UTC+2), Scott Ribe escribió:
On Jul 23, 2015, at 6:16 AM, Rafa F <seph...@gmail.com> wrote:
>
> In rails every evolution of a model must be executed through migrations, isn't it?
No. You don't have to use migrations at all; if you're managing your db schema some other way already, you can continue to do so. Migrations are a convenience for projects where the db is managed entirely within the scope of a rails app.
--
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/09798bae-879c-40a7-8295-251d919cc30c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment