Notes on remote-workspace v0.2

[vilicvane]

Major features I would like to have with remote-workspace v0.2:

Possibly multi-node support

Single node makes it relatively hard to scale on demand. Currently we are running on a 16 CPU core / 128G RAM configuration with 9 developers online at the same time. Though there are still room to upgrade for larger teams, but the sky has a limit and it also brings availability issue (might not be a strong argument).

By supporting multiple nodes and scale the deployment dynamically, we might be able to further reduce the cost.

Ability to develop locally

Some of our teammates have desktop computers and want to use their own for performance reason. It would be nice to register their desktop computers and sync the workspace before they get offline.

Possibly related solutions

• docker commit

Robust user management

Currently it's barely able to make things connected and work. Also there would be a problem if two users connect the same remote-workspace at the same time, the later one would share the same code server boot with the information of the first connected user.

Possibly related solutions

• Add Linux user for every remote user.

Workspace image with prebuilt project content

This would make it much faster to boot a remote workspace, as in our case, we are spending more than 1 minutes to pull and prebuild the project.

---

Some stretch goals

Remote USB debugging

Possibly related solutions

• usbip, see also https://github.com/cezanne/usbip-win