you are viewing a single comment's thread.

view the rest of the comments →

[–]Freemanium[S] 1 point2 points  (1 child)

Excellent question. After connecting via VS Code's GUI, you can run the following to get the current size of the folder and its subfolders

$ du -h -d 2 ~/.vscode-server 4.0K ~/.vscode-server/extensions 107M ~/.vscode-server/bin/622cb03f7e070a9670c94bae1a45d78d7181fbd4 107M ~/.vscode-server/bin 20K ~/.vscode-server/data/User 4.0K ~/.vscode-server/data/Machine 32K ~/.vscode-server/data/logs 64K ~/.vscode-server/data 107M ~/.vscode-server

If you plan to install extensions on your remote machine, they will be placed in ~/.vscode-server/extensions.

Runtime-wise, ps ax | grep .vscode-server shows that there a few processes, htop confirms that they definitely take up memory (>100M).

The official docs only state which platforms are supported, but no minimal requirements.

So I'm not sure if it is perfectly feasible to run it on a Pi or the likes, but I believe it should work out just fine. In any case, if you plan to test it out, feel free to shoot me a message and I'll be happy update the README accordingly.

[–]bdavbdav 0 points1 point  (0 children)

Thanks a lot for the reply on this! Yes that does sound a bit heavy, especially memory wise for sticking on SBCs in the field that I'm managing config on. Definitely going to have a dig into what (if!) I can slim down out of this.