Deploy a template
Walk through Deploy from template: pick a stack, choose application and environment, adjust this run only, review, and land on your services.
Deploy from template is the main way to turn a template into running Services inside an Application. Follow the steps at the top of the page; they change depending on whether you create a new Application or Environment or reuse existing ones.
Before you start
- You need permission to view templates and to create Services (and Environments when you add a new one). If you use Create a new application in the wizard, you also need permission to create Applications. If something is blocked, ask an Organisation admin. See Roles and permissions in the sidebar.
- Every app in the template must use a supported Git host: GitHub, GitLab, Bitbucket, Azure DevOps, or Gitea. If an app line is not set up that way, it is left out of this deploy and you see a warning. Database and Docker lines are not affected.
- Existing environment: Only environments on your worker or linked servers appear. Environments on certain dFlow-managed pools cannot be selected here. If none qualify, create a new Environment on a server you control.
- New environment: You pick one server that is not already tied to another Environment (busy servers show In use).
How to open the wizard
- From Templates: click Deploy on an Official or Community card.
- From the menu: open Deploy from template, then use Official, Community, or Personal to pick a template.
- From another page: sometimes the template (and occasionally the Application and Environment) is already chosen so you land closer to the end.
Steps you may see
Pick template (when the template is not fixed yet): choose Official, Community, or Personal, then select one card. The screen shows how many services will deploy.
Target: choose an Application (existing or Create a new application) and whether the Environment is Existing or New.
New application: name (up to 50 characters) and optional description. The app may start as draft until you finish setup elsewhere.
New environment name: quick choices such as Production, Staging, or Development, or a Custom name. Options already used in that application are greyed out.
Compute (for a new environment): pick dFlow compute (your dFlow worker nodes) or Custom compute (other servers you linked), then select a free server. Use Add new server if the list is empty.
Configure: a visual map of the stack. Changes here apply only to this deployment; the library template stays the same. You need at least one service left on the map to continue.
Review: check the template, destination, and a rough size hint (not a bill or a capacity guarantee). Then start the deploy.
If apps were skipped
You might see: N app service(s) skipped (unrecognized or missing git provider). That means one or more Git apps in the template could not be included. Ask the template author to set each app’s Git host correctly in Create template, or pick another template.
Draft application or environment
If the Application or Environment is still in draft, use the buttons the page offers (Complete application setup, Finish environment setup, and similar) and finish the setup flow. When the product supports it, you can return to template deploy afterward.
No environment in the list
If you see No eligible environments, every environment on that app is on compute that does not support this flow. Create a new Environment on your own server, or use another Application that already has one.
When deploy succeeds
You should see Template deployment started and land on the Environment you chose. A draft Application often becomes active after a successful template deploy.
If something still fails
- Nothing to deploy: the template may only contain skipped apps; pick another template or fix the blueprint.
- Server in use: choose a different server or free one up according to your team’s process.
- Error message in a toast: read the text (capacity, conflicts, validation). Template troubleshooting lists common cases.
Next steps
- Environment variables (after deploy tweaks)
- Template configuration (authors and deep detail)