3 ms·

He's exactly the same as the other guy. Under the guise of modernisation, he's introducing even more technical debt and gratuitous overcomplexity. Look at it

by rleigh 7y ago

He's exactly the same as the other guy. Under the guise of modernisation, he's introducing even more technical debt and gratuitous overcomplexity. Look at it this way. In 15 years time, that ancient docker setup may well be as insecure, unmaintainable and poorly-regarded as PHP5 is today. And another generation of admins and developers will repeat the cycle all over again with the new hotness of day.

johnchristopher 7y ago
> Look at it this way. In 15 years time, that ancient docker setup may well be as insecure, unmaintainable and poorly-regarded as PHP5 is today. Surprise, surprise, when you don't maintain and update your stack it becomes unmaintainable and insecure. News at 11. Why the heck are you implying that updating it now means we don't manage and update it for the next 15 years ? What do you suggest, then ? Keep things as is ? I remind you that the thing is insecure as fuck and it becomes hard to add features or patch the app because it's running on an old version of apache/php/mysql.
neurostimulant 7y ago
Actually, php with docker is really nice and simpler compared to the old "install Apache/nginx to your server" method. Upgrading is easy, just pull new images and restart the containers. Horizontal scaling is also a lot easier using stuff like glusterfs as volume driver. It even easier if your app is modern and don't need ability to self-modify source code as you don't need fancy volume driver. If you decide to drop dockerized setup in the future, I imagine it should be easy to do so as all you need is move the source code to the new host, is it not?
k__ 7y ago
I didn't even think about the missing updates in the future when I wrote my comment. It just all sounded to me like someone hating at one dude who did crappy development and then tries to solve that problem with Docker instead of a process. In my eyes, Docker is the epitome of crappy development. "Oh we don't care anymore, we just throw all into a container and be done with it."
- johnchristopher 7y ago
  > In my eyes, Docker is the epitome of crappy development. "Oh we don't care anymore, we just throw all into a container and be done with it." That's actually the plan. We need to keep it running in legacy mode until the updated and patched version of the app is ready to be deployed. Main org IT don't want EOL and unsupported pieces in its infra anymore unless it can isolate it. Next version is going to be service based and scalable. A WAMP installation can't do that. Am I being trolled ? Because I don't see the people bashing docker or glorifying the values of an insecure but simple setup giving alternatives. What should we do then ?
  - k__ 7y ago
    Maybe you found one of the few good reasons to use Docker, I don't know. I just have the impression, Docker is the way if people don't really want to think about a solution.

by rleigh 7y ago

johnchristopher 7y ago

> Look at it this way. In 15 years time, that ancient docker setup may well be as insecure, unmaintainable and poorly-regarded as PHP5 is today. Surprise, surprise, when you don't maintain and update your stack it becomes unmaintainable and insecure. News at 11. Why the heck are you implying that updating it now means we don't manage and update it for the next 15 years ? What do you suggest, then ? Keep things as is ? I remind you that the thing is insecure as fuck and it becomes hard to add features or patch the app because it's running on an old version of apache/php/mysql.

neurostimulant 7y ago

Actually, php with docker is really nice and simpler compared to the old "install Apache/nginx to your server" method. Upgrading is easy, just pull new images and restart the containers. Horizontal scaling is also a lot easier using stuff like glusterfs as volume driver. It even easier if your app is modern and don't need ability to self-modify source code as you don't need fancy volume driver. If you decide to drop dockerized setup in the future, I imagine it should be easy to do so as all you need is move the source code to the new host, is it not?

k__ 7y ago

I didn't even think about the missing updates in the future when I wrote my comment. It just all sounded to me like someone hating at one dude who did crappy development and then tries to solve that problem with Docker instead of a process. In my eyes, Docker is the epitome of crappy development. "Oh we don't care anymore, we just throw all into a container and be done with it."

johnchristopher 7y ago
> In my eyes, Docker is the epitome of crappy development. "Oh we don't care anymore, we just throw all into a container and be done with it." That's actually the plan. We need to keep it running in legacy mode until the updated and patched version of the app is ready to be deployed. Main org IT don't want EOL and unsupported pieces in its infra anymore unless it can isolate it. Next version is going to be service based and scalable. A WAMP installation can't do that. Am I being trolled ? Because I don't see the people bashing docker or glorifying the values of an insecure but simple setup giving alternatives. What should we do then ?
- k__ 7y ago
  Maybe you found one of the few good reasons to use Docker, I don't know. I just have the impression, Docker is the way if people don't really want to think about a solution.