Hi there. I started using syncthing a few months ago, thank you for a great piece of software.
My use-case is to run a bridged VPN (openvpn) between a few sites and have nodes on each site that replicate users and common data directories. For now the architecture is a star but we could go p2p in the future.
The satellite sites are running all (?) the required services on a Pi 3 dropped on some local network. The user owning the common data is the same on all nodes. Some users have local accounts on more than 1 node.
Re: syncthing, I came to set it up without any master folders nor .stignores. This is slightly risky and a bit sub-optimal (at the main site and contrary to all satellites storage is nfs-mounted; client machines are Apple macs dropping hidden files everywhere) but conflicts are almost non-existent in this configuration. I will mention here that I love the “limitBandwidthInLAN” option.
Problem, I started cloning my Pi 3 software image on new instances. And I was severely bitten when putting a new node online without having generated a new machine ID. Basically, most files disappeared from the shared folders, but I was lucky enough to have one node offline and could recover. I will display my stupidity and inconsequence here, but this near-disaster happened to me … twice. The 1st time, I had no idea what happened, restored data and left it at that. The second time I saw a hostname being recognized as another one, and from there I went on to investigate the Machine ID concept.
To save the hide of dummies like me I would suggest adding a big warning about the risk of cloning machines/accounts. Or perhaps tie/verify Machine ID against host characteristics, like a MAC address or hostname?
Anyways. Thanks a lot to all the devs and contributors who made syncthing what it is. I can’t wait to see what’s next.