WordPress
Root & Branch Cloud offers two ways to run WordPress: Manual and Automated. The difference is how you install and update WordPress, themes, and plugins.
Which should I choose?
Section titled “Which should I choose?”Choose Manual to install plugins, change themes, and apply updates directly through the WordPress dashboard. No code repository is needed.
Choose Automated if you or your developer manage the site’s code in Git or a Docker image, then deploy updates to the live site.
| Manual | Automated | |
|---|---|---|
| Getting started | We install WordPress for you. | You supply a WordPress project or Docker image. |
| Themes and plugins | Install and update through WordPress. | Add or update in your project, then deploy. |
| Posts, pages, and site settings | Edit through WordPress. | Edit through WordPress. |
| Direct file changes | Available through SFTP. | Site code is read-only. |
| Media uploads | Saved on the site’s disk. | Saved on an uploads disk or external storage. |
If you are unsure, start with Manual. Automated does not update plugins or themes for you.
What is included?
Section titled “What is included?”Technology stack
Section titled “Technology stack”| Technology | Role |
|---|---|
| FrankenPHP and Caddy | Manual’s PHP application server and HTTP routing. Automated uses the runtime and web server supplied by your image. |
| MySQL | Stores WordPress content, users, and settings in both modes. |
| Varnish | Caches HTTP responses in front of WordPress in both modes. |
| WP-CLI | Command-line WordPress management; included with Manual, image-dependent with Automated. |
Included database
Section titled “Included database”Creating a WordPress app automatically creates a MySQL database in the same project, named <app-name>-db. For example, my-site creates my-site-db.
Most MySQL guidance in the Databases guide also applies here, including connection details, backups, and resource changes.
The database belongs to the WordPress app and cannot be deleted separately. Deleting the app also deletes its database and data permanently.
Shared settings
Section titled “Shared settings”These settings apply to both modes.
Manage in: App Apps → your WordPress app; Database Databases → <app-name>-db.
Resources and storage
Section titled “Resources and storage”| Setting | Manage in | What to know |
|---|---|---|
| App resources | App | Choose how much CPU and memory WordPress can use. |
| Database resources | Database | Choose how much CPU and memory MySQL can use. |
| Database storage | Database | Choose how much disk size MySQL can use; separate from the disk used for site files and uploads. |
See Billing and limits for resource tiers and pricing.
Domains and HTTPS
Section titled “Domains and HTTPS”App Both modes support a custom domain with automatic HTTPS certificates. Manage domains in Settings; see Domains and SSL for connection instructions.
Page caching
Section titled “Page caching”App Both modes start with a 128 MB page cache. Admin pages, logged-in visits, and form submissions bypass it.
Clear old cached pages in Settings → Varnish Cache. Edit caching rules in Config → Varnish.
Scheduled tasks
Section titled “Scheduled tasks”Automatic WordPress scheduled tasks are checked every five minutes, for jobs such as publishing scheduled posts. There is no dashboard setting for the schedule.
Environment variables
Section titled “Environment variables”App Manage runtime variables in Environment. The platform creates the following required system variables automatically.
| Variables | Manual | Automated |
|---|---|---|
DB_HOST, DB_NAME |
<app-name>-db |
<app-name>-db |
DB_USER, DB_PASSWORD |
Generated credentials | Generated credentials |
WP_HOME |
https://<primary-domain> |
https://<primary-domain> |
WP_SITEURL |
https://<primary-domain> |
https://<primary-domain>/wp |
AUTH_KEY, SECURE_AUTH_KEY, LOGGED_IN_KEY, NONCE_KEY |
Generated | Generated |
AUTH_SALT, SECURE_AUTH_SALT, LOGGED_IN_SALT, NONCE_SALT |
Generated | Generated |
WP_ENV |
Not supplied or required | production |
Editing system variables
- Required values - cannot be removed or left empty. A rejected save lists the affected variable names.
- Database connection - values remain editable, but must identify a working database with valid credentials.
- Keys and salts - changing them signs out existing WordPress sessions.
- Site URLs - manage these through domain settings.
Mode-specific guides
Section titled “Mode-specific guides”Choose a guide for setup, storage, updates, and configuration specific to your mode:
- Manual WordPress - manage the live site through WordPress and SFTP.
- Automated WordPress - deploy site code from Git or a Docker image.

