apps¶
these pages cover what runs on the platform, and why each app is set up the way it is. each page shows its stack's files from git, and the text repeats a fragment only where something is unusual enough to need one.
- every app is a stack in git, at
stacks/<env>/<stack>/compose.yml. portainer deploys it to the swarm or to a standalone host, see stacks in git - the conventions are named binds, digests,
deploy.labels, the time zone and secrets as files. not every stack meets all of them: several images have a tag and no digest, frigate and the arr stack use plain binds, and oauth2-proxy's cookie secret is an environment variable - the swarm page and each standalone host's page list what runs where
| group | apps |
|---|---|
| dns and network | adguard, cloudflare ddns, traefik, nginx proxy manager, oauth2-proxy |
| certificates | acme.sh for the ASRock Rack BMC and Synology DSM |
| media and home | the arr stack, frigate, infinitude, mosquitto |
| web and tools | wordpress, omni-tools, bentopdf |
| swarm plumbing | auto-label nodes |
the monitoring stacks are in monitoring.