WordPress Automation

Provision isolated WordPress environments with web-server, PHP-FPM, database, TLS and backup integration.

One-Click documentation · Step-by-step guide

The WordPress module is a lifecycle workflow rather than a simple installer. It coordinates the web server, site user, PHP runtime, database, TLS and operational state for each deployment.

Create and Manage

one-click --wp-create
one-click --wp
one-click --wp-admin
one-click --wp-backup

Isolation Model

Dedicated Linux system users per site.
Independent PHP-FPM pools.
Isolated filesystem ownership.
Per-site web-server configuration.
Workload-aware backup organisation.

Environment Structure

/etc/one-click/wordpress/<domain>/www
/etc/one-click/wordpress/backups/<domain>
/etc/letsencrypt/live/<domain>

TLS

Use one-click --ssl to issue or integrate Let's Encrypt certificates for supported virtual hosts. The workflow can update web-server configuration and redirect handling as part of the site lifecycle.

Staging and Site Changes

Use the WordPress management workflow to work with a staging copy before making changes to the live site. A staged virtual host is not proof that WordPress core, its database and URLs were cloned successfully: check the staging login page, media and expected content first.

Make a verified backup of the live site before replacing content or databases. Do not push staging to production unless the specific push workflow has been verified in your installed release.

PHP and Caching

Sites can use isolated PHP-FPM runtimes and optional Redis caching. When changing PHP versions or caching settings, check compatibility with the site and its plugins. Use the per-site management options rather than changing every site's global configuration.

← Documentation index Explore the project on GitHub →