Walkthrough Setup
We have provided Walkthroughs for you to try NATS (and JetStream) on your own. In order to follow along with the walkthroughs, you could choose one of these options:
The
nats
CLI tool must be installed, and a local NATS server must be installed (or you can use a remote server you have access to).You can use Synadia's NGS.
You could even use the demo server from where you installed NATS. This is accessible via
nats://demo.nats.io
(this is a NATS connection URL; not a browser URL. You pass it to a NATS client application).
Installing the nats
CLI Tool
nats
CLI ToolFor MacOS:
For Arch Linux:
For other versions of Linux and for Windows:
The .deb
or .rpm
files and Windows binaries (even for ARM) are available here GitHub Releases.
Installing the NATS server locally (if needed)
If you are going to run a server locally you need to first install it and start it. Alternatively if you already know how to use NATS on a remote server, you only need to pass the server URL to nats
using the -s
option or preferably create a context using nats context add
, to specify the server URL(s) and credentials file containing your user JWT.
Installing the NATS server via a Package Manager
On Mac OS:
On Windows:
On Arch Linux:
For other versions of Linux or other architectures, you can install a release build as shown below.
Downloading a Release Build
You can find the latest release of nats-server
here.
You could manually download the zip file matching your systems architecture, and unzip it. You could also use curl
to download a specific version. The example below shows for example, how to download version 2.6.2 of the nats-server
for Linux AMD64:
and finally, copy it to the bin
folder (this allows you to run the executable from anywhere in the system):
Start the NATS server (if needed)
To start a simple demonstration server locally, simply run:
(or nats-server -m 8222
if you want to enable the HTTP monitoring functionality)
When the server starts successfully, you will see the following messages:
The NATS server listens for client connections on TCP Port 4222.
Last updated