flabberghaster

flabberghaster wrote

this is assuming the only thing the server is running is linux apache mysql and php; but you'd just write your PHP code and create a package like an RPM or what have you, that deploys it to the right place, and your configs for the rest of things would also either be their own packages, or managed by some script or puppet.

It all depends i guess. I suppose it probably is much easier to manage if you just compose some images, than if you say "you gotta configure the machine" because if you can abstract away much of that stuff into containers then you're not stuck on one distro of linux, so i get why people use docker (which I call dorker btw).

3

flabberghaster wrote

I do think containers are a bandaid for having too many dependencies or a workaround for people who don't want to make their software easy to deploy. Like you shouldn't have to ship an entire inner OS with runtime and everything, it should just compile and run. Sometimes that's not feasible for valid reasons, but often it's a way to get away with having a bad release process or having your software too complicated to set up.

2

flabberghaster wrote

I worked with it like 8 years ago and didn't like it; that's just down to it being much less mature back then, and also me not wanting to learn it.

The OCI standard is pretty mature now and there's a lot better tooling. I should stop being a curmudgeon and learn how to use it to be honest, but i'm a grouch who likes to do things the old way.

3

flabberghaster wrote

you're not gonna like this but you have a mathematical mind and you'd be good at programming if you wanted to do it. I'm sorry to say this. But unfortunately your ability to break down a complex problem into the most basic version and work backwards from there is a very valuable skill.

3