1
Support web socket timeout env variable
Source: louislam/uptime-kuma#7839 · opened by @mayberryjp
📑 I have found these related issues/pull requests
did not see anything related
🔖 Feature description
The websocket timeout is 15 or 20 seconds but its not configurable. it downloads a ~30k file for every monitor it appears. on low bandwidth links, that may take a second per monitor.
you can start to see the problem -- the socket times out, pages reloads.
<img width="463" height="580" alt="Image" src=" />
✔️ Solution
support a configurable socket timeout that can be passed through container ENV variables e.g: docker compose. that's the request.
❓ Alternatives
can not figure out any other option
📝 Additional Context
_No response_
did not see anything related
🔖 Feature description
The websocket timeout is 15 or 20 seconds but its not configurable. it downloads a ~30k file for every monitor it appears. on low bandwidth links, that may take a second per monitor.
you can start to see the problem -- the socket times out, pages reloads.
<img width="463" height="580" alt="Image" src=" />
✔️ Solution
support a configurable socket timeout that can be passed through container ENV variables e.g: docker compose. that's the request.
❓ Alternatives
can not figure out any other option
📝 Additional Context
_No response_
No pledges yet. Be the first to back this.
No comments yet.