Walk in, press on button, hang up jacket and get stuff out of bag, type in password, grab coffee.

That’s a pretty common morning pattern I see.

If it’s only you (or your household) that is accessing the services then something like hosting a tailscale VPN is a relatively user friendly and safe way to set-up remote access.

If not, then you’d probably want to either use the aforementioned Cloudflare tunnels, or set up a reverse proxy container (nginx proxy manager is quite nice for this as it also handles certs and stuff for you). Then port forward ports 80 and 443 to the server (or container if you give it a separate IP). This can be done in your router.

In terms of domain set-up. I’ve always found subdomains (homeassistant.domain.com) to be way less of a hassle compared to directories (domain.com/homeassistant) since the latter may need additional config on the application end.

Get a cheap domain at like Cloudflare and use CNAME records that point domain.com and *.domain.com to your dyndns host. Iirc there’s also some routers/containers that can do ddns with Cloudflare directly, so that might be worth a quick check too.

Guess I’m a bit too young for that still lol. We got a pair of ISDN2 lines in 1994 (so technically also 256k lol) at home, but I was too young to remember that. With cable internet coming in 97, that was technically still slower than bonded isdn at the very start.

In a way I was very privileged growing up when it came to Internet. My dad’s company at the time paid good money to get all the latest (often testing phase) stuff to his house in return for being available 24/7.

Talking about Lan uplinks, in the early 2010’s I had the joy of working with a 20gb uplink at a small university LAN (the sysadmin got a good amount of free pizza and beers for that one). I spent a large amount of my savings on a 10gb NIC only to find out my hard drive couldn’t keep up lol.

There’s a couple SD-WAN solutions out there that you can do this with. Essentially route all your traffic through one or more VPSes while still keeping things like port forwards and STUN working properly.

I’ve had to use it to enable proper video feeds to and from people that had Spectrum as their ISP.

Practically all bikes in the Netherlands still look like that today. They’re a tool to get you from A to B and this design has proven very reliable for that.

U-locks for bikes are a rarity as well. Basically all bikes have a lock built-in, that you optionally pair with a chain if you park it somewhere deemed unsafe.

We have a bunch of torrent compacts at work and they’re honestly great cases too. Also very good at keeping high end parts cool at a low noise level.

I’ve always been a fan of closed Fractal cases. They do no-non sense right.

What kind of storage usage can I expect from running this? I would also assume that the database would heavily prefer solid state storage?

Edit: the author answered that question here already: https://lemmy.world/comment/4148270

You essentially pay for convenience. If there was a streaming service that had everything I would gladly pay good money for it, since there isn't, I have to curate my own library instead.

Having good indexers/Usenet providers and automations takes away a lot, if not all the time needed to hunt down good releases. That saved time and hassle is what's worth the ~100/year for me.

For some reason every registrars dns panel has its own weird restrictions, bugs and interface quirks. Pointing the nameservers to Cloudflare at least makes for a consistent experience.