testing what the chef needed to run a docker website would look like
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
chef
cloudformation
packer
util
vagrant/blog-full
.drone.yml
.gitignore
README.md
TODO.md

README.md

website-docker

A project I am putting together to see what it looks like to build a machine using chef and docker together

Build Status

Running Tests

Foodcritic Analysis:

cd chef
bundle install
bundle exec foodcritic -f all site-cookbooks/

Kitchen Tests:

cd chef
bundle install

# List the currently running images
bundle exec kitchen list

# Login to one of the boxes that has been converged. Used for manual testing.
kitchen login blog-full-raring64

# Run chef and get a VM setup. Note that this will not tear down the VM
# and should be used for development.
bundle exec kitchen converge [blog-full-raring64]

# Run the tests for in the kitchen. Note that this will not tear down the VM
# and should be used for development.
bundle exec kitchen verify [blog-full-raring64]

# Destroy test instances that may be hanging around from the above commands
bundle exec kitchen destroy

# Run all tests and destroy the image after complete. Without the --destroy
# flag the vms would not get torn down on a test failure. Used mostly in 
# CI environments
bundle exec kitchen test --destroy