Failed to sync if gatling-rsync is started after making changes

[droidlabour]

Failed to sync if gatling-rsync is started after making changes

[smerrill]

What you've described is the correct behavior. Gatling picks up changes by watching for creation of files or writes to files while the process is running (much like Vagrant's built-in rsync-auto command.)

[droidlabour]

Ok, but I think it should be a feature.

[smerrill]

At present, you could do vagrant rsync; vagrant gatling-rsync-auto when you start the gatling rsync to do what you want.

Since this is designed to be a drop-in replacement for Vagrant's rsync-auto command, I don't want it to work differently out of the box. That said, let me look to see how easy it would be to put together an optional parameter that would do an initial sync before starting up.

[craiga]

When rsync-auto runs, it does do an initial sync to make sure any changes you've made locally are copied across.

$ vagrant rsync-auto
==> default: Doing an initial rsync...
==> default: Rsyncing folder: /Users/craiga/my-source-code/ => /var/my-source-code
==> default:   - Exclude: [".vagrant/", ".git*"]
==> default: Watching: /Users/craiga/my-source-code

Perhaps this is new behaviour?

[smerrill]

This has been released to RubyGems as version 0.1.0.

https://rubygems.org/gems/vagrant-gatling-rsync/versions/0.1.0