Inspired by dannyfritz/commit-message-emoji
See also gitmoji.
Commit type | Emoji |
---|---|
Initial commit | 🎉 :tada: |
Version tag | 🔖 :bookmark: |
New feature | ✨ :sparkles: |
Bugfix | 🐛 :bug: |
Inspired by dannyfritz/commit-message-emoji
See also gitmoji.
Commit type | Emoji |
---|---|
Initial commit | 🎉 :tada: |
Version tag | 🔖 :bookmark: |
New feature | ✨ :sparkles: |
Bugfix | 🐛 :bug: |
// ==UserScript== | |
// @name Translate Amazon | |
// @namespace http://your.homepage/ | |
// @version 0.1 | |
// @description Translate the Amazon service names into plain English. See https://www.expeditedssl.com/aws-in-plain-english | |
// @author @ideasasylum | |
// @match https://*.console.aws.amazon.com/console/home?* | |
// @grant none | |
// ==/UserScript== |
#!/bin/bash | |
# | |
# Docker toolbox init OS X | |
# | |
FORCE=${1-true} | |
USERS="/Users" | |
VAR="/var/folders" |
app: | |
build: . | |
links: | |
- db:db | |
- redis:redis | |
- memcache:memcache | |
volumes: | |
- ./:/app | |
environment: | |
PGHOST: db |
require 'json' | |
require 'optparse' | |
require 'net/http' | |
require 'net/https' | |
def parse_options(argv) | |
####################################### | |
# Please change the following as needed | |
####################################### |
# The following example imports subkey DF6C5C29 into a secret keyring that | |
# already contains 55C794A2 | |
% gpg --list-secret-keys | |
sec 4096R/AF72A573 2012-06-17 | |
uid Andrew Ho <andrewho@andrewho.co.uk> | |
ssb 4096R/55C794A2 2012-06-17 | |
% mkdir 55C794A2 | |
% cd 55C794A2 |
# Custom Keymap for RubyMine (by fxn) | |
The keymap I work with, inspired by my past Emacs years, these are configurable | |
in Preferences -> Keymap. | |
Most of these have no conflict with the existing shortcuts, I use the default | |
keymap for Mac OS X and add these ones (an action can have several shortcuts). | |
To configure two strokes enter the first one in the main textfield (eg, C-g), | |
check "Second Stroke" and the second one there (eg, c). |
A slightly updated version of this doc is here on my website.
I visited with PagerDuty yesterday for a little Friday beer and pizza. While there I got started talking about Go. I was asked by Alex, their CEO, why I liked it. Several other people have asked me the same question recently, so I figured it was worth posting.
The first 1/2 of Go's concurrency story. Lightweight, concurrent function execution. You can spawn tons of these if needed and the Go runtime multiplexes them onto the configured number of CPUs/Threads as needed. They start with a super small stack that can grow (and shrink) via dynamic allocation (and freeing). They are as simple as go f(x)
, where f()
is a function.
This configuration works with Upstart on Ubuntu 12.04 LTS
The reason why it needs to be done this way (i.e. with the pre-start
and post-stop
stanzas), is because Upstart
is unable to track whever Unicorn master process re-execs itself on hot deploys. One can use it without hot-deploys
and run Unicorn in foreground also, it then only needs one exec stanza.
This presumes you are not using RVM, so no voodoo dances.