Deploy from a template

One-click deploys of software that is already configured.

A one-click deploy of software that is already configured: WordPress, Ghost, n8n, Plausible, Supabase, MinIO, Uptime Kuma and a few hundred more. Pick it, name it, and it starts with generated passwords.

The catalogue is an online service, so new entries appear without updating Deplo. A template has one or more variants: a docker-compose.yml plus its description and screenshots.

Deploy one

Find what you want

Open Templates in the sidebar (on a phone, under More), or the Template tile in the new-app wizard. The page has Featured templates, Search templates, categories and collections. All templates lists the whole catalogue A to Z.

The template catalogue with its categories

Pick a variant

With several variants, Choose a variant next to Deploy switches between them. Click Deploy.

One template page: variants

Fill in the wizard

The new-app wizard opens already filled in. Set the App name, read any notice at the top, then open Advanced:

  • Deploy to: the server.
  • Environment variables, Edit variables: passwords are generated, and anything the template needs from you is listed here.
  • Compose, Edit compose: change the stack before it runs. Copy the original first: there is no way back.

Click Deploy, or open the arrow next to it for Create without deploying.

After it is running

It is a normal Compose app, and yours to change: edit the Compose file, the variables, the domains. Volumes, Backups and Logs all work. A domain names the Container it routes to, and there is no rollback.

Good to know

  • Updating the catalogue entry does not update apps you already created from it.
  • Read the variables before you deploy. Some templates need a domain or an admin email at first start, and keep the first value they get.
  • A template can include configuration files. They show up under the app's storage.
  • The same template twice in one Environment and server clashes on service names like db. The wizard shows Names already in use and offers Rename and deploy, which renames the clashing services. To pick your own names, cancel and edit the stack under Advanced. See Network isolation.
  • Browsing is open to anybody on the team. Deploying needs create_apps.
  • If the catalogue is unreachable, apps you already deployed keep working.
  • The names and logos in the catalogue belong to their owners. Listing them is not an affiliation or an endorsement.

Troubleshooting

SymptomWhat to check
The template catalog is unreachableThe instance cannot reach the catalogue service. Check its outbound network access, or point DEPLO_TEMPLATES_API_URL at your own mirror.
One container keeps restartingUsually a required variable was left blank. Read that container's logs.

More in Deploys and builds.

Next steps

Did this page help you?

On this page