I have been using it for the last 3 months to expose services from my home internet (plex, wireguard, etc.) through a VPS and I’m pretty happy with it. It’s relatively simple to set up, I haven’t had any outages so far, and it’s nice that it supports UDP port forwarding as well as TCP (for wireguard).
You could go even further and use hard links. That way, you can have two paths pointing to the same data on the partition, with the space getting cleaned up only after all references to it are removed.
As another German, I can confirm that the “first e in mesmer” way is how Germans would pronounce it. See for example 11seconds into this German video also officially from SUSE’s YouTube channel - a SUSE employee and German native speaker who is moderating a series of talks is using that pronunciation.
It’s just a tiny mistake that most Germans are used to hearing Americans make all the time (see also Porsche which is also not pronounced porsh, nor por-shay, but porsh-eh) and will politely ignore, but since this aims to be an educational video, should be pointed out to be slightly incorrect
Hey URL, go and fetch your friend JSON!
Makes perfect sense.
I’m pretty happy with Digital Ocean if I need a temporary VPS because I can pay by the minute and the UI is great. Anything that I want to stay alive for more than a month or two, I do on a single 6-core VPS rented long-term from Netcup, a low-cost German provider, deploying with Docker and Traefik.
This will work in general. One point of improvement: right now, if the request fails, the panic will cause your whole program to crash. You could change your function to return a
Result<Html, SomeErrorType>instead, and handle errors more gracefully in the place where your function is called (e.g. ignoring pages that returned an error and continuing with the rest).Look into anyhow for an easy to use error handling crate, allowing you to return an
anyhow::Result<Html>