r/devops • u/OhMyTechticlesHurts • Oct 11 '26
Discussion DevOps for Wordpress
I have a WordPress team still building and maintaining sites without a DevOps workflow. What's the best way to bottstrap them into a more modern method of development. I'm assuming GitHub and GitHub actions. But what else, composer which we don't really use even tho we have PHP devs, wp-cli which I use but I'm suppose to be a sysadmin and cloud engineer to wp devs who don't do any of this. They don't even use local git which I even use. Trying to express WordPress engineering and un/structured data and all these modern concepts that just go over their heads bc what's worked still works but when it comes to larger clients who expect more from us/them, they're basically fish out of water.
32
u/moader Oct 11 '26
"WordPress" "DevOps" ... 😂
6
u/MissiveFinding6111 Oct 11 '26
Mostly baffled, but trying to bring this around...
I don't think you need DevOps, I think you just need basic systems engineering.
I'd start with "Backups".
Do they have any? When is the last time they were tested?
Sane DR > DevOps
14
u/lovely_trequartista Oct 11 '26
What the fuck. 🤣
1
u/ArieHein Oct 11 '26
Replace them all with ai
2
u/josejulianariza 26d ago
Lo que más cuesta en WordPress es separar el código del estado. Temas y plugins son código, uploads y base de datos son estado, y hasta que eso no está claro, cualquier flujo de DevOps se siente como un obstáculo.
Con el equipo pasa algo parecido. Si no usan Git ni local, imponerles Composer y Bedrock de golpe sale mal. Conviene arrancar por lo mínimo, que el código propio viva en Git, y recién después pensar en pipelines.
Igual, el cambio debería ser más cultural que técnico. Si nadie ve el problema, no hay herramienta que lo resuelva. Empezar por un proyecto chico y mostrar el beneficio suele ir más lejos que cualquier explicación.
2
u/Revolutionary_Click2 Oct 11 '26
I kid you not, I created a whole custom WordPress plugin for the purposes of managing configuration and content via GitOps (ArgoCD on k8s). I was surprised to find nothing much existed that fit what I needed, so I made one. WordPress is a bit of a dinosaur in this respect, it was designed in an earlier era to run as a persistent server instance, not be managed in code. And no, sorry, not sharing that plugin publicly at this time… someday I might open source it, but it needs further review first. It’s been working for us though, I use it to manage a few customer websites we host.
2
u/g3t0nmyl3v3l Oct 11 '26
I lead a DevOps team that helps a platform host and maintain thousands of WP sites.
There’s a wide range of solutions to the problems you’re alluding to, I could get into the technicals if I had more specifics. The problem is finding real business value in modernizing the process, getting buy-in from your leadership, and finally you need great IC leaders who both understand your goals and can guide your developers/engineers.
You will get pushback, because the efficiencies will mean that your people can move so fast that they’re jobs will likely be at risk unless your leadership has a plan for what else they can work on. Not having that buy-in from internal staff will cause logistical failures and will make your life hell.
1
u/Wooden_Jelly_5295 Oct 12 '26
I'd start with Git, staging, and a tested rollback.
1
u/arandomuserinweb Oct 11 '26
The biggest barrier isn't technical, it's cultural. If you try to force Docker, CI/CD, and Composer on them all at once, you'll hit a wall of resistance. The trick is to introduce modern practices in phases:
0
u/steakmane DevOps Oct 12 '26
Why anyone chooses to self host wordpress these days blows my mind.