Deploy the WordPress + MySQL template with OpenTofu

Stand up WordPress with Nginx and PHP-FPM plus MariaDB on a private subnet using the validated OpenTofu template wordpress-mysql. MySQL stays on a private address; one floating IP serves the WordPress install screen over HTTP.

Prerequisites#

You need:

• A Quake AI account with application credentials
• OpenTofu 1.6.0 or later (installation guide)
• OpenStack credentials sourced into the shell (source openrc.sh). See the OpenStack CLI guide.
• An SSH key pair already uploaded to the project. See Add an SSH key.
• A copy of the wordpress-mysql template from the template reference page
• A plan tier that supports the default flavors (s1a.small for WordPress and m2a.large for MySQL). Override both in terraform.tfvars if your subscription requires smaller sizes.

Step 1: Configure variables#

Copy terraform.tfvars.example to terraform.tfvars and set the required values:

wp_domain   = "blog.example.com"
key_name    = "YOUR_KEY_NAME"
db_password = "YOUR_STRONG_PASSWORD"

Defaults for flavors, volume size, and network CIDR are documented on the WordPress + MySQL on Compute reference page.

Step 2: Apply the template#

From the template directory, run:

tofu init
tofu plan
tofu apply

Type yes when prompted. Provisioning takes several minutes while cloud-init installs MariaDB and WordPress on both instances.

When the run finishes, note wordpress_ip and mysql_private_ip from the outputs.

Step 3: Verify the WordPress install screen#

Cloud-init on both instances takes several minutes after tofu apply completes. Poll the WordPress floating IP until HTTP returns the installation page:

curl -s -o /dev/null -w "%{http_code}\n" http://$(tofu output -raw wordpress_ip)/

When cloud-init finishes, the command prints 200. Open the same URL in a browser. The page title reads WordPress › Installation. The MySQL tier stays on the private subnet; you reach it only through WordPress.

If the curl check returns 000 or 502, wait two minutes and retry.

Optional: SSH to the WordPress instance while cloud-init runs:

ssh -i YOUR_PRIVATE_KEY_PATH ubuntu@$(tofu output -raw wordpress_ip)

Next steps#

• WordPress + MySQL on Compute template
• Deploy the Simple VM template
• Self-Managed PostgreSQL template

Clean up#

Run tofu destroy from the project directory when finished. Type yes to confirm. Verify in the Console that both instances, the data volume, and the floating IP are gone.