I'd like to recommend you have API support added to your system. I'd love to be able to launch and control Cloudways services through an API.
Roel De Leender commented
We are thinking about choosing for cloudways, but automatic deployments is a must for us. Any news?
AdminCloudways (Admin, Cloudways) commented
It is high on our agenda to revisit all our git implementation and we are considering something like Eric says, so to integrate with third party services that facilitate the whole dev flow instead of trying to build something ourselves.
We don't have an ETA for this atm though.
Any news om this?
This will be great to include into our workflow systems. Where we create a project internally and would like to automatically create a matching application.
We want our clients to choose a package from our website that includes a 512MB or 1GB or 2 GB server with WordPress and our plugin recipe (not yours) plus cloud flare cdn and have your system automatically create this for us. It is automated for your processes but we cannot see how we can automate it. We can't access the DO API from you, whmcs is not available .... So we end up doing a lot of manual work .... We don't want to do it this way.
I would recommend that you integrate Git/github, bitbucket, Cloud9, PHPstorm, etc., and then tie your brand to those services. You would get a lot of marketing milage (SEO and other) out of it.
Really, if people are choosing either DO, AWS, or Google as a preferred platform for reasons other than price, then they are likely developers they are likely relying upon some kind of version control system.
Randy Lee commented
Or make it a git server of it's own so that desktop can get pushed to it without need for anything like github.
This would then beg the question of being able to roll back/forward to any given commit point from a web counsole -- what version is being run on the server pulldown...
Giuseppe Aiello commented
To be able to push on the git repository and automatically see the changes online it would be great if we could manually define a POST hook URL in Bitbucket or Github. This way only users that really want this functionality can activate it, without the need to manually Pull from the Console.
For example, in PHP, a solution like this would be enough: https://gist.github.com/oodavid/1809044#file-deploy-php