Crazy Thought: cipi.sh integration

[batonac]

I know I'm going out on a limb here, but I just had this thought and couldn't help but pass it on.

It's always felt just a bit disjointed to me how the scripting is handled by WPCD. I mean, it works well most of the time, but it also feels inherently messy with the mix of logic between PHP and shell scripts/sessions. It would feel much cleaner to install a service on each server that interacts with WPCD using a REST API.

I stumbled across https://github.com/andreapollastri/cipi not too long ago, and it seems to check most of the same boxes as WPCD for server and site management. S3 backups and OpenLiteSpeed support are the most obvious missing features at the moment, but at least S3 backups look to be landing soon. Of course, WPCD provides a lot more than Cipi when you factor in that it's native-WP and supports provisioning, billing, and client-access support (to mention a few), which is why WPCD is so awesome.

That said, Cipi provides a REST API for managing sites, servers, etc. It seems that collaborating with this project and performing the underlying site and server management using this API could really simplify WPCD code, and allow for a really helpful "separation of concerns", so to speak. It would conceivably eliminate a "single point of failure" as well, in the case of a failure of a WPCD server. Things like providing a file manager for the server could potentially be simplified through this as well. It also should allow for an elimination of duplicate efforts.

Love it or hate it, I'm just thinking out loud...