41–47 of 47 posts
Earlier quoted context omitted.
If i somehow can't connect to the VM anymore "vagrant halt" followed by "vagrant up" usually fixes that. Doesn't happen alot though.
Halt breaks too, though!
Sort of neat. We already share our vagrants within our office as we port forward from the host computers to the guest. Thus to access bob's vagrant I just go http://bob-computer:3120/ , etc... We use this feature periodically and it is useful in those cases. I guess this new feature is mostly for remote collaborations where you are not in the same secure network. PS. Vagrant is one of the most reliable parts of our h…
I know this isn't the right place for it but here we go: it's a total PITA when somehow the VM connection gets severed and "vagrant ssh" won't work and "vagrant shutdown" won't shutdown cleanly, so you have to kill it by hand and then reboot MANUALLY in virtualbox because the VM gets stuck in the grub menu after a non-clean kill. So then you have to wait for it to boot completely, then shut down normally and then run…
Sort of neat. We already share our vagrants within our office as we port forward from the host computers to the guest. Thus to access bob's vagrant I just go http://bob-computer:3120/ , etc... We use this feature periodically and it is useful in those cases. I guess this new feature is mostly for remote collaborations where you are not in the same secure network. PS. Vagrant is one of the most reliable parts of our h…
I know this isn't the right place for it but here we go: it's a total PITA when somehow the VM connection gets severed and "vagrant ssh" won't work and "vagrant shutdown" won't shutdown cleanly, so you have to kill it by hand and then reboot MANUALLY in virtualbox because the VM gets stuck in the grub menu after a non-clean kill. So then you have to wait for it to boot completely, then shut down normally and then run…
Earlier quoted context omitted.
So they can only get their job done if they are in the same timezone or if you don't happen to reboot your laptop? Those don't seem like great use cases. Plus if you are at the point of QA/PM review of what you've done, the code has already been checked into source control. They could just as easily spin up their own VM with the Vagrantfile.
GP said dev server, not laptop. I think in that context it's reasonable. I used Vagrant for CI builds for a while, and I would have liked the ability to automatically share an internal url to the environment so that when coworkers submitted code that broke the build, they would have a single link to follow to get access to the particular environment on the particular server that serviced their job. Some vagrant envs…