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
824da0fb
Commit
824da0fb
authored
Jun 12, 2013
by
Mitchell Hashimoto
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
website: shell documentation
parent
b2a9e925
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
49 additions
and
1 deletion
+49
-1
website/source/docs/provisioners/shell.html.markdown
website/source/docs/provisioners/shell.html.markdown
+48
-0
website/source/layouts/docs.erb
website/source/layouts/docs.erb
+1
-1
No files found.
website/source/docs/provisioners/shell.html.markdown
0 → 100644
View file @
824da0fb
---
layout
:
"
docs"
---
# Shell Provisioner
Type:
`shell`
The shell provisioner provisions machines built by Packer using shell scripts.
Shell provisioning is the easiest way to get software installed and configured
on a machine.
## Basic Example
The example below is fully functional.
<pre
class=
"prettyprint"
>
{
"type": "shell",
"inline": ["echo foo"]
}
</pre>
## Configuration Reference
The reference of available configuratin options is listed below. The only
required element is either "inline" or "path". Every other option is optional.
*
`inline`
(array of strings) - This is an array of commands to execute.
The commands are concatenated by newlines and turned into a single file,
so they are all executed within the same context. This allows you to
change directories in one command and use something in the directory in
the next and so on. Inline scripts are the easiest way to pull of simple
tasks within the machine.
*
`path`
(string) - The path to a script to upload and execute in the machine.
This path can be absolute or relative. If it is relative, it is relative
to the working directory when Packer is executed.
*
`remote_path`
(string) - The path where the script will be uploaded to
in the machine. This defaults to "/tmp/script.sh". This value must be
a writable location and any parent directories must already exist.
*
`execute_command`
(string) - The command to use to execute the script.
By default this is
`sh {{ .Path }}`
. The value of this is treated as a
[
configuration template
](
/docs/templates/configuration-templates.html
)
.
The only available variable in it is
`Path`
which is the path to the
script to run.
website/source/layouts/docs.erb
View file @
824da0fb
...
...
@@ -47,7 +47,7 @@
<li><a
href=
"/docs/builders/custom.html"
>
Custom
</a></li>
<li
class=
"nav-header"
>
Provisioners
</li>
<li><a
href=
"
#
"
>
Shell Scripts
</a></li>
<li><a
href=
"
/docs/provisioners/shell.html
"
>
Shell Scripts
</a></li>
<li><a
href=
"#"
>
Custom
</a></li>
<li
class=
"nav-header"
>
Other
</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