vagrant-digitalocean
vagrant-digitalocean copied to clipboard
devopsgroup-io
Rsync works but not rsync-auto
I have this in my Vagrantfile I have :
config.vm.synced_folder "./", "/var/www", type: "rsync", rsync__auto: true
If I do a vagrant rsync everything is OK
➜ do_puphpet vagrant rsync
==> default: Rsyncing folder: /home/user/do_puphpet/ => /var/www
==> default: Rsyncing folder: /home/user/do_puphpet/ => /vagrant
➜ do_puphpet
but when I try to do a vagrant rsync-auto
➜ do_puphpet vagrant rsync-auto
==> default: New synced folders were added to the Vagrantfile since running
==> default: `vagrant reload`. If these new synced folders are backed by rsync,
==> default: they won't be automatically synced until a `vagrant reload` is run.
There are no paths to watch! This is either because you have no
synced folders using rsync, or any rsync synced folders you have
have specified `rsync_auto` to be false.
➜ do_puphpet
I user vagrant version 1.6.5 on linux and vagrant-digitalocean plugin version 0.7.0
This looks like none of the rsync settings are respected. I have rsync__exclude and rsync__auto and both seem to have no effect.
Rsync does not seem to work for me (Windows 7 host). I tried to go through the --debug but I don't see any errors. I can see the rsync dir's are adding during start. But no sync acutally occurs when using vagrant rsync or vagrant rsync-auto. Using docker image on Digital Ocean, but doesn't seem to be the cause.
It ends with: INFO runner: Running action: #<Vagrant::Action::Builder:0x3deeec8>
Related?
Does this plugin even support Rsync?
In case it helps anyone, I published a blog post of how we use unison instead of rsync to perform bidirectional sync'ing with Vagrant/DigitalOcean: https://keylocation.sg/blog/vagrant-and-unison-without-a-plugin/
We've now been using that approach with this vagrant-digitalocean plugin for months and no major issues found (this technique works for VirtualBox too so helped us with the transition).
Thanks for the hint. Seems like a viable option. But somehow this is also breaking the whole vagrant idea. It essentially means I had to do vagrant rebuilts like vagrant destroy / vagrant up / wait for completion / setup unison / start unison / new terminal / run Provisioning. I wouldn't know how to tell it my team. Am 28.06.2015 1:05 nachm. schrieb "Rhys Arkins" [email protected]:
In case it helps anyone, I published a blog post of how we use unison instead of rsync to perform bidirectional sync'ing with Vagrant/DigitalOcean: https://keylocation.sg/blog/vagrant-and-unison-without-a-plugin/
We've now been using that approach with this vagrant-digitalocean plugin for months and no major issues found (this technique works for VirtualBox too so helped us with the transition).
— Reply to this email directly or view it on GitHub https://github.com/smdahlen/vagrant-digitalocean/issues/160#issuecomment-116257475 .
@dkerkow setting up is a once-off though, perhaps 5-10 minutes per person excluding your usual vagrant up time. All things being equal it would be nice if this form of sync "just worked" inside Vagrant like shared folders do, but otherwise it's not much of an imposition.
BTW we originally wanted to have unison "embedded" in our vagrant up and invoked automatically but decided against it, as:
- Occasionally you need to start over or resolve unison conflicts (depends on what type of files you're syncing back, really, and if a file gets updated multiple times in a row before unison can finish sync'ing the previous version)
- We like having the verbosity of unison sync (i.e. seeing what files have changed) and there'd be nowhere for that output unless it's in its dedicated terminal
I run vagrant up many times in a day, so unison doesn't help there. Also, rsync is used by chef-solo to upload cookbooks, so I still need rsync to work at least for pushing out files.
