[ my public key: https://keybase.io/sigio; my proof: https://keybase.io/sigio/sigs/W-Ro0IScNveaQpMbvTlIuVZPOO8mUKYX6KwW60eXx-0 ]
meet.hn/city/51.9966792,4.5597397/South-Holland
You can even put it in a seperate zone (which I do) by using a CNAME for _acme-challenge.domain.tld.
I have it to a seperate subdomain, which is served by a seperate desec.io account, which is only used for this specific subdomain.
My setup is having a wildcard DNS record and a wildcard certificate for my 'home' domain. It has a fixed IP from my ISP, so you always end up on haproxy, which then forwards to individual ports/ip's in the internal network.
I can do filtering based on source-ip from there, so traffic from myself/internal will be allowed, and outside traffic (not from some allowlisted ip's) will get blocked.
ACME validation is done via DNS, so nothing needs to be accessable for that to issue certificates. Internally I will usually also use the public IP for services, so no need for a split-dns.
I'd love to see more OpenWRT hardware that was capable of 2x2.5, 2x5 or 2x10gbit without any wifi, preferably in a case that can be rackmounted without too much trouble (so keeping it under 1U height). I'm currently running a stack of Zyxel T5600's, which are quite capable arm64 openwrt boxes. Those in a rackmount but with sodimm support or in 8+GB ram versions (and some sata/nvme storage, USB3) would be amazing.
That, or the massive lightning that's going through the region, (due to the heatwave). Since it's quite late at night, heat wouldn't be my first guess.
Don't know if this is a regression from before, since in the RHEL 5/6 days I used XFS filesystems as my default filesystem on large storage-pools. Since XFS doesn't have a shrink option, I would create filesystems of a few gigabytes in size, and grow them whenever needed. I mostly used them for monthly archiving of uploads to a customer's website, so there would be a YYYY-MM lvm volume with an XFS filesystem, and during the month it would be grown automatically from a cronjob if space got tight.
I'm quite sure I must have had a bunch of full filesystems there, and never ran into any crashing issues with full XFS filesystems (though these were not the 'root' filesystem). But even on my current laptop (with debian 12/13) I'm running XFS on all filesystems (besides /boot and /efi), and they report being full often enough without any crashes/reboots.
While it would be nice, I think this would instantly write-off the car in UK and western europe, as various connected features not working on cars that came with them, or are 'new enough' to require them, cause mandatory yearly tests (MOT / APK(NL)) to fail, meaning you can't legally drive the car again until these are fixed and re-tested.
Yeah, my main reason to stay away from Keepass, everything is in a single versioned binary file. I like 'passwordstore.org', where every secret is it's own gpg-encrypted textfile in a git repo. Every change is a commit, easy to see history, easy to revert or know which version is newest. And easy to selfhost, you just need a place to git push/pull from.
Also worked for the dutch government for the last 5 years. All or most of the projects we did have been open-sourced on github over the years. Currently there are plans to move them to code.overheid.nl I think, though I no longer work there currently. (I was the github org-admin for the department)
Local government can quickly change that, if they get their act together. Here in the Hague, there's literally thousands of public chargers available on the city's residential streets. Coupled with the fact that the charging-price is city-mandated at a fixed rate (currently around 35ct/kwh), this gives a perfectly fine solution for most people. (I can charge at home, for 20ct/kwh currently, so that's even nicer)
That's why I only buy Thinkpads from the business/professional lines... Replaced the keyboard om my t480 for $24, and replacing it myself was a 2 minute job (2 screws, pop 2 connectors, replace, and put back together).