On Fri, Apr 16, 2010 at 11:32 AM, Michael Pavling <pavl...@gmail.com> wrote: > On 15 April 2010 23:16, carlitux <carlitos....@gmail.com> wrote: >> a tool to exclude all my non standard ruby >> installation (all libraries and only use the standard instillation), >> but with the option to install any library only into the sandbox >> without problems with version with my system installation. > > You could always set up a dedicate virtual machine for the project. > For instance, I've had good results with the TurnkeyLinux Rails > Appliance installed in VirtualBox. You can access it like any other > networked machine and keep your development environment there. > > It causes a few extra hoops to jump through, but gives you a total sandbox.
This is how I normally work. Each of my clients have their own environment in their own virtual machine. Versions of stuff, indexers, memcache, databases... What would be a mess to maintain in a single dev machine is clean and under control this way. No matter what I did in my machine during the last month, if client C needs something I just fire up their VM and I know that's their isolated setup I could not interfere with, it has everything ready right away. Self-contained backups are trivial as well. You need some RAM though. I use VMware with Ubuntu. I normally edit from the Mac side via Samba, and have consoles from the VM floating around with Unity. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
