I think a common issue preventing folks from using this was the fact that a websocket and webserver port are both required, it made reverse proxies more challenging than they should be.
With this release, I included nginx and if accessed through port 80 (internal ofc), all traffic will travel through that port. The container's nginx and the program will identify that they are behind nginx and use a /ws endpoint on port 80.
At the same time, I did not want to introduce a breaking change, and so, you can continue to expose ports 8080 and 8765 if they are set up and working. They will continue to work in the way that they have. They will see that they are not behind nginx and not rely on the /ws endpoint, instead accessing the necessary ports directly.
So, this hopefully does not introduce a breaking change, but let me know if it does.