How to deploy WordPress on Zenifra

WordPress can be deployed on Zenifra as an HTTP project from the official image. This guide shows the recommended configuration, the required variables, and how to validate the result.

Prerequisites

A verified account and access to the console.
Permission to create projects in the organization (project.create).
Credit or a saved card for the selected plan; see Payment models.

WordPress is in the public Templates catalog. Use Deploy to create the application with the recommended configuration, or Customize to review plan, storage, and variables and optionally create a database with it before confirming. The steps below show a manual configuration from the official image.

Step 1: create the HTTP project

In the console, click + Create Project, choose HTTP, and fill in:

Field	Value
Project source	OCI Image
Image	`docker.io/library/wordpress:6.9.0-php8.2-apache`
Registry	Public, no authentication
Plan	Premium Plus (2 vCPU and 2 GB RAM) for a well-performing site. For high traffic, consider larger plans.
Port	`80`
Instances	1. Multiple instances require extra shared-media configuration in WordPress.
Persistent storage	Yes, 10 GB, directory `/var/www/html`

Pick a name between 6 and 32 characters, using lowercase letters, numbers, and hyphens; it also defines the *.clients.zenifra.com address. For testing, hourly billing is the cheapest; for continuous use, compare it with monthly.

Storage

Required. Media uploads, plugins, and themes live in this directory; without it, everything is lost on restart.

Step 2: configure environment variables

Add the variables below in the Environment variables step:

WORDPRESS_DB_HOST=<mariadb-host>:<port>
WORDPRESS_DB_USER=app
WORDPRESS_DB_PASSWORD=<mariadb-password>
WORDPRESS_DB_NAME=app
WORDPRESS_CONFIG_EXTRA=define('MYSQL_CLIENT_FLAGS', MYSQLI_CLIENT_SSL);

WordPress needs MySQL or MariaDB. First create a managed MariaDB and copy the host, port, and password from the console. Managed MariaDB accepts only TLS connections; the WORDPRESS_CONFIG_EXTRA variable makes WordPress connect to the database over TLS. See Environment variables.

Step 3: create and validate

Review the estimated cost and click Create Project. When it finishes, the console opens the project page with the public address.

Open the project URL and finish the WordPress installation (language, site title, and admin user). Upload an image to the media library, pause and resume the project, and confirm it is still available: this validates persistent storage.

If the application does not respond, check the project logs, the configured port, and the troubleshooting guide.

Production recommendations

Configure your custom domain before finishing the installation, so site URLs already use the final address.
Keep WordPress, themes, and plugins up to date.
Back up the database and the wp-content directory regularly.

To remove the project, open it in Projects and click Delete. Deletion is permanent and erases storage.