Initial commit

.autotest

@@ -0,0 +1,19 @@
+#!/bin/ruby
+
+require 'autotest/timestamp'
+
+require 'autotest/growl'
+
+#This turns off screen clearing between tests.  Leave it "false" until you ensure that autotest is running properly, otherwise you may miss some errors written to the screen.  
+Autotest::Growl::clear_terminal = false
+
+#Turn on Growl notifications of test runs when files are changed.
+Autotest::Growl::show_modified_files = true
+
+#Make notifications sticky so you won't miss them: you must click notification to dismiss instead of it fading after time.
+#This doesn't currently work, but it will be nice if it ever does get fixed...
+Autotest::Growl::sticky_failure_notifications = true
+
+require 'autotest/inotify'
+
+

.bashrc

@@ -0,0 +1,113 @@
+# ~/.bashrc: executed by bash(1) for non-login shells.
+# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
+# for examples
+
+
+# This loads RVM into shell sessions.
+[[ -s "$HOME/.rvm/scripts/rvm" ]] && source "$HOME/.rvm/scripts/rvm"  
+
+
+# If not running interactively, don't do anything
+[ -z "$PS1" ] && return
+
+
+if [[ -n "$PS1" ]] ; then
+
+  # don't put duplicate lines in the history. See bash(1) for more options
+  # ... or force ignoredups and ignorespace
+  HISTCONTROL=ignoredups:ignorespace
+
+  # append to the history file, don't overwrite it
+  shopt -s histappend
+
+  # for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
+  HISTSIZE=1000
+  HISTFILESIZE=2000
+
+  # check the window size after each command and, if necessary,
+  # update the values of LINES and COLUMNS.
+  shopt -s checkwinsize
+
+  # make less more friendly for non-text input files, see lesspipe(1)
+  [ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"
+
+  # set variable identifying the chroot you work in (used in the prompt below)
+  if [ -z "$debian_chroot" ] && [ -r /etc/debian_chroot ]; then
+      debian_chroot=$(cat /etc/debian_chroot)
+  fi
+
+  # set a fancy prompt (non-color, unless we know we "want" color)
+  case "$TERM" in
+      xterm-color) color_prompt=yes;;
+  esac
+
+  # uncomment for a colored prompt, if the terminal has the capability; turned
+  # off by default to not distract the user: the focus in a terminal window
+  # should be on the output of commands, not on the prompt
+  #force_color_prompt=yes
+
+  if [ -n "$force_color_prompt" ]; then
+      if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
+	  # We have color support; assume it's compliant with Ecma-48
+	  # (ISO/IEC-6429). (Lack of such support is extremely rare, and such
+	  # a case would tend to support setf rather than setaf.)
+	  color_prompt=yes
+      else
+	  color_prompt=
+      fi
+  fi
+
+  if [ "$color_prompt" = yes ]; then
+      PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
+  else
+      PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
+  fi
+  unset color_prompt force_color_prompt
+
+  # If this is an xterm set the title to user@host:dir
+  case "$TERM" in
+  xterm*|rxvt*)
+      PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
+      ;;
+  *)
+      ;;
+  esac
+
+  #Add RVM gemset name to PS1
+  PS1="\$(~/.rvm/bin/rvm-prompt) $PS1"
+
+  # enable color support of ls and also add handy aliases
+  if [ -x /usr/bin/dircolors ]; then
+      test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
+      alias ls='ls --color=auto'
+      #alias dir='dir --color=auto'
+      #alias vdir='vdir --color=auto'
+
+      alias grep='grep --color=auto'
+      alias fgrep='fgrep --color=auto'
+      alias egrep='egrep --color=auto'
+  fi
+
+  # some more ls aliases
+  alias ll='ls -alF'
+  alias la='ls -A'
+  alias l='ls -CF'
+
+  # Alias definitions.
+  # You may want to put all your additions into a separate file like
+  # ~/.bash_aliases, instead of adding them here directly.
+  # See /usr/share/doc/bash-doc/examples in the bash-doc package.
+
+  if [ -f ~/.bash_aliases ]; then
+      . ~/.bash_aliases
+  fi
+
+  # enable programmable completion features (you don't need to enable
+  # this, if it's already enabled in /etc/bash.bashrc and /etc/profile
+  # sources /etc/bash.bashrc).
+  if [ -f /etc/bash_completion ] && ! shopt -oq posix; then
+      . /etc/bash_completion
+  fi
+fi 
+
+

.rspec

@@ -0,0 +1,3 @@
+--colour
+--drb
+

Gemfile

@@ -0,0 +1,40 @@
+#A note about versions: these versions are ones that have been confirmed to WORK for the purposes here (Hartl book).  If you use different versions, they may cause problems compatibility-wise.  Change at your own risk.
+
+source 'http://rubygems.org'
+
+gem 'rails', '3.0.3'
+gem 'sqlite3-ruby', :require => 'sqlite3'
+gem 'gravatar_image_tag'
+gem 'will_paginate', '3.0.pre2'
+gem 'heroku'
+gem 'taps'
+
+group :development do
+  gem 'rspec-rails', '2.3.0'
+  gem 'annotate-models'
+  gem 'faker'
+end
+
+group :test do
+  gem 'rspec', '2.3.0'
+  gem 'webrat', '0.7.1'
+  gem 'spork', '0.8.4'
+  gem 'factory_girl_rails'
+  gem 'ffi', '1.0.4'
+  gem 'rb-inotify', '0.8.4'
+  gem 'autotest-growl', '0.2.9'
+
+  gem 'autotest', '4.4.6'
+  #autotest is required by autotest-inotify - it won't use autotest-standalone. If autotest-inotify ran with
+  #autotest-standalone, we could get rid of autotest and ZenTest, which are superflous here - alas, we can't.
+  #If you aren't going to use autotest-inotify, you can lighten the load and use autotest-standalone instead of loading the autotest/ZenTest combo.
+
+  gem 'autotest-rails-pure', '4.1.2'
+  #required by autotest to detect file changes when running outside of ZenTest (We're not using ZenTest). The 'autotest' gem alone does not suffice.
+
+  gem 'autotest-inotify', '0.0.4'
+
+  gem 'ZenTest', '4.4.2'
+  #We don't actually need ZenTest, but it is installed automatically as a dependency of autotest-inotify
+end
+