DevTools Templates
This inventory describes the v2.12.8 source manifests in the devtools 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
| Template ID | Source availability | Minimum CPU cores | Minimum memory MB |
|---|---|---|---|
code-server | Available | 1 | 1024 |
drone | Available | 1 | 256 |
gitea | Available | 1 | 256 |
minio | Available | 1 | 512 |
n8n | Available | 1 | 512 |
registry | Available | 1 | 256 |
uptime-kuma | Available | 1 | 128 |
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.
Application accounts and data
Follow the selected application's first-login instructions. The application's account and the panel's Keycloak login are separate unless an explicit integration is configured. A template's existence does not enable every upstream feature, configure external runners/providers, or certify compliance.
Review named volumes and external dependencies before changing or retiring a service. Plan application-specific backups and inspect the backup/restore limitations.