Skip to content
This repository has been archived by the owner on Dec 24, 2019. It is now read-only.

A collection of Chef cookbooks for integration into Vagrant dev-boxes

License

Notifications You must be signed in to change notification settings

dotless-de/devbox-bookshelf

Repository files navigation

devbox-bookshelf

A collection of Chef cookbooks for integration into Vagrant dev-boxes.

Currently under heavy development, thus not guarantied to be complete or even working under all circumstances.

Targets latest Ubuntu LTS and CentOS.

A generated devbox follows our vagrant pattern "export guest's /home/vagrant via NFS, mount and edit on host."

Usage

  • (optional) fork
  • checkout
  • run librarian-chef install
  • Create a Vagrantfile (either vagrant init or rename Vagrantfile.sample) and edit for your needs. Esp. make sure to:
    • use a sane value for your private network IP. The default value 33.33.33.33 might be in use on your system
    • use a correct base-box (box_url) which matches your vm-provider (vmware fusion/workstation, virtual box, etc.pp.)
  • vagrant up [--provider=vmware_fusion]

Box requirements

Consider using a basebox image created by our packer templates.

Running Integration Tests

Integration tests will run using opscode test-kitchen. They'll spawn a vmware fusion vagrant box and run some simple (yet not complete) tests inside the box. Due to the nature of things, this can take quite some time.

To run test, install dependencies first:

bundle install

Run bundle exec kitchen list to get a list of available test instances. For running minimal tests only you may run:

bundle exec kitchen test "minimal-.*"

A test instance is destroyed when tests on this box passed. You may resume a test by running e.g. bundle exec kitchen verify "minimal-.*".

About

A collection of Chef cookbooks for integration into Vagrant dev-boxes

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published