a3dfde5cec
* conversion stage 1 * correct image paths * add sidebar title to frontmatter * docs/concepts and docs/internals * configuration docs and multi-level nav corrections * commands docs, index file corrections, small item nav correction * secrets converted * auth * add enterprise and agent docs * add extra dividers * secret section, wip * correct sidebar nav title in front matter for apu section, start working on api items * auth and backend, a couple directory structure fixes * remove old docs * intro side nav converted * reset sidebar styles, add hashi-global-styles * basic styling for nav sidebar * folder collapse functionality * patch up border length on last list item * wip restructure for content component * taking middleman hacking to the extreme, but its working * small css fix * add new mega nav * fix a small mistake from the rebase * fix a content resolution issue with middleman * title a couple missing docs pages * update deps, remove temporary markup * community page * footer to layout, community page css adjustments * wip downloads page * deps updated, downloads page ready * fix community page * homepage progress * add components, adjust spacing * docs and api landing pages * a bunch of fixes, add docs and api landing pages * update deps, add deploy scripts * add readme note * update deploy command * overview page, index title * Update doc fields Note this still requires the link fields to be populated -- this is solely related to copy on the description fields * Update api_basic_categories.yml Updated API category descriptions. Like the document descriptions you'll still need to update the link headers to the proper target pages. * Add bottom hero, adjust CSS, responsive friendly * Add mega nav title * homepage adjustments, asset boosts * small fixes * docs page styling fixes * meganav title * some category link corrections * Update API categories page updated to reflect the second level headings for api categories * Update docs_detailed_categories.yml Updated to represent the existing docs structure * Update docs_detailed_categories.yml * docs page data fix, extra operator page remove * api data fix * fix makefile * update deps, add product subnav to docs and api landing pages * Rearrange non-hands-on guides to _docs_ Since there is no place for these on learn.hashicorp, we'll put them under _docs_. * WIP Redirects for guides to docs * content and component updates * font weight hotfix, redirects * fix guides and intro sidenavs * fix some redirects * small style tweaks * Redirects to learn and internally to docs * Remove redirect to `/vault` * Remove `.html` from destination on redirects * fix incorrect index redirect * final touchups * address feedback from michell for makefile and product downloads
99 lines
3.4 KiB
Markdown
99 lines
3.4 KiB
Markdown
---
|
|
layout: "intro"
|
|
page_title: "Install Vault - Getting Started"
|
|
sidebar_title: "Getting Started"
|
|
sidebar_current: "gettingstarted"
|
|
description: |-
|
|
The first step to using Vault is to get it installed.
|
|
---
|
|
|
|
# Install Vault
|
|
|
|
Vault must first be installed on your machine. Vault is distributed as
|
|
a [binary package](/downloads.html) for all supported platforms and
|
|
architectures. This page will not cover how to compile Vault from source,
|
|
but compiling from source is covered in the [documentation](/docs/install/index.html)
|
|
for those who want to be sure they're compiling source they trust into
|
|
the final binary.
|
|
|
|
## Installing Vault
|
|
|
|
To install Vault, find the [appropriate package](/downloads.html) for
|
|
your system and download it. Vault is packaged as a zip archive.
|
|
|
|
After downloading Vault, unzip the package. Vault runs as a single binary
|
|
named `vault`. Any other files in the package can be safely removed and
|
|
Vault will still function.
|
|
|
|
The final step is to make sure that the `vault` binary is available on the `PATH`.
|
|
See [this page](https://stackoverflow.com/questions/14637979/how-to-permanently-set-path-on-linux)
|
|
for instructions on setting the PATH on Linux and Mac.
|
|
[This page](https://stackoverflow.com/questions/1618280/where-can-i-set-path-to-make-exe-on-windows)
|
|
contains instructions for setting the PATH on Windows.
|
|
|
|
## Verifying the Installation
|
|
|
|
After installing Vault, verify the installation worked by opening a new
|
|
terminal session and checking that the `vault` binary is available. By executing
|
|
`vault`, you should see help output similar to the following:
|
|
|
|
```text
|
|
$ vault
|
|
Usage: vault <command> [args]
|
|
|
|
Common commands:
|
|
read Read data and retrieves secrets
|
|
write Write data, configuration, and secrets
|
|
delete Delete secrets and configuration
|
|
list List data or secrets
|
|
login Authenticate locally
|
|
server Start a Vault server
|
|
status Print seal and HA status
|
|
unwrap Unwrap a wrapped secret
|
|
|
|
Other commands:
|
|
audit Interact with audit devices
|
|
auth Interact with auth methods
|
|
lease Interact with leases
|
|
operator Perform operator-specific tasks
|
|
path-help Retrieve API help for paths
|
|
policy Interact with policies
|
|
secrets Interact with secrets engines
|
|
ssh Initiate an SSH session
|
|
token Interact with tokens
|
|
```
|
|
|
|
If you get an error that the binary could not be found, then your `PATH`
|
|
environment variable was not setup properly. Please go back and ensure that your
|
|
`PATH` variable contains the directory where Vault was installed.
|
|
|
|
Otherwise, Vault is installed and ready to go!
|
|
|
|
## Command Completion
|
|
|
|
Vault also includes command-line completion for subcommands, flags, and path
|
|
arguments where supported. To install command-line completion, you must be using
|
|
Bash, ZSH or Fish. Unfortunately other shells are not supported at this time.
|
|
|
|
To install completions, run:
|
|
|
|
```sh
|
|
$ vault -autocomplete-install
|
|
```
|
|
|
|
This will automatically install the helpers in your `~/.bashrc` or `~/.zshrc`, or to
|
|
`~/.config/fish/completions/vault.fish` for Fish users. Then restart your terminal
|
|
or reload your shell:
|
|
|
|
```sh
|
|
$ exec $SHELL
|
|
```
|
|
|
|
Now when you type `vault <tab>`, Vault will suggest options. This is very
|
|
helpful for beginners and advanced Vault users.
|
|
|
|
## Next
|
|
|
|
Now Vault is installed we can start our first Vault server! [Let's do
|
|
that now](/intro/getting-started/dev-server.html).
|