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

Corrected the meta text on the artifice page.

This commit is contained in:
Chris Bednarski 2015-08-10 10:25:19 -07:00
parent 8484c2e2a0
commit 4416954461
2 changed files with 18 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
website/source/docs/post-processors/artifice.html.markdown
View File

@ -1,8 +1,10 @@
--- ---
description: | description: |
The Atlas post-processor for Packer receives an artifact from a Packer build and The artifice post-processor overrides the artifact list from an upstream builder
uploads it to Atlas. Atlas hosts and serves artifacts, allowing you to version or post-processor. All downstream post-processors will see the new artifacts you
and distribute them in a simple way. specify. The primary use-case is to build artifacts inside a packer builder --
for example, spinning up an EC2 instance to build a docker container -- and then
extracting the docker container and throwing away the EC2 instance.
layout: docs layout: docs
page_title: 'Atlas Post-Processor' page_title: 'Atlas Post-Processor'
... ...
@ -45,8 +47,8 @@ Artifice helps you tie together a few other packer features:
- Additional post-processors, which push the artifact to Atlas, Docker - Additional post-processors, which push the artifact to Atlas, Docker
hub, etc. hub, etc.
You will want to perform as much work as possible inside the VM. Ideally You will want to perform as much work as possible inside the VM. Ideally the
the only other post-processor you need after artifice is one that uploads your only other post-processor you need after artifice is one that uploads your
artifact to the appropriate repository. artifact to the appropriate repository.
## Configuration ## Configuration
@ -64,13 +66,14 @@ The configuration allows you to specify which files comprise your artifact.
This minimal example: This minimal example:
1. Spins up a cloned VMware virtual machine 1. Spins up a cloned VMware virtual machine
2. Installs a [consul](https://consul.io/) release 2. Installs a [consul](https://consul.io/) release
3. Downloads the consul binary 3. Downloads the consul binary
4. Packages it into a `.tar.gz` file 4. Packages it into a `.tar.gz` file
5. Uploads it to Atlas. 5. Uploads it to Atlas.
VMX is a fast way to build and test locally, but you can easily substitute another builder. VMX is a fast way to build and test locally, but you can easily substitute
another builder.
``` {.javascript} ``` {.javascript}
{ {
@ -143,5 +146,5 @@ artifact (the vmx file in this case) and it will not have the desired result.
} }
] ]
You can create multiple post-processor chains to handle multiple builders (for example, You can create multiple post-processor chains to handle multiple builders (for
building linux and windows binaries during the same build). example, building linux and windows binaries during the same build).

4
website/source/docs/post-processors/compress.html.markdown
View File

@ -27,8 +27,8 @@ you will need to specify the `output` option.
detected packer defaults to `.tar.gz` behavior but will not change detected packer defaults to `.tar.gz` behavior but will not change
the filename. the filename.
You can use `{{.BuildName}}` and `{{.BuilderType}}` in your output path. You can use `{{.BuildName}}` and `{{.BuilderType}}` in your output path. If
If you are executing multiple builders in parallel you should make sure you are executing multiple builders in parallel you should make sure
`output` is unique for each one. For example `packer_{{.BuildName}}.zip`. `output` is unique for each one. For example `packer_{{.BuildName}}.zip`.
- `compression_level` (integer) - Specify the compression level, for - `compression_level` (integer) - Specify the compression level, for