- Use vscode ssh-tunnel. I don't enjoy editing with vscode but this is imo the smoothest experience. If there is latency between your machine and the cluster, you won't notice it because the editing is actually done to local files, with vscode very regularly syncing those local files with the copies on the cluster
- Run a very lightweight editor directly in the cluster (eg neovim) and just edit directly on the cluster in a single cpu job. For the very rare time I'm editing while not connected to the internet. I'll just git pull locally (as if me and editing locally and me editing on cluster are like two different devs). Requires a good connection to the cluster otherwise it will feel laggy
Ways I edit files on a cluster :
- Use vscode ssh-tunnel. I don't enjoy editing with vscode but this is imo the smoothest experience. If there is latency between your machine and the cluster, you won't notice it because the editing is actually done to local files, with vscode very regularly syncing those local files with the copies on the cluster
- Run a very lightweight editor directly in the cluster (eg neovim) and just edit directly on the cluster in a single cpu job. For the very rare time I'm editing while not connected to the internet. I'll just git pull locally (as if me and editing locally and me editing on cluster are like two different devs). Requires a good connection to the cluster otherwise it will feel laggy