@master resolves to a version that installs Trivy via a nested
setup-trivy composite action, which does an actions/checkout against
github.com with a token. On Gitea's act_runner that fails with "Input
required and not supplied: token" even when the token is explicitly
set to an empty string (act_runner doesn't distinguish empty from
unset). v0.26.0 introduced that composite/setup-trivy split; v0.25.0
is the last release that ships as a self-contained Docker image with
Trivy already baked in, so it needs no token at all.
Co-Authored-By: Claude Sonnet 5 <[email protected]>
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]>
CI invokes the pytest console script directly (pytest tests/ -v), which
unlike `python -m pytest` does not add the repo root to sys.path. That
broke imports of the top-level data_processing/nightscout_client
modules from the test files. Add pythonpath = ["."] so it works
regardless of invocation style.
Co-Authored-By: Claude Sonnet 5 <[email protected]>
gitea.thuis.local doesn't resolve on this network; the real internal
Gitea hostname is gitea.zb.local. Also load .env via python-dotenv so
the app works the same under PowerShell as bash, and add .dockerignore
so .env never ends up baked into the image.
Co-Authored-By: Claude Sonnet 5 <[email protected]>
willemjanandClaude Sonnet 5