Thanks, Debo. By the way, a colleague came upon a weird workaround:
- Use a standard share in the Vagrantfile, say: config.vm.synced_folder "website", "c:/website_vbox_share" - In the guest, create a symlink to yet another spot: mklink /D "c:\website_symlink" "c:\website_vbox_share" - In the guest, create a share from that symlink: net share website=C:\website_symlink - In the guest's IIS, point the web root to the new, local share: \\localhost\website I don't have a provisioner for all of that yet, but those are the nuts and bolts. Super-straightforward, huh? :-/ Jamie On Wednesday, July 29, 2015 at 3:58:31 PM UTC-4, Debo wrote: > > Hi Jamie, > > sorry for the delay, so what I've used on the guest is the rsync version > available here > > http://www.mingw.org/wiki/MSYS > > I installed it using a custom powershell provisioner made by me. > > If the project is quite big and you are having problems with performance > you might also want to have a look into this plugin > > https://github.com/smerrill/vagrant-gatling-rsync > > I didn't try it myself so I can't say whether it's good or not. > > I hope it helps. > > Best, > Debo > > On Mon, 27 Jul 2015 at 20:29 Marco De Bortoli <[email protected] > <javascript:>> wrote: > >> About the configuration of rsync you should find everything on the >> Vagrant website, for the guest you should just simply add to your >> provisioner a step to install rsync. I don't remember now what I've used >> but I can tell you tomorrow if that's ok. >> >> Cheers, >> Debo >> >> On Mon, 27 Jul 2015 at 18:44 Jamie Jackson <[email protected] >> <javascript:>> wrote: >> >>> Is there a writeup of using rsync with a Windows host/Windows guest? >>> >>> I happen to already have cygwin (with rsync) on the host, but I'm not >>> sure what is required on the guest side. >>> >>> Thanks, >>> Jamie >>> >>> On Fri, Jul 24, 2015 at 6:18 PM, Marco De Bortoli < >>> [email protected] <javascript:>> wrote: >>> >>>> Hi Jamie, >>>> >>>> the only thing that I found to work quite fine and without too much >>>> hassle on windows was the use of rsync. >>>> You develop locally and rsync takes cares to copy things over when >>>> required. It doesn't require too much configuration and permissions works >>>> alright. >>>> >>>> I hope that helps. >>>> >>>> Cheers, >>>> Debo >>>> >>>> On Fri, 24 Jul 2015 at 22:03 Jamie Jackson <[email protected] >>>> <javascript:>> wrote: >>>> >>>>> As has been mentioned before >>>>> <https://groups.google.com/d/topic/vagrant-up/mk4MfEayVGg/discussion>, >>>>> using standard VirtualBox shares from a Windows guest to a Windows host >>>>> is >>>>> problematic when developing for IIS. (The permissions don't work out.) >>>>> >>>>> I've seen recommendations in a few places to manually configure an SMB >>>>> share on the host, and to use that from the guest; however, I don't know >>>>> how to approach the permissions. >>>>> >>>>> - For which user should the host share be created? (Domain user? >>>>> Machine user?) >>>>> - On the guest, how does IIS access the share (UNC? a Mapping?)? >>>>> - Does the IIS application pool need special configuration? >>>>> >>>>> I also tried type: "smb", to see how it configures things, but a) it >>>>> didn't seem to work (wouldn't get past the port mapping) and most >>>>> importantly b) it needs to run as administrator, and I don't want to run >>>>> Vagrant as admin. >>>>> >>>>> In other words, I'm not really interested in getting type: "smb" to >>>>> work as a permanent solution, I'm just looking for the right strategy to >>>>> set it up manually. >>>>> >>>>> Thanks, >>>>> Jamie >>>>> >>>>> -- >>>>> This mailing list is governed under the HashiCorp Community Guidelines >>>>> - https://www.hashicorp.com/community-guidelines.html. Behavior in >>>>> violation of those guidelines may result in your removal from this >>>>> mailing >>>>> list. >>>>> >>>>> GitHub Issues: https://github.com/mitchellh/vagrant/issues >>>>> IRC: #vagrant on Freenode >>>>> --- >>>>> 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 [email protected] <javascript:>. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/vagrant-up/8918a711-ba50-4ea3-b822-11257f38072b%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/vagrant-up/8918a711-ba50-4ea3-b822-11257f38072b%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- >>>> This mailing list is governed under the HashiCorp Community Guidelines >>>> - https://www.hashicorp.com/community-guidelines.html. Behavior in >>>> violation of those guidelines may result in your removal from this mailing >>>> list. >>>> >>>> GitHub Issues: https://github.com/mitchellh/vagrant/issues >>>> IRC: #vagrant on Freenode >>>> --- >>>> 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 [email protected] <javascript:>. >>>> >>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/vagrant-up/CAM6ypFHamt9PVEXUTeD3gfVfg0_O3cvpwG71DkLzBj36zLemdw%40mail.gmail.com >>>> >>>> <https://groups.google.com/d/msgid/vagrant-up/CAM6ypFHamt9PVEXUTeD3gfVfg0_O3cvpwG71DkLzBj36zLemdw%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>> >>> >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- >>> This mailing list is governed under the HashiCorp Community Guidelines - >>> https://www.hashicorp.com/community-guidelines.html. Behavior in >>> violation of those guidelines may result in your removal from this mailing >>> list. >>> >>> GitHub Issues: https://github.com/mitchellh/vagrant/issues >>> IRC: #vagrant on Freenode >>> --- >>> 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 [email protected] <javascript:>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/vagrant-up/CA%2BonWPeZzp7seFiBkLrA5N9q2xVKOaxVBgYjyu1k3hqB61F2%3Dw%40mail.gmail.com >>> >>> <https://groups.google.com/d/msgid/vagrant-up/CA%2BonWPeZzp7seFiBkLrA5N9q2xVKOaxVBgYjyu1k3hqB61F2%3Dw%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/0f80f849-323d-437e-b40c-3ec9b95a2f4a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
