This is a Rails 3.2 app running on Ruby 1.9.2 and deployed to Heroku's Cedar stack. It has an RSpec and Cucumber test suite which should be run before committing to the master branch.
Use our laptop script to get Homebrew, Postgres, Redis, RVM, Ruby 1.9.2, and Bundler:
Use our dotfiles to get commands like
git up and
git down for a clean git history:
Get the code:
git clone firstname.lastname@example.org:your-account/your-app.git
Set up the app:
cd your-app bundle bake db:create bake db:migrate
Run the whole test suite with:
Run individual specs like:
Run individual features like:
Tab complete to make it even faster!
When a spec or feature file has many specs in them, you sometimes want to run just what you're working on. In that case, specify a line number:
s spec/models/user_spec.rb:8 cuc features/visitor_signs_in.feature:105
To run the app in development mode, use Foreman, which was installed from the
It will pick up on the Procfile and use Thin as the app server instead of Webrick, which will also be used by Heroku's Cedar stack.
git pull --rebase grb create feature-branch bake
This creates a new branch for your feature. Name it something relevant. Run the tests to make sure everything's passing. Then, implement the feature.
bake git add -A git commit -m "my awesome feature" git push origin feature-branch
Open up the Github repo, change into your feature-branch branch. Press the "Pull request" button. It should automatically choose the commits that are different between master and your feature-branch. Create a pull request and share the link in Campfire with the team. When someone else gives you the thumbs-up, you can merge into master:
git up git down git push origin master
For more details and screenshots of the feature branch code review process, read this blog post.