| #!/bin/bash | |
| if [ "$1" = "-h" -o "$1" = "--help" -o -z "$1" ]; then cat <<EOF | |
| appify v3.0.1 for Mac OS X - http://mths.be/appify | |
| Creates the simplest possible Mac app from a shell script. | |
| Appify takes a shell script as its first argument: | |
| `basename "$0"` my-script.sh |
| #!/bin/sh | |
| # This program has two feature. | |
| # | |
| # 1. Create a disk image on RAM. | |
| # 2. Mount that disk image. | |
| # | |
| # Usage: | |
| # $0 <dir> <size> | |
| # |
Locate the section for your stash remote in the .git/config file. It looks like this:
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = [email protected]:private/repository.git
Now add the line fetch = +refs/pull-requests/*:refs/remotes/origin/pull-requests/* to this section. Obviously, change the stash url to match your project's URL. It ends up looking like this:
| (def adjectives [ | |
| "adorable" | |
| "adventurous" | |
| "aggressive" | |
| "alert" | |
| "attractive" | |
| "average" | |
| "beautiful" | |
| "blue-eyed " | |
| "bloody" |
| var sys = require("sys"); | |
| var fs = require('fs') | |
| var adjectives = []; | |
| var animals = []; | |
| var stdin = process.openStdin(); | |
| stdin.addListener("data", function(d) { | |
| if (adjectives.length === 0) { |
Generate a GPG Key and revocation cert per http://www.gnupg.org/gpg/en/manual.html:
gpg --key-gen
gpg --output revoke.asc --gen-revoke <my user ID or email>
Once gpg key in keyring we can encrypt and decrypt files.
| #!/bin/sh | |
| # Convert Markdown to Confluence | |
| # | |
| # Supported syntax | |
| # * heading (1-6) | |
| # * blockquote (only single line ".bq") | |
| # * code block fence (```) | |
| # * inline code (`foo`) | |
| # * link ([name](url)) |
| #!/usr/bin/env bash | |
| size=1024 # MB | |
| mount_point=$HOME/tmp | |
| name=$(basename "$mount_point") | |
| usage() { | |
| echo "usage: $(basename "$0") [mount | umount | remount | check | orphan]" \ | |
| "(default: mount)" >&2 | |
| } |
The standard way of understanding the HTTP protocol is via the request reply pattern. Each HTTP transaction consists of a finitely bounded HTTP request and a finitely bounded HTTP response.
However it's also possible for both parts of an HTTP 1.1 transaction to stream their possibly infinitely bounded data. The advantages is that the sender can send data that is beyond the sender's memory limit, and the receiver can act on
| <?php | |
| namespace JesusGoku; | |
| /** | |
| * NamesGenerator | |
| * | |
| * Port of NameGenerator use for Docker | |
| * | |
| * @author Jesús Urrutia <[email protected]> |
