gusteau 1.0.7.dev → 1.1.0

data/.travis.yml

@@ -1,8 +1,11 @@
 language: ruby
 rvm:
-  - 1.8.7
   - 1.9.3
   - 2.0.0
-  - rbx
+  - rbx-19mode
+
+matrix:
+  allow_failures:
+      - rvm: rbx-19mode
 env:
   - COVERAGE=coveralls

data/README.md

@@ -6,8 +6,6 @@
 [![Coverage Status](https://coveralls.io/repos/locomote/gusteau/badge.png)](https://coveralls.io/r/locomote/gusteau)
 [![Dependency Status](https://gemnasium.com/locomote/gusteau.png)](https://gemnasium.com/locomote/gusteau)
 
-------------
-
 Gusteau is an easy to use configuration manager for Chef Solo and Vagrant. It aims to:
 
 * Provide existing Chef Solo users with a more efficient workflow
@@ -156,7 +154,7 @@ In addition to specifying `attributes` for environments you can set node-specifc
 ```
 environments:
   staging:
-    attributes:    
+    attributes:
       hostname: staging
     nodes:
       one:
@@ -186,4 +184,4 @@ By default, Gusteau uploads and sets Chef Solo up to use cookbooks from `./cookb
 ```
 cookbooks_path: [ './my-cookbooks', '../something-else' ]
 roles_path: './base-roles'
-```
+```

data/lib/gusteau/version.rb

@@ -1,3 +1,3 @@
 module Gusteau
-  VERSION = "1.0.7.dev"
+  VERSION = "1.1.0"
 end

data/template/README.md.erb

@@ -16,7 +16,7 @@ A configuration file for Vagrant which includes gusteau as a plugin. It detects
 
 ### cookbooks
 
-Gusteau uploads `site-cookbooks` and `cookbooks` directories when you converge a node. Between the two, `cookbooks` is a directory for your vendorized cookbooks. This example project uses Berkshelf, so in order to populate the directory run
+By default, Gusteau uploads `site-cookbooks` and `cookbooks` directories when you converge a node. Between the two, `cookbooks` is a directory for your vendorized cookbooks. This example project uses Berkshelf, so in order to populate the directory run
 
 ```
 berks install --path ./cookbooks
@@ -46,24 +46,23 @@ gusteau converge example-box
 
 ## Testing your Chef-Repo
 
-It is a very good practice to have tests for your Chef-driven infrastructure.
-This project includes an example [test-kitchen](https://github.com/opscode/test-kitchen) setup to get you started.
+It is a very good practice to have integration tests for your Chef-powered infrastructure.
+This project includes an example setup to get you started.
 
 The tests are implemented using the excellent [serverspec](http://serverspec.org/) framework.
 
 There are two important bits to have a look at:
 
-### test
+### spec
 
 The directory where integration tests are placed.
 
-### .kitchen.yml
+### `spec/spec_helper.rb`
 
-Test-kitchen configuration file where test platforms and suites are specified.
+Where serverspec is configured against your Gusteau nodes.
 
 To run the tests:
 
 ```
-bundle exec kitchen test
+bundle exec rake spec
 ```
-

metadata

@@ -1,8 +1,8 @@
 --- !ruby/object:Gem::Specification
 name: gusteau
 version: !ruby/object:Gem::Version
-  version: 1.0.7.dev
-  prerelease: 6
+  version: 1.1.0
+  prerelease: 
 platform: ruby
 authors:
 - Vasily Mikhaylichenko
@@ -10,7 +10,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-07-09 00:00:00.000000000 Z
+date: 2013-07-10 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: optitron
@@ -301,13 +301,16 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: -925332581546681744
+      hash: -4376898351999153113
 required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
   requirements:
-  - - ! '>'
+  - - ! '>='
     - !ruby/object:Gem::Version
-      version: 1.3.1
+      version: '0'
+      segments:
+      - 0
+      hash: -4376898351999153113
 requirements: []
 rubyforge_project: 
 rubygems_version: 1.8.23