How to install ruby-lsp if application runs in VM/Docker and VSCode runs on host?

[tisba]

In my setup, for many projects, I run VSCode on macOS and my application runs either in Docker or another VM (using some file sharing mechanism).

Unless I'm overlooking something, I don't quite know how am I supposed to install ruby-lsp in this case. In case that's not supported, that might be worth a note in the README.

[vinistock]

If you add the ruby-lsp to the application's bundle, does it not work? Is there anything printed to the Ruby LSP's channel in the output tab?

[tisba]

Sorry, I should have said that from the beginning 🙈 Yes, I can add it to the Gemfile and it works.

The Gemfile is massive and optimized/configured for a Linux environment (b/c it runs in Docker or a VM). I would have to install a lot of other dependencies to be able to build all the native extensions. Also, not everybody on the team uses VSCode (or ruby-lsp) for that matter.

Anyway, is there an option to specify a different Gemfile maybe?

I'd be also interested in the reasoning for having ruby-lsp managed by bundler.

PS: no offense btw, I'm well aware that ruby-lsp is an opinionated LSP and purpose build for Shopify's use :)

[CKolkey]

You can specify a different gemfile for bundler. Here's what I use for work: https://gist.github.com/CKolkey/bf0bef4fa931e75d635e91b12d0c188a

If you need to update the real gemfile for any reason, remember to prefix BUNDLE_GEMFILE=Gemfile

[tisba]

wow, thank @CKolkey! I totally forgot about that bundler feature! Any idea how to make VSCode/ruby-lsp pickup custom environment variables? 🤔 By setting BUNDLE_GEMFILE=Gemfile.dev and just have ruby-lsp in there, I could sidestep the problem of having to install a truckload of stuff, that I don't even need.

[CKolkey]

Not sure about the vs-code stuff (neovim user). Maybe something like https://direnv.net/ will work? And/or if you launch vs-code from the shell via code? Just guessing there.

[vinistock]

There's some more information about the need to include the Ruby LSP in the bundle in #1475 and a proposal for another alternative in #1496.

TL;DR: using a global installation makes it difficult to deal with RuboCop extensions and can result in different developers formatting the code differently and not matching CI. The suggestion to point the LSP to a different gemfile is a potential fix, we just haven't gotten around to implementing it yet.

[coldnebo]

I have externalities that won't run locally (easily, like freetds). Like @tisba, I have very specific Linux deps in my container that are hard to get working properly on Mac, and nearly impossible on Windows.

It seems some work in emacs has already gone the route of providing remoting capability: https://emacs-lsp.github.io/lsp-mode/tutorials/docker-integration/

Remote capabilities would be nice. Until then, this is mostly just a curiosity for me. (or I can use emacs! :D )