along with the compose.yaml file, unless I need it in a different drive for any reason

btw, the prices of managed runners are going down, not increasing

https://docs.github.com/en/billing/reference/actions-runner-pricing#standard-github-hosted-runners

still good to have a self-hosted alternative though

ah right, my bad

fwiw, you can self host a GitHub actions runner

I’m the only user of my setup, but I configure docker compose stacks, use configs as bind mounts, and track everything in a git repo synchronized every now and then.

about the same specs as my TV, but 10" less and 4x its price

deleted by creator

deleted by creator

def possible, cloudflare DDoS their own dashboard a few months ago with some react code

https://blog.cloudflare.com/deep-dive-into-cloudflares-sept-12-dashboard-and-api-outage/

That’s the neat part: you don’t. If their idea of anti cheat means taking over my machine to scan everything that runs on it, it’s a lost battle. Either find a way to do it server side based on behavioral heuristics, or don’t bother.

sir, this is a wendy’s

“never trust the client” is pretty much a motto of infosec, idk what the hell game devs expect

I think you need something like restic with a retention policy

https://restic.readthedocs.io/en/stable/060_forget.html#removing-snapshots-according-to-a-policy

--keep-{hourly,daily,weekly,monthly,yearly}

other solutions that implement similar policies are kopia and rustic

the advantage of using an off the shelf solution is that it’s almost certainly more reliable than what anyone can come up with in a few hours, and, it works with incremental backups, so your space requirements are drastically reduced depending how often you run it.

Intel has some GPUs that are more cost effective than NVIDIA’s when it comes to VRAM.

Arc A770 is selling for $370 in the US, and the new B50 for $399, both with 16GB.

B60 has 24GB, but I’m not sure where to find it.

huh, I just adopted mkdocs in a project, glad they’re keeping the config backwards compatible for a while

everyday to once a month, depending how often I use the server

IME usually waiting longer to apply larger updates causes more issues than smaller and more frequent ones

lol the readme reads “a not so terrible” but the repo description reads like

A terrible web ui and RPC server for yt-dlp

yeah, I adopted it last year and I probably wouldn’t have picked it today. I’m glad that despite of that, in the end it’s just an S3 compatible storage and, thanks to that, it’s not too difficult to replace.

We do it for an immediate benefit not for some hypothetical apocalyptic scenario result of a half baked conspiracy theory.

It’s a bit like calling people who camp in the woods, fish, or rock climb “preppers” because these would be useful skills after the modern civilization.

this is one of the most misused templates