Use the current WordPress baseline
The starter pins WordPress 7.0.1 on the official PHP 8.3 Apache image and pairs it with MySQL 8, matching the current recommended WordPress runtime baseline.
Apps and platforms · plans from $10/month
Deploy WordPress.Keep content and credentials durable.
Run WordPress 7.0.1 on PHP 8.3, provision its MySQL 8 database, generate stable authentication salts, and persist uploads, themes, and plugins across releases.
Keep the repositoryInspect build and logsCustom domains and TLS
Adios deploy
Candidate release
WordPress
SOURCE
Git
REGION
de
ROUTE
HTTPS
01Source received
02Build completed
03Runtime started
04Health check passed
Promoted route
production.adios.run
A production path for
WordPress 7.0.1PHP 8.3MySQL 8Generated saltsPersistent wp-content
The production path
A working WordPress project still needs a safe release.
The application or service is only one part of production. Build evidence, runtime state, health, secrets, logs, routes, and the promoted version should remain inspectable together.
Keep every sensitive value out of source
Adios generates the database password plus all eight WordPress authentication keys and salts, then injects them through the runtime secret boundary.
Persist both halves of the site
Managed MySQL stores posts and settings while the wp-content volume preserves media, plugins, and themes. Back up and restore both state stores together.
From source to release
Three steps keep the deployment path reviewable.
Use the source and production behavior the project already has. The manifest records what the platform should build or provision and how the result becomes ready.
- 01
Start with source or a template
Bring the existing repository, or inspect and deploy one of the exact starter variants linked below.
$adios login - 02
Review the deployment contract
Keep commands, runtime or service version, health behavior, and secret references in adios.yaml.
$git diff -- adios.yaml - 03
Deploy and inspect the result
Follow build and runtime evidence, verify the candidate, and open the promoted route or service connection.
$adios up
adios.yaml
Your projectbase: wordpress:7.0.1-php8.3-apache
secrets:
MYSQL_PASSWORD: secret://generate:32
WORDPRESS_AUTH_KEY: secret://generate:64
WORDPRESS_SECURE_AUTH_KEY: secret://generate:64
# Six additional WordPress keys and salts are generated too.
resources:
db:
type: database
template: mysql:8
database: wordpress
username: wordpress
password: secret://MYSQL_PASSWORD
start_cmd: sh /app/start-wordpress.sh
port: 80
volumes:
- /var/www/html/wp-contentUse generated secrets for every WordPress key and salt, and treat the MySQL database and wp-content volume as one backup set.
Deployable starting points
Start WordPress from a template when the repository is not ready.
The WordPress starter includes the pinned runtime image, managed MySQL resource, stable generated salts, proxy-aware configuration, and persistent content mount.
Web apps
WordPress 7.0.1 with MySQL
WordPress 7.0.1 on PHP 8.3 with managed MySQL, generated salts, and persistent wp-content.
PHPBundled
- Template key
- wordpress
- Runtime
- php@8.3
- Repository
- templates
- Source path
- php/wordpress
git clone https://github.com/adiosdotdev/templates.git
cd templates/php/wordpress
adios upBefore production
Verify the workload.Then promote it.
The safest first release starts with a reproducible build or service configuration and a preview that exercises the dependencies production will actually use.
Ready when…
- The installer opens only on the intended HTTPS route.
- The generated database credential and salts resolve at runtime.
- Uploads, themes, and plugins survive a new release.
- Database and wp-content backups share a tested restore procedure.
Preview when…
- A plugin or theme changes PHP or extension requirements.
- A release includes a WordPress database migration.
- Media paths, proxy headers, or the public hostname change.
Questions, answered
What to know before deploying WordPress.
Review the runtime or service boundary, template path, failure behavior, and production checks before creating the first release.
Which WordPress and PHP versions does the template use?
The template pins WordPress 7.0.1 on PHP 8.3 with Apache and uses managed MySQL 8. WordPress currently recommends PHP 8.3+ and MySQL 8.0+.
Are the WordPress authentication salts generated?
Yes. The manifest generates all four authentication keys and all four salts as durable Adios secrets, so they are not committed to Git or regenerated on every release.
What does the persistent volume contain?
The volume mounts wp-content, which contains media uploads, installed plugins, and themes. Posts, users, settings, and other relational state remain in managed MySQL.
How should I back up WordPress?
Back up managed MySQL and wp-content on a coordinated schedule, then test restoring both into a non-production deployment before relying on the procedure.
Does Adios provide HTTPS for WordPress?
Yes. The template is proxy-aware and Adios serves the promoted route through managed HTTPS. Verify the generated route before attaching a custom domain.
Related deployment paths
Connect the rest of the stack.
Deploy PHP
Install production dependencies, start the application on a declared port, verify health, and connect the promoted release to domains and TLS.
Deploy MySQL
Start MySQL 8 with persistent storage, create a dedicated application database and user, protect both passwords, and verify data after restart.
Deploy Strapi
Build the Strapi 5 admin application on Node.js 24, connect managed PostgreSQL, generate every production secret, and keep local media uploads on durable storage.
Deploy Next.js
Deploy static pages, server-rendered routes, and APIs from one persistent Node.js release.
The first release
Deploy WordPress with the source and evidence attached.
Start from the repository or a template, review the deployment contract, and inspect what becomes the promoted production version.