code-server in JupyterHub improvements #209

New issue

Closed

opened 2023-10-10 02:10:14 +00:00 by a · 0 comments

a commented

2023-10-10 02:10:14 +00:00

Owner

I fixed a few long-standing problems with the code-server configuration in JupyterHub.

The command for launching code-server used to contain --user-data-dir=.config/Code - OSS/ --extensions-dir=.vscode-oss/extensions/ which I removed. (This was originally intended so that Code OSS and code-server could share configuration data, but there's no reason to use Code OSS on exozyme) Thus, these two directories have been automatically moved to ~/.local/share/code-server and ~/.local/share/code-server/extensions. (Note: You can find old backups of your home directory in /.snapshots in case something went wrong during the move)
code-server is now configured to bind on a Unix socket in a directory only readable by your current user, which is a better solution to #173 since now passwords are unnecessary.
JupyterHub runs killall -u $USER /usr/lib/code-server/lib/node first to kill any running code-server processes so that they don't accumulate infinitely. (Because the JupyterHub process has systemd sandboxing, I'm not 100% sure this fixes the problem)

I fixed a few long-standing problems with the code-server configuration in JupyterHub. 1. The command for launching code-server used to contain `--user-data-dir=.config/Code - OSS/ --extensions-dir=.vscode-oss/extensions/` which I removed. (This was originally intended so that Code OSS and code-server could share configuration data, but there's no reason to use Code OSS on exozyme) Thus, these two directories have been automatically moved to `~/.local/share/code-server` and `~/.local/share/code-server/extensions`. (Note: You can find old backups of your home directory in `/.snapshots` in case something went wrong during the move) 2. code-server is now configured to bind on a Unix socket in a directory only readable by your current user, which is a better solution to #173 since now passwords are unnecessary. 3. JupyterHub runs `killall -u $USER /usr/lib/code-server/lib/node` first to kill any running code-server processes so that they don't accumulate infinitely. (Because the JupyterHub process has systemd sandboxing, I'm not 100% sure this fixes the problem)