yeah

Mirror’s Edge Catalyst-ass computer (agree, it looks great!)

I don’t have any secrets in my config or a private key or anything and I’m currently running 4 servers from the same config (it used to be 8 or even more machines at some point even, including desktops).

But yes, it’s a multi-file config, it would be absolutely crazy to not split it up with how large it is.

The database store is in /var/lib/postgres. You can just connect that disk somewhere else and start the database using the same (important!) major release of Postgres. I think the major version number is in the folder name. Then do whatever from there.

It’s a thing in Bavaria as well. I’m trying to erase it from my vocabulary because I hate it too.

Very good post :)

I just about lost it at everything in this paragraph

The door creaked open. Guido van Rossum looked like the typical output of GNU Autotools. He introduced me to the only other survivor: Special DevOps Mikhail Molotov. “We lost Travis. We lost Jenkins…” Molotov lamented.

Oh really? Nice, that’s news to me. Last I checked (admittedly not recently) it needed a bunch of 32-bit libraries installed to even start the client.

Since we’re talking about Steam here for example, Valve have not even bothered to release a 64-bit x86 client, let alone Arm client, except for Mac.

Gentoo can do this with Portage sets. They’re essentially a more simple way of creating a meta package which just installs other packages. And you can also write config packages which installs configuration for other packages.

Hm, okay, that does sound like the real client IP will get lost and every connection will appear to come from the proxy then. It would be good if that were passed somehow. My current setup adds the X-Forwarded-For header for example.

Oh interesting, I’ll have to look into that. Is this with that “proxy protocol” I’ve seen mentioned? If not, does this preserve it pass through the client socket address?

Tbf, technically data is still decrypted at the reverse proxy and then re-encrypted. So if someone manages to reconfigure the proxy or read its memory somehow they could read traffic in plain text.

However then since they have to control the VPS, they could also get a new cert for that domain (at least the way I’ve configured it) even if it was passed as is to the real host via a tunnel and read the plaintext data that way, so I don’t think a tunnel protects against anything.

If someone manages to get root (!) access on this VPS it’s over either way.

Yes, you can just use a reverse proxy for IPv4 only and point it to the IPv6 upstream. That is what I do, with a separate DNS record which then combines the two. See the DNS records for id.knifepoint.net (CNAME), http.vineta.knifepoint.net (AAAA, A) and vineta.knifepoint.net (AAAA).

The reverse proxy config and certificate management is set up with NixOS, if it helps: https://git.dblsaiko.net/systems/tree/nixos/defaults/v4proxy.nix https://git.dblsaiko.net/systems/tree/nixos/modules/sys2x/v4proxy.nix

The experimental status is more about that not everything is implemented yet (not that everything can be implemented, for example due to HTML not being oriented around having multiple pages in a document), so you have to write a bit of raw HTML sometimes. This is an example of how raw HTML looks, it’s the shell for my webpage.

There’s experimental HTML support. I’m using Typst as a static site builder for my website.

Two different rDNS names, for stuff that uses it. For example if you want to run mail and an IRC bouncer under different domain names.

Lists with 100k items? Impressive. I can see how with a document like that it will run out of memory. Is it a stack overflow? You could try increasing the stack size in that case.

As a Typst enjoyer I have to say this isn’t it imo from a quick look at the readme. Typst’s mix of markup and code modes is excellently designed and a high bar for anything to beat, and this looks like it doesn’t come remotely close. (I do have to say, I also heavily dislike Markdown in general)