luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

Website: a few additional tweaks to intro/getting-started/join.html.

This commit is contained in:
Ryan Breen 2015-03-14 14:21:54 -04:00
parent a8ab990ab0
commit e9b08700a7
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
website/source/intro/getting-started/join.html.markdown
View File

@ -105,8 +105,8 @@ Successfully joined cluster by contacting 1 nodes.
You should see some log output in each of the agent logs. If you read You should see some log output in each of the agent logs. If you read
carefully, you'll see that they received join information. If you carefully, you'll see that they received join information. If you
run `consul members` against each agent, you'll see that both agents run [`consul members`](/docs/commands/members.html) against each agent,
now know about each other: you'll see that both agents now know about each other:
```text ```text
vagrant@n2:~$ consul members vagrant@n2:~$ consul members
@ -139,9 +139,10 @@ credentials. Now, whenever a new node comes up with a Consul agent, it
will automatically join your Consul cluster without any hardcoded will automatically join your Consul cluster without any hardcoded
configuration. configuration.
Alternatively, you can use the Alternatively, you can join a cluster at startup using the
[`-join` flag](http://www.consul.io/docs/agent/options.html#_join) [`-join` flag](http://www.consul.io/docs/agent/options.html#_join) or
with a hardcoded address of a known Consul agent to join a cluster. [`start_join` setting](http://www.consul.io/docs/agent/options.html#start_join)
with hardcoded addresses of other known Consul agents.
## Querying Nodes ## Querying Nodes