Is your feature request related to a problem? Please describe.
Having to run metals backend or sbt jobs running using LSF is necessary for some environments where users ssh to login servers and launch jobs from there. This creates a complexity where VS Code remote is only available through the login servers; however, running hundreds of sbt, or Java instances in those machines is not ideal. VS Code extension could allow the user to choose LSF or a separate machine for the Metals backend.
Describe the solution you'd like
Having the ability to run the sbt metals backed in other machines either by providing an ssh tunnel or LSF.
Describe alternatives you've considered
The login servers are the only gateways to the server clusters. There is no alternative for this poblem.
Is your feature request related to a problem? Please describe.
Having to run metals backend or sbt jobs running using LSF is necessary for some environments where users ssh to login servers and launch jobs from there. This creates a complexity where VS Code remote is only available through the login servers; however, running hundreds of sbt, or Java instances in those machines is not ideal. VS Code extension could allow the user to choose LSF or a separate machine for the Metals backend.
Describe the solution you'd like
Having the ability to run the sbt metals backed in other machines either by providing an ssh tunnel or LSF.
Describe alternatives you've considered
The login servers are the only gateways to the server clusters. There is no alternative for this poblem.
Additional context
No response
Search terms
remote backend, ssh, LSF, bsub