glucose-dashboard/docker-compose.yml at 11489bccdd1fe69d9363fd2e9089cd3337d0897e - glucose-dashboard - Gitea: Git with a cup of tea

willemjan/glucose-dashboard

Files

T

willemjanandClaude Sonnet 5 e0d6b79e68 use the working duckdns hostname for the registry, fix trivy github auth

gitea.zb.local resolves but is plain HTTP, which Docker refuses as a
registry without daemon-level insecure-registry config. gitea.zb.lan
resolves but nothing answers there yet (proxy not configured for it).
gitea.zb-kw.duckdns.org is confirmed reachable end-to-end over HTTPS,
including the registry v2 API, from both the runner and the deploy
target, so use that consistently. Also fix aquasecurity/trivy-action's
token-setup-trivy input, which defaults to gitea.token and gets
rejected by github.com when it tries to clone the install script.

Co-Authored-By: Claude Sonnet 5 <[email protected]>

2026-07-25 22:02:53 +02:00

10 lines

307 B

YAML

Raw Blame History

 services:
   glucose-dashboard:
     image: gitea.zb-kw.duckdns.org/willemjan/glucose-dashboard:latest
     container_name: glucose-dashboard
     restart: unless-stopped
     ports:
       - "8501:8501"
     env_file:
       - .env # zie .env.example — NIGHTSCOUT_URL + NIGHTSCOUT_TOKEN of NIGHTSCOUT_API_SECRET