Chris Fidao

That's interesting, so the `override.vm.box_url = "http://files.vagrantup.com/precise64_vmware.box"` line is probably defunct now I guess, but I don't see a VMware version of it: https://vagrantcloud.com/search?utf8=%E2%9C%93&sort=&provider=&q=ubuntu%2Ftrusty64

Thanks I'll check it out soon! On Tuesday, September 30, 2014, Jeffrey Vandenborne < [email protected]> wrote: > This machine should work > > — > Reply to this email directly...

Looks like we can use "provider.setup" options - check it out on the readme: https://github.com/smdahlen/vagrant-digitalocean ``` config.ssh.username = vagrant provider.setup = true ```

I'm not sure we can make assumption on the network to bridge on - for example, my wifi is on en0 instead of en1: 

I'm not sure on that, that would be nice tho!

Hey! I have a few questions on this: - Are you sure $HOME still works everywhere it's been changed (tested this)? A lot of those scripts are run as root...

Correct I was on my Mac. Vagrant bridges to an existing network interface, or creates a new on on your host machine. When you add the following: ``` ruby config.vm.network...

Mmm good questions then - I'm not sure on the best way to handle the AWS when the user is "ubuntu". It still looks like that's only an issue on...

Howdy! We've had some updates to the repo, and this is now creating merge conflicts. Let me know if you're interested in pursuing it as discussed (your strategy sounds good!)

Great - however, can yo update your repository with the latest? We made a lot of changes this weekend to try to get to a 1.0 release and now this...