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]> 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]> 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]> 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]. >>> 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]. >> > 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]. > 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/CAM6ypFEWbguB%2BZBo1Q5N6bEHYr_hBne7KEEN8jtLW7nHBMaOvQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
