Yeah, but that is gone if you literally forget it.

Problem is you need a way to decrypt that shit with memory loss and a burned down house.

I recently started a “backup ring” with my buddies who have their own servers too. It’s just folders synced over sync thing, each has their own folder, and we put stuff there that we want to access even in case everything I own burns out. Works pretty well so far.

If you want DNS only in your LAN, you need to self host a DNS server and register this domain locally (by putting it in some config file of yours)

Audiobookshelf is insanely good. It’s almost a perfect application. Seemingly it does ebooks too, but I haven’t used that yet.

Just use the god damn browser

TeamSpeak exists too

There are dozens of us?

I use synphonium with my jellying server, works just fine.

deleted by creator

I found open-ssl to be much harder to use. Do you just manually make new certificates with the CA in CLI?

At some point it’s good to let things die

In that case, i recommend step-ca, which is a certificate authority server with acme support anyone can self host. The setup took a while but it’s been running for months now without problems for me.

No proper CA should give out a certificate for an IP, that’s a no go by the common rules.

The background is that certificate revocation is a broken system and having short lived certificates makes the problem go away. You don’t need to worry about how to tell people that some certificate is bad if it’s only valid for a few days.

Ideally, certificates would only be valid for a few days, it should be automated anyway. This has other downsides as I can imagine, like creation of more traffic. My self signed CA for my home LAN has 4 days as standard, and it works perfectly fine.

While true I feel like your comment misses the point. A raspberry pi is just a computer, not a magic solution box that’s kept maintained and updated by some guy. Their product isn’t a service, it’s just the device.

It’s a hard fork by now, but the switch should still be pretty painless.

In what way? Works for me

Forgejo actions is basically GitHub actions. The difference in my ci scripts is a single line and you can even use GitHub action templates or whatever they’re called.

You just need to add some runners to your server, which is pretty easily doable by just using some docker container and deploying that multiple times

You can set A DNS entries without wildcard in the configs (with head scale at least), just use their magic DNS thing that works with hostnames or just self host DNS and tell your tailnet to use that.