HAproxy is good at what it does but it’s only good at proxying and simple rules.

It's possible to write very complex rules/ACLs with HAproxy... stick-tables, ACLs with regexes on whatever HTTP header, source or destination ACLs, map files, geoblocking, lua scripting, load-balancing from round-robin to host header load balancing, dynamic backend servers provisionning through DNS... Not that you can't do it with Nginx (it started as a reverse-proxy before becoming a jack of all trades), nor that nginx isn't a great tool (it is!), but HAProxy can do very complex things too. It also follows the good ol' UNIX philosophy of "one program to do one thing and do it well" and thus doesn't try to be a webserver, hence why you need a webserver behind it to serve anything from static files to PHP/Python/whatever.

You're welcome! scratch and distroless are indeed basically the same thing, scratch being the 'official' docker minimal image while distroless is from google - as I'm more a Kubernetes user (at home and at work) than a Docker user, I tend to think about distroless first :) - my apologies if my comment was a bit confusing on this matter.

By the way, have fun experimenting with docker (or podman), it's interesting, widely used both in selfhosting and professional environments, and it's a great learning experience - and a good way to pass time during these long winter evenings :)

A bit late but you might want to have a look at docker multi-stage build documentation which does exactly what you did (start from a base image then copying stuff from it to your own image), something like that:

FROM someimage:sometag AS build
[do stuff]
FROM minimalimage:someothertag
COPY --from=build /some/file /some/other/file
[and so on]
USER somebody
CMD ["/path/somecommand"]

Which will simplify building new images against newer "build" image newer tags easier.

btw, you were quite creative on this one! You also might want to have a look at the distroless image, the goal being to only have the bare minimum to run your application in the image: your executable and its runtime dependencies.

Can confirm, recently installed it on a friends' dell G3 laptop and I was quite impressed to see that it recognized both the nvidia graphics card and the intel GPU without a hitch, and installed the nvidia proprietary driver directly from the live usb.

Then I installed it on my wife's mother thinkpad x260, because she was bored with Windows "getting in [her] way" (her words, not mine) and wanted to try something else (70 years old grandma, main usage is web browsing, mails, some accounting on LibreOffice Calc, Zoom with her friends and... that's all). Everything worked out of the box (well, the x260 is pretty standard by the way). I showed her how to upgrade, how to use her software, how to install or uninstall software from the package manager GUI, and how to use workspaces. She didn't call for help once, and, for the moment, when I ask her about it she's quite pleased with it.

I'm a Debian and OpenBSD guy but recently got a second hand thinkpad yoga X390 laptop and decided to give Pop a try on it. From touchscreen to touchpad gestures to automatic screen rotation in tent or tablet mode - everything works out of the box (except for the fingerprint reader, but well, we're used to that). Basically it's Ubuntu 22.04 LTS without the snap hassle and a recent kernel (6.4 right now). For what I tested it on, it's always been a pleasant experience.

Of course, YMMV, and I might as well go back to my trusty Debian Stable + flatpak setup if things goes awry but right now I'm quite impressed with what they've managed to do.

Kudos for mentionning powerDNS, it's an amazing software :)

One thing I love with powerDNS is the various backends available, notably the postgreSQL and mariaDB/mysql ones. Only the primary powerdns instance modifies the database records, the secondary instances just read from database (master or replicas). Thus, no real need for AXFR: as soon as you added/modified a record on the primary, the secondary pdns servers will see it in the database.

The pdnsutil CLI tool is also really convenient, and the powerDNS API is a godsend when you need to automatise stuff for thousands of domains and hundred of thousands of records. There's also a nice third-party webUI (powerdns-admin, docker image: pdnsadmin/pda-legacy). Bonus, Terraform does have a powerdns provider.

At work we use dnsdist (from powerDNS too) to load-balance between our powerdns instances (with caching!), and to filter out/rate-limit/temporary ban bad actors (dns laundering, records enumeration and such for example).

Not really, in my case it's just that I either access it from home or through VPN, so I don't need to expose it outside of my home and work networks.

I had the same problem with the kubernetes lemmy.ml community yesterday night, but this morning I was able to find it through the search and subscribe to it (although for the moment it seems quite calm to say the least :)). I'm probably wrong here, but the lemmy.ml staff posted an announcement stating it was quite overloaded with the influx of new users - maybe to keep things afloat they are rate-limiting some resource-hungry api calls?

edit: also, as @anthonyg just mentioned, it might also be a propagation time between instances - if I understand correctly the sdf lemmy instance is quite recent.