madscience 0.0.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: d663ca902dac91136dee8d76a24b2b969a927f8c
+  data.tar.gz: ad13b9a208e731d49555bab3be816b0cda0dde81
+SHA512:
+  metadata.gz: 117990acc715bf9998d3d641510f4e3ab1123ab8cb186652b719b70caee7e74725399eec563e03fa4d43fed4e0a95c96825bb0903ffb0075b5d52b2564e1ddf8
+  data.tar.gz: dda335908e202e492a2c090f0404d6aae45e17b53c8fb7b70e9348ecde20268b0cad0cb23ca8e996d9295d07f0afedfa7182d757278148c56058fd36777fce30

data/.gitignore

@@ -0,0 +1,17 @@
+*.gem
+*.rbc
+.bundle
+.config
+.yardoc
+Gemfile.lock
+InstalledFiles
+_yardoc
+coverage
+doc/
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp

data/Cheffile

@@ -0,0 +1,9 @@
+#!/usr/bin/env ruby
+#^syntax detection
+
+site 'http://community.opscode.com/api/v1'
+
+cookbook 'vagrant',
+  :git => 'https://github.com/jtimberman/vagrant-cookbook'
+cookbook 'virtualbox',
+  :git => 'https://github.com/jtimberman/virtualbox-cookbook'

data/Cheffile.lock

@@ -0,0 +1,34 @@
+SITE
+  remote: http://community.opscode.com/api/v1
+  specs:
+    apt (2.4.0)
+    chef_handler (1.1.6)
+    dmg (2.2.0)
+    windows (1.33.1)
+      chef_handler (>= 0.0.0)
+    yum (3.2.2)
+
+GIT
+  remote: https://github.com/jtimberman/vagrant-cookbook
+  ref: master
+  sha: bd1af8d31f9f20a7856b66f641b37f093ec3c530
+  specs:
+    vagrant (0.2.0)
+      dmg (>= 0.0.0)
+      windows (>= 0.0.0)
+
+GIT
+  remote: https://github.com/jtimberman/virtualbox-cookbook
+  ref: master
+  sha: f694fbed1827128f9aa915e07c2a2d5598c0c6f6
+  specs:
+    virtualbox (0.7.2)
+      apt (>= 0.0.0)
+      dmg (>= 0.0.0)
+      windows (>= 0.0.0)
+      yum (>= 0.0.0)
+
+DEPENDENCIES
+  vagrant (>= 0)
+  virtualbox (>= 0)
+

data/Gemfile

@@ -0,0 +1,4 @@
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in madscience.gemspec
+gemspec

data/LICENSE.txt

@@ -0,0 +1,9 @@
+Vagrant-Cookbook copyright 2013-2014 Joshua Timberman,
+Virtualbox-Cookbook copyright 2013-2014 Joshua Timberman,
+everything else Copyright (c) 2014, Noah Gibbs
+
+License for everything else is proprietary. For now, please do not
+redistribute without the prior written permission of Noah Gibbs.
+
+Except Joshua Timberman's Vagrant and VirtualBox cookbooks. You can
+redistribute those according to the Apache 2.0 license.

data/README.md

@@ -0,0 +1,126 @@
+# MadScience
+
+The MadScience stack helps deploy your Rails application to a new local VM and
+a matching production environment.  It uses Vagrant, Chef and Capistrano. It
+stores deployment credentials under your home directory in the
+.deploy_credentials subdirectory.
+
+The Mad Science Stack is based on a class called Ruby Mad Science
+(http://rubymadscience.com), a paid product.
+
+Each version of the Mad Science Stack is tested with a specific version of
+each tool. The current version of the Mad Science Stack, Version 0.0.1,
+installs and uses these other specific tool versions:
+
+   Chef: 11.12.8
+   Librarian-Chef: 0.0.3
+   Knife-Solo: 0.4.2
+   Vagrant: 1.6.3
+   Vagrant-Omnibus: 1.4.2
+   VirtualBox: 4.3.12
+   Capistrano: 3.2.1
+   Capistrano-Rails: 1.1.1
+   Capistrano-Bundler: 1.1.2
+   Capistrano-RVM: 0.1.1
+   SSHKit: 1.5.1
+
+Note that this doesn't include the tools that are (usually) deployed to like
+NGinX, Ubuntu Linux and so on -- those depend on the deploy repository.
+
+Not all of this software is used by every deploy repository. For instance,
+Capistrano can be optional. But if you use it with a given version of
+MadScience, that's the version being used.
+
+The MadScience stack also has these dependencies:
+Bundler and RubyGems (some recent version)
+SSH
+A git repo to deploy, unless you just want the sample app
+
+A deploy repo will also use a number of specific gem and cookbook versions, of
+course.
+
+## Installation
+
+Add 'madscience' to your Gemfile or install it manually:
+
+   gem install madscience
+
+You'll also need Git and SSH installed already.
+
+It's possible to clone this repo and run madscience locally, too.
+
+## Usage
+
+After you've installed the Mad Science gem ("gem install madscience"), you'll
+want to run the setup command:
+
+   sudo madscience setup
+   # OR, with rvm:
+   rvmsudo madscience setup # this leaves RVM's env vars set properly
+
+This will install, help install or check versions of all software in the
+currently installed Mad Science Stack version. It will get you set up
+correctly or complain if it can't. Make sure to use the right Ruby if you're
+using a version manager (RVM, chruby, rbenv, etc.)
+
+It will also set up initial deploy credentials such as SSH keys. You can
+modify the results in ~/.deploy_credentials if you like. The default setup is
+meant to be tolerably secure and fairly convenient. You only need one
+~/.deploy_credentials directory no matter how many Rubies you have.
+
+### Cloning
+
+The setup command will set up basic deployment credentials if you don't have
+them. It will also set up VirtualBox and Vagrant, and install the appropriate
+tools and gems.
+
+However, you'll still need a deploy repo - code that's specific to your setup,
+including what host to install to, what Chef cookbooks to use and where to
+find your application.
+
+There's a default one (NOTE: currently it's a private repo! There will be a
+public repo for this later.) Or you can set the MADSCIENCE_REPO environment
+variable to customize what repo to clone from, or just clone the repo
+yourself, locally.
+
+   # No sudo here, you don't want root (admin) to own these files
+   madscience clone
+
+This will clone and configure a new repository which you can configure for
+your app(s).
+
+### Implementation
+
+The setup command will run Chef locally on your development machine. So it'll
+leave behind a Chef temp directory (/var/chef on Linux or Mac OS X machines.)
+That's also why you need to run it as the administrator -- that and the fact
+that you're installing virtualization software, of course.
+
+### Running locally
+
+If you've cloned the madscience gem from GitHub and don't have it installed,
+you'll want to run it like this:
+
+   # No RVM? Change "rvmsudo" to "sudo"
+   bundle install
+   librarian-chef install
+   rvmsudo bundle exec bin/madscience setup
+   bundle exec bin/madscience clone
+
+## License
+
+* Author:: Noah Gibbs (the.codefolio.guy@gmail.com)
+* Vagrant-Cookbook copyright 2013-2014 Joshua Timberman, Apache 2.0 License
+* Virtualbox-Cookbook copyright 2013-2014 Joshua Timberman, Apache 2.0 License
+* Everything else (C) Noah Gibbs, 2014
+
+With the exception of Joshua Timberman's cookbooks, this code is under the MIT
+license.
+
+## Contributing
+
+1. Fork it ( http://github.com/noah.gibbs/madscience/fork )
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Add some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create new Pull Request

data/Rakefile

@@ -0,0 +1 @@
+require "bundler/gem_tasks"

data/TODO

@@ -0,0 +1,17 @@
+Mac and Linux:
+  Ensure current user has an id_rsa/id_dsa SSH key available
+
+Windows:
+  runas /user:Administrator "cmd /C chef-client"  (or equivalent chef-solo)
+  install Vagrant and VirtualBox MSI files, check registry for definitive MSI version string
+
+    MSI PLEASE NOTE - For proper idempotence the resource's package_name should be
+    the same as the 'DisplayName' registry value in the uninstallation data
+    that is created during package installation. The easiest way to
+    definitively find the proper 'DisplayName' value is to install the package
+    on a machine and search for the uninstall information under the following
+    registry keys:
+      HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall
+      HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Uninstall
+      HKEY_LOCAL_MACHINE\Software\Wow6464Node\Microsoft\Windows\CurrentVersion\Uninstall
+      For maximum flexibility the source attribute supports both remote and local installation packages.

data/bin/madscience

@@ -0,0 +1,90 @@
+#!/usr/bin/env ruby
+
+MADSCIENCE_REPO_URL = ENV['MADSCIENCE_REPO'] ||
+  "git@github.com:noahgibbs/rubydeploy-deploy-repo.git"
+
+# TODO: Add Windows runas incantation to replace sudo on Windows
+USAGE_INFO = <<USAGE
+Usage:
+  sudo #{$0} setup
+  #{$0} clone
+
+  OR
+
+  rvmsudo #{$0} setup
+  ${$0} clone
+USAGE
+
+# First, make sure we have the right Ruby version
+# TODO: add more checks for RUBY_VERSION, RUBY_PLATFORM, etc. Ensure MRI.
+if RUBY_PLATFORM == "java"
+  raise "Please install and run the MadScience gem in the Ruby you'll be deploying with! That means MRI 1.9.2+!"
+end
+unless RUBY_VERSION[0..1] == "2." || RUBY_VERSION[0..2] == "1.9"
+  raise "Please install Ruby version 1.9.2+ for MadScience compatibility!"
+end
+
+# Require the MadScience gem, which will then be in $LOAD_PATH
+require "madscience"
+require "madscience/version"
+
+cur_dir = Dir.pwd
+
+# Change to MadScience dir to get correct Gemfile
+ms_path = $LOAD_PATH.detect { |p| File.exist? File.join(p, "..", ".madscience_gem_location") }
+raise "Can't find MadScience gem in $LOAD_PATH: #{$LOAD_PATH.inspect}!" unless ms_path
+Dir.chdir File.join(ms_path, "..")
+
+# Set up Bundler with the MadScience gem's Gemfile
+require "bundler"
+Bundler.setup
+
+# TODO: make sure we're running with sufficient permissions - or use sudo?
+# On Mac and Linux, can check for Process.uid == 0
+
+if ARGV[0] == "setup"
+  if ARGV.size > 1
+    puts "#{$0} setup takes no other arguments!"
+    exit -1
+  end
+  # Now we'll use Chef to install the right version of Vagrant
+  # with the right plugin(s).
+
+  system("librarian-chef", "install")
+  system("chef-solo", "-c", "solo.rb") or exit -1
+  exit 0  # Success!
+end
+
+if ARGV[0] == "clone"
+  if ARGV.size > 1
+    puts "#{$0} clone takes no other arguments!"
+    exit -1
+  end
+
+  # Change back to pre-Bundler-setup directory where we were invoked
+  Dir.chdir cur_dir
+
+  location = "../deploy_repo"
+
+  # Now we'll git clone the MadScience repo, at a branch corresponding to our MadScience version
+  # TODO: check out MadScience::VERSION branch when we start having real releases
+  cmd = "git clone #{MADSCIENCE_REPO_URL} #{location}"
+
+  unless system cmd
+    puts "Couldn't successfully clone MadScience repo from #{MADSCIENCE_REPO_URL}, branch #{MadScience::VERSION}!"
+    exit -1
+  end
+
+  puts "Successfully cloned repo into #{location} under directory #{cur_dir}. Now go in and customize it."
+  exit 0
+end
+
+if ARGV == []
+  puts "No command given."
+  puts USAGE_INFO
+  exit -1
+end
+
+puts "Unrecognized command: #{ARGV.inspect}!"
+puts USAGE_INFO
+exit -1

data/cookbooks/apt/CHANGELOG.md

@@ -0,0 +1,183 @@
+apt Cookbook CHANGELOG
+======================
+This file is used to list changes made in each version of the apt cookbook.
+
+v2.4.0 (2014-05-15)
+-------------------
+- [COOK-4534]: Add option to update apt cache at compile time
+
+
+v2.3.10 (2014-04-23)
+--------------------
+- [COOK-4512] Bugfix: Use empty PATH if PATH is nil
+
+
+v2.3.8 (2014-02-14)
+-------------------
+### Bug
+- **[COOK-4287](https://tickets.opscode.com/browse/COOK-4287)** - Cleanup the Kitchen
+
+
+v2.3.6
+------
+* [COOK-4154] - Add chefspec matchers.rb file to apt cookbook
+* [COOK-4102] - Only index created repository
+
+
+v2.3.6
+------
+* [COOK-4154] - Add chefspec matchers.rb file to apt cookbook
+* [COOK-4102] - Only index created repository
+
+
+v2.3.4
+------
+No change. Version bump for toolchain sanity
+
+
+v2.3.2
+------
+- [COOK-3905] apt-get-update-periodic: configuration for the update period
+- Updating style for rubocops
+- Updating test-kitchen harness
+
+
+v2.3.0
+------
+### Bug
+- **[COOK-3812](https://tickets.opscode.com/browse/COOK-3812)** - Add a way to bypass the apt existence check
+
+### Improvement
+- **[COOK-3567](https://tickets.opscode.com/browse/COOK-3567)** - Allow users to bypass apt-cache via attributes
+
+
+v2.2.1
+------
+### Improvement
+- **[COOK-664](https://tickets.opscode.com/browse/COOK-664)** - Check platform before running apt-specific commands
+
+
+v2.2.0
+------
+### Bug
+- **[COOK-3707](https://tickets.opscode.com/browse/COOK-3707)** - multiple nics confuse apt::cacher-client
+
+v2.1.2
+------
+### Improvement
+- **[COOK-3551](https://tickets.opscode.com/browse/COOK-3551)** - Allow user to set up a trusted APT repository
+
+v2.1.1
+------
+### Bug
+- **[COOK-1856](https://tickets.opscode.com/browse/COOK-1856)** - Match GPG keys without case sensitivity
+
+v2.1.0
+------
+- [COOK-3426]: cacher-ng fails with restrict_environment set to true
+- [COOK-2859]: cacher-client executes out of order
+- [COOK-3052]: Long GPG keys are downloaded on every run
+- [COOK-1856]: apt cookbook should match keys without case sensitivity
+- [COOK-3255]: Attribute name incorrect in README
+- [COOK-3225]: Call use_inline_resources only if defined
+- [COOK-3386]: Cache dir for apt-cacher-ng
+- [COOK-3291]: apt_repository: enable usage of a keyserver on port 80
+- Greatly expanded test coverage with ChefSpec and Test-Kitchen
+
+v2.0.0
+------
+### Bug
+
+- [COOK-2258]: apt: LWRP results in error under why-run mode in apt 1.9.0 cookbook
+
+v1.10.0
+-------
+### Improvement
+
+- [COOK-2885]: Improvements for apt cache server search
+
+### Bug
+
+- [COOK-2441]: Apt recipe broken in new chef version
+- [COOK-2660]: Create Debian 6.0 "squeeze" specific template for
+  apt-cacher-ng
+
+v1.9.2
+------
+- [COOK-2631] - Create Ubuntu 10.04 specific template for apt-cacher-ng
+
+v1.9.0
+------
+- [COOK-2185] - Proxy for apt-key
+- [COOK-2338] - Support pinning by glob() or regexp
+
+v1.8.4
+------
+- [COOK-2171] - Update README to clarify required Chef version: 10.18.0
+  or higher.
+
+v1.8.2
+------
+- [COOK-2112] - need [] around "arch" in sources.list entries
+- [COOK-2171] - fixes a regression in the notification
+
+v1.8.0
+------
+- [COOK-2143] - Allow for a custom cacher-ng port
+- [COOK-2171] - On `apt_repository.run_action(:add)` the source file
+  is not created.
+- [COOK-2184] - apt::cacher-ng, use `cacher_port` attribute in
+  acng.conf
+
+v1.7.0
+------
+- [COOK-2082] - add "arch" parameter to apt_repository LWRP
+
+v1.6.0
+------
+- [COOK-1893] - `apt_preference` use "`package_name`" resource instead of "name"
+- [COOK-1894] - change filename for sources.list.d files
+- [COOK-1914] - Wrong dir permissions for /etc/apt/preferences.d/
+- [COOK-1942] - README.md has wrong name for the keyserver attribute
+- [COOK-2019] - create 01proxy before any other apt-get updates get executed
+
+v1.5.2
+------
+- [COOK-1682] - use template instead of file resource in apt::cacher-client
+- [COOK-1875] - cacher-client should be Environment-aware
+
+V1.5.0
+------
+- [COOK-1500] - Avoid triggering apt-get update
+- [COOK-1548] - Add execute commands for autoclean and autoremove
+- [COOK-1591] - Setting up the apt proxy should leave https
+  connections direct
+- [COOK-1596] - execute[apt-get-update-periodic] never runs
+- [COOK-1762] - create /etc/apt/preferences.d directory
+- [COOK-1776] - apt key check isn't idempotent
+
+v1.4.8
+------
+* Adds test-kitchen support
+- [COOK-1435] - repository lwrp is not idempotent with http key
+
+v1.4.6
+------
+- [COOK-1530] - apt_repository isn't aware of update-success-stamp
+  file (also reverts COOK-1382 patch).
+
+v1.4.4
+------
+- [COOK-1229] - Allow cacher IP to be set manually in non-Chef Solo
+  environments
+- [COOK-1530] - Immediately update apt-cache when sources.list file is dropped off
+
+v1.4.2
+------
+- [COOK-1155] - LWRP for apt pinning
+
+v1.4.0
+------
+- [COOK-889] - overwrite existing repo source files
+- [COOK-921] - optionally use cookbook\_file or remote\_file for key
+- [COOK-1032] - fixes problem with apt repository key installation