Closed EugenMayer closed 7 years ago
fswatch_strategy
option to prevent issues like https://github.com/EugenMayer/docker-sync/issues/209sync_strategy: 'unison'
BTW, while working daily with unison
and really happy with it, unison
has still some instabilities. I always have a log window with debug mode activated displayed on my screen to ensure files are correctly synced. Most of the time, a simple (or multiple) restart fix the issue, but unison + daemon will hide any information to the end user of eventual problems.
well we will provide logs here https://github.com/EugenMayer/docker-sync/pull/65#issuecomment-278565262 so you can still tail -f and have the same thing. I also use unison only these days and i have very little to none glitches at all. And we are talking about 5-7 different guys using it on different pretty large projects with different stack types ( huge web stacks, java stacks, ruby stacks ). So i would really call this one "stable enough"
Documented here https://github.com/EugenMayer/docker-sync/wiki/Migration-Guide - still need the code changes
done
What steps need to be done when we change the default of docker-sync to unison?