Hi David, FYI - over the years I accumulated a few tweaks which make it well usable on Windows (for me at least), including ssh and rsync support. You might be interested in that: https://github.com/tknerr/bills-kitchen
If you are not tied to Windows + VirtualBox for some reason, you could also try to run it on Ubuntu with LXC containers (and vagrant-lxc plugin), which is super fast. Example environment here: https://github.com/tknerr/dev-box/ HTH, Torben On Mon, Mar 9, 2015 at 1:34 PM, David Severski <da...@severski.net> wrote: > +BIG_INT. > > Vagrant on Windows (yes, running under a cmd or powershell window) is a real > hit-and-miss experience. Between the rsync issues (of which, the ENV hack is > only the latest in a long stream of problems) and the gawd awful SMB sync > feature introduction that either breaks installs or leaves tons of cruft on > ostensibly clean host machines, vagrant is a real PITA for Windows users. > Unfortunately, there just isn't a big enough community of Windows users > active here to get the attention needed to mature this solution. > > David > > > On Tuesday, March 3, 2015 at 4:18:22 PM UTC-8, David wrote: >> >> As a new Vagrant user I followed the instructions here, installing the >> cygwin rsync package and then adding it to my Windows path. >> >> I figured it should just work, but upon reload I started getting errors >> like: >> >> rsync: change_dir "/c/workspace" failed: No such file or directory (2) >> >> I tried a bunch of other ways of specifying the path in Vagrantfile such >> as: >> >> config.vm.synced_folder "../workspace", "/workspace", type: "rsync", >> rsync__auto: "true" >> config.vm.synced_folder "C:/workspace", "/workspace", type: "rsync", >> rsync__auto: "true" >> config.vm.synced_folder "/cygdrive/c/workspace", "/workspace", type: >> "rsync", rsync__auto: "true" >> >> but all resulted in the same error. There are a lot of results when >> Googling Vagrant rsync problems making it harder to find the right one. >> Finally I found this issue, and embedded in the many comments spanning more >> than a year there is the suggestion to add this line: >> >> ENV["VAGRANT_DETECTED_OS"] = ENV["VAGRANT_DETECTED_OS"].to_s + " cygwin" >> >> And it works! That is great, however the problem is Vagrant. I'm not >> familiar with the Vagrant culture, but is this seriously the best way to >> document long-standing essential workarounds. If you're not going to fix it >> that's one thing, but can it least be documented? The official documentation >> says: >> >> "On Windows, rsync installed with Cygwin or MinGW will be detected by >> Vagrant and works well." >> >> Are all new users just supposed to spend 30 minutes sorting out this >> problem while the maintainers ignore it for another year? Very strange >> initial experience with Vagrant after hearing some good things. >> >> >> > -- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to vagrant-up+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
