Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
P
packer
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Kristopher Ruzic
packer
Commits
f02e5cde
Commit
f02e5cde
authored
Jun 08, 2013
by
Mitchell Hashimoto
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
website: what is packer
parent
aa421412
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
9 additions
and
3 deletions
+9
-3
website/source/docs/what-is-packer.html.markdown
website/source/docs/what-is-packer.html.markdown
+9
-2
website/source/layouts/docs.erb
website/source/layouts/docs.erb
+0
-1
No files found.
website/source/docs/what-is-packer.html.markdown
View file @
f02e5cde
...
...
@@ -7,7 +7,9 @@ layout: "docs"
Packer is a tool for creating identical machine images for multiple platforms
from a single source configuration. Packer is lightweight, runs on every major
operating system, and is highly performant, creating machine images for
multiple platforms in parallel.
multiple platforms in parallel. Packer does not replace configuration management
like Chef or Puppet. In fact, when building images, Packer is able to use tools
like Chef or Puppet to install software onto the image.
A _machine image_ is a single static unit that contains a pre-configured operating
system and installed software which is used to quickly create new running machines.
...
...
@@ -18,7 +20,8 @@ VMDK/VMX files for VMware, OVF exports for VirtualBox, etc.
Historically, creating
these images has been a predominantly manual process. Any existing automated tools were able to
create only one type of image. Packer, on the other hand, is able to automatically
create any type of image, all from a single source configuration.
create any type of image, all from a single source configuration. This unlocks
untapped potential in developing, testing, and deploying applications.
Pre-baked machine images have a lot of advantages, but we've been unable to
benefit from them because they have been too tedious to create and manage.
...
...
@@ -45,3 +48,7 @@ they'll be caught early, rather than several minutes after a machine is launched
can be quickly launched and smoke tested to verify that things appear to be
working. If they are, you can be confident that any other machines launched
from that image will function properly.
Packer makes it extremely easy to take advantage of all these benefits.
What are you waiting for? Let's get started!
website/source/layouts/docs.erb
View file @
f02e5cde
...
...
@@ -25,7 +25,6 @@
<div
class=
"well sidebar-nav"
style=
"padding: 8px 0;"
>
<ul
class=
"nav nav-list"
>
<li><a
href=
"/docs/what-is-packer.html"
>
What is Packer?
</a></li>
<li><a
href=
"#"
>
Use Cases
</a></li>
<li><a
href=
"#"
>
Installation
</a></li>
<li
class=
"nav-header"
>
Basics
</li>
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment