iSharkFly-Docs
/
packer-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #9059 from hashicorp/d-update-getting-started 

docs/getting-started: Update PATH install instructions
This commit is contained in:
Wilken Rivera 2020-04-14 08:34:54 -04:00 committed by GitHub
parent c9c0ee65d3 9eccbb4cfe
commit 5075fc6ff7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
website/pages/intro/getting-started/index.mdx
View File

@ -32,11 +32,10 @@ have any near term plans to provide system packages.
Next, unzip the downloaded package into a directory where Packer will be
installed. On Unix systems, `~/packer` or `/usr/local/packer` is generally good,
depending on whether you want to restrict the install to just your user or
install it system-wide. If you intend to access it from the command-line, make
sure to place it somewhere on your `PATH` before `/usr/sbin`. On Windows
systems, you can put it wherever you'd like. The `packer` (or `packer.exe` for
Windows) binary inside is all that is necessary to run Packer. Any additional
files aren't required to run Packer.
install it system-wide. If you intend to access Packer from the command-line, make
sure to place it somewhere on your `PATH`. On Windows systems, you can install
the binary wherever you'd like. The single `packer` (or `packer.exe` for
Windows) binary contains all that is necessary to run Packer.
After unzipping the package, the directory should contain a single binary
program called `packer`. The final step to