konnosuptime.yml38 lines · main
| 1 | # Uptime Kuma dashboard router. Uptime Kuma itself lives as a Docker |
| 2 | # swarm service (briven-uptime-kuma) on dokploy-network, exposed |
| 3 | # externally via this Traefik dynamic config. |
| 4 | # |
| 5 | # Deploy path: |
| 6 | # scp infra/traefik/uptime.yml \ |
| 7 | # root@187.124.64.116:/etc/dokploy/traefik/dynamic/uptime.yml |
| 8 | # |
| 9 | # TLS: single hostname, served via the existing letsencrypt resolver |
| 10 | # (HTTP-01 challenge). DNS for dev-uptime.briven.tech is set to |
| 11 | # DNS-only (grey cloud) on Cloudflare so Let's Encrypt can reach the |
| 12 | # origin on port 80 during the challenge. |
| 13 | |
| 14 | http: |
| 15 | routers: |
| 16 | briven-uptime-kuma-web: |
| 17 | rule: "Host(`dev-uptime.briven.tech`)" |
| 18 | entryPoints: |
| 19 | - web |
| 20 | service: briven-uptime-kuma-api |
| 21 | middlewares: |
| 22 | - redirect-to-https |
| 23 | |
| 24 | briven-uptime-kuma-websecure: |
| 25 | rule: "Host(`dev-uptime.briven.tech`)" |
| 26 | entryPoints: |
| 27 | - websecure |
| 28 | service: briven-uptime-kuma-api |
| 29 | middlewares: [] |
| 30 | tls: |
| 31 | certResolver: letsencrypt |
| 32 | |
| 33 | services: |
| 34 | briven-uptime-kuma-api: |
| 35 | loadBalancer: |
| 36 | servers: |
| 37 | - url: "http://briven-uptime-kuma:3001" |
| 38 | passHostHeader: true |