Files
app-catalog-felhom.eu/templates/uptime-kuma/docker-compose.yml
T
admin 28ce33baf1
gates / gates (push) Successful in 1s
Revert "LIVE-TEST (controller v0.237.0 slice 4), REVERTED IN THE SAME SESSION: uptime-kuma 2.4.0 -> 2.3.2"
This reverts commit 01c631d — and is itself the real catalog tag change (2.3.2 -> 2.4.0) that
Scenario A of the slice-4 live validation updates the deployed throwaway across. catalog_since is
back to its original value.

Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
2026-09-13 12:07:28 +02:00

48 lines
1.6 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.4.0
container_name: uptime-kuma
restart: unless-stopped
environment:
- TZ=Europe/Budapest
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