gfoster

Keybase proof

I hereby claim:

• I am gfoster on github.
• I am gfoster594 (https://keybase.io/gfoster594) on keybase.
• I have a public key whose fingerprint is 1B0F 0381 005D 1CDE 5EE2 CA88 112C 1426 CEF0 CC17

To claim this, I am signing this object:

gfoster

[[snippets]]
  description = "Ansible Deploy"
  command = "ansible-playbook -i inventories/staging deploy.yml --extra-vars='application=v3 migrate=true branch=production' --limit <limit>"

[[snippets]]
  description = "Ansible Restart"
  command = "ansible-playbook restart.yml -i inventories/staging --limit <limit>"

[[snippets]]
  description = "s1"

gfoster

[[snippets]]
  description = "Ansible Deploy"
  command = "ansible-playbook -i inventories/staging deploy.yml --extra-vars='application=v3 migrate=true branch=production' --limit <limit>"

[[snippets]]
  description = "Ansible Restart"
  command = "ansible-playbook restart.yml -i inventories/staging --limit <limit>"

[[snippets]]
  description = "s1"

gfoster

[[snippets]]
  description = "Ansible Deploy"
  command = "ansible-playbook -i inventories/staging deploy.yml --extra-vars='application=v3 migrate=true branch=production' --limit <limit>"

[[snippets]]
  description = "Ansible Restart"
  command = "ansible-playbook restart.yml -i inventories/staging --limit <limit>"

[[snippets]]
  description = "s1"

gfoster

[[snippets]]
  description = "Ansible Deploy"
  command = "ansible-playbook -i inventories/staging deploy.yml --extra-vars='application=v3 migrate=true branch=production' --limit <limit>"

[[snippets]]
  description = "Ansible Restart"
  command = "ansible-playbook restart.yml -i inventories/staging --limit <limit>"

gfoster

## FACTS ##

- set_fact: "nginx_conf_file=production-{{ item }}"
  when: "nginx_conf_file is not defined and cluster_env == 'production' and '{{ item }}' in group_names"
  with_items: "{{applications}}"

- set_fact: "nginx_conf_file={{ cluster_env }}"
  when: nginx_conf_file is not defined

## GO ##

gfoster

# -*- mode: yaml -*-

## DB ##

[mysql-master]
staging-1.taskrabbit.in
staging-2.taskrabbit.in
staging-3.taskrabbit.in
staging-4.taskrabbit.in
staging-5.taskrabbit.in

gfoster

#!/usr/bin/env ruby

HELP = <<EOS
git-wtf displays the state of your repository in a readable, easy-to-scan
format. It's useful for getting a summary of how a branch relates to a remote
server, and for wrangling many topic branches.

git-wtf can show you:
- How a branch relates to the remote repo, if it's a tracking branch.
- How a branch relates to integration branches, if it's a feature branch.

gfoster

[alias]
    unstage = reset
    # pull request manipulation
    pr = !git pull-request
    preq = "!f() { git fetch -fu ${2:-origin} refs/pull/$1/head:pr/$1 && git checkout pr/$1; }; f"
    # 'add all' stages all new+changed+deleted files
    aa = !git ls-files -d | xargs git rm && git ls-files -m -o --exclude-standard | xargs git add
    # 'add grep' stages all new+changed that match $1
    ag = "!sh -c 'git ls-files -m -o --exclude-standard | grep $1 | xargs git add' -"
    # 'checkout grep' checkouts any files that match $1