Disconnect WebSocket if user is idle for 1 hour

[nhooyr]

See #1274 (comment)

[antofthy]

Depends on what you mean by idle.

In our case idle is when the web socket is NOT being used, in which can we want to terminate the containing docker environment. We do this by watching the "heartbeat" file.
#1050

We do not want to disconnect if the user keeps his browser open to code-server, though I can see that some users/developers would like that.

Also what do you mean by disconnect? Logout the user so they need to re-type the password? Terminate Code-server?

[nhooyr]

So this is independent of the heartbeat file. I think if someone leaves code-server open on their desktop for like 6 hours but does nothing, we shouldn't keep the WebSocket up, we should just disconnect the WebSocket.

Disconnect just means drop the WebSocket.

[coadler]

Maybe we could make this an option?

--idle-timeout=1h

[antofthy]

As long as it is clear in the doc's.

Mind you I don't think the "heartbeat" file is documented either, except here in git "issues".
Hmmm... Nope, the only mention of heartbeat in the git download is in the "server.ts" code.

Looks like a case of "Use the source, Luke!" :-)

[nhooyr]

Yea we really need to document that.

[antofthy]

Even if the option was provided, it is more likely we will continue to use the heartbeat file, as we monitor it from outside the docker instance, and shutdown the docker instance completely when we reach our time out. That is we need to do more than shutdown the web socket on timeout.

So just the heartbeat file needs to be documented. Where ever that is done.

[nhooyr]

Yea I agree, the websocket will disconnect naturally anyway since their computer will just go to sleep if they leave it on for an excessive amount of time.

[nhooyr]

It's documented now.

https://github.com/cdr/code-server/blob/9a3b9fcac23e6bd7f01e46bae94ea7c017bbc0f7/doc/FAQ.md#heartbeat-file