Files
app-catalog-felhom.eu/templates/uptime-kuma/docker-compose.yml
T
admin 35dd5cf03c
gates / gates (push) Successful in 1s
uptime-kuma: 2.4.0 -> 2.5.5, its first ladder step, both venues proven (R-462)
A new front-door fixture: the app's own socket.io messages over plain HTTP polling (setup, login,
addStatusPage), read back through its public /api/status-page/<slug>, with an absent-slug control.
Bench 9401 (harness v4, swap 0): proven, 10-min watch 0 kills (anon peak 43.3 %); the abort starts
and serves. Box 9202: done in 33.9 s through the setup gate, the status page read back.
Written by upgrade-test.py --write-ladder.

Evidence: felhom.eu/documentation/audits/more-night-apps-2026-09-30/

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
2026-09-30 18:51:17 +02:00

53 lines
2.0 KiB
YAML

# Uptime Kuma - Szolgáltatás és weboldal monitoring
# Domain: ${SUBDOMAIN}.${DOMAIN}
# Database: None (file-based)
# RAM: ~50M (mem_limit: 256M) | Pi-compatible: Yes
#
# Environment variables:
# DOMAIN - Your domain (e.g., demo-felhom.eu)
services:
uptime-kuma:
image: louislam/uptime-kuma:2.5.5
container_name: uptime-kuma
restart: unless-stopped
environment:
- TZ=Europe/Budapest
# R-613 (measured 2026-09-23): without this, 2.x parks at its SETUP-DATABASE wizard on first boot
# — the main server never starts, and the probe's any-answer check calls it healthy. With it the
# database choice is made (SQLite in /app/data) and the real server starts: /api/entry-page
# answers entryPage, /metrics 401. An install that already chose keeps its data/db-config.json.
- UPTIME_KUMA_DB_TYPE=sqlite
volumes:
- uptime_kuma_data:/app/data
networks:
- traefik-public
deploy:
resources:
limits:
memory: 256M
# uptime-kuma:2 ships its healthcheck as a compiled binary at /app/extra/healthcheck (WORKDIR /app);
# the old override pointed at a v1-era /app/extra/healthcheck.mjs that does NOT exist in v2, so the
# container stayed permanently "unhealthy" → Traefik withheld the route → the URL 404'd although the
# app was running (F5). Use the correct binary and the image's own timing (180s first-boot window).
healthcheck:
test: ["CMD", "extra/healthcheck"]
interval: 30s
timeout: 30s
retries: 5
start_period: 180s
labels:
- "traefik.enable=true"
- "traefik.http.routers.uptime-kuma.rule=Host(`${SUBDOMAIN}.${DOMAIN}`)"
- "traefik.http.routers.uptime-kuma.entrypoints=websecure"
- "traefik.http.routers.uptime-kuma.tls=true"
- "traefik.http.routers.uptime-kuma.tls.certresolver=letsencrypt"
- "traefik.http.services.uptime-kuma.loadbalancer.server.port=3001"
volumes:
uptime_kuma_data:
networks:
traefik-public:
external: true