Comment Screen, Vim in a VM (Score 1) 1055
At the moment I'm developing a Python based web app. I started using PyDev/Eclipse but found the environment more hindrance than aid.
I then got the idea to package up my development environment into a Virtualbox VM. I modeled the VM as closely as possible to the production environment. I run a screen session with several Vim instances (using windows and tabs). I then ssh to the VM. I find this convenient for a number of reasons:
- my development env is as close as possible to the production env
- I don't need any unnecessary daemons running on my physical OS (e.g. Apache, MySQL, etc)
- the VM can be versioned (via snapshots)
- I can suspend the VM and restore it to the exact state it was previously in (same screen/vim sessions, same daemon states)
- the VM is only has 256MB RAM allocated to it; I can start VirtualBox and restore my VM in less time than it takes to open Eclipse
In my experience, having your development environment behave exactly the same *every* time you use it is not to be overlooked.