Add to package managers

[ghuh]

It would be really nice to distribute this through brew and other package managers rather than everyone needing to build this from source

[rcjsuen]

@ghuh Thank you for the feedback. We do have binaries on our releases page. Are you able to use those instead of compiling from source?

[ghuh]

Oh I certainly can. The advantage of a package system is easy upgrades. You just run brew upgrade and you get the latest and greatest docker-language-server along with the rest of your updates.

I've added go install github.com/docker/docker-language-server/cmd/docker-language-server@latest to my upgrade script to grab any changes, but that's really a clunky solution. Auto updating with pre-built binaries either requires a much fancier script (essentially rebuilding a package manager) or it has to be done manually. None of those are really great solutions when we have things like brew that handle it all for us on both Linux and Mac (plus about a dozen other package managers for other instillation options)

[rcjsuen]

@ghuh Thanks for the info. Just wanted to make sure the release binaries are usable and there wasn't a glaring bug there or something. :)

Could you let us know which editor you are using?

1. Visual Studio Code should include the binary with our extension.
2. JetBrains editors with the LSP4IJ plugin will download the binary from GitHub.
3. Neovim should download the binary from GitHub with the help of Mason.

I understand that brew would make your life easier with a brew upgrade but just trying to understand which editor integration is requiring users to install the language server manually. Or perhaps you have some other use case we are not thinking about?

[ghuh]

I actually forgot the most important use case of a package manager 🤦 , making sure the same packages are installed on all computers. I have a common Brewfile I use for all my dev machines; Linux (x86 and Arm) and MacOS.

The editor I'm using is Helix and I want LSPs on all machines to be the same (including headless servers). So the use case is ssh'ing into a machine used as a docker host and using Helix to modify a compose file should be the same experience as doing it on my local machine.

Side note: You may want to include setup instructions for Helix since it is growing in popularity as a vim alternative (I'm a 20 year vim veteran taking the plunge to learn some new muscle memory...).

[rcjsuen]

@ghuh Thank you for sharing these details. I will sync with the team and provide an update as soon as I am able.

Side note: You may want to include setup instructions for Helix since it is growing in popularity as a vim alternative (I'm a 20 year vim veteran taking the plunge to learn some new muscle memory...).

I do see that someone contributed something to the Helix repository (helix-editor/helix#14391). It was merged in September but there hasn't been a new release since July. Would that remove the need for Helix setup instructions if a new release was made?

[ghuh]

I do see that someone contributed something to the Helix repository (helix-editor/helix#14391). It was merged in September but there hasn't been a new release since July. Would that remove the need for Helix setup instructions if a new release was made?

It's always nice to include an example of passing in configuration options, but a new release certainly makes it easier.