One-click templates

Catalog

15 templates, bundled inside aoox

Result

A compose stack (source: template)

Secrets

Passwords/secrets generated automatically

Catalog

The catalog is written into aoox's own code — it isn't fetched from the internet at runtime, so it still works offline and can't be swapped out by anyone else. All passwords, secrets, and keys are generated automatically (alphanumeric) when left blank.

Notes per template

Templates that need a database ship their own PostgreSQL inside the stack (not a managed database), with named volumes for the data and health checks so the app only starts once the database is ready. Image versions are pinned to a specific tag, not latest. Licenses differ per project; check the project website before using one commercially.

Deploying a template

1. Templates menu → pick a template

   Or, from a project page, click From template so the project is already selected. A search box is available for the catalog.

2. Fill in the deploy dialog

   Section	Notes
   Project & Name	The name becomes the stack's slug; the compose project = aoox-<slug>.
   Hostname per service + HTTPS	One row per exposable service (e.g. RustFS has two: Console and API). Leave blank if you don't want a domain.
   Host port per service	An alternative to a domain: the stack can then be opened at <server-ip>:<port>. Port clashes are rejected when saving — see Stack access.
   Variables	Fields with a label and hint from the template. Ones marked required must be filled in (e.g. Public URL for Ghost/Gitea, Public host for n8n). The rest: blank = default / generated.

   Public URL must match the domain

   Ghost, Gitea, n8n, Grafana, Metabase, Directus, Mattermost, Vaultwarden, and Nextcloud use the public URL/host to build their own links and webhooks. Fill it in exactly matching the hostname you've set up, scheme included (https://blog.example.com) — if it differs, the admin pages/links will point to the wrong place.

3. Deploy

   You're taken to the new compose stack's page. The deploy runs in the background (the first image pull can take a few minutes); watch the Last action log until the status is running.

4. Verify

   Open the hostname you set up. For the initial admin credentials (e.g. the RustFS access and secret keys, DB password), check the stack's env under the Settings tab — generated values are stored there.

Example: WordPress with a domain

Project     : shop
Name        : blog
Service     : wordpress → blog.example.com  [HTTPS ✓]
Variables   : DB_PASSWORD (blank → generated)
              DB_ROOT_PASSWORD (blank → generated)

Once it's running, open https://blog.example.com and finish the WordPress wizard. The MySQL database lives inside the stack (not a managed database) — backing it up is then up to a plugin/script of your own, or move it to a managed database by editing the compose file.

After deploying

• The compose file is stored in aoox and can be edited under the stack's Settings tab (a textarea), then redeployed — e.g. to add a service, change an image tag, or point at a managed database.
• The stack env holds the variable values (including generated ones); change it and redeploy if needed.
• A domain per service can be added/changed via the Domain card; suggested services come from the catalog.
• Stop / Start / Delete work the same as any other compose stack — Delete removes the volume data.

Common pitfalls

Next steps