cue the inevitable 'why not using x' etc - but it's always interesting to hear what the heads are using day-to-day
back
1 comments
I really want to post "why not use Vagrant to automate all of that?" but I stopped myself.
vagrant forces you to run in a virtual machine, bit more inconvenient than running on the local physical host.
I've found it's pretty seamless. You're editing files on your local dev machine, which vagrant auto-mounts in the guest OS. Ports are automatically forwarded to your host dev machine, so my workflow is literally exactly the same as if I developed directly in OS X. The only difference is first having to run "vagrant ssh" to run commands in the dev environment, but for having a repeatable, share-able, isolated environment with all dependent libraries automatically installed, it's well worth typing "vagrant ssh".
I find memory hogging server processes running a different OS than my server to have too many inconveniences.