A stable version of transmission-web-control has been released.
Rebuilding the docker-transmission-openvpn image should update it.
In the meantime, if you want to get an update in a running container, executing the following will update it:
curl -sL `curl -s https://api.github.com/repos/ronggang/transmission-web-control/releases/latest | jq --raw-output '.tarball_url'` | tar -C /opt/transmission-ui/transmission-web-control/ --strip-components=2 -xz
Hey guys, thanks for nudging this. I've been a bit AFK the last month. But this should have solved itself by now, right?
Latest tag is built 6 days ago, dev is built 2 days ago. Or do you think I should tag a new release?
When I manually pull a new "latest" it does update, and yes, it seems fixed.
Oh, and to answer your last question, it's probably worth tagging a minor or patch release so people will know that something noteworthy changed. I don't know what formally changed in this version of transmission-web-control, but anecdotally it seems much more well behaved than the previous version.
Solved for me as well :-)
Most helpful comment
In the meantime, if you want to get an update in a running container, executing the following will update it: