Daniel Maksymilian Syrnicki
f377a5a387
louislam/uptime-kuma:1 with one data volume and port 3001. Admin account bootstrapped from the first browser visit to :3001 — no Furtka settings form needed. Catalog release 26.7-alpha. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
29 lines
1,003 B
YAML
29 lines
1,003 B
YAML
# Furtka Uptime Kuma — self-hosted status monitor.
|
|
#
|
|
# The volume `furtka_uptime-kuma_data` is created by the Furtka reconciler
|
|
# from the manifest's "volumes" list before this compose file is brought
|
|
# up; it's declared `external: true` here so docker compose doesn't try
|
|
# to manage its lifecycle.
|
|
#
|
|
# Image pin: `louislam/uptime-kuma:1` tracks the 1.x major and rolls new
|
|
# patch/minor releases in place. Good enough for now — revisit to a
|
|
# digest once the Furtka app-update UI reports a diff so users can see
|
|
# what moved.
|
|
#
|
|
# No admin bootstrap via env vars: Kuma creates its admin account from
|
|
# the first browser visit to :3001. That's a deliberate Kuma design
|
|
# choice, and it's why this app has no manifest.settings — nothing for
|
|
# the Furtka install form to ask.
|
|
|
|
services:
|
|
kuma:
|
|
image: louislam/uptime-kuma:1
|
|
restart: unless-stopped
|
|
ports:
|
|
- "3001:3001"
|
|
volumes:
|
|
- furtka_uptime-kuma_data:/app/data
|
|
|
|
volumes:
|
|
furtka_uptime-kuma_data:
|
|
external: true
|