https://github.com/tknerr/sample-infrastructure-repo

sample infrastructure repository based on vagrant and application cookbooks
https://github.com/tknerr/sample-infrastructure-repo

Last synced: about 2 months ago
JSON representation

sample infrastructure repository based on vagrant and application cookbooks

• Host: GitHub
• URL: https://github.com/tknerr/sample-infrastructure-repo
• Owner: tknerr
• Created: 2013-10-05T01:56:05.000Z (over 11 years ago)
• Default Branch: master
• Last Pushed: 2016-05-10T16:41:48.000Z (over 8 years ago)
• Last Synced: 2023-03-23T00:22:27.310Z (almost 2 years ago)
• Language: Ruby
• Size: 21.5 KB
• Stars: 16
• Watchers: 2
• Forks: 1
• Open Issues: 2
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# README

[![Circle CI](https://circleci.com/gh/tknerr/sample-infrastructure-repo/tree/master.svg?style=shield)](https://circleci.com/gh/tknerr/sample-infrastructure-repo/tree/master)

This is a sample infrastructure repository using the [vagrant-toplevel-cookbooks](https://github.com/tknerr/vagrant-toplevel-cookbooks) plugin to resolve the top-level cookbook dependencies for each of the `Vagrantfile`'s VMs in isolation.

The aim is to get the whole infrastructure up and running with a single `vagrant up`, with all the cookbook dependency resolution happening under the hood.

# TODO

Other stuff that should be demonstrated here:

- [ ] encrypted data bags

- [ ] different providers (e.g. lxc, aws)

- [ ] Cheffile vs. Berksfile

- [ ] different provisioners (puppet?)

# USAGE

First, make sure you have the required Vagrant plugins installed:

	vagrant plugin install vagrant-omnibus

	vagrant plugin install vagrant-toplevel-cookbooks

Now you can bring up and provision the VMs in the `Vagrantfile` with a single command:

	vagrant up app_v1

	vagrant up app_v2