The public facing site for Brick Hack.

Install ruby, mysql, and other required development environment tools.

$ brew install rbenv ruby-build rbenv-readline rbenv-gem-rehash rbenv-default-gems rbenv-binstubs
$ brew install redis
$ brew install mysql

Download & configure local environment, vendor everything style.

$ git clone [email protected]:codeRIT/brickhack.io.git
$ cd brickhack.io
$ rbenv install
$ bin/setup

Optionally, you can use Pow to host your local development environment. With it, you can visit http://brickhack.io.dev/

$ brew install pow
$ gem install powder
$ powder link

Afterwards, you can restart the server with powder restart when needed.

If you choose not to use Pow, you can still initiate a local rails server with bin/rails server and visit http://localhost:3000

Verify you have a unix console emulator. We recommend the full version of cmder.

Download & install RailsInstaller 3.0 (alpha) from http://railsinstaller.org/

Download & install redis from https://github.com/rgl/redis/downloads

Download & configure local environment, vendor everything style.

$ git clone [email protected]:codeRIT/brickhack.io.git
$ cd brickhack.io
$ bin/setup

Start your local environment: bin/rails server

• Mail View - Email templates can be previewed at http://localhost:3000/rails/mailers
• Mail Catcher - When active, emails will be captured by MailCatcher instead of slipping into a black hole (no emails are ever sent in development). Visit mailcatcher.me and follow instructions under "How" to get setup. Note: in order for mail to be sent, you must start a local Sidekiq worker using bundle exec sidekiq.
• Guard - Automatically runs tests based on the files you edit. bundle exec guard
• Coverage - Test coverage can be manually generated via the bin/rake coverage:run command. Results are then made available in the coverage/ directory.
• Sidekiq - Run background jobs (such as emails) and view active & completed jobs. Spin up Sidekiq with bundle exec sidekiq. A web portal will be available at http://localhost:3000/sidekiq (also available in production).

Code pushed will automatically build on Travis CI. Upon a successful build to the develop or master branches, Travis will deploy to our instance(s) of Dokku. See the Production Environment Setup page for details.