deduplicating is fine, the question is what it will do on a restore.

As far as I can tell from searching the web, duplicacy will restore two (or more) hard linked files as separate files. (Apart from the obvious one of losing the connection, your restore directory takes more space than the original).

Restic (again searching, but this I can probably test since I use restic) will restore them properly – i.e., preserving the hard link

The tutorials section is very basic; I am not talking at that level. The patterns page is closer to the level of complexity that one needs help with, and it does cover several items, but you have 30-40 directives, many with several options, global options, and so on, so there’re bound to be gaps.

In the other comment you said this is “90% of the feedback we get”, and I can certainly understand the frustration – people want documentation to magically solve their specific problem quickly, without having to read anything extraneous to it, which is clearly impossible.

As I said before, I’ll keep it in mind next time I need to do something if I can’t find it easily in the docs I’ll at least highlight the effort it took, what I searched/read/found, etc., so you have something concrete.

Spot on.

Of course from their point of view that’s “not helpful”. Maybe I’ll spend some time looking at it to come up with something, if I have time.

at the moment my caddy setup is stable; I am recounting my experience from memory.

It may be useful to consider what I said in a broader perspective – i.e., what you have is an excellent reference but it does not help discovery of task-oriented solutions.

Sorry I am unable to express the problem better than that. Will keep an eye out in future if I can get more concrete and open an issue or something.

Totally agree.

The main problem is it’s all written as a reference – for people who already understand what/how, who need to just refresh their memory of the actual syntax.

There’s very little explanatory stuff for people who need more than that. I had to read the same stuff multiple times, traversing many (or often, the same!) links, make notes, and then form a mental picture of what is going on.

I suspect you’re either reacting to the “Tom” (which is what the T in TOML stands for), making it sound like some “one guy’s” project that never really took off…

…or the fact that it reminds you of the Windows INI file format. (TBH, git’s config file also uses something that reminds me of Windows INI, and it took me a while to get over it)