Fair enough. Well, you definitely should be moving those over to Docker then, it’ll be much better for efficient use of resources.

Curious as to why you don’t just run those as separate games on the same server, since Foundry has the functionality for that?

Either way, running Foundry in docker is a solid idea. I’ll grab a link to the image I use when I get the chance.

Also, why two Foundry servers?

You definitely wouldn’t want to use them in any kind of RAID for a start.

Yeah, try to avoid using USB hard drives.

A refurbished business PC is an excellent choice (or, better yet, make friends with someone who works in an IT department and grab a few machines when they’re being thrown out; you’d be amazed how often companies dump perfectly good hardware). Don’t worry about the windows license, you’re not actually paying for it by the time you get to refurb prices.

You should easily be able to pick up something decent for under $200 (hopefully that fits your budget). If you go with a small form factor (not ultra small) you can probably get an SSD and two 3.5" drives in there (watch out for the small form factor Lenovos though, they only have one 3.5" slot). Alternatively, look for a larger desktop tower style that could have 3 or 4 drive bays if you want to do something like a RAID5.

Don’t sweat too much about buying older hardware. What’s old and busted for Windows is lightning fast when we’re talking about self-hosting a file server or a Pihole.

I love 1Password, they’re great (I personally use Bitwarden for my passwords, but would happily recommend either of them). But by putting both your authenticator codes and your passwords in the same place, you now have a single point of failure. What happens if someone finds an exploit in 1Password that gives them access to your account? The whole point of 2FA is to not have a single point of failure.

That’s still a single point of failure. What happens if someone finds an exploit that bypasses the login process entirely?

That seems like it defeats the “2” part of 2FA. If your password manager is compromised the attackers now how complete access.

Ah. Whoosh on me I guess.

Wait, wut?

Important note; some WD Reds are still SMR. You have to check which specific type.

Awsome resource. You win the Internet today.

For the record, so are a lot of 3.5s. Always read up on your drives before buying.

Get to grips with Docker. OCI containers are the standard method of self hosting basically everything now, so once you’re comfortable with Docker and compose files, literally anything you could want to host is available as a drop in component for your system.

An excellent way of playing around with Docker is to install Dockge. It’s a web UI with some really helpful features. First, it can convert Docker Run commands into compose files for you (once you start to play around with this it’ll be clear why that matters), and second, its very good at pointing out where and how you’ve made errors in your compose files. But most importantly, unlike Portainer (the most popular Docker UI) it works with the Docker command line rather than trying to replace it. With Dockge you know exactly where all of your files are and if any part of your setup breaks you can repair it very easily. It also doesn’t have Portainer’s problem of flashing error messages on the screen for 0.3 seconds then whisking them away. It exposes the entire Docker terminal output so your debugging process is much, much easier.

You’ll also want to learn about reverse proxies (I reccomend Caddy for its unbelievably simple config file; an entire site is three lines). These are really important for serving multiple different services from one source.

For anything that you can’t run in Docker, VMs are an acceptable solution, and LXC containers are a better solution, but one that requires a little more work to get to grips with (fun fact, LXC has its own web UI, which is fantastic, but almost nobody seems to even know it exists). Since you’re already familiar with Linux, you may want to ignore the suggestion to use Proxmox and just set up a server with your preferred flavour and go from there. All of this can be done with any modern Linux distro, so you might as well work in an environment you’re comfortable in.

You are correct, left hand is a fork bomb. Specifically, it creates and then runs a function named “:”. What this function does is pipe its output into itself while running in a background process, which instantly spawns infinite copies of itself. Technically I believe the : character could be any character as its just a name. The creator just picked a colon for aesthetics.

Found the person who’s never used tar :-P

Yeah, what kind of idiot doesn’t parallelize their timer function.

… aaaaaand you’ve killed us all.

Yeah, general practice is to either elevate privelige by switching accounts, or by using sudo. Having both just increases your attack surface to no practical benefit (especially since you can technically still switch to a root account with “sudo - i” even if you’re going the sudo route).

You did. If you leave your root password blank it’ll automatically add the user account you create in the following step to sudo and disable the root account.

If you want to have both a root account and a user account with sudo, you’ll have to do that manually, but that’s a pretty unusual setup.