Open shaharsol opened 8 years ago
According to vagrant rsync documentation, vagrant itself cannot do bi-directional rsync. I guess the only option is through NFS.
I dont really care about the underlying implantation as long as changes on the aws machine are reflected on the local host. On Mar 18, 2016 18:15, "Yufan Lou" notifications@github.com wrote:
According to vagrant rsync documentation https://www.vagrantup.com/docs/synced-folders/rsync.html, vagrant itself cannot do bi-directional rsync. I guess the only option is through NFS.
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/mitchellh/vagrant-aws/issues/450#issuecomment-198431420
This is what we use for this functionality.
https://github.com/smerrill/vagrant-rsync-back
You just have to be careful. If you push to the server, edit something locally, and then do an rsync-back it will overwrite all of your local changes. I may or may not have done that to myself a few times. ;)
I afraid NFS may not work very well and requires some extra things installed inside image (which makes images preparation more complex).
I would think more of using sshfs for that. But not sure what's the vagrant support on this. May look into that later myself.
I've decided to utilize CodeMill to offer $30 to anyone who will add this feature to mitchellh/vagrant-aws:
In the basic vagrant getting started guide, the synced folder tutorial is to modify a file on the guest system and see how it is reflected on the host system. This feature is missing from the vagrant-aws provider and I wish it existed, either via rsync or nfs.
In order to develop this and earn $30, please proceed to the task page at CodeMill.
The work will be done on my own fork, and when it's finished I will send a pull request to mitchellh/vagrant-aws so the entire community can enjoy this feature. This will be my contribution.