WordPress with MariaDB

What you can use it for

• Publish a blog or a content-managed website.
• Run WordPress alongside its own database service.

Choose the right configuration

This configuration includes WordPress and MariaDB, so you do not need to supply a separate database. Site files use /var/www/html and database data uses /var/lib/mysql. Choose another WordPress variant if your application requires MySQL or an existing database; a file backup alone will not restore the whole site.

What this template creates

Configuration to review

This template has no additional declared inputs. Review the generated variables, endpoints and resource settings in the deployment form.

How to deploy

1. Select Configure deployment and sign in or create an account.
2. Choose a new or existing project and select an available region.
3. Review services, required inputs, storage and compatibility warnings. Submit the deployment only when the configuration is ready.
4. Inspect deployment logs, complete the application's setup and test its endpoints before production use.

Check your deployment

Finish the installer, publish a test post and upload an image. Open the post while signed out and verify the image URL. During a planned restart, check that the post and upload remain available. Test password-reset email separately if the site needs it; reaching the homepage does not verify email delivery or recovery.

Operating this application

• Open the generated domain and finish the WordPress installer. Set a unique administrator password and confirm the site URL.
• Back up the database and uploaded files together. Verify that both survive a restart and can be restored.
• Check plugin and theme compatibility before upgrades. SMTP credentials and third-party services require their own configuration.

Hosting costs

Include both the WordPress and MariaDB services, both storage volumes and visitor traffic in your estimate. Media uploads, plugins and database growth change resource needs; paid themes, plugins and email services have separate charges.

CPU, memory, storage and network usage contribute to your bill. The selected region affects resource prices. A multi-service template incurs usage for each service; external APIs and software licenses are separate.

Source and validation

This deployment configuration comes from Coolify's Apache-2.0 licensed open template collection and is adapted through Polyer's compose importer.

Static compatibility analysis is not a live application verification. Test your chosen configuration and recovery workflow before using it for production.

Editorial content reviewed: 2026-10-15

Upstream documentation ↗Template source and license ↗