defunkt

(This is the text of the keynote I gave at Startup Riot 2009. Will update when video becomes available.)

Hi everyone, I'm Chris Wanstrath, and I'm one of the co-founders of GitHub.

GitHub, if you haven't heard of it, has been described as "Facebook for developers." Which is great when talking about GitHub as a website, but not so great when describing GitHub as a business. In fact, I think we're the polar opposite of Facebook as a business: we're small, never took investment, and actually make money. Some have even called us successful.

Which I've always wondered about. Success is very vague, right? Probably even relative. How do you define it?

After thinking for a while I came up with two criteria. The first is profitability. We employ four people full time, one person part time, have thousands of paying customers, and are still growing. In fact, our rate of growth is increasing - which means January was our best month so far, and February is looking pretty damn good.

nesquena

# COLORS
LIGHT_GRAY="\[\033[0;37m\]"; BLUE="\[\033[1;36m\]"; RED="\[\033[0;31m\]"; LIGHT_RED="\[\033[1;31m\]"; 
GREEN="\[\033[0;32m\]"; WHITE="\[\033[1;37m\]"; LIGHT_GRAY="\[\033[0;37m\]"; YELLOW="\[\033[1;33m\]";
# GIT PROMPT (http://gist.github.com/120804)
function parse_git_branch { 
  git branch --no-color 2> /dev/null | sed -e '/^[^*]/d' -e 's/* \(.*\)/ \(\1\)/'; 
}
function parse_git_status { 
  git status 2> /dev/null | sed -e '/(working directory clean)$/!d' | wc -l; 
}

jamiecobbett

# Adapted from http://stackoverflow.com/questions/1686779/multifile-rake-build
# Runs a task (in this case the default task) for each Rakefile nested in the current directory 
task :default do
  FileList["*/**/Rakefile"].each do |project|
    next if project =~ /^admin_console/
    next if project =~ /^logging/
    # clear current tasks
    Rake::Task.clear
    #load tasks from this project
    load project

nesquena

# http://ph7spot.com/musings/getting-started-with-autotest

$ gem install redgreen autotest-standalone autotest-fsevent autotest-growl autotest-rails-pure
$ mate ~/.autotest

    require 'redgreen/autotest'
    require 'autotest/timestamp'
    require 'autotest/growl'
    require 'autotest/fsevent'
    require "autotest/restart"

nesquena

# brew install git bash-completion

# Completion
if [ -f `brew --prefix`/etc/bash_completion ]; then
  . `brew --prefix`/etc/bash_completion
fi

# Editor
export EDITOR='mate -w'

nesquena

- Run software update
- Install Purchased Apps from App Store
- Disable caps lock key (Sys Pref => Keyboard => Modifier Keys)
- System Pref -> Expose -> Setup corners for spaces and expose
+ System Pref -> Security -> Sleep Password
- Setup Dropbox to Get Files
- Install 1Password
  - Use dropbox synced file for keychain
  - Install browser extension for chrome
- Install Prey

johnreilly

#
# Cookbook Name:: nodejs
# Recipe:: default
#

if ['solo'].include?(node[:instance_role])

  nodejs_file = "node-v0.1.101.tar.gz"
  nodejs_dir = "node-v0.1.101"
  nodejs_url = "http://nodejs.org/dist/#{nodejs_file}"

drnic

# from http://www.pixelbeat.org/settings/.inputrc


# By default up/down are bound to previous-history
# and next-history respectively. The following does the
# same but gives the extra functionality where if you
# type any text (or more accurately, if there is any text
# between the start of the line and the cursor),
# the subset of the history starting with that text
# is searched (like 4dos for e.g.).

adelcambre

curl https://gist.github.com/raw/788740/4b337df4be4be4338e2466ef775cd685b57d9601/gistfile1.diff | patch -p0

tmm1

This is now obsolete. Upgrade to Propane 1.1.2 and use https://gist.github.com/825404 instead.

Screenshots

Use it

Propane 1.1.0