mirror of
https://github.com/taigrr/nats.docs
synced 2025-01-18 04:03:23 -08:00
GitBook: [master] 82 pages modified
This commit is contained in:
committed by
gitbook-bot
parent
7e27f03c98
commit
b082996143
@@ -4,7 +4,7 @@ NATS Streaming provides a rich set of commands and parameters to configure all a
|
||||
|
||||
* [Command Line Arguments](cmdline.md)
|
||||
* [Configuration File](cfgfile.md)
|
||||
* [Store Limits](storelimits.md/)
|
||||
* [Store Limits](storelimits.md)
|
||||
* [Persistence](persistence/)
|
||||
* [Securing](tls/)
|
||||
* [Securing](tls.md)
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Configuration file
|
||||
# Configuration File
|
||||
|
||||
You can use a configuration file to configure the options specific to the NATS Streaming Server.
|
||||
|
||||
@@ -73,7 +73,7 @@ In general the configuration parameters are the same as the command line argumen
|
||||
| encrypt | Specify if server should encrypt messages \(only the payload\) when storing them | `true` or `false` | `encrypt: true` |
|
||||
| encryption\_cipher | Cipher to use for encryption. Currently support AES and CHAHA \(ChaChaPoly\). Defaults to AES | `AES` or `CHACHA` | `encryption_cipher: "AES"` |
|
||||
| encryption\_key | Encryption key. It is recommended to specify the key through the `NATS_STREAMING_ENCRYPTION_KEY` environment variable instead | String | `encryption_key: "mykey"` |
|
||||
| credentials | Credentials file to connect to external NATS 2.0+ Server | String | `credentials: "streaming_server.creds"` |
|
||||
| credentials | Credentials file to connect to external NATS 2.0+ Server | String | `credentials: "streaming_server.creds"` |
|
||||
|
||||
## TLS Configuration
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Command line arguments
|
||||
# Command Line Arguments
|
||||
|
||||
The NATS Streaming Server accepts command line arguments to control its behavior. There is a set of parameters specific to the NATS Streaming Server and some to the embedded NATS Server.
|
||||
|
||||
|
||||
@@ -134,6 +134,7 @@ Below is what would be displayed with the above store limits configuration. Noti
|
||||
|
||||
Suppose you have set a channel limit to hold at most 100 messages, and the channel currently holds 72 messages. The server is stopped and the message limit for this channel is lowered to 50 messages, then the server is restarted.
|
||||
|
||||
On startup, the server will apply the store limits, which means that this channel will now hold the maximum number of messages (50) and the 22 oldest messages will be removed due to the channel limit.
|
||||
On startup, the server will apply the store limits, which means that this channel will now hold the maximum number of messages \(50\) and the 22 oldest messages will be removed due to the channel limit.
|
||||
|
||||
We strongly recommend not raising the limit back to the higher limit if messages have been removed in the previous step because those removed messages may or may not become available again depending on the store implementation or if running in clustering mode or not.
|
||||
|
||||
|
||||
@@ -32,7 +32,7 @@ The embedded NATS server specifies TLS server certificates with these:
|
||||
--tlscacert <file> Client certificate CA for verification
|
||||
```
|
||||
|
||||
The server parameters are used the same way you'd [secure a typical NATS server](../../../nats-server/configuration/securing_nats/tls.md).
|
||||
The server parameters are used the same way you'd [secure a typical NATS server](../../nats-server/configuration/securing_nats/tls.md).
|
||||
|
||||
Proper usage of the NATS Streaming Server requires the use of both client and server parameters.
|
||||
|
||||
@@ -42,7 +42,7 @@ For example:
|
||||
% nats-streaming-server -tls_client_cert client-cert.pem -tls_client_key client-key.pem -tls_client_cacert ca.pem -tlscert server-cert.pem -tlskey server-key.pem -tlscacert ca.pem
|
||||
```
|
||||
|
||||
Further TLS related functionality can be found in [Securing NATS > TLS](../../../nats-server/configuration/securing_nats/tls.md). Note that if specifying cipher suites is required, a configuration file for the embedded NATS server can be passed through the `-config` command line parameter.
|
||||
Further TLS related functionality can be found in [Securing NATS > TLS](../../nats-server/configuration/securing_nats/tls.md). Note that if specifying cipher suites is required, a configuration file for the embedded NATS server can be passed through the `-config` command line parameter.
|
||||
|
||||
### Connecting to Remote NATS Server with TLS Enabled
|
||||
|
||||
Reference in New Issue
Block a user