2017-09-08 02:14:12 +00:00
|
|
|
---
|
|
|
|
|
layout: "docs"
|
|
|
|
|
page_title: "server - Command"
|
New Docs Website (#5535)
* 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
2018-10-19 15:40:11 +00:00
|
|
|
sidebar_title: "server"
|
2017-09-08 02:14:12 +00:00
|
|
|
sidebar_current: "docs-commands-server"
|
|
|
|
|
description: |-
|
|
|
|
|
The "server" command starts a Vault server that responds to API requests. By
|
|
|
|
|
default, Vault will start in a "sealed" state. The Vault cluster must be
|
|
|
|
|
initialized before use.
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
# server
|
|
|
|
|
|
|
|
|
|
The `server` command starts a Vault server that responds to API requests. By
|
|
|
|
|
default, Vault will start in a "sealed" state. The Vault cluster must be
|
|
|
|
|
initialized before use, usually by the `vault operator init` command. Each Vault
|
|
|
|
|
server must also be unsealed using the `vault operator unseal` command or the
|
|
|
|
|
API before the server can respond to requests.
|
|
|
|
|
|
|
|
|
|
For more information, please see:
|
|
|
|
|
|
|
|
|
|
- [`operator init` command](/docs/commands/operator/init.html) for information
|
|
|
|
|
on initializing a Vault server.
|
|
|
|
|
|
|
|
|
|
- [`operator unseal` command](/docs/commands/operator/unseal.html) for
|
|
|
|
|
information on providing unseal keys.
|
|
|
|
|
|
|
|
|
|
- [Vault configuration](/docs/configuration/index.html) for the syntax and
|
|
|
|
|
various configuration options for a Vault server.
|
|
|
|
|
|
|
|
|
|
## Examples
|
|
|
|
|
|
|
|
|
|
Start a server with a configuration file:
|
|
|
|
|
|
|
|
|
|
```text
|
|
|
|
|
$ vault server -config=/etc/vault/config.hcl
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
Run in "dev" mode with a custom initial root token:
|
|
|
|
|
|
|
|
|
|
```text
|
|
|
|
|
$ vault server -dev -dev-root-token-id="root"
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
## Usage
|
|
|
|
|
|
|
|
|
|
The following flags are available in addition to the [standard set of
|
|
|
|
|
flags](/docs/commands/index.html) included on all commands.
|
|
|
|
|
|
|
|
|
|
### Command Options
|
|
|
|
|
|
|
|
|
|
- `-config` `(string: "")` - Path to a configuration file or directory of
|
|
|
|
|
configuration files. This flag can be specified multiple times to load
|
|
|
|
|
multiple configurations. If the path is a directory, all files which end in
|
|
|
|
|
.hcl or .json are loaded.
|
|
|
|
|
|
|
|
|
|
- `-log-level` `(string: "info")` - Log verbosity level. Supported values (in
|
|
|
|
|
order of detail) are "trace", "debug", "info", "warn", and "err". This can
|
2018-06-05 14:23:32 +00:00
|
|
|
also be specified via the VAULT_LOG_LEVEL environment variable.
|
2017-09-08 02:14:12 +00:00
|
|
|
|
|
|
|
|
### Dev Options
|
|
|
|
|
|
|
|
|
|
- `-dev` `(bool: false)` - Enable development mode. In this mode, Vault runs
|
|
|
|
|
in-memory and starts unsealed. As the name implies, do not run "dev" mode in
|
|
|
|
|
production.
|
|
|
|
|
|
|
|
|
|
- `-dev-listen-address` `(string: "127.0.0.1:8200")` - Address to bind to in
|
|
|
|
|
"dev" mode. This can also be specified via the `VAULT_DEV_LISTEN_ADDRESS`
|
|
|
|
|
environment variable.
|
|
|
|
|
|
|
|
|
|
- `-dev-root-token-id` `(string: "")` - Initial root token. This only applies
|
|
|
|
|
when running in "dev" mode. This can also be specified via the
|
|
|
|
|
`VAULT_DEV_ROOT_TOKEN_ID` environment variable.
|