Skip to content
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

rsync after vagrant destroy? #129

Closed
vinhdizzo opened this issue Mar 14, 2016 · 2 comments
Closed

rsync after vagrant destroy? #129

vinhdizzo opened this issue Mar 14, 2016 · 2 comments

Comments

@vinhdizzo
Copy link

Hi,

I know the project directory get's rsync'ed to /vagrant in the server that gets spunned up in GCE. I noticed that the /vagrant doesn't get rsync'ed back to the project directory when vagrant destroy is executed. Would it make sense to have this happen? Thanks.

@Temikus
Copy link
Collaborator

Temikus commented Mar 14, 2016

Hi @vinhdizzo!

I would suggest filing a feature request with vagrant itself to support it in their rsync implementation.
The current custom syncing mechanism stays with this provider currently only until NFS capability gets sorted out: hashicorp/vagrant#6781

... or I write some hack in to disable NFS, but I'd rather avoid that to be honest ...

Cheers,
A.

@Temikus
Copy link
Collaborator

Temikus commented May 25, 2018

Deduping on #175 since that issue is more general.

Currently Vagrant doesn't implement bi-directional sync yet. However, people report that at least 2 plugins achieve that (like vagrant-unison or vagrant-scp): hashicorp/vagrant#3062

If you have any issues with interoperability - let me know and I'll do my best to see if I can make it work.

@Temikus Temikus closed this as completed May 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants