DX improvements and updates#25
Conversation
|
Now that were to a fairly stable plateau, I agree that versioning should happen. Give me a few days to get back to this. |
|
I notice this removes the dockerhub publishing. I assume home assistant pulls from ghcr without issue? I deploy to synology and it has trouble with ghcr, so I prefer dockerhub for that. Since I dont build containers localy for development, I may see about building on push, but only pushing to a container registry on release. This would give me an artifact I can get from github to test with, but only publoshing to ghcr and dockerhub on release. |
|
I understand, it was just a suggestion from my side. I personally haven't had any issues with GitHub Registry in Home Assistant or local development. I’ll leave it as is if you already have a plan for how to fix it. |
|
For easier local dev and testing, here’s my flow:
It’s a great setup because "the production" integration stays connected to Home Assistant, while I test my updates in parallel. |
|
Also @BrianHumlicek , I have a question about tests. Since I haven't written a single line of .NET before NeoHub, please go easy on me! 😄 |
@BrianHumlicek — my suggestion is to avoid tagging images as latest.
Using
:latestmakes maintenance harder. For example, in the Home Assistant App it's not possible to bump the app version when the Docker image uses the latest tag. Versioned tags (with semver) allow stable releases and proper version bumps in the app and its integrations.I suggest releasing it as e.g. 0.1.0 — it's early app stage but it works.
I also added GHA cache for Docker layers (on my fork this reduced build time by about 2–3 minutes) and
docker-compose.local.ymlfor local development