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

Merge pull request #3823 from mitchellh/f-singlebinary 

Update documentation to single binary
This commit is contained in:
Rickard von Essen 2016-09-12 07:47:15 +02:00 committed by GitHub
parent 9dc7ce52cf 21a957ddcd
commit 12426b314f
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
website/source/docs/installation.html.md
View File

@ -28,8 +28,8 @@ 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. On Windows systems, you can put it wherever you'd like.
After unzipping the package, the directory should contain a set of binary
programs, such as `packer`, `packer-build-amazon-ebs`, etc. The final step to
After unzipping the package, the directory should contain a single binary
called `packer`. The final step to the
installation is to make sure the directory you installed Packer to is on the
PATH. See [this
page](https://stackoverflow.com/questions/14637979/how-to-permanently-set-path-on-linux)
@ -37,6 +37,8 @@ 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.
\~> **NOTE:** Packer is now distributed as a single binary. If you are upgrading from an older version, ensure to delete all the packer-* binary.
## Verifying the Installation
After installing Packer, verify the installation worked by opening a new command