Gabriel Martinez GMartinez-Sisti

Ansible Vault Environment Variable

Per http://docs.ansible.com/ansible/playbooks_vault.html you can set an environment variable to use a password file for vault access. We can use this to create an environment variable to hold the password.

Password Script

Copy vault-env from this project to ~/bin. Then add this to your ~/.bashrc:

export ANSIBLE_VAULT_PASSWORD_FILE=~/bin/vault-env

An Ansible summary

Jon Warbrick, July 2014, V3.2 (for Ansible 1.7)

Configuration file

intro_configuration.html

First one found from of

Install Docker on Proxmox 4

Proxmox 4 is based on Debian Jessie. Reference for this install: https://docs.docker.com/engine/installation/linux/debian/#/install-using-the-repository

Add the Docker repo for Debian Jessie

$ apt-get install curl
$ curl -fsSL https://apt.dockerproject.org/gpg | apt-key add -
$ echo "deb https://apt.dockerproject.org/repo/ debian-jessie main" > /etc/apt/sources.list.d/docker.list

$ apt-get update

How to add a collapsible section in markdown

1. Example

Click me

Heading

Foo
Bar
- Baz

Qux

Story: Writing Scripts with Go

This is a story about how I tried to use Go for scripting. In this story, I’ll discuss the need for a Go script, how we would expect it to behave and the possible implementations; During the discussion I’ll deep dive to scripts, shells, and shebangs. Finally, we’ll discuss solutions that will make Go scripts work.

Why Go is good for scripting?

While python and bash are popular scripting languages, C, C++ and Java are not used for scripts at all, and some languages are somewhere in between.

	## Based of config provided by logstash ... modified to suit our captures

	## Documentation of the haproxy log formats can be found at the following links:
	## http://code.google.com/p/haproxy-docs/wiki/HTTPLogFormat
	## http://code.google.com/p/haproxy-docs/wiki/TCPLogFormat

	HAPROXYTIME (?!<[0-9])%{HOUR:haproxy_hour}:%{MINUTE:haproxy_minute}(?::%{SECOND:haproxy_second})(?![0-9])
	HAPROXYDATE %{MONTHDAY:haproxy_monthday}/%{MONTH:haproxy_month}/%{YEAR:haproxy_year}:%{HAPROXYTIME:haproxy_time}.%{INT:haproxy_milliseconds}

	# Sample Nginx config with sane caching settings for modern web development
	#
	# Motivation:
	# Modern web development often happens with developer tools open, e. g. the Chrome Dev Tools.
	# These tools automatically deactivate all sorts of caching for you, so you always have a fresh
	# and juicy version of your assets available.
	# At some point, however, you want to show your work to testers, your boss or your client.
	# After you implemented and deployed their feedback, they reload the testing page – and report
	# the exact same issues as before! What happened? Of course, they did not have developer tools
	# open, and of course, they did not empty their caches before navigating to your site.

	resource "aws_iam_policy" "terraform_create_policy" {
	name = "terraform_create_policy"
	path = "/"
	policy = "${data.aws_iam_policy_document.terraform_create_policy.json}"
	}

	data "aws_iam_policy_document" "terraform_create_policy" {
	statement {
	sid = "1"
	actions = [

	:root {
	--primary: #09F;
	--accent: #57A;

	--background: #080808;
	--background-elevated: #222;
	--background-hover: rgba(255, 255, 255, 0.1);
	--sidebar-background: #1a2129;

	--border-dim: #666;

	---
	- hosts: all

	vars:
	UBUNTU_COMMON_ROOT_PASSWORD: 'xxxxx'
	UBUNTU_COMMON_DEPLOY_PASSWORD: 'xxxxx'
	UBUNTU_COMMON_LOGWATCH_EMAIL: [email protected]
	ubuntu_common_deploy_user_name: deploy
	ubuntu_common_deploy_public_keys:
	- ~/.ssh/id_rsa.pub