Sergey Kozharinov

It doesn’t make a lot of sense for LetsEncrypt to spend time adding support for such certs, since both a domain name and a cert from another CA are cheaper than buying an IPv4 block

certificates can only be obtained for domain names

That is not true, nothing prevents it on the technical side, and even some trusted CAs sell them under certain conditions

This comment is posted through my personal private instance :)

• email - postfix, dovecot, roundcube (mostly unused), rspamd
• vpn - firezone for managing wireguard, v2ray
• web analytics - offen
• password manager - vaultwarden
• status monitor - uptime-kuma
• cloud - nextcloud
• music streaming - navidrome
• seedbox - qbittorrent with vuetorrent webui
• media streaming - jellyfin
• docker container registry
• firefox sync server
• lemmy instance

Their clunky and unpleasant Ui, but mainly this

A series of VPSes running AlmaLinux, I have a relatively big Ansible playbook to setup everything after the server goes online. The idea is that I can at any time scrape the server off, install an OS, put in all the persistent data (Docker volumes and /srv partition with all the heavy data), and run a playbok.

Docker Compose for services, last time I checked Podman, podman-compose didn’t work properly, and learning a new orchestration tool would take an unjustifiable amount of time.

I try to avoid shell scripts as much as possible because they are hard to write in such a way so that they handle all possible scenarios, they are difficult to debug, and they can make a mess when not done properly. Premade scripts are usually the big offenders here, and they are I nice way to leave you without a single clue how the stuff they set up works.

I don’t have a selfhosting addiction.

I would recommend Porkbun, been using it for almost 1.5 years after I had to migrate from Namecheap. Wouldn’t really recommend the latter

The check $LEMMY_HOSTNAME == http* will give a false positive if (for whatever reason) the domain name starts with http