rwest

These two files should help you to import passwords from mac OS X keychains to 1password.

Assumptions:
1) You have some experience with scripting/are a power-user. These scripts worked for me
   but they haven't been extensively tested and if they don't work, you're on your own!
   Please read this whole document before starting this process. If any of it seems
   incomprehensible/frightening/over your head please do not use these scripts. You will
   probably do something Very Bad and I wouldn't want that.
2) You have ruby 1.9.2 installed on your machine. This comes as standard with Lion, previous
   versions of OS X may have earlier versions of ruby, which *may* work, but then again, they

g3d

#Mac OS X

Mensch coding font

Apps

• Webkit
• Chrome
• Firefox

MohamedAlaa

tmux shortcuts & cheatsheet

start new:

tmux

start new with session name:

tmux new -s myname

anthonysterling

# Usage:    IE={box} vagrant up
#
# Eg.       IE=XPIE6 vagrant up

boxes = {
    "XPIE6"     => "http://aka.ms/vagrant-xp-ie6",
    "XPIE8"     => "http://aka.ms/vagrant-xp-ie8",
    "VistaIE7"  => "http://aka.ms/vagrant-vista-ie7",
    "Win7IE8"   => "http://aka.ms/vagrant-win7-ie8",
    "Win7IE9"   => "http://aka.ms/vagrant-win7-ie9",

bmhatfield

# In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env
# variable pointing GPG to the gpg-agent socket. This little script, which must be sourced
# in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start
# gpg-agent or set up the GPG_AGENT_INFO variable if it's already running.

# Add the following to your shell init to set up gpg-agent automatically for every shell
if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then
    source ~/.gnupg/.gpg-agent-info
    export GPG_AGENT_INFO
else

sindresorhus

# In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env
# variable pointing GPG to the gpg-agent socket. This little script, which must be sourced
# in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start
# gpg-agent or set up the GPG_AGENT_INFO variable if it's already running.

# Add the following to your shell init to set up gpg-agent automatically for every shell
if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then
    source ~/.gnupg/.gpg-agent-info
    export GPG_AGENT_INFO
else

peff

#!/usr/bin/perl
#
# Generate a listing of all paths ever used in the repository, along with the
# disk space used by the path throughout the entire history.  Note that sizes
# for trees are cumulative; they include the sizes of all of the paths below
# them, in addition to the tree storage itself. All sizes are in bytes, and
# reflect git's delta and zlib compression.
#
# One caveat is that this is just the _current_ on-disk size. The on-disk size
# of each object may change if git repacks and chooses different delta bases,

jonico

<dashboard>
  <label>Octodemo performance stats</label>
  <row>
    <panel>
      <chart>
        <title>Top fetched repos</title>
        <search>
          <query>index="octodemo" upload-pack user| top repo</query>
          <earliest>@w0</earliest>
          <latest>now</latest>

bmhatfield

# If you use bash, this technique isn't really zsh specific. Adapt as needed.
source ~/keychain-environment-variables.sh

# AWS configuration example, after doing:
# $  set-keychain-environment-variable AWS_ACCESS_KEY_ID
#       provide: "AKIAYOURACCESSKEY"
# $  set-keychain-environment-variable AWS_SECRET_ACCESS_KEY
#       provide: "j1/yoursupersecret/password"
export AWS_ACCESS_KEY_ID=$(keychain-environment-variable AWS_ACCESS_KEY_ID);
export AWS_SECRET_ACCESS_KEY=$(keychain-environment-variable AWS_SECRET_ACCESS_KEY);

jonico

#!groovy
import groovy.json.JsonOutput
import groovy.json.JsonSlurper

def label = "mypod-${UUID.randomUUID().toString()}"
podTemplate(label: label, yaml: """
spec:
      containers:
      - name: mvn
        image: maven:3.3.9-jdk-8