Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standardize installation methods for Windows #586

Open
mesakomarevich opened this issue Apr 27, 2023 · 0 comments
Open

Standardize installation methods for Windows #586

mesakomarevich opened this issue Apr 27, 2023 · 0 comments

Comments

@mesakomarevich
Copy link

Problem

The Windows installation instructions and installation methods for several NATS projects are inconsistent or out of date.

NATS Server

When reading through Installing a NATS Server > Installing via a Package Manager, the instructions for Windows tell us to install via Chocolatey, but neglects to mention that you can also install via Scoop. Further to this issue, the version of NATS Server available on Chocolately was last updated in 2019, but the version available on Scoop is up to date

NATS CLI

The docs for installing the NATS CLI don't even mention installation on Windows. However, the NATS CLI can be installed from the Scoop Extras bucket, but cannot be installed on Chocolatey.

Suggestions

Chocolatey

There seem to be two good options here:

  • Remove the references to installing the NATS Server through Chocolatey and officially depricate or remove the package, if possible.
  • Update the version of NATS Server available through Chocolatey and add the ability to install the NATS CLI through Chocolatey.

Scoop

Add installation instructions for Scoop to both the NATS Server and NATS CLI docs.

General package management

I am not sure what the exact processes or procedures are for creating a release of NATS Server or NATS CLI, but it is my opinion that any distribution avenue (Chocolatey, Scoop, Docker, etc.) detailed in the installation docs should be maintened by the NATS team, and updated as part of the release process. I know that this may not be the best place to discuss this point, but this seemed to be the only repo with overlap between docs, server, and CLI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant