thinking in an effort to make my various websites more manageable i might start running them through docker maybe?
cos a problem i have is, it all runs in PHP and all on the same server so if I want to update PHP then I need to make sure Everything is compatible with the new version all at once, from the blogs to the wiki to ye olde neofuji and even my one surviving twitter bot. but if they were in separate containers then they could all just coexist with different versions
recently at work i set up a dev environment for a new project using docker from scratch and it was actually a big piece of piss so that's what's got me thinking along those lines
i suppose it adds overhead on the server though & probably raises plenty of its own maintenance problems. there's still a lot i don't understand about it
so maybe i should go and research it instead of tooting about it eh
so where i've got so far is -
I have multiple sites running on the same VPS and my general idea is "one domain/subdomain = one containerised 'app'"
so my first thought was each could be self contained & have its own web server, but ofc multiple web servers can't listen on the same ports so "something" would have to route between them
and apparently that something has to be *another* web server acting as a reverse proxy
which feels like it's getting overcomplicated. too many servers
so my 2nd thought is, what if i just have the one web server, running natively, and then only a php-fpm container for each domain, and the server just routes traffic to those containers?
this seems like it's quite easy to do with nginx, i think
however: i'm currently running apache & the ideal would be to gradually switch sites over, so i'm wondering if there's a way to do that with apache instead, so i could have nonconverted sites running as-is and converted ones running in docker
apparently, yes you can do this
so this could be a plan?!
https://stackoverflow.com/questions/59862387/how-to-deploy-php-fpm-on-docker-container-and-apache-nginx-on-localhost-ubuntu
Another thing I'm realising is that there isn't really a reason to run one container per site if I don't need to
Because (at least the way I'm planning to set it up) the container is only running PHP-FPM, it doesn't actually contain the site files, it just has a directory shared from the host filesystem
So multiple sites can still use the same one as long as they're compatible with the same PHP version & I only need as many containers as I need PHP versions. Which to begin with will be 1
well it's 2:30 am and this vulgar message in a browser window is the result of me finally having got that setup working locally as a proof of concept. after an extremely hairy upgrade of apache. and with extra fun complications due to the host os being windows and the container being linux. now i'm going to bed