Use something like Backblaze or Hetzner storage boxes for off-site backups. There are a number of tools for making this painless, so pick your favorite. If you have the means, I recommend doing a disaster recovery scenario every so often (i.e. disconnect existing drives, reinstall the OS, and load everything from remote backup).

Generally speaking, follow the 3-2-1 rule:

• 3 copies of everything on
• 2 different types of media with
• 1 copy off site (at least)

For your situation, this could be:

• 3 copies - your computer (NVMe?), TrueNas (HDD?), off-site backup; ideally have a third local device (second computer?)
• 2 media - NVMe and HDD
• 1 copy off site - Backblaze, Hetzner, etc

You could rent a cloud server, but it’ll be a lot more expensive vs just renting storage.

All of them? Maybe an international consortium that pays devs in their home currency.

I think there could be more to it. Louis Rossmann had personal issues with the lead dev there a year or two ago due to how they interact in their forum, and I think he had some great reasons to be concerned. Since then the lead dev has stepped away as project lead, but I doubt the bad blood is completely gone.

I think it’s a bit suspicious that they don’t mention what feature(s) FUTO wanted. Given their interaction with other projects, I’m guessing they wanted a “supporter” badge for people who have bought the software (no change in functionality other than the badge). I’m guessing also that due to their interaction with Rossmann, they’re uninterested in clarifying, esp. if it would put FUTO in a better light if they did.

Then again, maybe FUTO is a bunch of scumbags. It just seems the slant against them is so much stronger than the actual negative impact from a handful of repos having source-available licenses instead of FOSS licenses.

My read is that FUTO as a software movement is totally fine, it does what it claims on the tin. The people behind FUTO are a different story, and the main person bankrolling it seems to have friends with odd views (I think they’re blown out of proportion, but they’re still concerning).

You’ll never find a perfect movement. Here’s what FUTO seems to prioritize:

• local first alternatives to big tech
• source availability, but in a way big tech can’t use but home users can
• profitability for devs without coercion or feature gates

That sounds pretty good to me! I’d prefer it to be FOSS, but allowing me to distribute modifications for non-commercial use is probably good enough for most things.

I probably disagree with their founder politically, and I’d run FUTO differently, but I think their software is good and I could maintain it myself if needed, and at the end of the day, that’s what matters to me.

FUTO doesn’t seem interested in getting involved in politics, they’re merely musing philosophically, and their products aren’t profitable, so it doesn’t really matter to me what their political positions are.

Privacy guides is the forked project by the original contributors.

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.

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.