The docker-build.yml workflow automatically builds and publishes multi-architecture Docker images for the Code Glue Home Assistant addon.
- Push to
mainbranch: Builds and publishes as:latesttag - Push to
devbranch: Builds and publishes as:devtag with modified config - Tag push (
v*): Builds and publishes versioned releases - Manual trigger: Via workflow_dispatch
-
Main branch builds:
- Uses
config.yamlas-is - Publishes to
ghcr.io/digital-alchemy-ts/code-glue:latest - Suitable for production Home Assistant installations
- Uses
-
Dev branch builds:
- Automatically modifies
config.yamlduring build to:- Change name to "Code Glue (Dev)"
- Set slug to
code_glue_dev(allows side-by-side installation with production) - Set version to "dev"
- Change icon to outline variant
- Update port to 3790
- Point image to
:devtag
- Publishes to
ghcr.io/digital-alchemy-ts/code-glue:dev - Can be installed alongside the production addon
- Automatically modifies
-
Multi-architecture support:
- Builds for:
linux/amd64,linux/arm64,linux/arm/v7 - Covers all Home Assistant supported architectures
- Builds for:
- Add repository to Home Assistant:
https://github.com/Digital-Alchemy-TS/code-glue - Install "Code Glue" addon
- Home Assistant will pull the
:latestimage
- Add repository to Home Assistant:
https://github.com/Digital-Alchemy-TS/code-glue - Install "Code Glue (Dev)" addon
- Home Assistant will pull the
:devimage - Uses separate slug
code_glue_dev- can run alongside production
Since the workflow handles config modifications automatically, you don't need to maintain separate config files:
- Make changes on your branch
- Merge to
devfor testing → workflow builds:devimage - Test in Home Assistant with the dev addon
- Merge to
mainfor release → workflow builds:latestimage