taigrr/nats.docs
1
0
Fork 0
mirror of https://github.com/taigrr/nats.docs synced 2025-01-18 04:03:23 -08:00
Code Issues Projects Releases Wiki Activity

Syntax/grammar review

Browse Source
This commit is contained in:
Ginger Collison 2021-03-23 09:05:19 -05:00 committed by GitHub
parent 9113f39963
commit f4b87b1dca
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
jetstream/resource_management.md
View File

@ -1,8 +1,6 @@
# Multi-tenancy & Resource Mgmt # Multi-Tenancy & Resource Management
## Multi Tenancy and Resource Management JetStream is compatible with NATS 2.0 Multi-Tenancy using Accounts. A JetStream enabled server supports creating fully isolated JetStream environments for different accounts.
JetStream is compatible with NATS 2.0 Multi Tenancy using Accounts. A JetStream enabled server supports creating fully isolated JetStream environments for different accounts.
To enable JetStream in a server we have to configure it at the top level first: To enable JetStream in a server we have to configure it at the top level first:
@ -20,7 +18,7 @@ jetstream {
} }
``` ```
At this point JetStream will be enabled and if you have a server that does not have accounts enabled all users in the server would have access to JetStream At this point JetStream will be enabled and if you have a server that does not have accounts enabled, all users in the server would have access to JetStream
```text ```text
jetstream { jetstream {
@ -63,8 +61,8 @@ If you try to configure JetStream for an account without enabling it globally yo
### `nsc` CLI ### `nsc` CLI
If your setup is in opertor mode, JetStream specific account configuration can be stored in account jwt. If your setup is in operator mode, JetStream specific account configuration can be stored in account JWT.
The earlier acount named HR can be configured as follows: The earlier account named HR can be configured as follows:
```bash ```bash
nsc add account --name HR nsc add account --name HR
@ -73,7 +71,7 @@ nsc edit account --name HR --js-mem-storage 1G --js-disk-storage 512M --js-stre
## `nats` CLI ## `nats` CLI
As part of the JetStream efforts a new `nats` CLI is being developed to act as a single point of access to the NATS eco system. As part of the JetStream efforts a new `nats` CLI has been developed to act as a single point of access to the NATS ecosystem.
This CLI has been seen throughout the guide, it's available in the Docker containers today and downloadable on the [Releases](https://github.com/nats-io/jetstream/releases) page. This CLI has been seen throughout the guide, it's available in the Docker containers today and downloadable on the [Releases](https://github.com/nats-io/jetstream/releases) page.
@ -97,9 +95,9 @@ $ nats --help
... ...
``` ```
You can set these using the CLI flag, the environmet variable - like **NATS\_URL** - or using our context feature. You can set these using the CLI flag, the environment variable - like **NATS\_URL** - or using our context feature.
A context is a named configuration that stores all these settings, you can switch between access configurations and designate a default. A context is a named configuration that stores all of these settings, you can switch between access configurations and designate a default.
Creating one is easy, just specify the same settings to the `nats context save` Creating one is easy, just specify the same settings to the `nats context save`
@ -134,7 +132,7 @@ The `nats context select` command can be used to set the default context.
All `nats` commands are context aware and the `nats context` command has various commands to view, edit and remove contexts. All `nats` commands are context aware and the `nats context` command has various commands to view, edit and remove contexts.
Server URLs and Credential paths can be resolved via the `nsc` command by specifying an url, for example to find user `new` within the `orders` account of the `acme` operator you can use this: Server URLs and Credential paths can be resolved via the `nsc` command by specifying an URL, for example to find user `new` within the `orders` account of the `acme` operator you can use this:
```text ```text
$ nats context save example --description 'Example.Net Server' --nsc nsc://acme/orders/new $ nats context save example --description 'Example.Net Server' --nsc nsc://acme/orders/new