DEPLOYING

The marketplace

One-click templates for common services — databases, dashboards, tooling — preconfigured for DockBoard.

Thirty services you can install in one click — already wired for DockBoard, with the ports, volumes and variables set the way they need to be. It saves you writing a Compose file for software whose Compose file has been written ten thousand times.

What is in there

Category	Templates
Databases	PostgreSQL, MySQL, MongoDB, Redis — and the clients: DBGate, Adminer, phpMyAdmin, pgAdmin, Mongo Express, RedisInsight.
DevOps	Portainer, Grafana, Uptime Kuma, Gitea, FlareSolverr.
CMS	WordPress, Ghost, PrestaShop.
Storage	MinIO, Nextcloud.
Email	Roundcube, SnappyMail, Mailpit — the webmails and the catch-all for development.
Dev	Code-Server, 9Router.
Other	n8n (automation), Vaultwarden (passwords), Plausible (analytics), Plex and Jellyfin (media).

The database templates run a database as an application. For one DockBoard manages — with credentials, backups and lifecycle handled for you — use databases instead. The marketplace entry is for the case where you want the container and nothing around it.

Installing

01Pick a template and the project to install it into.
02Fill in whatever it asks for. Most templates ask for nothing; some want an initial admin password, and leaving that blank generates a strong one and shows it once.
03Install. The result is a normal application: same logs, same restart controls, same domain attachment, same deletion.

Installed services join the project network, so your own applications reach them by name without publishing a port. A Grafana installed next to your API needs no public address to scrape it.

Installing needs the marketplace:install permission, which the developer role holds. Ports are allocated by the same authority that assigns them to applications, so a template can never land on a port that is already taken — or on one DockBoard reserves for itself.

Your own Compose file

The marketplace also takes a Compose document you supply, installing it the same way as a shipped template. Convenient — and it is the one place where a tenant hands the platform a document that says what to run.

So it is screened. Host-escape primitives are refused outright, with the offending line named:

privileged: true and added capabilities.
Host namespaces — pid: host and its relatives.
Mounting the Docker socket, or the host root, into a container.

This screen is not cosmetic. Without it, anyone who can install into a project could reach host root from inside a container — which would make the whole project permission model decorative. The same check runs on every other path where a Compose document enters the platform, so there is no cheaper door around it.

Afterwards

A marketplace install is not a managed subscription — DockBoard does not update the service for you. It is your application from that point on: you choose when to move to a newer image tag, and its data lives in volumes that survive that move.

Anything holding data you care about — Vaultwarden, Nextcloud, Gitea — deserves a backup schedule the day you install it, not the day you need one.