Friday, January 27, 2017
Use Docker. Go to my web site Ruby on Racetracks at http://www.rubyonracetracks.com/, click on Installation, and click on "Getting Started". You can have Ruby on Rails ready to roll in minutes, not hours. You can also reset the Docker container to its original conditions in just a few seconds.
I make sure that my rbenv-general Docker images include the latest versions of Ruby and Rails and the versions currently used in Rails Tutorial.
In my opinion, the main reason for having Ruby on Rails directly in the host OS is to be on the same page as teammates who rely on this setup. Because it takes hours of babysitting processes to set this up and because you can't reset this development environment willy-nilly (as you can under the Docker way), I will NOT rely on Ruby on Rails in the host OS as my primary setup.
-- I make sure that my rbenv-general Docker images include the latest versions of Ruby and Rails and the versions currently used in Rails Tutorial.
In my opinion, the main reason for having Ruby on Rails directly in the host OS is to be on the same page as teammates who rely on this setup. Because it takes hours of babysitting processes to set this up and because you can't reset this development environment willy-nilly (as you can under the Docker way), I will NOT rely on Ruby on Rails in the host OS as my primary setup.
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/6d6c2341-45c0-40f3-b458-e1afa748f77b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment