A ZSH theme optimized for people who use:
- Solarized
- Git
- Unicode-compatible fonts and terminals (I use iTerm2 + Menlo)
For Mac users, I highly recommend iTerm 2 + Solarized Dark
#!/bin/sh | |
# Shell script to install your public key on a remote machine | |
# Takes the remote machine name as an argument. | |
# Obviously, the remote machine must accept password authentication, | |
# or one of the other keys in your ssh-agent, for this to work. | |
# | |
# http://www.devthought.com/2009/09/19/get-ssh-copy-id-in-mac-os-x/ | |
# |
# | |
# This is an example of a knife.rb configuration that uses yml and a | |
# simple env var (CHEF_ENV) to manage multiple hosted Chef environments. | |
# | |
# Example usage: | |
# export CHEF_ENV=evnironment_01 | |
# knife status | |
# | |
# Based on: http://blog.blankpad.net/2010/09/28/multiple-knife-environments---the-return/ | |
# |
# MANAGED VIA GIT https://gist.github.com/spuder/11360474 | |
# CHANGES MAY BE OVERWRITTEN | |
# Import the bash_ps1, adds dotted lines after every command | |
if [ -f "$HOME/.bash_ps1" ]; then | |
. "$HOME/.bash_ps1" | |
fi | |
export CLICOLOR=1 |
#!/bin/bash | |
#Usage: Execute the following command: | |
<<COMMENT1 | |
curl -L https://gist.github.com/spuder/11360474/raw/ | bash -x | |
COMMENT1 |
# -*- mode: ruby -*- | |
# vi: set ft=ruby : | |
# Vagrantfile API/syntax version. Don't touch unless you know what you're doing! | |
VAGRANTFILE_API_VERSION = "2" | |
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| | |
config.vm.synced_folder "../", "/vagrant_data" # Mount directory up a level so puppet module list can find modules | |
config.vm.synced_folder ".", "/vagrant" |
#!/usr/bin/env bash | |
# A simple script to build a docker container | |
# Pre and Post functions are where you place any optional commands (eg. git clone) | |
# Sets name for docker container docker build -t 'foo/bar:latest | |
readonly DOCKER_USER='foo' | |
readonly DOCKER_NAME='bar' | |
readonly DOCKER_TAG='latest' | |
# Mac and boot2docker don't use root for docker command |
ttps://github.com/puppetlabs/modulesync | |
https://github.com/petems/puppet-doc-lint | |
http://puppet-analytics.org | |
http://www.slideshare.net/petems/puppet-module-anti-patterns | |
forge.puppetlabs.com/puppetlabs/tomcat | |
http://tech.opentable.co.uk/blog/categories/beaker/ | |
https://github.com/liamjbennett/beaker/tree/bitvise_hacks | |
https://github.com/theforeman/kafo | |
https://github.com/puppet-community |
If you want to check whether a node run_list
includes a specific role (upon
expansion), then you could use role? method on the Node
object:
node.role?('name')
Alternatively, you can see whether either would work for you:
node.roles.include?('name')
node.run_list?('role[name]')
# Remove items used for building, since they aren't needed anymore | |
#https://github.com/riywo/packer-example/blob/master/scripts/cleanup.sh | |
set -x | |
#Stop Logging | |
service rsyslog stop | |
# Clean Logging | |
logrotate –f /etc/logrotate.conf | |
rm –f /var/log/*-???????? /var/log/*.gz |