"That's very rarely the thought process in the real world when you're dealing with a production system though. Most developers who have the seniority and experience to make the call to upgrade something aren't just upgrading for the fun of it."
you and i's experience varies greatly, Ive worked at a number of firms that update things based solely on age(and boredom) and nothing else... thats what happens when non-tech people steer the ship. I also see this happening a lot to justify someone existence on payroll.
Well there's your problem. Stop working for morons. :D
it wasn't always the morons in charge of biz, sometimes it's just bored morons in charge of things. bloat causes this.
Re:PHP 5 and 7.0 end of life
by parliament32 on Friday July 19, 2019 @03:07PM
(#20481565)
But that sounds exactly what GP is doing, "I am in the process of dockerizing almost everything in sight."
Why do you need Docker to run a WAMP server?
Re:PHP 5 and 7.0 end of life
by beatgammit on Saturday July 20, 2019 @11:48AM
(#20486432)
You don't need it, but it certainly helps you know what your environment is so you can upgrade/patch one piece at a time without affecting everything. Need a new libc for your database? Feel free to upgrade it without worrying if your webserver or plugins will break. Also, you can more exactly replicate your production environment on your local development machine or replace production if the machine dies.
I love docker for anything where I'm not going to be running whatever is in the repository of whatever Linux distribution I'm running.
Re:PHP 5 and 7.0 end of life
by johnchristopher on Saturday July 20, 2019 @12:06PM
(#20486529)
That WAMP server is serving multiple virtual hosts. We now need to be able to migrate some services living behind those hosts under different stack versions. Some services are production ready and can be deployed with a more recent LAMP stack but some can't. I don't have an infinite number of servers to put all those services on but I do have the resources for containers.
Reminder: when that WAMP server is down (which is an issue all by itself, the physical server has downtime as well), everything is down. Even static websites.
That's very rarely the thought process in the real world when you're dealing with a production system though. Most developers who have the seniority and experience to make the call to upgrade something aren't just upgrading for the fun of it. It's more like...
"it's old and hundreds of security patches and performance improvements have been released in versions that have come along since it was current, and the core developers aren't supporting this version any more so we're in for a world of hurt if anything goes wrong, and we have the bandwidth to fix this problem right now where we might not in the future so let's change it"