compose-apps
/compose-apps
Deploy a self-hosted app that ships as a docker-compose file or upstream images (Mattermost, Gitea, Nextcloud, a database). Use when the user wants such an app running for them.
- Author
- xarantolus ↗
- Repository
- botler ↗
- Licence
- MIT
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Deploy a self-hosted app that ships as a docker-compose file or upstream images (Mattermost, Gitea, Nextcloud, a database). Use when the user wants such an app running for them.
Original author description
Deploy a self-hosted app that ships as a docker-compose file or upstream images (Mattermost, Gitea, Nextcloud, a database). Use when the user wants such an app running for them.
How it works
SKILL.md has no level-two headings · 34 lines, 373 words
SKILL.md preview
---
name: compose-apps
description: Deploy a self-hosted app that ships as a docker-compose file or upstream images (Mattermost, Gitea, Nextcloud, a database). Use when the user wants such an app running for them.
---
# Apps from a docker-compose file
There is no `docker compose` here: each compose service becomes one botler service
(`jobs/<name>/job.toml`, `lifetime = "service"`), so each gets the hub's supervision, restarts,
secrets and approvals. Use the upstream images as they are; write a Dockerfile only when the image
really needs changing.
| compose | job.toml |
|---|---|
| `image: postgres:16-alpine` | `from = "docker.io/library/postgres:16-alpine"` (fully qualified, a version tag or digest, never `latest`) |
| `command:` / `entrypoint:` | `command = [...]` (omit for the image's own) |
| `environment:` (plain settings) | `environment = { POSTGRES_DB = "app" }` |
| `environment:` (passwords, tokens) | a secret group: `secrets = ["app-db"]` (ask with `request_secrets`); its keys arrive as environment variables |
| `depends_on:` / reaching `db:5432` | `services = ["app-db"]` in the dependent; it reaches `http://app-db:5432` (or plain TCP) by name |
| `expose:` | `port = 5432` |
| `ports: "8080:80"` | `port = 80` plus `[[publish]] port = 80, host_port = 8080` (asks the user) |
| `volumes: data:/var/lib/x` | `volume = true` mounts one volume at `/data`: point the app there (`PGDATA = "/data/pgdata"`, a config option, or the app's data-dir variable) |
| `healthcheck: test: [...]` | `[health] heartbeat = "1m"`, `grace = "3m"`, `command = [...]` (the hub runs it in the container) |
| `restart: always` | nothing: services always restart |
Name the jobs `<app>` and `<app>-db` and so on. The volume belongs to the job's name
(`botler-job-<name>`): **renaming or removing a job with `volume = true` loses its data**, so keep
the names of anything already deployed. To move a deployed service from a Dockerfile to `from`,
keep its name and check that the image reads its data from the same place under `/data`.
With `from`, the hub hands the volume to the image's own user at every start (Podman's `U`
option), so an image that runs as a non-root user (Mattermost runs as `mattermost`) can write
existing data too. A Dockerfile job's volume is left as it is; don't add `USER root` to get
around that, use `from`.
`trial_run` each service before proposing (its `/data` is empty and thrown away); start the
database first. The first deployment of each service asks the user once.
Versions
The database has no other skills named compose-apps.
Database snapshot: 13.11.2026 · package version 97e1b41be2ce (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90add-service
Use when installing, adding, updating or moving a self-hosted app or container on the homeserver with Docker Compose (Immich, Jellyfin, Plex, Nextcloud, Vaultwarden and others), or when choosing which app fits a need. - 100generating-docker-compose-files
Execute use when you need to work with Docker Compose. This skill provides Docker Compose file generation with comprehensive guidance and automation. Trigger with phrases like "generate docker-compose", "create compose file", or "configure multi-container app". - 100generating-docker-compose-files
Execute use when you need to work with Docker Compose. This skill provides Docker Compose file generation with comprehensive guidance and automation. Trigger with phrases like "generate docker-compose", "create compose file", or "configure multi-container app". - 100nextcloud-webhooks
Receive and authenticate Nextcloud webhooks. Use when setting up a webhook endpoint for the Nextcloud webhook_listeners app, checking the secret header added with authMethod "header", debugging 401s, or handling events like NodeCreatedEvent, NodeWrittenEvent, NodeDeletedEvent… - 100docker-compose-basics
Use when defining and running multi-container Docker applications with Docker Compose YAML configuration. - 100docker-compose
Docker Compose for multi-container apps. Covers services, networks, and volumes. Use for local development environments. USE WHEN: user mentions "docker-compose", "docker-compose.yml", "multi-container", "service dependencies", "docker compose up", asks about "local dev…