Installing

    With Docker you can install the server easily without scattering binaries and other artifacts on your system. The only pre-requisite is to .

    To run NATS on Docker:

    1. docker run -p 4222:4222 -ti nats:latest

    which should output

    1. [1] 2019/05/24 15:42:58.228063 [INF] Starting nats-server version #.#.#
    2. [1] 2019/05/24 15:42:58.228115 [INF] Git commit [#######]
    3. [1] 2019/05/24 15:42:58.228201 [INF] Starting http monitor on 0.0.0.0:8222
    4. [1] 2019/05/24 15:42:58.228740 [INF] Listening for client connections on 0.0.0.0:4222
    5. [1] 2019/05/24 15:42:58.228765 [INF] Server is ready
    6. [1] 2019/05/24 15:42:58.229003 [INF] Listening for route connections on 0.0.0.0:6222

    More information on containerized NATS is available here.

    On Windows:

    1. choco install nats-server

    On Mac OS:

      To test your installation (provided the executable is visible to your shell):

      Typing nats-server should output something like

      1. [41634] 2019/05/13 09:42:11.745919 [INF] Starting nats-server version 2.*.*
      2. [41634] 2019/05/13 09:42:11.746240 [INF] Listening for client connections on 0.0.0.0:4222
      3. ...
      4. [41634] 2019/05/13 09:42:11.746249 [INF] Server id is NBNYNR4ZNTH4N2UQKSAAKBAFLDV3PZO4OUYONSUIQASTQT7BT4ZF6WX7
      5. [41634] 2019/05/13 09:42:11.746252 [INF] Server is ready

      On Linux:

      1. yay nats-server

      From the releases page, copy the link to the release archive file of your choice and download it using curl -L.

      For example, assuming version X.Y.Z of the server and a Linux AMD64:

      1. unzip nats-server.zip -d nats-server

      which should output something like

      1. Archive:  nats-server.zip
      2.    creating: nats-server-vX.Y.Z-linux-amd64/

      and finally:

      1. sudo cp nats-server/nats-server-vX.Y.Z-linux-amd64/nats-server /usr/bin

      If you have Go installed, installing the binary is easy:

      1. GO111MODULE=on go get github.com/nats-io/nats-server/v2

      This mechanism will install a build of , which almost certainly will not be a released version. If you are a developer and want to play with the latest, this is the easiest way.

      To test your installation (provided the $GOPATH/bin is set) by typing nats-server which should output something like

      1. [41634] 2019/05/13 09:42:11.745919 [INF] Starting nats-server version 2.6.2
      2. [41634] 2019/05/13 09:42:11.746240 [INF] Listening for client connections on 0.0.0.0:4222
      3. ...
      4. [41634] 2019/05/13 09:42:11.746249 [INF] Server id is NBNYNR4ZNTH4N2UQKSAAKBAFLDV3PZO4OUYONSUIQASTQT7BT4ZF6WX7
      5. [41634] 2019/05/13 09:42:11.746252 [INF] Server is ready

      If you are having issues when using the recent versions of NATS and Go modules such as:

      1. go: github.com/nats-io/go-nats@v1.8.1: parsing go.mod: unexpected module path "github.com/nats-io/nats.go"
      2. go: github.com/nats-io/go-nats-streaming@v0.5.0: parsing go.mod: unexpected module path "github.com/nats-io/stan.go"

      To fix it:

      Or if you want to import the NATS Server v2 to embed it, notice the /v2 after the nats-server module name. If that is not present, then go modules will not fetch it and would accidentally end up with 1.4.1 version of the server.

      1.     github.com/nats-io/nats-server/v2 v2.0.0
      2.     github.com/nats-io/nats.go v1.8.1
      3. )

      If embedding both NATS Streaming and NATS Servers:

      1. require (
      2.     github.com/nats-io/nats-server/v2 v2.0.0 // indirect
      3.     github.com/nats-io/nats-streaming-server v0.15.1
      4. )

      2) Next, update the imports within the repo:

      3. find ./ -type f -name "*.go" -exec sed -i -e 's/github.com\/nats-io\/go-nats/github.com\/nats-io\/nats.go/g' {} \;
      5. find ./ -type f -name "*.go" -exec sed -i -e 's/github.com\/nats-io\/gnatsd/github.com\/nats-io\/nats-server\/v2/g' {} \;
      7. find ./ -type f -name "*.go" -exec sed -i -e 's/github.com\/nats-io\/nats-server/github.com\/nats-io\/nats-server\/v2/g' {} \;

      3) (Recommended) Run Go fmt as the rename will affect the proper ordering of the imports

      When using go get to fetch the client, include an extra slash at the end of the repo. For example:

      1. GO111MODULE=on go get github.com/nats-io/nats.go/@latest
      2. GO111MODULE=on go get github.com/nats-io/nats.go/@v1.8.1

      When trying to fetch the latest version of the server with go get, you have to add v2 at the end:

      1. GO111MODULE=on go get github.com/nats-io/nats-server/v2@latest

      Otherwise, go get will fetch the v1.4.1 version of the server, which is also named (gnatsd), the previous name for nats-server.

      1. GO111MODULE=on go get github.com/nats-io/nats-server@latest
      2. go: finding github.com/nats-io/gnatsd/server latest
      3. go: finding golang.org/x/crypto latest

      In order to use an older tag, you will have to use the previous name (gnatsd) otherwise it will result in parsing errors.

      For more information you can review the original issue in GitHub.