Upgrade PHP 7.3, 7.2 & 7.1 to current iterations.
Security vulnerability alerts for the following versions of PHP

PHP 7.1 versions prior to 7.1.32

PHP 7.2 versions prior to 7.2.22

PHP 7.3 versions prior to 7.3.9

As of today, There are currently no reports of these vulnerabilities being exploited in the wild.
Successfully exploiting the most severe of these vulnerabilities could allow for arbitrary code execution in the context of the affected application. Depending on the privileges associated with the application, an attacker could install programs; view, change, or delete data; or create new accounts with full user rights. Failed exploitation could result in a denial-of-service condition.
https://www.cisecurity.org/advisory/multiple-vulnerabilities-in-php-could-allow-for-arbitrary-code-execution_2019-087/

An account having multiple servers organized in teams and projects, makes it difficult to monitor all the deployments without needing to go into each server separately and the notifications are just too many to handle or even to effectively locate a problem.

Would be very useful to have a cockpit panel which gives a birds eye view of all the servers (logically organized in to teams and projects) showing a summary status that includes;

Server level availability, accessibility and general health status (CPU, Mem, Disk).

If more information is needed on a specific server a drill down to the monitoring panel for that server is presented.
Which also includes the server specific notifications would really make life easy.

There is suggestions dating back to 2016,17,18 and 19 to be able to do this but still no working solution?

You are able to do this at other platforms such as at Heroku, AWS, Azure and more.

Else the staging functionality would be pretty useless or at least an hassle to deal with if you need to reset your .env every time before you push your code while using a framework.

I do under stand that the servers are hosted at other services and could be a bit tricky to set env if there apis dosen't support it.But at least add it for those that dose...

Or an other approach would be to add an ignore functionality for specific files such as .env when pushing data.

The .env file and its vars should NEVER be track by git and should ALWAYS be ignored do to it cant include secrets or in laravel/lumens case even passwords.

I was advised by your support to create a php script that calls Cloudways api to trigger the staging push then overwrite my .env after this i done.
This works but still this would not be a valid solution in my opinion do the secrets and passwords has to be hard coded and/or tracked.. Also if you have many applications hosted you also need to create this script for every application you create.

ssl is automatically installed every time wordpress is installed

I'm building a WordPress multisite platform for customers to sign up like Wix.com Squarespace.com etc

My requirements are
- Domain mapping
- Auto-ssl

So far, WP Ultimo integrates with:

WP Engine
Works automatically – no additional set-up required.

WPMU DEV Hosting
Works automatically (including auto-SSL) – no additional set-up required.

Closte.com
Works automatically (including auto-SSL) – no additional set-up required.

Cloudways
Works automatically, but requires additional set-up. Read the Tutorial →

CPanel
Works automatically, but requires additional set-up. Read the Tutorial →

RunCloud.io
Works automatically, but requires additional set-up. Read the Tutorial →

ServerPilot.io
Works automatically, but requires additional set-up. Read the Tutorial →

Please see this article for full details:

https://help.wpultimo.com/en/articles/2636790-getting-started-with-domain-mapping-in-wp-ultimo