Databases Templates

This inventory describes the v2.12.8 source manifests in the databases category. Available means the manifest is not marked Coming Soon; it is not proof of a successful deployment, a current browser card, or a security review. The browser's unfiltered catalog is paginated; use category/search controls to find an entry. See Template System.

Template List

Before deploying

Select an available card and review its current variables, image/source version, resource limits and application instructions. Coming Soon entries cannot be deployed. Minimum memory is a declared requirement, not a capacity guarantee. Required password inputs and generated system secrets are different: a blank password field does not automatically generate a value.

Use Template Deploy for the deployment steps and Template Authoring for the manifest schema. Container health checks report readiness; they do not by themselves restart a hung application or provide automatic image/security updates.

Database operation

The manifests declare their own variables and volume paths. PostgreSQL uses POSTGRES_DB; MySQL uses MYSQL_DATABASE. Redis declares a password-protected server command; the manifest does not configure the previously documented AOF, LRU eviction or fixed snapshot schedule. Configure database behavior deliberately.

Qdrant declares a generated API key, a /qdrant/storage volume and HTTP exposure on port 6333 for its REST interface/dashboard. Database TCP access and service network reachability must be arranged for the consuming application; an HTTPS service link is not a SQL protocol proxy. Do not assume arbitrary services can reach each other by the display name.

The panel backup worker is not a universal database backup system: it invokes PostgreSQL tooling or archives /data in the first container. Read the backup coverage, restore and retention warnings and arrange recovery for the actual database and volume paths.