Align Docker release workflow with the ebooks project's registry setup
Docker Image bauen und veröffentlichen / docker (push) Successful in 20m29s
Docker Image bauen und veröffentlichen / docker (push) Successful in 20m29s
Switch from a dynamically-derived registry/GITHUB_TOKEN login to the same pattern already proven in the ebooks project: a fixed git.arnef.de/arnef/nidus registry/image, docker/login-action with REGISTRY_USERNAME/REGISTRY_PASSWORD repo secrets, docker/metadata-action for tag/label generation (version, major.minor, latest, short SHA), and a final buildx/system prune cleanup step. Also add a manual workflow_dispatch trigger. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
@@ -108,14 +108,16 @@ docker compose exec davserver nidusctl -config /app/config.yaml addressbook crea
|
||||
Pushing a version tag (e.g. `v1.2.3`) or publishing a release triggers
|
||||
[`.github/workflows/docker-release.yml`](.github/workflows/docker-release.yml),
|
||||
which builds and publishes a multi-arch (`linux/amd64` + `linux/arm64`)
|
||||
image to this repository's own container registry, tagged with both the
|
||||
version and `latest`. Point `docker-compose.yaml`'s `image:` at it instead
|
||||
of `build: .` to use it directly, e.g.:
|
||||
image to `git.arnef.de/arnef/nidus`, tagged with the version, `<major>.<minor>`,
|
||||
`latest`, and the short commit SHA. It authenticates via the
|
||||
`REGISTRY_USERNAME`/`REGISTRY_PASSWORD` repository secrets. Point
|
||||
`docker-compose.yaml`'s `image:` at it instead of `build: .` to use it
|
||||
directly, e.g.:
|
||||
|
||||
```yaml
|
||||
services:
|
||||
davserver:
|
||||
image: <registry>/<owner>/<repo>:latest
|
||||
image: git.arnef.de/arnef/nidus:latest
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
Reference in New Issue
Block a user