What's New✨

We’ve just pushed out a critical upgrade to all SpinupWP customer servers to patch a Composer vulnerability.

We have a policy at SpinupWP of never making any changes to your server unless we consider them to be absolutely critical. Composer has released a fix for a command injection security vulnerability that was reported a few weeks ago. We felt that it was important to act on, so we’ve automatically updated Composer on your server.

The main impact of this vulnerability is to services passing user input to Composer, including Packagist.org and Private Packagist.

You can now switch your sites to run on PHP 8!

Upgrading your site to use PHP 8 can be done by clicking on the Settings menu item from the site dashboard and changing your PHP version to 8.0.

To make things easier, we also released an upgrade that allows WP-CLI to run its commands using the PHP version of the site it’s running on. This means that if you keep your sites on PHP 7.4, everything will work as you expect it to, making for a much smoother server and site management workflow.

WP-CLI will now use the site’s selected PHP version instead of using the latest version of PHP on the server.

Our most recent upgrade was an improved sign-in process as we added social sign-on capabilities for accessing the SpinupWP app. You can register a new account or sign in to an existing one using Google, GitHub, or Twitter.

Suppose you have previously signed up using an email and password combination? No problem, you can enable a social sign-in from the Your Account > Security page.

We launched the new site dashboard screen in March, which provides you with a high-level overview of any specific site. Each section of the new dashboard clicks through to the relevant area in SpinupWP so that you can make changes with ease.

We added the ability to purge a site’s object cache and correct a site’s file permissions from the dropdown at the top on the site dashboard.

You can now modify non-root database user privileges, giving you the ability to allow individual database users access to multiple databases on a server.

Under the Nginx settings for a site, we added a new toggle that will create the necessary Nginx rewrite rules for a WordPress multisite running as a subdirectory install when enabled.

We enabled the Strict-Transport-Security header by default for any HTTPS enabled sites.

You can now see each server’s disk space usage right from the server dashboard. We also released a comprehensive article on how to audit your server’s hard disk if you’re running out of disk space.

To automatically correct file permissions for your site, head over to the site’s settings screen and click ‘Correct File Permissions’ from the dropdown by the ‘Clone Site’ button in the top right corner.