Skip to main content
Live. This area is documented as current, user-reliable behavior.

​
Goal

Operate a StackShift-hosted WordPress site without leaving StackShift for routine checks.

​
Prerequisites

  • A direct WordPress project

​
Workflow

1
Open the project overview to see runtime, DB, storage, and plugin state.
2
Run safe actions (reset password, flush permalinks, maintenance mode, flush cache, DB upgrade, core update).
3
Review the operational history list for recent changes and outcomes.

​
The overview

The control surface reads live metadata from the site: runtime status, database, storage, and installed plugin and theme state. It is the place to check how a WordPress site is doing without opening wp-admin or the node.

​
Safe actions

A narrow set of safe operational actions runs against the site and is audit-logged in the history list.
  • Reset the admin password.
  • Flush permalinks.
  • Enable or disable maintenance mode.
  • Flush the object cache.
  • Run a database upgrade.
  • Update the WordPress site URL.
  • Update WordPress core.

​
Themes, staging, and history

  • Install and activate themes from the WordPress theme marketplace.
  • Clone a staging copy of the site to test changes.
  • Review the operational history to see recent actions and their outcomes.

​
Expected result

Operators see WordPress runtime state and recent operations directly in StackShift, with every safe action audit-logged.

Deploy WordPress on StackShift

Launch single-site WordPress as a template-backed stack with bundled MariaDB and persistent storage.

Back up and restore a WordPress stack

Use StackShift stack backups for WordPress content and bundled MariaDB data, then validate the app after restore.

WordPress plugin and theme releases

Connect a WordPress plugin or theme repo, let StackShift package it into a release, preview it, promote draft/beta/stable channels, and install the exact release on a running StackShift WordPress site.