We can limit revisions by using
define('WPPOSTREVISIONS', false);
or
define('WPPOSTREVISIONS', 20);

Make this available via the UI and ability to set defaults for all WP sites.

It would be great to have an option to export the WPTK "Sets" and then being able to import them in WPTK on the other servers.

The Wordpress Toolkit sets are only allowing preinstalling plugins and theme but does not allow any configurations such as site name, permalink settings or any other plugin related configurations

I offer to switch Wordpress toolkit screenshot service to use only fixed and published IPs, for security purpose.

For now, the only way to manage WordPress Smart Updates notifications is to enable/disable them at all under Tools & Settings > Notifications > WordPress application updates.

Please add feature to manage Smart Updates notifications, particularly receiving only failed updates.

For example, the customer has a WordPress set with the required plugins.

And this WordPress set is defined in ServicePlans > ServicePlanName > Additional Services > WordPress Toolkit

However, after creating the subscription example.com in Domains > example.com > WordPress > Plugins can be found that plugins like Hello Dolly or Akismet Anti-Spam are also installed however they were not pre-selected.

Please add the CLI method to prevent the installation of such unnecessary for customer plugins.

For now the database server assigned to the domain via service plan is used to host WordPress database. Would be nice to add ability to choose other database servers if exist as they might be more suitable for customer needs.

Like the wp-cron feature released recently it would be useful to have other functionality like
- Warn if not using InnoDB
- Clear out and limit post revisions
- Disable revisions
- Cleanup autoload options
- Cleanup sessions
- Image crushing

Currently, WP Toolkit offers possibility to add a subdomain prefix for staging.

So, considering the main domain is "domain.tld", WP toolkit offers "staging.domain.tld" as an option.

We use a slightly different scheme, and it our setup our staging will looks like "domain.review" (note "review" instead of tld).

It will be nice to specify default staging tld (as it currently implemented for "staging" subdomain) and have possibility to use such scheme of the staging (instead of selecting the domain from the list manually)