-
-
Save fideloper/dab171a2aa646e86b782 to your computer and use it in GitHub Desktop.
# -*- mode: ruby -*- | |
# vi: set ft=ruby : | |
Vagrant.configure("2") do |config| | |
config.vm.box = "precise64" | |
config.vm.box_url = "http://files.vagrantup.com/precise64.box" | |
config.vm.network :private_network, ip: "192.168.33.10" | |
config.vm.synced_folder ".", "/vagrant", | |
id: "core", | |
:nfs => true, | |
:mount_options => ['nolock,vers=3,udp,noatime'] | |
# Optionally provision PHP | |
# config.vm.provision "shell", path: "https://gist.github.com/fideloper/7074502/raw/install.sh" | |
end |
I had to add these lines to Vagrantfile to access localhost:8080
config.vm.network "forwarded_port", guest: 80, host: 8080
Am i doing this wrong?
@kmaxat
If you have something like this in you Vagrantfile:
config.vm.network :private_network, ip: "192.168.33.10"
Then you could use 192.168.33.10
instead of localhost:8080
Hi - my understanding is that, because the watched files are on the host machine, but the gulp / grunt / etc processes are on the guest machine, that it's very unreliable because of the complexity of mapping the file system updates from the host OS, to a potentially wildly different guest OS.
It's small comfort, but if you can run the gulp / grunt / etc on your host machine, you should see better results, but obviously this isn't helpful if you're trying to run something like forever or nodemon.
@Ilyes512 Just tested, and that specific line is giving me error when doing vagrant up
.
@mgustafsson1 definitely gona try that. I was also bothered by the huge latency of Grunt Watch and so I have been issuing the "Grunt" command to compile my sass files manually(almost when'd back to CodeKit).
edit:
Nice, it works! It's almost instant (1 to 2 sec max instead of the 9 to 10 seconds) :) Thanks for the tip! Will have to read your link and see what the other options do (ie nolock,vers=3,udp,noatime) and if I should add one of those in togather with
actimeo
.