The trickier part here his connecting your domain to your raspberry pi and allowing the big internet to access it. You have a few options:

• Set up dynamic DNS to direct your domain name to your (presumably dynamic) home IP address. Assign the rpi a static IP address on your home network. Forward ports 80 and 443 to that address. The world knows your home IP address, and you’re dependent on your router for security. No spam or DDOS protection.
• Use a service such as cloudflare tunnel. You’re dependent on cloudflare or whoever, but it’s an easier config, you don’t need to open ports in your firewall, and your home IP address is not public. (I recommend this option.)

Either way, don’t forget to set up HTTPS. If you aren’t dead-set on using nginx, caddyserver does this entirely automatically.

I’ve been using caddyserver for awhile and love it. Config is nicely readable and the defaults are very good.

If encryption is enabled, don’t worry about it. Otherwise ‘dd if=/dev/zero of=definitely-the-bad-drive-do-not-fuck-this-up bs=4M’

Agreed, that should be many tens of pages not one. Also the mobile layout isn’t very good. I think it’s important to remember that normies use their phones for almost everything.

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.

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

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.

We all have every vaccine you can get. It’s possible I’m misremembering exactly what disease it was, but I promise you that a single instance of our kid in a ball pit ruined a vacation for two families.

Ballpits encourage contact with eyes, mouth, and nose, then spread it all around over the balls. They are especially difficult to clean. It would be difficult to design a better disease transmission vector if you were trying.

Speaking as a parent with a horrible experience involving rotavirus:

NEVER, under ANY circumstances should you allow your kid into a ball pit. Just fucking don’t, they are gross and your whole family will puke and shit for days.

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

It’s the only time normies encounter the word.

How do you feel about crypto?

They don’t have to, algorithms do whatever they are designed to do. Long division is an algorithm.

Profit motives are the issue here.