Skip to content
This repository

The friendly code review system.

branch: master
Octocat-spinner-32 bin Be more specific about the cache bust lines to filter May 08, 2012
Octocat-spinner-32 client [Client] Remove some files that shouldn't have been checked in. August 08, 2012
Octocat-spinner-32 config Default config files for a production installation February 28, 2013
Octocat-spinner-32 doc Move config/environment -> environment, to match fezzik's default con… April 16, 2012
Octocat-spinner-32 lib Fix a bug with syntax highlighting September 24, 2013
Octocat-spinner-32 log Create a log directory August 24, 2011
Octocat-spinner-32 migrations Indentation fix. February 14, 2013
Octocat-spinner-32 models Ensure that deleted users are not sent emails. February 13, 2013
Octocat-spinner-32 node_modules Remove the lessc binary from node_modules January 28, 2012
Octocat-spinner-32 public Fix a bug with implicit use of 'event' April 04, 2013
Octocat-spinner-32 resque_jobs Reflow comment text. February 12, 2013
Octocat-spinner-32 script Only allow a single fetch_commits job at a time. May 30, 2013
Octocat-spinner-32 test Fix a bug with syntax highlighting September 24, 2013
Octocat-spinner-32 views Enable a 3 month commit search window September 24, 2013
Octocat-spinner-32 .gitignore Ignore the demo deploy config. August 16, 2012
Octocat-spinner-32 .gitmodules Remove the wiki as a submodule. More trouble than it's worth to keep … June 28, 2012
Octocat-spinner-32 .rbenv-version Update rbenv version to 1.9.3-p194. August 08, 2012
Octocat-spinner-32 .rvmrc Add a .rvmrc. August 08, 2012
Octocat-spinner-32 CHANGES.markdown Update changelog with 0.3.0 changes. April 30, 2012
Octocat-spinner-32 Gemfile Remove dependency on pry, freeing up open4 ~>1.0 for use August 20, 2013
Octocat-spinner-32 Gemfile.lock Remove dependency on pry, freeing up open4 ~>1.0 for use August 20, 2013
Octocat-spinner-32 Pathfile Slim down our bloated pathfile. January 28, 2012
Octocat-spinner-32 Procfile Explicitly order the resque jobs from fast and important -> slow and … April 26, 2012
Octocat-spinner-32 README.markdown README tweaks March 01, 2013
Octocat-spinner-32 Rakefile Update Fezzik and Rake. October 25, 2012
Octocat-spinner-32 Vagrantfile Upgrade Vagrantfile for use with vagrant >=1.1 September 27, 2013
Octocat-spinner-32 barkeep_server.rb Fix up bad error response message. March 21, 2013
Octocat-spinner-32 config.ru Update Pinion to the newest version. August 08, 2012
Octocat-spinner-32 environment.prod.rb Default config files for a production installation February 28, 2013
Octocat-spinner-32 environment.prod.sh Default config files for a production installation February 28, 2013
Octocat-spinner-32 environment.rb Better explain the REDIS_DB and REDIS_DB_FOR_RESQUE config vars February 27, 2013
Octocat-spinner-32 install_barkeep.sh Minor updates to install script and vagrantfile September 24, 2013
README.markdown

Overview

Barkeep is a fast, fun way to review code. Engineering organizations can use it to keep the bar high.

To see a video of Barkeep in action, visit getbarkeep.org.

Barkeep is standalone software that you host. Once it's set up, you can use it to track and code review any number of git repos available on the internet. It's designed to be easy to run on Ubuntu.

Getting started

If you're ready to install Barkeep, see the Installing Barkeep wiki page for instructions and a one-step shell script.

If you'd like to take Barkeep for a test-drive first or set up local development on your own machine you can quickly install it on a Vagrant VM. See the Vagrant wiki page for details.

Docs

See the wiki for instructions on setting up Barkeep for development, deploying it to your own server and tracking git repos with it.

Read here for a comparison of Barkeep to other code review systems.

Contributing

Barkeep was designed to be easy to hack on with Mac or Ubuntu, so feel free to dive in. You can open a ticket to suggest a new feature. If you fix a bug or implement a small feature, send us a pull request. If you want to implement a larger feature, please post a description of the feature on the mailing list beforehand so that we can be sure it's something we want to add.

Simple style guidelines: mimic the style around you, cap lines at 110 characters, and follow the usual conventions for commit messages.

Mailing list

Please file user issues as tickets here on Github.

The Barkeep developer mailing list is used for discussion around developing Barkeep. You can email the group at getbarkeep@googlegroups.com.

Credits

Barkeep was written by the following engineers at Ooyala:

and with contributions from other Ooyalans and community members:

Barkeep is released under the MIT license.

Something went wrong with that request. Please try again.