Pre-checks
What problem does this solve?
Clawith's release process builds backend and frontend containers for private deployment, but it does not publish official public images. Docker Compose therefore builds both applications locally, which makes first-time installation and updates slower and requires a complete build toolchain.
Proposed solution
Publish the existing backend and frontend Dockerfiles to GitHub Container Registry when a GitHub Release is created. Publish linux/amd64 and linux/arm64 variants under the release tag, update latest only for the latest release, and let the default Docker Compose file pull those images while keeping --build available for local source builds.
Document the one-time GHCR visibility setup and the release behavior.
Willing to contribute?
Pre-checks
What problem does this solve?
Clawith's release process builds backend and frontend containers for private deployment, but it does not publish official public images. Docker Compose therefore builds both applications locally, which makes first-time installation and updates slower and requires a complete build toolchain.
Proposed solution
Publish the existing backend and frontend Dockerfiles to GitHub Container Registry when a GitHub Release is created. Publish linux/amd64 and linux/arm64 variants under the release tag, update latest only for the latest release, and let the default Docker Compose file pull those images while keeping --build available for local source builds.
Document the one-time GHCR visibility setup and the release behavior.
Willing to contribute?