require 'sinatra'
require 'zlib'
 
configure do
  set :server, :puma
end
 
get '/text' do
  body File.read("text")
end

#!/bin/bash
 
# Set up paths and whatnot
test -e ~/.bashrc && source ~/.bashrc
 
# We need tmux. Obvs.
if [[ -z `which tmux` ]]; then echo "You need tmux first!"; exit 1; fi
 
# Named variables are much more flexible
name="$1"

casper = require('casper').create()
 
casper.start 'http://docs.casperjs.org/en/latest/', ->
  createWeekStep = (weekNum, index, weeks) ->
    @then -> console.log("running step for week #{weekNum}")
  (i for i in [1..12]).forEach(createWeekStep, @)
 
casper.run()

On Mon, Mar 25, 2013 at 3:47 PM,  <alexba...@googlemail.com> wrote: 
> One thing that does confuse me, is how to specify a specific version of 
> someones code? say, their v1.0 or a git commit hash 
 
If you want to do this, the Best Practice method (currently) is to 
fork their repo, and maintain your fork at the revision you need. 
 
from https://groups.google.com/forum/#!topic/golang-nuts/t01qsI40ms4

#!/bin/bash
 
# I alias this script to `mux`:
#   $ alias mux=tmux-named
# Then I tell terminal to automatically attach new windows to my session named "main",
# by setting the preference named "Shells open with" to this command:
#   /path/to/tmux-named main
#
# When working on a particular project, I can jump a session for that project
# by running "mux project-name".

specs.4.8
prerelease_specs.4.8
versions.list
names.list
specs
deps
gems
*.sha512

# Using this file, you prompt looks something like this:
# <exit status> <username color coded with dotfiles git status> <cwd> <git branch or rev-name> <job status> $
# 💙 andre ~/src/bundler/bundler v1.3.0.pre.2~13 👥 $
 
BLUE='\001\033[0;34m\002'
CYAN='\001\033[0;36m\002'
GREEN='\001\033[0;32m\002'
YELLOW='\001\033[0;33m\002'
RESET='\001\033[0m\002'

 
  # Homebrew::tap to get dupes
  define homebrew::tap (
    $ensure = present,
  ) {
    if $ensure == 'present' {
      exec { "homebrew_tap_${name}":
        command => "brew tap ${name}",
        unless  => "brew tap | grep ${name}",
      }

Jul 15 06:05:43 bundler-api heroku/web.6:  Cycling 
Jul 15 06:05:48 bundler-api heroku/web.6:  Stopping all processes with SIGTERM 
Jul 15 06:05:51 bundler-api heroku/web.6:  Process exited with status 0 
Jul 15 06:05:51 bundler-api heroku/web.6:  State changed from up to down 
Jul 15 06:05:51 bundler-api heroku/web.6:  State changed from down to starting 
Jul 15 06:05:53 bundler-api heroku/web.6:  Starting process with command `bundle exec puma --include lib --port 57130 --environment production --threads 0:32` 
Jul 15 06:05:56 bundler-api heroku/web.6:  State changed from starting to up