Templates
Save a set of services as a template and deploy the whole stack into a new environment in one step.
Templates are not generally available yet — the Template entry in the Add menu is greyed out. This page describes how they work for when they ship.
A template is a saved description of one or more services — their images, variables, ingress, config mounts, storage, and healthchecks. Deploying a template creates all of them at once.
Use a template when you set up the same stack repeatedly: a standard app-plus-database pair, an internal tool your team keeps redeploying, or a starting point you hand to new projects.
Deploying a template
- Go to Templates in the top navigation.
- Find the template and click Deploy.
- The services are created in the active environment.
- Review them on the canvas, fill in any variables the template left blank, and click Apply.
Deploying a template stages the services like any other change — nothing runs until you apply.
Creating a template
- Go to Templates and click New.
- Give it a name and description.
- Add each service: its type, image and tag, variables, ingress ports, config mounts, storage, and healthchecks.
- Save.
Visibility
| Visibility | Who can deploy it |
|---|---|
| Private | Only you |
| Workspace | Everyone in the workspace |
| Public | Anyone on Simplifyd Cloud |
Do not put real secrets in a template you set to workspace or public. Leave those variables empty and fill them in after deploying.
Status
A template is draft while you are still editing it, published once it is ready to deploy, and archived when you no longer want it offered but do not want to delete it.
Duplicating and deleting
Use the menu on a template to Duplicate it — handy for making a variant without rebuilding it — or Delete it. Deleting a template does not affect services already deployed from it.
