I guess my response would be that I don’t know what I’d be missing, because I don’t know enough to know what I should know.
There is a quote that goes something like “There are things we know, things we don’t know, things we know that we don’t know, and things that we don’t know we don’t know.”
For example, I’ve been “lurking” in the forums, trying to see what I might learn before I started using Syncthing. Just the other day I noticed this comment in the thread Helping first sync by manual copy:
Always make sure that if you add many files to a folder that is used by Syncthing, that the folders are either paused or Syncthing is not running. Then run rescan.
That caught my attention because it goes counter to what I would have expected, namely, that the best way to make sure the Syncthing is up-to-date is to make sure that it’s running when a large change is made.
I’m not sure why the above advice was given, whether it’s a work-around for a bug/glitch/performance issue, or whether the “rescan” feature is just more effective at dealing with this particular issue. (I suppose another possibility is that the advice given is not something that everyone agrees on.)
What happens if you add a lot of files to a folder that Syncthing is actively monitoring and don’t know to use the “pause/rescan” option? Will it fail? Will it miss some files? Or will it just be slow and take a lot of CPU while it catches up?
That seemed particularly useful information when setting up a new folder, which I was about to do, and it’s also not something I feel like I would have known if I hadn’t just happened to see it on the forums.
That’s just one example, of course. I have no idea what other “good pieces of advice” aka “best practices” might be out there.
That’s sort of where I was coming from. I guess it’s the next step beyond I understand the basics of setting up basic sync.
What are some things that people who use Syncthing might say “Here are some things/tips/tricks/suggestions that are good to know when you’re getting started.”