WordPress

​

Towbar manifests

id: wordpress-mariadb
name: WordPress MariaDB
type: mariadb
container:
  network: application
  networkAlias: wordpress-mariadb
  resources:
    cpus: 1
    memory: 1g
secrets:
  runtime:
    - MYSQL_ROOT_PASSWORD
    - MYSQL_DATABASE
    - MYSQL_USER
    - MYSQL_PASSWORD
environments:
  production:
    server: 192.0.2.10

id: wordpress
name: WordPress
buildServer: null
deployment:
  type: image
  image: wordpress:6.9.0-php8.4-apache
container:
  port: 80
  network: application
  volumes:
    - name: wp-content
      mountPath: /var/www/html/wp-content
      initialData: image
environments:
  production:
    server: 192.0.2.10
rollout:
  type: recreate
  maintenanceMode: true
  reason: Persistent application data uses a single writer
secrets:
  runtime:
    - WORDPRESS_DB_HOST
    - WORDPRESS_DB_NAME
    - WORDPRESS_DB_USER
    - WORDPRESS_DB_PASSWORD
domains:
  primary: wordpress.example.com
tls:
  mode: direct

​

Configure

1. Prepare the example server, connect the repository, and map production to the branch containing these manifests. Replace the example server IP and domain. Commit the manifests, then sync the repository and inspect the resolved configuration.
2. Save the initialization values in the table below for the mariadb Datastore under Datastore → Settings → Secrets. Deploy it first and wait for readiness. These values create the database and user only on an empty volume.
3. Set the Service’s declared runtime values under Service → Settings → Secrets using the table below. Replace descriptions and placeholders with actual values; do not commit passwords or keys.
4. Keep the Service’s named volumes attached across deployments. Towbar’s Datastore backup policy does not back up Service volumes, so include them in your own recovery plan.
5. Deploy the Service, then perform the checks below before enabling auto-deploy.

​

Datastore values

​

Runtime values

​

Verify