A tool to help manage codebar.io members and events.
First thing you will need, is to install Ruby 2.1.2
Using rvm
rvm install 2.1.2Using rbenv
rbenv install 2.1.2
rbenv global 2.1.2gem install bundler
bundle install --without productionYou can use the --wihout production flag to avoid installing the pg gem for PostgreSQL. You don't need it anyway on development!
bundle exec rake db:create
bundle exec rake db:migrate db:test:prepareCreate an application at https://github.com/settings/applications/new with
http://localhost:3000 as the Homepage URL and http://localhost:3000/auth/github
as the Authorization callback URL.
Once your development application is setup, create a file named .env in the root of the
application folder with the GitHub key and secret like so:
GITHUB_KEY=YOUR_KEY
GITHUB_SECRET=YOUR_SECRET
Note: Windows doesn't like creating a file named .env so do the following from a cmd prompt in your application folder:
echo GITHUB_KEY=YOUR_KEY >> .env
echo GITHUB_SECRET=YOUR_SECRET >> .env
bundle exec rake db:seedbundle exec rakeNote: JavaScript acceptance tests are relying on the Poltegeist driver, which requires PhantomJS. For more information about installing PhantomJS, please take a look here.
You can pick one of the open issues, fix a bug, improve the interface, refactor the code or improve test coverage!
If there is something else that you would like to work on, open an issue first so we can discuss it. We are always open to new ideas and ways of improving planner!




