I've used PW in probably, at least, 100 project the last 10 years. I've been wanting to quit shared hosting since at least five years but I don't have a good idea exactly how yet (as a 1-man company) and I was hoping to get insights and inspiration in your workflows. I've prepared by moving over entirely to Linux, and I'm runing a bunch of VPS's for some personal projects. I also do all my dev work remote, on a VPS. I can set up debian reasonably okay, I think.
My biggest issues are:
1. Every shared hosting has a different interface and different constraints
2. I can't easily copy live -> staging -> test, working with updated data is a manual hassle
3. I currently have no shared hosting that ticks all boxes (in the Netherlands)
4. Since PW is a CMS I have to update the live data-model manually (there is no 'migrate up'). I don't think I can solve this problem through any devops magic, but still worth mentioning as one of the biggest pain points. The answer to this problem might be to step over to Laravel, or similar, I assume.
My goals and hopes are:
-1. (Edit): **FOSS**. I would want to avoid tying up my professional life to any service with tiers and a subscription model
0. **Have the same basic architecture for all projects**
1. Automate backup and restore, and streamline it across all projects
2. Streamline replication from live -> staging and -> test, so I can work on a fresh copy of data without having to use phpmyadmin
3. Have a more robust and portable and setup where I can spawn vps's with a click
4. have a more robust deployment process (better than git-ftp) that is easy to reverse.
I realize this is a very wide devops question, but I'm curious about how you do it - the ones who who took this step away from shared hosting. I know someone who runs a rails shop, and hes using docker/kubernetes - that is probably the answer, I think. But I still wonder exactly how this would apply to PW.