Since there’s nothing really happening here and it does feel like my contributions aren’t overly welcomed on github either, I’m now using this custom dockerfile to build my home assistant container:
If you decide to replicate this and experience issues, please do not complain to the devs etc etc.
This is unsupported. Your own risk. May break in the future. Whatever
RUN apk add gzip
RUN for i in $(find /usr/local/lib/python3.8/site-packages/hass_frontend/ -iname "*.js.gz"); do zcat $i | sed 's/https:\/\/brands.home-assistant.io/\/local\/brands/g' > "$i.copy"; gzip "$i.copy"; mv "$i.copy.gz" "$i" ; done
RUN for i in $(find /usr/local/lib/python3.8/site-packages/hass_frontend/ -iname "*.js"); do cat $i | sed 's/https:\/\/brands.home-assistant.io/\/local\/brands/g' > "$i.copy"; mv "$i.copy" "$i" ; done
With this, the frontend fetches its icons from
/local/brands/ which works very well.
I just added a
brands folder to my
config/www directory and filled it with the latest build of the brands icons repo
These can be generated by running
git clone https://github.com/home-assistant/brands
and will appear in the
It would be even nicer if the dockerfile could take care of that, but since I’m mapping my config directory into the container, this may lead to issues.
Overall, I’m very sad that I’m repeatedly forced to work around things instead of fixing them at the root. Especially since this works amazingly well. It didn’t even require me to add a custom component which provides another HTTP Endpoint for the brand icons.
I do of course agree that it makes sense for some deployments (e.g. raspberry pis) to not bloat the docker image too much.
Not having the option to self-host it though… well