Feature Ideas

Allow users to connect their plugin & theme license for 1-click activation on sites they are creating on InstaWP or migrating to a hosting provider.

At the moment, the first admin user account seems to be used for Magic login after for staging sites. There should ideally be a dropdown to select which admin user account is to be used.

Allow the selection of the datacentre location for staging sites created from within the WordPress plugin to speed up staging creation.

Facility to add Terminal, Server logs and (not sure how) Local folder sync.

Export sites to Google Drive for safe keeping.

When you create a staging site from a live site, it is not possible to push the changes in files and/or database back to the live site (unless you use 2 way sync, which works on "content" level). We will create a functionality which will help push files and/or db (similar to WP Migrate) from and to staging sites live sites.

Ability to set a standard/global WordPress admin email address for WordPress installs I have a specific dev email address for staging/maintenance/website development. InstaWP uses the email address linked to my InstaWP account as the standard WP admin email address which is not preferred. Ability to change the WordPress admin email address Now we aren't able to receive the conformation email when changing the WP admin email address (a workaround is using a plugin but it would be nice if we can change the WP admins email without adding plugins).

Anyone with eyeballs

Context: "View logs" pop-up of each website. Idea: Having two more buttons on the debug.log of each site - CLEAR and DELETE logs. CLEAR button - will only clear the current contents of the logs (visually), so that you can continue testing and therefore, generating new logs, and have an easy way of capturing ONLY each test/scenario's logs generated, while keeping the entire full log in the original /wp-content/debug.log file for later usage. DELETE logs button - this, will of course, simply delete all logs (including the debug.log file) , which of course will then show up again if it's generated and so on (this is what happens now, but I am using manual labor to go into "Code Editor", surf on /wp-content/ and manually remove debug.log each time, which is a bit frustrating.

When creating a new site (whether from scratch, or via a template) could we please be able to set the site expiration? By default this is 15 days (I think). When creating sites for testing I only want them to be around for a couple of hours. I know I could add some extra code to manually delete them but it would be som convenient to just have them auto-expire after a couple of hours. Fingers crossed this isn't too hard to add support for. :-)

Enable users to upload and deploy WordPress zip plugins across all managed sites directly from the InstaWP dashboard. Key Features: Centralized plugin upload and deployment. Bulk installation across multiple sites in one action. Ensure consistent plugin versions across all sites. Save time by eliminating the need for individual site logins. Example: I wanted to add new CommandUI plugin to all sites, but had to open all sites individually and upload zip plugin.

I don't see an option to create a staging of a connected site. I had to go to the website, InstaWP Hub and then request for a staging to be made in order to pull this into the hosting environment.

Providing the ability to use xdebug would enable advanced debugging capabilities when trying to track down gnarly problems that customers are experiencing that are not reproducible in local dev environments.

If you enter an existing or reserved site name, then the modal closes and gives an error as attached - Installation Failed! All good, but clicking on add new site, then one needs to select any plugins they have already selected before again. So maybe a possibility to check name availability when entered, or open modal again and give error within that?

when using a backup tool on a site I use for example AIO WP Migration (no longer needed for migration now, but the backup option works well) When having a staging, the backup plugin keeps backing up the staging as well of course... would there be an option somewhere down the road that makes it possible to disable such a plugin from executing on a staging?