Browse Source

[nats] Release v1.0.6

Details can be found [here](https://github.com/nats-io/gnatsd/releases/tag/v1.0.6)
Ivan Kozlovic 7 years ago
parent
commit
7224e37d66
1 changed files with 9 additions and 5 deletions
  1. 9 5
      nats/content.md

+ 9 - 5
nats/content.md

@@ -15,7 +15,8 @@
 # use -p or -P as needed.
 
 $ docker run -d --name nats-main %%IMAGE%%
-[INF] Starting nats-server version 1.0.4
+[INF] Starting nats-server version 1.0.6
+[INF] Git commit [02dd205]
 [INF] Starting http monitor on 0.0.0.0:8222
 [INF] Listening for client connections on 0.0.0.0:4222
 [INF] Server is ready
@@ -31,17 +32,18 @@ $ docker run -d --name=nats-2 --link nats-main %%IMAGE%% -c gnatsd.conf --routes
 
 # If you want to verify the routes are connected, try this instead:
 $ docker run -d --name=nats-2 --link nats-main %%IMAGE%% -c gnatsd.conf --routes=nats-route://ruser:T0pS3cr3t@nats-main:6222 -DV
-[INF] Starting nats-server version 1.0.4
-[DBG] Go build version go1.8.3
+[INF] Starting nats-server version 1.0.6
+[DBG] Go build version go1.9.4
+[INF] Git commit [02dd205]
 [INF] Starting http monitor on 0.0.0.0:8222
 [INF] Listening for client connections on 0.0.0.0:4222
-[DBG] Server id is BEfslG6VOmnIbMQcXTVaVJ
+[DBG] Server id is TH1MRk9Mug4fgIDdcXIo6R
 [INF] Server is ready
 [INF] Listening for route connections on 0.0.0.0:6222
 [DBG] Trying to connect to route on nats-main:6222
 [DBG] 172.17.0.2:6222 - rid:1 - Route connection created
 [DBG] 172.17.0.2:6222 - rid:1 - Route connect msg sent
-[DBG] 172.17.0.2:6222 - rid:1 - Registering remote route "vay01L4cPxqy75GIDcqKq7"
+[DBG] 172.17.0.2:6222 - rid:1 - Registering remote route "kxi2il81mIY4TsgwdGl9Fb"
 [DBG] 172.17.0.2:6222 - rid:1 - Route sent local subscriptions
 ```
 
@@ -88,6 +90,7 @@ Server Options:
     -ms,--https_port <port>          Use port for https monitoring
     -c, --config <file>              Configuration file
     -sl,--signal <signal>[=<pid>]    Send signal to gnatsd process (stop, quit, reopen, reload)
+        --client_advertise <string>  Client URL to advertise to other servers
 
 Logging Options:
     -l, --log <file>                 File to redirect log output
@@ -114,6 +117,7 @@ Cluster Options:
         --routes <rurl-1, rurl-2>    Routes to solicit and connect
         --cluster <cluster-url>      Cluster URL for solicited routes
         --no_advertise <bool>        Advertise known cluster IPs to clients
+        --cluster_advertise <string> Cluster URL to advertise to other servers
         --connect_retries <number>   For implicit routes, number of connect retries