The friendly code review system.
Ruby CoffeeScript CSS HTML Shell
Permalink
Failed to load latest commit information.
bin Be more specific about the cache bust lines to filter May 9, 2012
client [Client] Remove some files that shouldn't have been checked in. Aug 8, 2012
config Add authentication protocol var to deploy May 8, 2015
doc Move config/environment -> environment, to match fezzik's default con… Apr 17, 2012
lib Redirect to /signin when user cancels oauth2 login Jun 23, 2015
log Create a log directory Aug 25, 2011
migrations Indentation fix. Feb 14, 2013
models Ensure that deleted users are not sent emails. Feb 14, 2013
node_modules Update jasmine-node Jan 26, 2015
public Fix a bug with implicit use of 'event' Apr 4, 2013
resque_jobs Reflow comment text. Feb 13, 2013
script Only allow a single fetch_commits job at a time. May 30, 2013
test Add user_order to commit email test Jan 26, 2015
views Enable a 3 month commit search window Sep 24, 2013
.gitignore Initial pass at google oauth2 integration Mar 28, 2015
.gitmodules Remove the wiki as a submodule. More trouble than it's worth to keep … Jun 29, 2012
.rbenv-version Update rbenv version to 1.9.3-p194. Aug 8, 2012
.rvmrc Add a .rvmrc. Aug 9, 2012
CHANGES.markdown Update changelog with 0.3.0 changes. Apr 30, 2012
Gemfile Initial pass at google oauth2 integration Mar 28, 2015
Gemfile.lock Initial pass at google oauth2 integration Mar 28, 2015
Pathfile Slim down our bloated pathfile. Jan 29, 2012
Procfile Explicitly order the resque jobs from fast and important -> slow and … Apr 27, 2012
README.markdown README tweaks Mar 1, 2013
Rakefile Update Fezzik and Rake. Oct 25, 2012
Vagrantfile Upgrade Vagrantfile for use with vagrant >=1.1 Sep 27, 2013
barkeep_server.rb Rename google_oauth2 to oauth2 Mar 28, 2015
config.ru Update Pinion to the newest version. Aug 9, 2012
environment.prod.rb Default config files for a production installation Feb 28, 2013
environment.prod.sh Default config files for a production installation Feb 28, 2013
environment.rb Rename google_oauth2 to oauth2 Mar 28, 2015
install_barkeep.sh break install script on error (e.g. dpkg already taking the lock) Nov 20, 2014

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.