I've been interested in doing something like this ever since VSCode remote work has become stable. My main side project right now is a Kotlin backend, so I'm waiting for IntelliJ's very-very-new remote features to get a bit more robust (they just added some abilities for WSL and run targets on remote platforms in early access, but I think you still can't e.g. run your IDE's analysis engine on a remote box and avoid local builds entirely yet). That said, if you're able to live entirely in VSCode & command line, you'd be all set here.It really is wild how the VSCode language server architecture enables all this, btw. I'm not sure whether this was an intentional goal of the LSP when they started working on it, or if it was originally just to keep the language analysis in a separate process and this wound up being a nice benefit, but being able to run all of your editor's language features on another box and just use the editor as a dumb client for them is brilliant.
908B64B197|5 years ago
You can always mount your remote filesystem on your local machine for the few tasks that are not convenient to do in the editor or terminal.
dsissitka|5 years ago