Using templates — Rumus Cloud

What a template is

A template describes a service completely: image and tag, ports, volumes, health check, and the variables that must be provided. Deploying one asks only for what it cannot guess.

rumus template list --category database
rumus template show postgresql
rumus deploy create postgresql --project billing-service --name db

Variables

Required variables are validated before the container starts, so a missing password is reported in the interface rather than in a crash loop.

Template	Required	Optional
postgresql	POSTGRES_PASSWORD	POSTGRES_DB, POSTGRES_USER, shared_buffers
redis	—	REDIS_PASSWORD, maxmemory, maxmemory-policy
n8n	N8N_ENCRYPTION_KEY	WEBHOOK_URL, timezone, database connection
wordpress	WORDPRESS_DB_HOST, WORDPRESS_DB_PASSWORD	table prefix, debug flags

Volumes

Templates declare where data lives. Volumes survive redeployment, and expanding one does not interrupt the service. A stopped service keeps its volume and keeps billing for it.

Version pinning

Templates carry a pinned version. Patch releases within the same minor are advanced for you and announced in the changelog. Major versions require an explicit change, because they usually need a migration.

Before a major version change. Take a snapshot, read the upstream release notes, and deploy the new major to a second service first. The platform keeps both running so you can compare before switching.