What type of issues?
And related, sync % reflecting ignored files. For example I've ignored a bunch of transient things like node_modules so my backup server sync is permanently at 70% even though it's actually up to date with all the files I want synced.
1. An "stignore.txt" at the root of a shared directory. This gets automatically synced to every device.
2. "#include stignore.txt" in '.stignore' that I need to manually write on every new device.
After the initial setup, which wasn't that hard after all, but took more effort than doing nothing and continue on Dropbox I was amazed. My setup became better as now my phone is a real client that syncs files, not just a file browser that can "star" and cache some files, and there's more granularity on what's shared.
I'm aware of https://github.com/syncthing/syncthing-lite but the consensus seems to be it is not quite there yet. I should perhaps give it another go.
See: https://www.dropboxforum.com/t5/Error-messages/Dropbox-clien...
https://www.dropbox.com/help/desktop-web/system-requirements...
I've around 70 servers with syncthing on them and i am using it with Route53 for use as CDN.
One thing i am missing is that, i want to sync in a way that it's aware of the network topology and syncs from the nearest network first.
The downside is that all your data lives on every server.
Is there a smart way to sync only needed data using p2p for CDN application?
Yesterday I installed it again on my main PC (part of a migration from a different linux distro) and I was impressed: The notifications when adding new devices arrived with a very small delay, syncing just worked, file monitoring is now built in, the error message related to that (inotify limit) was helpful.
Syncthing came a long way and is great software, congrats for reaching 1.0!