By "reset", I'm talking about returning Ruby on Rails to its original state from just after you first installed it and before you did anything with it.
My Debian Stable Vagrant base box comes with RVM pre-installed, along with multiple versions of Ruby, each with multiple versions of Rails. This takes several hours to build, but I use a Packer script to automate the process. The end result is stored as my Vagrant base box. If you decided to use the "rvm implode" command just for kicks, how long would it be before you could start working on your Rails projects again? If you rely on Ruby on Rails installed directly in your host OS, this would take hours. On the other hand, if you were using my Vagrant box, it would be just a matter of destroying and rebuilding the box, and you'd be back in business in just a few minutes. Since Docker avoids the overhead of having a virtual machine (which has to be booted up), the Docker way would allow you to return to the original state immediately. You can be back in business in seconds. On Wednesday, August 19, 2015 at 2:02:03 PM UTC-5, Hassan Schroeder wrote: > > > Just curious -- what exactly do you mean by "reset" here? > > And what is the perceived problem with "reinstalling"? A fresh rails > install on Ruby 2.2.3 just now took ~30 seconds on a relatively old > MacbBook Air, and half that time was building nokogiri extensions. > > -- 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/2238f657-e1af-4948-8274-3eb602cdf0a2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
