3 ms·
> Modern IDEs tend to support SSHing out to remote hosts to perform builds there, so as long as you're ok with source code being visible on laptops you can at l
by 8organicbits 4y ago
> Modern IDEs tend to support SSHing out to remote hosts to perform builds there, so as long as you're ok with source code being visible on laptops you can at least shift the "I need a workstation with a bunch of CPU" problem out to the cloud.
I'd mention SSH port forwarding in this section. For webdev you'll want to run your server on the remote host and use the local web browser. SSH port forwarding works great for this. I recently used this setup to get some extra RAM for a short project that could only be run as a collection of memory hungry microservices. This way I could get the whole thing running on one box; I spun down the server once the project was done.
- pwarner 4y agoI get a sense this model is the future, but also don't know if anyone using it at scale? Any examples out there?
- easton 4y agoGitHub uses it internally (using their Codespaces product, which also just lets you SSH directly into the VM it creates): https://github.blog/2021-08-11-githubs-engineering-team-moved-codespaces/ https://github.blog/2021-08-11-githubs-engineering-team-move...
- qw 4y agoJetbrains has support for remote development environments. I haven't tried it myself, but it looks promising. https://www.jetbrains.com/remote-development/ https://www.jetbrains.com/remote-development/
- MarkSweep 4y agoI can confirm that using JetBrains Gateway to run IntelliJ is more pleasant than using Chrome Remote Desktop, X11 forwarding, JetBrains projector, or Xpra.
- sz4kerto 4y agoExcept it's still buggy like hell.
- MarkSweep 4y agoI should have said, being better than those alternatives is a very low bar.
- nsm 4y agoIs there a way in JB Gateway to re-use an existing project? I am in the office 50% of the time, working on my desktop with CLion. The other 50% I'm remote. The one time I tried Gateway, it asked me to create a new project, which meant building another index of a giant codebase, and not having any of my per-project settings. The time and disk space of another index turned me off right away. I couldn't find a way to just re-use the existing project. So for now I just suffer through using NoMachine to remote in, and then operate CLion.