Application to support working through sequential programming problems, with crowd-sourced code reviews.

This an early-stage experiment. In other words: Shield your eyes, children, the code is bolted on.

We welcome contributions as we work to figure out what this beast is.

Features may be here today, gone tomorrow.

The discussions are the most important thing in the application. That and the evolution of the code. It's not about getting code perfect or right, but using the pieces of code to talk about the little details of what makes code expressive.

There are excellent discussions, and it would be great to be able to extract the learning from these discussions, perhaps into blog posts, perhaps into checklists to help teach nitpicking.

We believe that there's learning in doing the exercises and receiving feedback, and there's also learning in reading other people's code and providing feedback.

It would be great if there were a way to have meta-discussions about providing feedback.

The messaging right now is a disaster. The site is confusing, the process is opaque, and it's hard to figure out where you need to look to figure stuff out.

The warmup exercises are collected from all over the web.

The common data for assignments are in

assignments/shared

This includes some metadata that gets sewn into a README, as well as a blurb that can be shown on the website.

Not all assignments will be appropriate for all languages.

The actual assignment consists of

• a test suite, where all test are pending except the first one
• a sample solution that passes the test suite

The languages/trails are configured in lib/exercism/curriculum/LANGUAGE.rb.

The list of assignments is just a really big array of assignment slugs in the order that they will be assigned.

Different languages/trails do not need to have the same assignments or the same order.

1. Install postgresql with: brew install postgresql or apt-get install postgresql-9.2
2. Copy .ruby-version.example to .ruby-version if you use a Ruby version manager such as RVM, rbenv or chruby
3. Install gems with: bundle
4. Get a client id/secret from Github at https://github.com/settings/applications/new.

• Name: whatever
• URL: http://localhost:4567
• Callback url: http://localhost:4567/github/callback

5. Presuming you have Postgres installed (if not: brew install postgres):

• create db user with: createuser exercism
• create database with: createdb -O exercism exercism_development

6. Run the database migrations with rake db:migrate.
7. Run test database migrations with RACK_ENV=test rake db:migrate (This is only useful for test environment)
8. Run the database seed with rake db:seed (if you want LOTS of data: rake db:seed[1000] or some other big number).
9. Copy the boot script scripts/boot.sh.example to scripts/boot.sh and fill in your GitHub details
10. Start the server with ./scripts/boot.sh
11. Login at http://localhost:4567.
12. Run MailCatcher with mailcatcher, and open your browser to localhost:1080.
13. Work through 'Frontend development setup' below and run lineman for correct styling at http://localhost:4567

1. Install node and npm

• osx: brew install node
• others see: https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager

2. Install lineman via sudo npm install -g lineman
3. cd frontend and start lineman with lineman run

• note lineman watches for file changes and compiles them automatically, it is not required to be running for the server to run

If you want to send actual emails, you will need to export the following environment variables:

• EMAIL_USERNAME
• EMAIL_PASSWORD
• EMAIL_DOMAIN
• EMAIL_SMTP_ADDRESS
• EMAIL_SMTP_PORT

You can do this in scripts/boot.sh for development.

There's a script in bin/console that will load irb with the exercism environment loaded.

Make sure your migrations are up-to-date with: rake db:migrate RACK_ENV=test

Make sure that mailcatcher is running.

Run tests with: rake test

To run a single test suite, you can do so with:

ruby path/to/the_test.rb

If it complains about dependencies, then either we forgot to require the correct dependencies (a distinct possibility), or we are dependening on a particular tag of a gem installed directly from github (this happens on occasion).

If there's a git dependency, you can do this:

bundle exec ruby path/to/the_test.rb

For the require, you'll need to figure out what the missing dependency is. Feel free to open an issue on github. It's likely that someone familiar with the codebase will be able to identify the problem immediately.

To enable code coverage run:

COVERAGE=1 rake test

Browse the results located in coverage/index.html

Let Heroku know that Lineman will be building our assets. From the command line:

heroku config:set BUILDPACK_URL=https://github.com/testdouble/heroku-buildpack-lineman-ruby.git

Thank you for wanting to contribute! ❤️💖❤️

Fork and clone. Hack hack hack. Submit a pull request and tell us why your idea is awesome.

For more details, please read the contributing guide.

GNU Affero General Public License

Copyright (C) 2013 Katrina Owen, [email protected]

This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details.