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

​
Goal

Deploy WordPress with the right first-boot, database, and persistence expectations.

​
Prerequisites

  • A StackShift account
  • The site title and the admin email, username, and password you want to use

​
Workflow

1
Start a WordPress site and provide the site name, site title, and admin email, username, and password.
2
Optionally pick a WordPress version, a custom domain, and placement; otherwise StackShift uses sensible defaults.
3
StackShift provisions a managed MySQL database, deploys the WordPress runtime, and runs first-boot install in the background.
4
When provisioning finishes, sign in at /wp-admin with the admin credentials you supplied.

​
How native WordPress is provisioned

  • The site runs on a native Apache + PHP WordPress runtime (not hand-rolled containers).
  • StackShift auto-provisions a managed MySQL database as a first-class database resource and wires WordPress to it — you never enter database credentials, they are generated.
  • WordPress files persist in a dedicated volume mounted at /var/www/html/wp-content.

​
First boot

Provisioning runs asynchronously: StackShift creates the managed database, deploys the runtime, then runs WordPress first-boot install with the site title and admin email, username, and password you provided. You supply only those WordPress details — the database is set up for you. Wait for provisioning to finish before signing in.

​
Single site or multisite

At create you can choose a single site or a WordPress multisite network. Multisite runs in one of two modes.
  • subdirectory: sites live under paths (example.com/site2). Simplest to run.
  • subdomain: sites live on subdomains (site2.example.com) and require wildcard DNS for the network domain.
  • A multisite network gives you a Network Admin at /wp-admin/network/ in addition to the per-site admin.

​
Hostname now, custom domain later

You can launch on a generated StackShift hostname and attach the final custom domain afterwards. WordPress stores its site URL internally, so if you change the hostname later you resync the URLs (redeploy or the update site URL action) to avoid redirect loops and broken assets.

​
Expected result

WordPress is running on the native runtime, backed by a managed MySQL database and a persistent wp-content volume.

Import an existing WordPress site

Bring an existing WordPress site onto StackShift by uploading a content-and-database archive; StackShift provisions a native site and migrates your content into it.

Connect a custom domain to WordPress

Understand how StackShift routing and WordPress site URLs interact before and after first boot.

Back up and restore a WordPress stack

A complete WordPress backup is two parts: the stack backup for your files (wp-content) and the managed-database backup for the MySQL data. Back up and restore both, then validate the app.

Managed database overview

Understand project and standalone databases, stable endpoint identity, supported engines, recovery, and transfer eligibility.