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)

I’d never heard of VPSs prohibiting any specific use case; I have 3 restic repos on my VPS and have had them for close to 6 years now (well, borg until early this year, now restic, but it’s the same principle).

I’ve looked through all the server types in https://www.hetzner.com/legal/system-policies (my VPS provider) and I can’t find anything about not using for data backup.

(They only prohibit: crypto mining, IP address scanning, changing the MAC address, and using fake source IPs.)

if the message itself is not important/sensitive, or can be suitably obfuscated without loss, use ntfy.sh

• pick a word. Let’s say you pick Quei3Oju
• install ntfy.sh app on your phone, and subscribe to the channel Quei3Oju
• send messages from the server using curl -d "Backup successful" ntfy.sh/Quei3Oju

no passwords, no secrets. Risk: anyone who knows that word (or the operator of ntfy.sh) can see your messages. Hence why the point about sensitivity of the message itself

Edit 1: this is literally the main example if you browse to ntfy.sh :)

Edit 2: what a coincidence; I just saw this thread: https://old.reddit.com/r/selfhosted/comments/17ke5ax/ntfy_is_a_great_tool_what_do_you_use_it_for/ in the same sub!

use filebrowser and manually revoke access when you want

or use transfer.sh – the URL itself is randomised, so it kinda sorta “if you squint” acts like a password, and it autodeletes after a set time (which you can configure)