feat(service): add WordPress OpenLiteSpeed service template

[rishi-jat]

/claim #8264

Changes

• Added a new reusable WordPress + OpenLiteSpeed one-click service template intended as a production-ready reference.
• The template automatically provisions WordPress core files and generates wp-config.php using inline, idempotent bootstrap logic inside the container.
• Uses persistent volumes for both WordPress files and MariaDB data to ensure data durability across restarts and redeployments.
• Designed to work with Coolify’s built-in proxy and follow existing service template conventions.
• Scope is intentionally limited to a single service template file, without introducing additional services or behavior.

Issues

• fixes: [Enhancement]: Add a reusable WordPress + OpenLiteSpeed service template for production environments #8264
• /claim [Enhancement]: Add a reusable WordPress + OpenLiteSpeed service template for production environments #8264

Category

• Bug fix
• New feature
• Adding new one click service
• Fixing or updating existing one click service

Screenshots or Video

Note:
I am currently blocked from running a local Coolify instance due to issues installing and running the ServerSideUp Spin tool on macOS (Apple Silicon). This prevents me from recording a local demo at the moment.

The service template has been implemented following existing Coolify one-click service patterns and project guidelines.

A demo video will be uploaded as soon as I am able to complete a deployment on a working Coolify environment.

AI Usage

• AI is used in the process of creating this PR
• AI is NOT used in the process of creating this PR

AI was used as an assistant. All changes were reviewed, fully understood, and manually validated before submission.

Steps to Test

1. Checkout the next branch and pull this PR.
2. Open Coolify and add a new service.
3. Select WordPress + OpenLiteSpeed from the one-click services list.
4. Deploy the service with default settings.
5. Wait until both containers are healthy.
6. Open the generated service URL.
7. Verify:
   • WordPress installer loads correctly on first visit
   • Core files and configuration are already present
   • Restarting the service does not reinitialize WordPress files
   • Redeploying the service preserves existing data

Contributor Agreement

Important

• I have read and understood the contributor guidelines. If I have failed to follow any guideline, I understand that this PR may be closed without review.
• I have tested the changes thoroughly and am confident that they will work as expected without issues when the maintainer tests them

[Copilot]

Pull request overview

Adds a new Coolify one-click WordPress + OpenLiteSpeed + MariaDB compose template intended for production-style deployments.

Changes:

• Introduces a new compose template that runs OpenLiteSpeed alongside MariaDB.
• Adds bootstrap logic to download WordPress into a persistent volume and generate wp-config.php on first start.
• Configures persistent volumes and basic HTTP healthchecks for both services.

[Copilot]

The container downloads and unpacks WordPress at runtime from https://wordpress.org/latest.tar.gz. This adds an external availability dependency to every fresh deployment and makes installs non-reproducible as “latest” changes over time. Consider using a prebuilt image that already contains WordPress (or pinning to a specific WordPress version and validating the download, e.g., checksum/signature) to improve reliability.

[Copilot]

The bootstrap logic only creates wp-config.php (via wp config create) but does not perform a WordPress core install. Unless the image has additional automation, this typically means the user will still see the WordPress web installer on first visit, which conflicts with the PR description (“No setup wizard is shown”). Consider adding an idempotent wp core install step (and exposing admin user/email/password inputs), or adjust the PR description/expectations accordingly.

[rishi-jat]

@ShadowArcanisgt This time I have followed all the contribution guidelines please let me know if I miss anything ? Thanks!

[rishi-jat]

/cc @enricoangelon

[ShadowArcanist]

I am currently blocked from running a local Coolify instance due to issues installing and running the ServerSideUp Spin tool on macOS (Apple Silicon). This prevents me from recording a local demo at the moment.

The entire Coolify team using macOS with silicon chip for developing Coolify locally, if you are having any issue then please join our https://coollabs.io/discord and share your issue on the "one-click-service" channel.

Also you don't have to run Coolify locally to test templates like these, On your Coolify instance create a new resource and select the option "Docker compose empty" then paste the compose file content and deploy it.

Just a note: I can't promise any timeline for PR merges because only core developers decide if a PR should be merged or not, and they review PRs when they have sometime (please do not ping them)