NAS at the parents’ house. Restic nightly job, with some plumbing scripts to automate it sensibly.

Got a 3 year old kid with another on the way. I just need it to be reliable so the kid can watch Sesame Street and the lights keep working.

You can go a lot higher than 1000 without optimizing for UPS, they’ve made a lot of performance improvements over the years. Highly hardware dependent, of course

Which is why it’s a bottom tier private tracker

Edit: it’s actually not that bad but the rars are annoying and they should stop.

Private trackers tend to be more curated and better organized. Decent filenames, consistent organization and quality, correct metadata, no missing episodes or tracks, no RAR files, etc

I definitely see your point, but the difference is that it’s one thing to learn. Once you know docker, you can deploy and manage anything.

Cons of containers are slightly worse disk and memory consumption.

Pros:

• ease of installation
• declarative, consistent configuration
• security some degree of sandboxing
• dependency management is solved

Stick with the containers

but there is a reason i just explained it to you

Ok but is there room for the idea that your intuitions are incorrect? Plenty of things in the world are counter-intuitive. ‘docker-compose up -d’ works the same whether it’s one container or fifty.

Computer resources are measured in bits and clock cycles, not the number of containers and volumes. It’s entirely possible (even likely) that an all-in-one container will be more resource-heavy than the same services split across multiple containers. Logging from an all-in-one will be a jumbled mess, troubleshooting issues or making changes will be annoying, it’s worse in every way except the length of output from ‘docker ps’

I can see why editing config files is annoying, but why exactly are two services and volumes in a docker-compose file any more difficult to manage than one?

I disagree with pretty much all of this, you are trading maintainability and security for easy setup. Providing a docker-compose file accomplishes the same thing without the sacrifice

• separate volumes for configuration, data, and cache because I might want to put them in different places and use different backup strategies. Config and db on SSD, large data on spinning rust, for example.
• separate container for the database because the official database images are guaranteed to be better maintained than whatever every random project includes in their image
• separate networks because putting your reverse proxy on a different network from your database is just prudent

Liberal here, there is definitely a 2 tiered justice system in the US what are you even talking about

Our disagreement is over the idea that somehow the billionaire with an army of lawyers, who appointed half the judges his cases are in front of, and has been given every conceivable affordance and courtesy, is anywhere other than the top of the privileged tier.

Seems fine, but you’re sorta hitting two fields at once. Application development (coding) is a different skill set from devops/deployment (docker). I’d stay pretty surface level on docker and the CLI for now and focus on building your app. You’ll know when you need to go off and learn those things.

the fuck is a chegg?

Yeah, I tried it but that experience isn’t as good as a native app. No swipe gestures, and an extremely basic UI

Miniflux has served me very well for years, combined with a few different apps. Reeder on iOS, I can’t remember what I used on android but there were plenty of options

With AMD it’ll just work

Which is why we stopped using “gay” as a pejorative a long time ago?

So there’s a storage protocol called “S3” (I wanna say it stands for simple scalable storage?), first created by Amazon for AWS. Many types of software, including backup programs, have been designed to use it as a storage backend. There are now many S3 compatible providers, last I looked the best value was backblaze B2.

You need a backup program with end-to-end encryption, S3 compatibility, and whatever other features you like. I use restic but it’s CLI only, there’s also borg backup and many others.

If you encrypt locally with a good key, you don’t have to trust the remote storage provider. They just see a bunch of meaningless noise. Just don’t lose the key or your backup is useless.

At first glance I thought it said “extremist kinks”