The current option to add mailboxes from Rackspace is extremely limited.
The only way to order them, is via a small window and is very limited information.
I have no details at all about current mailboxes, quota usage etc...
Also, the only way to order mailboxes is by TYPING in the details in the window including the desired password for the mailbox???
Afterwards, I get a confirmation back from support with the password in the email.
It's completely unsafe to communicate about passwords this way.

And lastly, there is no control at all about the mailboxes.
I can't create extra alias, I can't activate forwarding, etc...
for each and every change we have to request via support and wait for them to fix it, while some things I can do very easy myself instantly.
I don't understand why there isn't a control panel to manage the mailboxes?

My suggestion is that all WordPress apps use the Woocommerce Varnish by default.

This way there's no risk of a user installing a normal WordPress app and later installing Woocommerce on it, only to find out that their cart is broken because of Varnish.

Here is why:

I found out that the WordPress app uses a unique Varnish and the Woocommerce app uses it's own unique Varnish.

I ran into a problem with a WordPress app that I later decided to install Woocommerce on. Once I did, the normal wp Varnish did not support Woocommerce and it broke my cart functionality. I had to make a new Woocommerce app and migrate my site over there so it could use the Woocommerce Varnish.

The support team told me that Woocommerce Varnish would also work for a plain WordPress app without Woocommerce.

Having to pay for a bandwidth that will rely on behavior of internet (such as robot attack, malware, what ever intention...) but not being able to stop the expense is not something anyone would sign for, woudl you?

Therefore, having an alarm on bandwith with a threshold set by us is something to consider. Though the monitoring can be done through SSH , alarm must be done by email since none of us are spending they day watching the bandwidth consumption.

I will not sign for the account for this reason. that is total not acceptable interm of business rules for the moment. Since I have no protection and can end up with a bill of $ 5000 without even knowing it and with no corresponding customers on the website.

On top of not being able to delete logs ourselves (which should be made possible - as suggested by other feature request), it would be massively useful if there was an option to set a timer for logs (both error & access) to be auto-cleaned.

Even if we can control the error logs to a degree (by fixing the application errors), we can't fully control access logs which is a problem because it literally means that the disk space for app is constantly growing - and if you don't pay attention it could take your site down due to full disk within a few weeks (more or less depending on disk size).

Long story short, would love to see a feature to setup a timer for auto cleaning all kinds of logs (older than X days; every 30 days, every 15 days, etc).

Actually, we can take SERVER backups but we can RESTORE single applications. This is good but it would be great if we could also take a backup of a single application.

Consider this : we'll deploy an upgrade but before we want to made a backup that we can restore just after deployment if anything goes wrong.

• Actually, we need to take a full server backup, which takes several minutes ;


• I f we could made a backup of this single app, it would take 90% less time.

This could be placed at the same level than RESTORE tab under Applications.

We have a console for Servers, where we can list all of our servers, enter each one and see the list of Applications on that server (by hitting application management and then viewing the drop-down list)

I'd like a console for viewing all applications, independent of server, so we could find a specific site without having to trudge through each server screen.

It'd simply act as a list of shortcuts directly into the Application Management screen for each.

At the end of the day, we only care about our Applications, that we need servers to host them is incidental, ideally we don't want to consider where they live, unless we need to alter some setting on that environment