sambot 0.1.107 → 0.1.108
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/lib/sambot/docs/cookbook/build.txt +16 -0
- data/lib/sambot/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: a1fc1a1eefcfd08915e42c733730c73a581106c2
|
4
|
+
data.tar.gz: aa79135d18b60a01b3942f89dadbe20289d8ac8a
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: b06b48af74c3b38b6f06b6d13694a33900aa3e59a39c87cc42c291e6031c9da61d507310b29ca41b715636d5a38e62f30f2983e8fb44646b836a562d3cd5176f
|
7
|
+
data.tar.gz: fe8cdd28b5c7eaca710499c13aeca93fc1191918b272c287b0e3f1c47a9cde748b17c4b93b2efd05056d8c3c76c34e5be42b78fd705a11daeb794659b455e358
|
@@ -6,6 +6,22 @@ The configuration file should be called .config.yml and stored in the root of
|
|
6
6
|
the Chef cookbook. After the command is run, all the files required to author
|
7
7
|
a cookbook will be placed in the same directory as the .config.yml file.
|
8
8
|
|
9
|
+
An example default structure for a cookbook would be the below:
|
10
|
+
|- recipes
|
11
|
+
|- default.rb
|
12
|
+
|- spec
|
13
|
+
|- .config.yml
|
14
|
+
|- README.md
|
15
|
+
|
16
|
+
The above is the minimal folder structure required for a cookbook.
|
17
|
+
|
18
|
+
The .config.yml has the following structure:
|
19
|
+
* name - the name of the cookbook
|
20
|
+
* version - the version of the cookbook
|
21
|
+
* platforms - the different platforms the cookbook can run on, centos and/or windows
|
22
|
+
* description - a description for the cookbook
|
23
|
+
* suites - the suites attribute that would go into the .kitchen.yml files and should follow exactly that structure
|
24
|
+
|
9
25
|
Furthermore, a pre-push Git hook will be generated which will check the cookbook
|
10
26
|
files before allowing the origin repository to be updated.
|
11
27
|
|
data/lib/sambot/version.rb
CHANGED