No description
Find a file
2012-10-03 22:45:08 -07:00
config Nah, don't require plain boxen 2012-10-02 16:25:10 -07:00
manifests fail if no FDE, this should be parity once rubygems provider is fixed 2012-10-03 22:45:08 -07:00
modules Update docs a bit for projects example 2012-10-03 11:25:10 -07:00
script Update for Boxen 0.1.0 development 2012-10-03 13:47:13 -07:00
shared Things managed by librarian-puppet go in shared/ 2012-10-03 10:24:21 -07:00
vendor bump puppet-boxen to 0.0.12 for security settings 2012-10-03 22:39:24 -07:00
.gitignore Bring back dat cache 2012-10-03 13:55:23 -07:00
.rbenv-version Initial commit 2012-10-02 11:43:59 -07:00
Gemfile Use the released 0.1.0 gem 2012-10-03 14:05:55 -07:00
Gemfile.lock bump boxen to 0.2.3 2012-10-03 20:27:34 -07:00
Puppetfile bump puppet-boxen to 0.0.12 for security settings 2012-10-03 22:39:24 -07:00
Puppetfile.lock bump puppet-boxen to 0.0.12 for security settings 2012-10-03 22:39:24 -07:00
README.md update README 2012-10-03 17:46:26 -07:00

Our Boxen

This is a template Boxen project designed for your organization to fork and modify appropriately.

Getting Started

  1. Fork this repository.
  2. Modify the Puppetfile and modules/ to your heart's content.
  3. Get a copy of your fork somewhere locally.
  4. Install the XCode Command Line Tools package. You need an Apple ID. We know. It sucks. You can thank Apple for not allowing the Command Line Tools to be redistributed publicly.
  5. cd to that dir and run script/boxen
  6. Rock out. 🤘