From a8d8683b464297f37262402af2f83e8b4c09b0ab Mon Sep 17 00:00:00 2001 From: Rob Genova Date: Wed, 8 Feb 2017 21:05:07 +0000 Subject: [PATCH] remove `https://consul.io` from join links; remove UI link to `downloads.html` --- website/source/intro/getting-started/join.html.markdown | 2 +- website/source/intro/getting-started/ui.html.markdown | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/website/source/intro/getting-started/join.html.markdown b/website/source/intro/getting-started/join.html.markdown index 7ba7194eae..f62475de81 100644 --- a/website/source/intro/getting-started/join.html.markdown +++ b/website/source/intro/getting-started/join.html.markdown @@ -141,7 +141,7 @@ learn about one existing member. After joining the cluster, the agents gossip with each other to propagate full membership information. ## Auto-joining a Cluster on Start -Ideally, whenever a new node is brought up in your datacenter, it should automatically join the Consul cluster without human intervention. Consul facilitates auto-join by enabling the auto-discovery of instances in AWS or Google Cloud with a given tag key/value. To use the integration, add the [`retry_join_ec2`](https://www.consul.io/docs/agent/options.html?#retry_join_ec2) or the [`retry_join_gce`](https://www.consul.io/docs/agent/options.html?#retry_join_gce) nested object to your Consul configuration file. This will allow a new node to join the cluster without any hardcoded configuration. Alternatively, you can join a cluster at startup using the [`-join` flag](https://www.consul.io/docs/agent/options.html#_join) or [`start_join` setting](https://www.consul.io/docs/agent/options.html#start_join) with hardcoded addresses of other known Consul agents. +Ideally, whenever a new node is brought up in your datacenter, it should automatically join the Consul cluster without human intervention. Consul facilitates auto-join by enabling the auto-discovery of instances in AWS or Google Cloud with a given tag key/value. To use the integration, add the [`retry_join_ec2`](/docs/agent/options.html?#retry_join_ec2) or the [`retry_join_gce`](/docs/agent/options.html?#retry_join_gce) nested object to your Consul configuration file. This will allow a new node to join the cluster without any hardcoded configuration. Alternatively, you can join a cluster at startup using the [`-join` flag](/docs/agent/options.html#_join) or [`start_join` setting](/docs/agent/options.html#start_join) with hardcoded addresses of other known Consul agents. ## Querying Nodes diff --git a/website/source/intro/getting-started/ui.html.markdown b/website/source/intro/getting-started/ui.html.markdown index 739d066567..cceb7255fe 100644 --- a/website/source/intro/getting-started/ui.html.markdown +++ b/website/source/intro/getting-started/ui.html.markdown @@ -17,7 +17,7 @@ key/value data. The UIs automatically support multi-datacenter. ![Consul Web UI](consul_web_ui.png) -To set up the [self-hosted UI](/downloads.html), start the Consul agent with the +To set up the self-hosted UI, start the Consul agent with the [`-ui` parameter](/docs/agent/options.html#_ui): ```text