What's New✨

We’ve rolled out new, responsive improvements to SpinupWP’s user interface. This update gives SpinupWP users an improved user experience on mobile devices, making it easier to manage your servers and sites on the go.

While the majority of SpinupWP users continue to access the app from a desktop or laptop, a small but growing contingent has been asking for these improvements to smaller screens. The improvements allow you to access your SpinupWP dashboard from a phone or tablet, with all the same functionality found in the desktop version. You can spin up new servers and reboot existing ones, create new sites, make changes to your account, and contact support when needed.

You can now select MariaDB 10.6 when provisioning a new server. SpinupWP will not update MariaDB to 10.6 on existing servers.

The ability to create path redirects is the latest improvement to SpinupWP. Path redirects let you redirect from a specific URL path to a different path. This is typically a path on the same domain, but it’s easily possible to redirect the user to a URL on a different domain.

This new functionality means it’s now ludicrously simple to create redirects and link old pages to updated versions.

We’ve added support for DigitalOcean OAuth, making it easier than ever to connect SpinupWP to your DigitalOcean account. It also makes the connection process more secure.

You no longer need to visit the DigitalOcean dashboard, generate a personal access token, copy it, and paste it in SpinupWP. The OAuth flow takes you from SpinupWP to DigitalOcean, asks you to authorize SpinupWP to use your DigitalOcean account, and then takes you back to SpinupWP. Much smoother and no messing with tokens.

To authorize SpinupWP with your DigitalOcean account, you only need to provision a new DigitalOcean server, and SpinupWP will handle the rest. Click Authorize on DigitalOcean during the server provisioning process, and you’ll be redirected to DigitalOcean, to authorize your account. It’s that easy!

If you’ve previously set up DigitalOcean as a server provider using the API Token method, you can visit the “Server Providers” screen in SpinupWP, and upgrade the existing token to use OAuth.

We’ve decreased the amount of time it takes to back up sites on multi-core servers. Backups are compressed using gzip to decrease the time it takes to transfer a backup to the backup storage location and reduce required storage space.

Running gzip in parallel leverages the capabilities of multi-core servers by distributing the compression tasks across multiple processors, utilizing all available CPU cores. This considerably shortens the time needed to create backups. Between this and other backup improvements, we’ve reduced the total queue time per day from around 500 hours to under 200 hours!

The SpinupWP REST API is now available! Using the API, you now have the ability to programmatically control your SpinupWP servers and sites.

This API is currently in BETA, which means it can change at any time. We highly recommend subscribing to the REST API Beta email list to be notified at least a day in advance of any updates.

We’ve released a very limited set of endpoints to start so we can gather input from REST API users. We’re also working on a PHP SDK, which uses the REST API and makes it easier to build PHP apps to manage SpinupWP resources.

You can get started with the REST API by reading the SpinupWP REST API documentation and creating your first API token. You can create API tokens for personal use, or for your team.

To generate a personal API token, navigate to the API Tokens tab in your “My Account” settings page in SpinupWP. API tokens you create via the “My Account” page are only relevant to resources created under your personal account.

If you are a team admin or a team owner, you can also generate access tokens from the API Tokens tab on the “Team Settings” page for any of your teams. API tokens you create via the “Team Settings” page are only relevant for resources associated with that team.

When debugging errors on WordPress sites, having quick access to your debug.log, error.log, and access.log files is vital. With the new SpinupWP site log viewer, you no longer need to SSH into your server and dig around for these files.

All you have to do is log into SpinupWP, go to a site’s dashboard and click on the Logs menu item. Here you can select any of the three log files to view the last 1,000 lines from each file. You can also use the refresh feature to see new log entries, scroll through the log contents, or set the viewer to fullscreen for a more detailed view.

We have loads of ideas to make this tool more useful in the future, like the ability to filter the logs using the grep command syntax.

As more and more development teams signed up for SpinupWP, it became clear that the events view screen needed some improvements. We’ve added a new team events view, which shows all events across an entire team. At the same time, we’ve improved the events view to indicate which site the event was actioned on.

Backblaze storage is a super affordable alternative to Amazon S3. As our customers have often requested it, we’ve made it available as a Storage Provider for your site backups. You can learn how to set up and enable Backblaze for your site backups in our Backblaze Storage Provider doc.

Wouldn’t it be great if you could somehow automate the manual tasks you have to complete after you’ve created a new WordPress site on SpinupWP? Maybe you need to install a specific theme, disable some default plugins, or configure specific site settings. Now you can, with the availability of the Deploy Script feature on all site types.

Previously only available on sites created from a cloned Git repository, the Deploy Script feature makes it possible to run any terminal commands after the new site is deployed. You can install any plugins or set WordPress-specific settings using WP-CLI and even run server-specific commands utilizing this feature.

At the moment, this is available when setting up a new site. We plan to add post-provision scripts for newly created servers and an account-wide way to create and manage scripts to run against new sites or servers in future iterations.

Inactive content is any content on your site that isn’t accessed often (like your Terms and Conditions page). Previously, inactive content was automatically removed from the cache if it was not accessed for 60 minutes. With this update, whatever you set your site’s Page Cache setting to, will also be applied to any content deemed inactive, and the cache duration will be set accordingly. Just one more way we’re helping keep your WordPress sites lightning fast.

Since launching our in-app notifications in June, we’ve been iterating on how to give SpinupWP users more precise control over the notifications they receive. It’s now possible to subscribe or unsubscribe to notifications for a specific server or site. Simply switch the Notifications toggle at the top of a server or site dashboard to set your notification preference.

The next step in the evolution of our notification system is only to notify you when something needs your attention. For example, is it really necessary to notify you the moment a server needs a reboot? No. We should certainly show that the server needs a reboot in the dashboard right away. However, it doesn’t warrant a notification until some time has passed and the server still hasn’t been rebooted.