Cloudways screenshots
-
I've moved from ASO to Cloudways and so far its performing well with DigitalOcean server.
Sharing few screenshots of CW interface.
Initial login screen
App Console (There are some quick controls to start, stop, delete, create a new app and clone from here)
Manage Server- Details
-
Manage Server- Details II
Manage Server- Details III
-
Backup & Server Addons
App Management
Let's Encrypt SSL & auto renewal + Restore
-
Add new application
-
Cool, thanks. What are you currently paying per month?
-
@thwr Looks like he's on the $5 / mo plan.
-
And it's an EU company based in Malta. Big win.
-
@Breffni-Potter said in Cloudways screenshots:
And it's an EU company based in Malta. Big win.
More like "the" company based in Malta. LOL
-
@Danp said in Cloudways screenshots:
@thwr Looks like he's on the $5 / mo plan.
Correct, I am now using $5 DigitalOcean instance for this now
-
Good to hear that you liked our service.
Just to let you know, we've updated our Platform few months back.
And here is short GIF that describes a bit about our new UI improvements.
Hope, everyone would like it.
-
@MustaasamSaleem video GIFs for the win!!
You can embed YouTube and Vimeo here too, if you have that kind of content to share.
-
@scottalanmiller Thanks for letting me know.
-
@MustaasamSaleem said in Cloudways screenshots:
@scottalanmiller Thanks for letting me know.
No problem!
-
I'm testing them out here today. Just tried "connect to database" and this is what it gave me...
* About to connect() to internal-cw-api-cg-1330422999.us-east-1.elb.amazonaws.com port 5000 (#0) * Trying 10.146.0.187... * connected * Connected to internal-cw-api-cg-1330422999.us-east-1.elb.amazonaws.com (10.146.0.187) port 5000 (#0) > GET /adminer/add_ip?hostname=112049-84868.cloudwaysapps.com&server_fqdn=112049-84868.cloudwaysapps.com&ip=217.27.120.169 HTTP/1.1 User-Agent: GuzzleHttp/6.2.0 curl/7.26.0 PHP/5.6.30-1~dotdeb+7.1 Host: internal-cw-api-cg-1330422999.us-east-1.elb.amazonaws.com:5000 * additional stuff not fine transfer.c:1037: 0 0 * additional stuff not fine transfer.c:1037: 0 0 * additional stuff not fine transfer.c:1037: 0 0 * additional stuff not fine transfer.c:1037: 0 0 * additional stuff not fine transfer.c:1037: 0 0 * additional stuff not fine transfer.c:1037: 0 0 * additional stuff not fine transfer.c:1037: 0 0 * additional stuff not fine transfer.c:1037: 0 0 * additional stuff not fine transfer.c:1037: 0 0 * additional stuff not fine transfer.c:1037: 0 0 * additional stuff not fine transfer.c:1037: 0 0 * additional stuff not fine transfer.c:1037: 0 0 * additional stuff not fine transfer.c:1037: 0 0 * HTTP 1.1 or later with persistent connection, pipelining supported < HTTP/1.1 504 GATEWAY_TIMEOUT < Content-Length: 0 < Connection: keep-alive < * Connection #0 to host internal-cw-api-cg-1330422999.us-east-1.elb.amazonaws.com left intact -
Working now, must have been a blip.
