Goal
Deploy a template-backed stack with the right operational expectations.Prerequisites
- A healthy node
- A published template
Workflow
What the template detail page gives you before deploy
- Current version, screenshots, docs link, and release notes
- Input counts for required and secret fields
- Operational confidence notes including backup readiness and named-volume posture
Deploying
Deploying a template renders it into a stack, so the placement choices are the same as any stack: least_loaded or a manual target node, optionally constrained by node selector tags. Supply the required inputs and secrets, review the rendered summary, and apply.After deploy
The result is a template-backed stack that records its version and inputs. From there it is managed through the template lifecycle — preview and apply upgrades rather than editing the rendered stack by hand, so provenance stays intact.Expected result
A template-backed stack is created and ready for lifecycle management.
Related guides
What templates are
Templates are versioned service blueprints that render into stacks with saved inputs and provenance.
Template inputs and secrets
Understand which template values are required, which are sensitive, and how they affect rendering and upgrades.
Updating template-backed stacks
Preview diffs, resolve missing inputs, and apply the latest published template version safely.