Hi,

You should implement backups the same way some of the best web hosting providers do:

1) Separate manual backups from the automated ones.
1.1) Manual backups should be "persistents" so they don't just disappear as the automated backups go on. Hence, the separate list only containing manual backups.

To avoid abuses, you can limit to 5 or even 3 maximum "spots" of manual backups at the same time. That way, we are forced to delete some to make further manual backups, so that we never exceed the limit of manual backups spots.

  1.2) You could, as well, allow us to disable automated backups. That way you reduce the load on your servers, as most people never use automated backups.

For more static websites, this is life changing as an initial manual backup could act like a "clean snapshot" we can use repeatedly over time as major issues occur (making the automated backups useless). And we could make one at each major update.

2) Please, please, please allow us to rename backups (manual ones only)
Automated backups shouldn't need to be renamed but manual backups should.
If we do some subsequent backups after major steps, we should be able to clearly see which backup was from which step of the website's development, even 5 months later, when we don't remember the workflow anymore.

Oh and those features should be "free". It would be outrageous if you implement those feature and make them paid ones.

Thank you very much in advance !

Paraphrasing an idea put forward for Magento sites...
The staging area is useless for us at the moment as our users constantly post and sell products, so by the time we have finished work on the staging site updating pages there have been new products added, products sold and so on...this means we cannot merge the staging site with live as it overwrites the orders and products in the database.

An option to exclude data specific to users, products, sales, etc, would be most welcome, so that we could push page layout and interface developments without affecting other content of the website.

Looking forward to a future implementation of this feature.
Keep up the good work!

Currently, it's only possible to create a new account with either a Gmail address or a branded email address.

I strongly encourage you and suggest allowing any email addresses to create a Cloudways account.

Gmail → can't force a client to use Gmail
Branded email → if the branded email should be migrated to Cloudways (using Rackspace) then its not recommended to use this email address to manage the CW account itself.

Workaround: Change email address after account creation. But this can be only done once. And it's again an annoying process for a client who needs to do that and confirm it.

Benefits of QuickBooks Hosting

QuickBooks Cloud Hosting enables you to save your software and data files on third-party cloud servers. This indicates that you can get access to your QuickBooks software and all the stored files and data from any place and anytime. QuickBooks hosting enables you to use the software without mobility restrictions.

Few Advantages of QuickBooks Hosting:

Access Anywhere
For several SME owners, this is the USP of QuickBooks hosting. You do not have to worry about being bound to a single computer. QuickBooks Hosting enable you to have access to your software with your tablet or smartphone. QuickBooks hosting provides you remote access, so you can effortlessly open your Windows-based software on your other devices and computers.

Increased Collaboration
The mobility granted by QuickBooks hosting is also essential for companies that have several QuickBooks users. You do not need to have QuickBooks on various devices, and users are not restricted in the way of accessing the software. This enables many users to access the software from any place at the same time.

Data Security
Plenty of sensitive data and information is stored in your accounting software. To avoid loss of data, you might save valuable data and reports on the computer. But what if your laptop or computer gets misplaced or destroyed. From disasters to hackers, it is important to safeguard your sensitive data. With QuickBooks hosting, many protection and security steps are taken to assure that only you and the people you select have access to your data.

Reduces IT Expenses
Some companies choose to have their separate servers for hosting QuickBooks. This can get costly when you combine the setup expenses, maintenance charges, and other costs. Using a remote server by QuickBooks hosting can be less costly than owning an onsite server. You can also increase your efficiency with the help of a Virtual Desktop Cloud.

To know more about QuickBooks Desktop Enterprise or Sage Conversion to QuickBooks visit Apps4Rent.

While the CloudWays service is great, I've been concerned for a while now that I can simply click to copy passwords for SFTP, SSH, databases & WordPress. My concerns have been amplified as yesterday over 1.2 million compromised passwords were stolen from GoDaddy because they stored their details in a similar way: https://wptavern.com/godaddy-data-breach-exposes-1-2-million-active-and-inactive-managed-wordpress-hosting-accounts

Simply put: ALL passwords stored on CloudWays should be salted & hashed. There should be no way for CloudWays (or me) to retrieve them once they've been saved. The fact that I can indicates they are being stored as plaintext, which is a huge security issue. Passwords should only be visible at the point of creation, and should then be stored and compared against a salted & hashed version - no one should EVER be able to retrieve their password.

Please make it a priority to change the way you store passwords for all of your systems, otherwise I'm very much concerned that you will suffer the same fate as GoDaddy.

When using a WordPress plugin like WebP Express (https://wordpress.org/plugins/webp-express/) or ewww.io, they are using an htaccess rule to redirect browsers that support webp images to the corresponding webp image files. This however does not work out of the box on Cloudways due to Cloudways' Nginx vhost.

Currently, I need to contact Cloudways for each application I want to add support for webp images to exclude images from the Nginx vhost. After that, the htaccess rules work correctly. This is also described by ewww: https://docs.ewww.io/article/16-ewww-io-and-webp-images

Can you please give us control of excluding images from the Nginx vhost ourselves? This would save your support and us much time.

Thank you for considering.

This is about the "Breeze" cache plugin for Wordpress, which is by the way amazing!

There is just one thing that is really annoying, that most of other cache plugin do. There is no option to purge the cache only for a specific page. With other cache plugin, it's possible to do it from the Wordpress bar at the top of the page and that's great to force refreshing a page for users, without having to delete the whole cache, thus slowing down the whole website for users during some time.

Thank you for the great work and best regards, David