Content management deployment templates
Publish websites and manage content. Database services and uploaded files have separate persistence needs; review both before deploying a CMS.
22 templates · Page 1 / 1
ClassicPress with MariaDB
ClassicPress with MySQL
ClassicPress without Database
Cockpit
Directus
Deploy Directus on Polyer to manage content and data through an admin app with generated REST and GraphQL APIs. This template runs one directus/directus:11 service with SQLite; the database file, uploads and extensions live on its volume. Review the admin sign-in and the CORS origin input before deploying.
Directus with PostgreSQL
DokuWiki
Drupal with PostgreSQL
Ghost
Deploy Ghost on Polyer to run a publishing platform for blogs, newsletters and membership sites. This template runs ghost:5 and a private MySQL 8.0 service, with Ghost's images and themes and the MySQL data on separate volumes. Before deploying, set the MySQL database input to ghost and review the SMTP inputs.
Joomla with MariaDB
MediaWiki
Moodle
Nitropage
Nitropage with PostgreSQL
Vvveb
Vvveb with MariaDB
Vvveb with MySQL
Wiki.js
Deploy Wiki.js on Polyer to run a wiki for team documentation and knowledge bases. This template runs ghcr.io/requarks/wiki:2 with a private PostgreSQL 16 service; pages, uploads and settings live in the database volume, and Wiki.js itself has no volume. Review this layout and run the setup wizard right after deploying.
WordPress with MariaDB
Deploy WordPress with a separate MariaDB service for a website or blog. This template includes both the application and its database. Uploaded files and database records need separate persistence and recovery checks.
WordPress with MySQL
WordPress without Database
How to choose
- For a blog or newsletter, Ghost runs 2 services and includes memberships, but bulk newsletter email needs a Mailgun account. WordPress, ClassicPress and Joomla extend broader sites with themes and extensions.
- If a frontend or app reads content through an API, choose a headless CMS. Directus generates REST and GraphQL APIs, with SQLite in one service or PostgreSQL in 3; Cockpit runs as one service.
- For documentation, DokuWiki stores pages as plain files and MediaWiki uses SQLite, each in one service. BookStack and Wiki.js add a database service; Wiki.js can also sync pages to a Git repository.