+ Choose from the options below (some are required) and download your
+ configuration file. Some variables may be sensitive, so we will give you
+ placeholders that you can replace after downloading.
+
+ <%= partial "builder/reveal_text_field", locals: {
+ label: "Address of a statsite server to forward metrics data to",
+ name: "statsite_address",
+ docs_url: "telemetry/#statsite_address"
+ } %>
+ <%= partial "builder/reveal_select_field", locals: {
+ label: "Prefix gauge values with local hostname",
+ name: "disable_hostname",
+ options: {
+ false: "No",
+ true: "Yes"
+ },
+ docs_url: "telemetry/#disable_hostname"
+ } %>
+
+
+
+ <%= partial "builder/reveal_text_field", locals: {
+ label: "Address of a statsd server to forward metrics data to",
+ name: "statsd_address",
+ docs_url: "telemetry/#statsd_address"
+ } %>
+ <%= partial "builder/reveal_select_field", locals: {
+ label: "Prefix gauge values with local hostname",
+ name: "disable_hostname",
+ options: {
+ false: "No",
+ true: "Yes"
+ },
+ docs_url: "telemetry/#disable_hostname"
+ } %>
+
+
+
+ <%= partial "builder/reveal_text_field", locals: {
+ label: "Circonus API Token used to create/manage check",
+ name: "circonus_api_token",
+ value: "",
+ sensitive_disabled: true,
+ docs_url: "telemetry/#circonus_api_token"
+ } %>
+ <%= partial "builder/reveal_text_field", locals: {
+ label: "App name associated with the API token",
+ name: "circonus_api_app",
+ value: "nomad",
+ docs_url: "telemetry/#circonus_api_app"
+ } %>
+ <%= partial "builder/reveal_text_field", locals: {
+ label: "Base URL to use for contacting the Circonus API",
+ name: "circonus_api_url",
+ value: "https://api.circonus.com/v2",
+ docs_url: "telemetry/#circonus_api_url"
+ } %>
+ <%= partial "builder/reveal_text_field", locals: {
+ label: "Interval at which metrics are submitted to Circonus",
+ name: "circonus_submission_interval",
+ value: "10s",
+ docs_url: "telemetry/#circonus_submission_interval"
+ } %>
+ <%= partial "builder/reveal_text_field", locals: {
+ label: "Circonus check.config.submission_url field",
+ name: "circonus_submission_url",
+ docs_url: "telemetry/#circonus_submission_url"
+ } %>
+ <%= partial "builder/reveal_select_field", locals: {
+ label: "Force activation of metrics which already exist and are not currently active",
+ name: "circonus_check_force_metric_activation",
+ options: {
+ false: "No",
+ true: "Yes"
+ },
+ docs_url: "telemetry/#circonus_check_force_metric_activation"
+ } %>
+ <%= partial "builder/reveal_text_field", locals: {
+ label: "Tag to narrow down the search results",
+ name: "circonus_check_search_tag",
+ docs_url: "telemetry/#circonus_check_search_tag"
+ } %>
+ <%= partial "builder/reveal_text_field", locals: {
+ label: "Name to give a check when it is created",
+ name: "circonus_check_display_name",
+ docs_url: "telemetry/#circonus_check_display_name"
+ } %>
+ <%= partial "builder/reveal_text_field", locals: {
+ label: "List of additional tags to add to a check when it is created",
+ name: "circonus_check_tags",
+ docs_url: "telemetry/#circonus_check_tags"
+ } %>
+ <%= partial "builder/reveal_text_field", locals: {
+ label: "ID of Circonus Broker to use when creating a new check",
+ name: "circonus_broker_id",
+ docs_url: "telemetry/#circonus_broker_id"
+ } %>
+ <%= partial "builder/reveal_text_field", locals: {
+ label: "Tag which will be used to select a Circonus Broker (when a Broker ID is not provided)",
+ name: "circonus_broker_select_tag",
+ docs_url: "telemetry/#circonus_broker_select_tag"
+ } %>
+ <%= partial "builder/reveal_select_field", locals: {
+ label: "Prefix gauge values with local hostname",
+ name: "disable_hostname",
+ options: {
+ false: "No",
+ true: "Yes"
+ },
+ docs_url: "telemetry/#disable_hostname"
+ } %>
+
+
diff --git a/website/source/docs/configuration/index.html.md b/website/source/docs/configuration/index.html.md
index 2d05966e37..09592bd833 100644
--- a/website/source/docs/configuration/index.html.md
+++ b/website/source/docs/configuration/index.html.md
@@ -8,6 +8,21 @@ description: |-
# Vault Configuration
+
+
Outside of development mode, Vault servers are configured using a file.
The format of this file is [HCL](https://github.com/hashicorp/hcl) or JSON.
An example configuration is shown below:
@@ -150,6 +165,7 @@ The following parameters are used on backends that support [high availability][h
such as request forwarding are enabled. Setting this to true on one Vault node
will disable these features _only when that node is the active node_.
+[config-builder]: /docs/configuration/builder.html
[storage-backend]: /docs/configuration/storage/index.html
[listener]: /docs/configuration/listener/index.html
[seal]: /docs/configuration/seal/index.html
diff --git a/website/source/downloads.html.erb b/website/source/downloads.html.erb
index 4ebaa55aa3..fc4871517a 100644
--- a/website/source/downloads.html.erb
+++ b/website/source/downloads.html.erb
@@ -6,16 +6,68 @@ description: |-
Download Vault
---
-
Download Vault
-
+
Download Vault
Below are the available downloads for the latest version of Vault
(<%= latest_version %>). Please download the proper package for your
- operating system and architecture.
+ operating system and architecture. Check out the
+
+ v<%= latest_version %> CHANGELOG
+
+ for information on the latest release.
+
+
+
+
+ <% product_versions.each do |os, arches| %>
+ <% next if os == "web" %>
+
diff --git a/website/source/intro/getting-started/dev-server.html.md b/website/source/intro/getting-started/dev-server.html.md
index 7200030f27..cd633cf73f 100644
--- a/website/source/intro/getting-started/dev-server.html.md
+++ b/website/source/intro/getting-started/dev-server.html.md
@@ -15,104 +15,172 @@ piece of the Vault architecture that interacts with the data storage and
backends. All operations done via the Vault CLI interact with the server over a
TLS connection.
-In this page, we'll start and interact with the Vault server to understand how
-the server is started.
+
-## Starting the Dev Server
+
+ First, we're going to start a Vault _dev server_. The dev server is a built-in,
+ pre-configured server that is not very secure but useful for playing with Vault
+ locally. Later in this guide we'll configure and start a real server.
-First, we're going to start a Vault _dev server_. The dev server is a built-in,
-pre-configured server that is not very secure but useful for playing with Vault
-locally. Later in this guide we'll configure and start a real server.
+ To start the Vault dev server, run:
-To start the Vault dev server, run:
+ ```text
+ $ vault server -dev
+ ==> Vault server configuration:
-```text
-$ vault server -dev
-==> Vault server configuration:
+ Cgo: disabled
+ Cluster Address: https://127.0.0.1:8201
+ Listener 1: tcp (addr: "127.0.0.1:8200", cluster address: "127.0.0.1:8201", tls: "disabled")
+ Log Level: info
+ Mlock: supported: false, enabled: false
+ Redirect Address: http://127.0.0.1:8200
+ Storage: inmem
+ Version: Vault v1.2.3
+ Version Sha: ...
- Cgo: disabled
- Cluster Address: https://127.0.0.1:8201
- Listener 1: tcp (addr: "127.0.0.1:8200", cluster address: "127.0.0.1:8201", tls: "disabled")
- Log Level: info
- Mlock: supported: false, enabled: false
- Redirect Address: http://127.0.0.1:8200
- Storage: inmem
- Version: Vault v1.2.3
- Version Sha: ...
+ WARNING! dev mode is enabled! In this mode, Vault runs entirely in-memory
+ and starts unsealed with a single unseal key. The root token is already
+ authenticated to the CLI, so you can immediately begin using Vault.
-WARNING! dev mode is enabled! In this mode, Vault runs entirely in-memory
-and starts unsealed with a single unseal key. The root token is already
-authenticated to the CLI, so you can immediately begin using Vault.
+ You may need to set the following environment variable:
-You may need to set the following environment variable:
+ $ export VAULT_ADDR='http://127.0.0.1:8200'
- $ export VAULT_ADDR='http://127.0.0.1:8200'
+ The unseal key and initial root token are displayed below in case you want to
+ seal/unseal the Vault or re-authenticate.
-The unseal key and initial root token are displayed below in case you want to
-seal/unseal the Vault or re-authenticate.
+ Unseal Key: 1aKM7rNnyW+7Jx1XDAXFswgkRVe+78JB28k/bel90jY=
+ Root Token: root
-Unseal Key: 1aKM7rNnyW+7Jx1XDAXFswgkRVe+78JB28k/bel90jY=
-Root Token: root
+ Development mode should NOT be used in production installations!
-Development mode should NOT be used in production installations!
+ ==> Vault server started! Log data will stream in below:
-==> Vault server started! Log data will stream in below:
+ # ...
+ ```
-# ...
-```
+ You should see output similar to that above. Vault does not fork, so it will
+ continue to run in the foreground. Open another shell or terminal tab to run the
+ remaining commands.
-You should see output similar to that above. Vault does not fork, so it will
-continue to run in the foreground. Open another shell or terminal tab to run the
-remaining commands.
+ The dev server stores all its data in-memory (but still encrypted), listens on
+ `localhost` without TLS, and automatically unseals and shows you the unseal key
+ and root access key. **Do not run a dev server in production!**
-The dev server stores all its data in-memory (but still encrypted), listens on
-`localhost` without TLS, and automatically unseals and shows you the unseal key
-and root access key. **Do not run a dev server in production!**
+ With the dev server running, do the following three things before anything else:
-With the dev server running, do the following three things before anything else:
+ 1. Launch a new terminal session.
- 1. Launch a new terminal session.
+ 2. Copy and run the `export VAULT_ADDR ...` command from the terminal
+ output. This will configure the Vault client to talk to our dev server.
- 2. Copy and run the `export VAULT_ADDR ...` command from the terminal
- output. This will configure the Vault client to talk to our dev server.
+ 3. Save the unseal key somewhere. Don't worry about _how_ to save this
+ securely. For now, just save it anywhere.
- 3. Save the unseal key somewhere. Don't worry about _how_ to save this
- securely. For now, just save it anywhere.
+ 4. Do the same as step 3, but with the root token. We'll use this later.
- 4. Do the same as step 3, but with the root token. We'll use this later.
+ ## Verify the Server is Running
-## Verify the Server is Running
+ Verify the server is running by running the `vault status` command. This should
+ succeed and exit with exit code 0. If you see an error about opening
+ a connection, make sure you copied and executed the `export VAULT_ADDR...`
+ command from above properly.
-Verify the server is running by running the `vault status` command. This should
-succeed and exit with exit code 0. If you see an error about opening
-a connection, make sure you copied and executed the `export VAULT_ADDR...`
-command from above properly.
+ If it ran successfully, the output should look like the below:
-If it ran successfully, the output should look like the below:
+ ```text
+ $ vault status
+ Key Value
+ --- -----
+ Sealed false
+ Total Shares 1
+ Version (version unknown)
+ Cluster Name vault-cluster-81109a1a
+ Cluster ID f6e0aa8a-700e-38b8-5dc5-4265c880b2a1
+ HA Enabled false
+ ```
-```text
-$ vault status
-Key Value
---- -----
-Sealed false
-Total Shares 1
-Version (version unknown)
-Cluster Name vault-cluster-81109a1a
-Cluster ID f6e0aa8a-700e-38b8-5dc5-4265c880b2a1
-HA Enabled false
-```
+ If the output looks different, especially if the numbers are different or the
+ Vault is sealed, then restart the dev server and try again. The only reason
+ these would ever be different is if you're running a dev server from going
+ through this guide previously.
-If the output looks different, especially if the numbers are different or the
-Vault is sealed, then restart the dev server and try again. The only reason
-these would ever be different is if you're running a dev server from going
-through this guide previously.
+ We'll cover what this output means later in the guide.
-We'll cover what this output means later in the guide.
+ ## Next
-## Next
+ Congratulations! You've started your first Vault server. We haven't stored
+ any secrets yet, but we'll do that in the next section.
-Congratulations! You've started your first Vault server. We haven't stored
-any secrets yet, but we'll do that in the next section.
+ Next, we're going to
+ [read and write our first secrets](/intro/getting-started/first-secret.html).
+
-Next, we're going to
-[read and write our first secrets](/intro/getting-started/first-secret.html).
+
+ We're going to start a Vault _server_ with the
+ configuration file that you
+ created.
+
+ To start the Vault server, run:
+
+ ```text
+ $ vault server -config=vault-config.hcl
+ ==> Vault server configuration:
+
+ Cgo: disabled
+ Listener 1: tcp (addr: "127.0.0.1:8200", cluster address: "127.0.0.1:8201", tls: "disabled")
+ Log Level: info
+ Mlock: supported: false, enabled: false
+ Storage: file
+ Version: Vault v0.1.2
+ Version Sha: ...
+
+ ==> Vault server started! Log data will stream in below:
+
+ # ...
+ ```
+
+ You should see output similar to that above. Vault does not fork, so it will
+ continue to run in the foreground.
+
+ ## Verify the Server is Running
+
+ Verify the server is running by running the `vault status` command. This should
+ succeed and exit with exit code 0. If you see an error about opening
+ a connection, make sure you copied and executed the `export VAULT_ADDR...`
+ command from above properly.
+
+ If it ran successfully, the output should look like the below:
+
+ ```text
+ $ vault status
+ Key Value
+ --- -----
+ Sealed false
+ Total Shares 1
+ Version (version unknown)
+ Cluster Name vault-cluster-81109a1a
+ Cluster ID f6e0aa8a-700e-38b8-5dc5-4265c880b2a1
+ HA Enabled false
+ ```
+
+ ## Next
+
+ Congratulations! You've started your first Vault server. You can now view the
+ Vault Web UI (at http://localhost:4200/ui
+ if you are running Vault locally) to guide you through the rest of getting set up.
+
+