traches

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 configuration
• security
• dependency management is solved

Stick with the containers

Oh nice! I’m stoked about the background sidecar operations, that will speed things up considerably

Sqlite compiles to wasm, you can run it in the browser

Thanks! I’m perfectly capable of both. They say cringing at your former self is a sign of growth

Honest answer? When trump said “Take the guns away first, due process later.” I was a pretty big gun nut at the time and it felt like a slap in the face. Shortly afterwards I encountered a YouTube video that actually explained the science behind climate change in a way that made it obviously true and that I hadn’t encountered before. The conservative worldview is a house of cards, once you take out a couple the whole thing falls apart pretty quickly.

Now I’m a very progressive atheist and more than a little ashamed of my former self. Still like guns, but I keep that to myself

Yeah, I wish he’d go back to being the greenhouse on mars guy

i used to be a republican so

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