-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vagrant rsync
command does not work
#137
Comments
@bryanwb The change has been reverted due to NFS issues: #94 I was hoping there is an official way to fix this, but considering that upstream bug is not getting update a workaround will probably be needed. Something like a custom action "FixSyncedFolders" which would force disable NFS with each folder. It's on my list of things to fix when I have some cycles. |
@Temikus tks for the quick reply. I have a workaround atm, but I'll try to come back to this |
Any updates on this issue? @Temikus Could you please share your workaround? |
@numediaweb Didn't have time to do this yet, I'm afraid. Will be happy to give you pointers or take a look at a PR, if you're willing to do one. Re:workaround - depends on what you're trying to do. The rsync command is not available but folders do sync via rsync correctly on "up". You need to resync without reprovisioning? |
@numediaweb @bryanwb This should be fixed, new release that uses built-in rsync is now available. |
This is likely related to #85. The rsync subcommand does not currently work w/ the google provider. The plugin does not generate the
.vagrant/machines/default/google/synced_folders
file that thevagrant rsync
command uses to perform the sync.The text was updated successfully, but these errors were encountered: