escoand
escoand
@nicolargo As you already have travis integration you could use https://docs.travis-ci.com/user/build-stages/share-docker-image/ as an extension. Your `dev` images are already multi-arch, couldn't you copy the workflow?
@BlackDark I would like to have it similar to https://github.com/nicolargo/glances/blob/develop/docker-files/Dockerfile but without all the gcc thingy...
I've no strong feelings against debian. My request was just to have a small stable image for my productive usecase. So I'm completly fine with your result so far.
@BlackDark Thanks.
I'm quite impressed by the final size. Fantastic and both are working with my simple setup.
Ok, maybe we have to wait a bit for HTTP/2 support evolves. The comments say the nginx doesn't have this image problems. Hopefully the performance will get better as well....
Oh fine, good to hear that. I walked through my issues without any reactions since months and cleaned my list a bit. Sorry for the inconveniences.
> If you want to test if your function is already working with different parameters, you can do it by simply quering another parameter at the display of the controller...
@fredlcore As far as I can see is BSB-LAN providing a history for some/important/any values. They need to get polled from the bus as well, or how is this done?...
Sure. I wasn't aware of how BSB-LAN works. So my idea would end in just sending other (or additional) MQTT telegrams than today.