spantaleev/matrix-docker-ansible-deploy
1
0
Fork 0
mirror of https://github.com/spantaleev/matrix-docker-ansible-deploy.git synced 2026-07-30 18:53:04 +10:00
Code Issues Packages Projects Releases Wiki Activity

Explain where the beeper-line container image comes from

Browse Source 
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Slavi Pantaleev
2026-07-28 21:48:40 +03:00
parent 4e95cecf81
commit fa59dde084
2 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/configuring-playbook-bridge-beeper-line.md
+5 -1
View File
@@ -36,7 +36,11 @@ matrix_bridge_beeper_line_enabled: true
### Using another container image
The playbook uses `docker.io/crispyduck/beeper-line` by default. To use an image that you have built and published elsewhere, override the complete image name:
Upstream does not publish container images publicly, as its CI only pushes them to Beeper's private registry. The playbook therefore uses [`docker.io/crispyduck/beeper-line`](https://hub.docker.com/r/crispyduck/beeper-line) by default, which is a community-maintained image built from the upstream source.
That image is only available for the amd64 architecture. On other architectures, the playbook self-builds the image from source automatically.
To use an image that you have built and published elsewhere, override the complete image name:
```yaml
matrix_bridge_beeper_line_container_image_self_build: false