orrious

Hi folks, I just received 10x superbrightleds.com G4-RGBW3W. To my surprise they are running 3.4. Please let me know which branch to pull and what debugs you would like.

https://www.superbrightleds.com/moreinfo/miniature-and-subminiature-bulbs/g4-led-smart-bi-pin-bulb-rgbw-color-changing-hubless-alexa-google-assistant-wi-fi-compatible-bluetooth-controller/6977/18351/ ``` # python3 -m tinytuya scan TinyTuya (Tuya device scanner) [1.6.4] [Loaded devices.json - 6 devices] Scanning on UDP ports 6666 and 6667 for devices (21 retries)... Walkway-02 Product...

Due to not being able to tuya-convert these devices to my own firmware, I've no choice but to run them on an isolated network. That said, it makes it easy...

When implementing, please provide support for both `PROXY` and `PROXYv2` protocols. DNSDIST has implemented as well and can be used for reference. https://dnsdist.org/advanced/passing-source-address.html#proxy-protocol

Yes, I used the provided docker-compose. My experience was when I first started the container, it created config.json as a directory rather than a file. Docker has no idea if...

I wouldn't move it to the /data dir. Create a new dir called /config and put it there. If you ever needed to add a new required key, you can...

So it's not a breaking change, in the Dockerfile, you can create a symbolic link from `/app/config.json` to `/app/config/config.json`. Then you can point at either location for a couple releases.

Has there been thought into only releasing containers in the future? You can make whatever changes you like in the container from one release to another.

Also, if defaultConfig.json is for adding new keys, why didn't it fill everything in with a blank file? When I touched `config.json` it still crashed. If we can get it...

With a symbolic link `ln -s /app/config/config.json /app/config.json`, it doesn't matter which you access, it's the same object that is being accessed / modified. How would this break the application?