commit
659abd407c
|
@ -4,7 +4,7 @@ layout: "docs"
|
|||
|
||||
# Packer Terminology
|
||||
|
||||
There are a handful of terms used throughout Packer documentation where
|
||||
There are a handful of terms used throughout the Packer documentation where
|
||||
the meaning may not be immediately obvious if you haven't used Packer before.
|
||||
Luckily, there are relatively few. This page documents all the terminology
|
||||
required to understand and use Packer. The terminology is in alphabetical
|
||||
|
|
|
@ -20,7 +20,7 @@ for your system and download it. Packer is packaged as a "zip" file.
|
|||
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. On Windows systems, you can put it whereever you'd
|
||||
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
|
||||
|
|
|
@ -73,7 +73,7 @@ The entire template should now [look like this](https://gist.github.com/mitchell
|
|||
|
||||
Additional builders are simply added to the `builders` array in the template.
|
||||
This tells Packer to build multiple images. The builder `type` values don't
|
||||
even need tdo be different! In fact, if you wanted to build multiple AMIs,
|
||||
even need to be different! In fact, if you wanted to build multiple AMIs,
|
||||
you can do that as well.
|
||||
|
||||
Validate the template with `packer validate`. This is always a good practice.
|
||||
|
|
Loading…
Reference in New Issue