-
-
Notifications
You must be signed in to change notification settings - Fork 286
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
unison and unox are required even while using rsync #288
Comments
got you on this, i think its just not as simple fixing this... But i am very interested in pull request |
It's also part of what I would like to do in #265.. if you're okay with it, I'll try to get the PR for refactoring configuration done and we can release that first, which should fix this issue.. and we can then have the PR for native volume and OS detection seperately.. |
If you can split it out without making it a huge rewrite of different topic's, i would love to see that happen! |
Any progress here by any hopes? Planning to release the next version, asking myself if that one could make it in |
I can say for sure that I will not be able to work on this, to many things going on at the moment. |
some progress are there, but nothing concrete yet, I'll try to get a PR ready by the end of the week.. sorry for the very slow progress.. |
Hello,
I was trying to use rsync as sync_strategy, but it seems that the check for the
unison
andunison-fsmonitor
it is hardcoded and does not respect thesync_stragegy
configuration?I got the first error:
...followed by:
The only way to run docker-sync was to install both unison and unison-fsmonitor.
In my opinion if the
rsync
strategy is an accepted solution I don't see the reason why i would want to install unison if i'm not going to use it. :)This is my
docker-sync.yml
file, if needed i can provide alsodocker-compose(-dev).yml
files.The text was updated successfully, but these errors were encountered: