News for hackers. Stuff that matters.
Re:Why Vagrant? by aroman on Sunday December 01, 2013 @12:04AM (#6826200)
Ah I see, very cool. You mentioned something about Gtk and Cairo — do you ever interact with the VM graphically, or do you only use it as (what amounts to, I suppose) a networked Linux sandbox running inside OS X.

Also, how do you push code to the instance to run/deploy the code?

Re:Why Vagrant? by aethr on Sunday December 01, 2013 @12:46AM (#6826300)
Vagrant mounts a filesystem at /vagrant on the guest vm with the contents of the folder where your Vagrantfile is. Typically this means you include a Vagrantfile in the root dir of your project, and then your entire project folder is available on the guest box.

I strongly suggest investigating the NFS mount option for this feature if you're using Virtualbox, as the performance difference is substantial over Virtualbox shared folders (which is the default for the /vagrant mount).

Edit: typo

Re:Why Vagrant? by chewxy on Sunday December 01, 2013 @01:26AM (#6826371)
I've not tried running anything graphically. My previous machines for the past 7 or so years have been linux. I have my own bootstrap scripts for Python and R and some of the libs require RGtk2 and stuff, which couldn't really work on OS X without a lot of fiddling (but installing them on Ubuntu machines were a breeze).

So when my bootstrap scripts failed, I ran them on a Vagrant based instance instead. Problem solved.