Deploying a template
Deploying a template
A template is a group of pre-connected services, deployed in one click: the application and its database, already wired together (environment variables, internal network, and volumes included).
Deploy in three clicks
- Open Templates in the sidebar (or the Templates tab when creating a service).
- Choose a stack from the catalog (WordPress, Ghost, n8n…)
- Select the destination project, adjust the services' base name if needed, then Deploy.
All the template's services appear on the project canvas, connected to each other. The main service receives a free subdomain that's immediately accessible.
What a template configures for you
| Element | Example (WordPress) |
|---|---|
| The services | MySQL + WordPress |
| The connections | WORDPRESS_DB_HOST, generated password, database created |
| The volumes | CMS content persisted automatically |
| The network | the database is only reachable from within the project |
| The domain | free subdomain ready to use |
Passwords and secrets are randomly generated on each deployment. Nothing is shared between two instances of the same template.
After deployment
The services in a template are normal services: you can change variables, the custom domain, scaling, and logs.
Deleting
Each service in the group is deleted individually, like any other service. Deleting the application service does not delete its database (and vice versa). To remove everything, delete both.