Sergey Bogatyrets serjs

In a perfect world, where things are done well, not just quickly, I would expect to find the following when joining the company:

Documentation

Accurate / up-to-date systems architecture diagram
Accurate / up-to-date network diagram
Out-of-hours support plan
Incident management plan

Overview

Here is an example shared configuration for knife. You can drop this off in your chef-repo/.chef/ directory, and multiple developers can use the same knife configuration to interact with more than one Chef server, or the Opscode platform.

By using Bash functions and environment variables we can change the chef server, which knife is configured to use, on the fly.

NOTE: knife will probably ignore your ~/.chef/knife.rb once you begin using a shared knife.rb in your chef-repo directory.

Preparation

	#!/bin/bash

	set -u
	set -e

	bold=$(tput -T ${TERM:-xterm} bold)
	normal=$(tput -T ${TERM:-xterm} sgr0)


	PYTHON_BIN='python3'

	#!/bin/bash
	### BEGIN INIT INFO
	# Provides: says-dot-com-production
	# Required-Start: $all
	# Required-Stop: $network $local_fs $syslog
	# Default-Start: 2 3 4 5
	# Default-Stop: 0 1 6
	# Short-Description: Start the says-dot-com-production unicorns at boot
	# Description: Enable says-dot-com-staging at boot time.
	### END INIT INFO