It would appear that Varnish 4.0.2 (which is on my server at www.bizi.fit) does NOT support HTTP/2. The recommended configurations are to enable HTTP/2 (which I have), and to use Varnish caching (for performance).
Are there any plans to upgrade Varnish to 5.0 (or perhaps upon request), in order to actually support HTTP/2. Currently, I can only get use out of HTTP/2 if I DISABLE Varnish cache.34 votes
In our provided WebStack ( nginx → varnish → apache ).
Since Nginx (which has support of HTTP/2) is in front this eliminates a need of upgrading varnish to 5.0 as far as HTTP/2 is concerned.
In case you are seeing issues please open a ticket through support panel, we will be happy to assists you further.
It doesn't make a lot of sense that applications are not listed under server settings. This seems like a logical addition.1 vote
From the main server screen, you can access the list of all applications installed on the server via the quick access icons on the top right (www, project and team).
Auto-scaling is now available on Kyup. Wish it would be available on Digital Ocean, Vultr, AWS, and Google as well1 vote
Unluckily this is a feature related to the provider not to Cloudways. Kyup has an infrastructure that allows for auto-scaling on a single server. None of the other providers offer this capability, so we can’t integrate it.
I would leave cloudways soon as it is not helping me with installing Mailwizz emails sending script.
A small change, which requires root privilages for a script to run at cloudways server is not possible. Support is not helpful at all in doing that change by himself. This is simply not acceptable.1 vote
I have noticed that Digital Ocean released floating IP's about a month ago. Will this be incorporated in the Cloudways Platform in the near future? This will be ideal for HA applications.
Jean, we try as hard as we can not to add provider specific features in our platform. That would mean adding complexity and locking certain features to certain vendors, something we definitely don’t want (same happens with AWS, GCE …).
To create a certain level of high availability on top of our platform, you could use DNS Made Easy fail-over failure http://help.dnsmadeeasy.com/dns-failover/configure-dns-failover/ (you would need to get your own DNSMadeEasy account, as we don’t support failover via our add-on). In any case, the issue of database sync would remain.
In our road-map, we have working on a highly available and auto-scalable option for the platform as a high priority.
For Wordpress (+WooCommerce) based sites.
According to this
Percona DB (MySQL) HHVM (Default) PHP-FPM (Backup) Nginx Varnish (Running by default) Memcached and APC WP-CLI
Complete installation instructions here
Here is the Blitz.io report - Average Response Time 136ms
Thanks for the feedback Prem. Our stack in fact performs already as well:
This is a wordpress test on our base stack (nginx → varnish → apache → mysql 5.5 ) with php 5.5. and you can see we compete.
We understand though that HHVM could be preferable on certain situations and we are working on it. You can follow here:
On the packages tab of Server Settings & Packages section you can play with additional packages that can speed up your specific setup (mariadb, mysql server 5.6, newer versions of PHP). We plan to add HHVM there.
- Don't see your idea?