puppet_pal 0.0.2 → 0.0.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/README.md +81 -0
- data/lib/puppet_pal/version.rb +1 -1
- metadata +1 -1
data/README.md
CHANGED
|
@@ -1,4 +1,85 @@
|
|
|
1
1
|
## Puppet Pal!
|
|
2
2
|
|
|
3
|
+
The puppet-pal is a lightweight replacement for librarian-puppet. For
|
|
4
|
+
our use cases here at turbosquid, it performs far faster than librarian
|
|
5
|
+
puppet, and is less buggy. Most of our puppet modules come from a single
|
|
6
|
+
repository at github, or from a private repo, with the occassional
|
|
7
|
+
module coming from puppet forge.
|
|
8
|
+
|
|
9
|
+
Because puppet-pal only pulls down a given repo once in a session, it is
|
|
10
|
+
very fast for this use case. It also does not attempt to resolve
|
|
11
|
+
dependencies, so it does not depend on the puppet gem (or even puppet)
|
|
12
|
+
being present on the host, unless you are pulling something from
|
|
13
|
+
puppet forge, in which case you will need puppet installed (although not
|
|
14
|
+
in gem form, unless you choose to do so).
|
|
15
|
+
|
|
16
|
+
There is no lockfile, since we don't worry about dependencies
|
|
17
|
+
|
|
18
|
+
## Installation
|
|
19
|
+
|
|
20
|
+
`gem install puppet_pal`
|
|
21
|
+
|
|
3
22
|
## Usage
|
|
4
23
|
|
|
24
|
+
In the directory that contains your Puppetfile, simply run `puppet-pal`.
|
|
25
|
+
puppet-pal will install the requested modules into the `modules/`
|
|
26
|
+
directory. Puppet Pal understands a subset of the Puppetfile commands
|
|
27
|
+
understood by librarian-puppet:
|
|
28
|
+
|
|
29
|
+
### mod
|
|
30
|
+
|
|
31
|
+
The `mod` command installs a module. The single required parameter
|
|
32
|
+
'name' indentifies the module to be installed. If no other options are
|
|
33
|
+
specified, then the module is pulled from puppetforge (via a `puppet
|
|
34
|
+
module install` call).
|
|
35
|
+
|
|
36
|
+
Otherwise, you may pass the `:git` option to specify a git repo, as well as a `:path`
|
|
37
|
+
option to specify a particular path within that repo.
|
|
38
|
+
|
|
39
|
+
### forge
|
|
40
|
+
For backward compatibility -- does nothing
|
|
41
|
+
|
|
42
|
+
### Example Puppetfile
|
|
43
|
+
|
|
44
|
+
forge "http://forge.puppetlabs.com"
|
|
45
|
+
|
|
46
|
+
mod 'puppetlabs/stdlib'
|
|
47
|
+
|
|
48
|
+
puppet_common_git = "git@foo.bar.com:myrepo/puppet-common.git"
|
|
49
|
+
|
|
50
|
+
mod 'base_packages',
|
|
51
|
+
:git => puppet_common_git,
|
|
52
|
+
:path=> "modules/base_packages"
|
|
53
|
+
mod 'solr',
|
|
54
|
+
:git => puppet_common_git,
|
|
55
|
+
:path=> "modules/solr"
|
|
56
|
+
mod 'mysql',
|
|
57
|
+
:git => puppet_common_git,
|
|
58
|
+
:path=> "modules/mysql"
|
|
59
|
+
mod 'digglr',
|
|
60
|
+
:git => puppet_common_git,
|
|
61
|
+
:path=> "modules/digglr"
|
|
62
|
+
mod 'rvm',
|
|
63
|
+
:git => puppet_common_git,
|
|
64
|
+
:path=> "modules/rvm"
|
|
65
|
+
mod 'deployment_utils',
|
|
66
|
+
:git => puppet_common_git,
|
|
67
|
+
:path=> "modules/deployment_utils"
|
|
68
|
+
mod 'python_web',
|
|
69
|
+
:git => puppet_common_git,
|
|
70
|
+
:path=> "modules/python_web"
|
|
71
|
+
mod 'apache',
|
|
72
|
+
:git => puppet_common_git,
|
|
73
|
+
:path=> "modules/apache"
|
|
74
|
+
mod 'collectd',
|
|
75
|
+
:git => puppet_common_git,
|
|
76
|
+
:path=> "modules/collectd"
|
|
77
|
+
|
|
78
|
+
### Additional command line options
|
|
79
|
+
|
|
80
|
+
* `--puppet_file -f ` Specify a puppetfile path other than the default
|
|
81
|
+
|
|
82
|
+
|
|
83
|
+
|
|
84
|
+
|
|
85
|
+
|
data/lib/puppet_pal/version.rb
CHANGED