Use Forgejo workflows and registry
All checks were successful
publish-latest / docker (push) Successful in 9s
ci / test (3.10) (push) Successful in 19s
ci / test (3.12) (push) Successful in 19s
ci / test (3.13) (push) Successful in 19s
ci / container (push) Successful in 7s
publish-image / docker (push) Successful in 8s

This commit is contained in:
Johan Lundberg 2026-07-30 23:35:14 +02:00
parent dbc7464b58
commit e7bde2b3f4
12 changed files with 134 additions and 40 deletions

View file

@ -48,9 +48,14 @@ cp .env.example .env
chmod 600 .env
# Edit .env and set the controller, SNMP credentials, mail server,
# sender, and recipients.
docker compose up -d --build
docker compose pull
docker compose up -d --no-build
```
Tagged releases are published to
`git.snakedesert.se/lundberg/wlc-monitor`. To build the image locally instead,
run `docker compose up -d --build`.
Verify the controller and mail paths:
```bash
@ -226,6 +231,12 @@ docker compose config --quiet
docker build -t wlc-monitor:test .
```
Forgejo Actions runs these checks for pushes and pull requests. Pushes to
`main` publish `edge` and commit-SHA container tags; version tags matching
`v*` publish the version and `latest` tags. Registry publication requires the
repository secret `REGISTRY_TOKEN`, following the same runner setup as the
other projects on this Forgejo instance.
## Contributing and security
Bug reports and pull requests are welcome; see