My instance has one.

Privacy guides is the forked project by the original contributors.

Sounds like incompetence to me. Cross platform networking code is tricky, but there are also copious libraries for this to the point where it’s a solved problem.

Why does it need to be 64-bit? Does it really need to address more RAM to launch games?

My vote is Podman with an immutable distro, like OpenSUSE MicroOS or Fedora Silverblue. Here are my reasons:

• rolling base, with very minimal footprint, so you don’t need to worry about upgrades
• podman runs proper rootless containers, so you get better security vs docker, which tends to run as root (breaking out does less damage if you manage permissions properly)
• deploying a new service (or moving a service) just means copying configs and running, no concerns about what the host has
• there’s nothing special about the host, so if MicroOS or Silverblue are abandoned, just copy the configs and data to a new host

It’s a little more work to set up, but once things are running, it’s drama free. And I think that’s the best thing to optimize for, keeping things boring is a good thing.

Idk, I explicitly set up Postgres, which took extra work since the default is SQLite. I use Postgres for my day job, so it makes sense to me to keep everything the same.

I use Postgres, because MySQL touched me inappropriately as a kid and MariaDB is too similar. Oh, and also because it’s what I use at work.

If you need to fix something, you should know what it is.

Yes, it’s possible to screw it up, but most people seem to be really nervous about screwing it up and don’t screw it up. There are plenty of tutorials and whatnot on PC building that you can follow, and they’ll tell you when you need to be careful (mostly just the CPU and PCIe cards like GPUs).

The average person will be fine if they do some amount of basic research. A modern PC only has like 6 parts anyway (motherboard, RAM, CPU, GPU, storage, and PSU), so there are only so many ways to get the wrong parts or something (mostly just mobo/CPU/RAM combo, which you can usually buy in a bundle). You don’t have to know what everything does, you just need to be able to follow detailed instructions, which the motherboard will provide.

No prob! Glad you got it to work, permissions can be a huge pain.

Passing that in basically overrides the [USER field in the Dockerfile](docker run -it --user $UID:$GID). Make sure that user/group combo has access to the render device.

Basically this:

docker run -it --user $UID:$GID

Pass it a user and group that have the appropriate access, and no more. You can also set this in Docker compose or whatever other abstraction you’re using.

This is totally fine for testing, but there are almost always better solutions.

And you can map internal users to external users. This isn’t as common with Docker since things tend to run as root, so maybe look up Podman docs where it’s more common since it’s whole schtick is running with minimal permissions.

I guess we have different ideas of what “enterprise tools” means. At the company I work at, we use Docker and Kubernetes on AWS ECS. Everything is in the cloud so there’s no hardware for something like Proxmox to abstract over, just Docker hosts running Docker containers.

That’s what I’m familiar with, and Docker containers are really well documented for a lot of services, so it made a ton of sense for me to start there. I think LXCs and VMs encourage the same types of bad behaviors that can complicate maintenance, whereas Docker containers encourage good behaviors that simplify maintenance (specifically one app per container). LXCs and VMs have their place, but I’m convinced Docker/Podman containers are the best default choice.

We also use waiter/waitress, maître d’, and sometimes steward/stewardess (esp. on airplanes). There’s technically a difference:

• waiter/waitress - brings food
• server - person the customer interacts with (i.e. takes orders)
• maître d’ (hotel) - head of wait staff
• steward/stewardess - serving customers is usually a secondary duty

I think “server” has become more popular because it’s gender neutral, but “waiter/waitress” is still quite common and most don’t make the distinction between the two.

I personally like the overlap between computer server and restaurant server because both exist to provide things upon request. The term “wait” that “waiter” comes from is pretty archaic.

Yeah, Windows isn’t that bad, but it’s not that good either. On servers, everything requires a million clicks or some random terminal command that’s impossible to find documentation for (was just passed down from senior to junior over the ages). I had to configure one for testing (embedded product that needed to work in Windows environments as well as Linux), and it took hours to do the most basic task. Granted, none of us were sysadmins, just devs, but we weren’t familiar with Linux or Windows servers, just desktops, and Linux was by far easier to configure.

Don’t pick Windows for your server without a good reason, you’ll get much more value from learning Linux than Windows.

What’s wrong with “server”? They serve you food, much like a computer server serves files.

I think it’s much better than “waiter” (which we also use) because I want them to bring food, not wait.

Yup, that’s the form I’m familiar with. Most idioms avoid gender entirely.

Sure, Docker is more or less an abstraction layer on top of LXC. It’s the same tech underneath, just a different way of interacting with it.