An all-in-one platform for managing hackathon registration & logistics, originally developed for BrickHack.

Read more at coderit.org/hackathon-manager/

• Hacker applications: Enable hackers to apply to your hackathon while providing all relevant information (contact info, school, demographics, etc)
• MyMLH support: Streamline the application process when users log in with MyMLH, a common platform for applying to any MLH hackathon. Basic info is pre-filled based on a common application, so hackers don't have to re-type it every time.
• Admissions & RSVPs: Facilitate accepting hackers to your hackathon & enable them to RSVP
• Bus Lists: Coordinate bus sign-ups during the RSVP process while communicating important information to riders & captains
• Email communication: Ensure hackers get consistent, timely information throughout their application process, while enabling your organizing team to communicate important information at any time.
• Statistics & Visualization: Surface key analytics about your admissions, distribution of applicants, progress towards attendance, etc.

HackathonManager is a standalone web app separate from your regular marketing website/public homepage.

A typical setup would be:

• brickhack.io — Marketing site with event info, schedule, sponsors, etc and a button to apply
• apply.brickhack.io — HackathonManager deployment to accept hacker applications + host management dashboard

This allows your public marketing site to operate however you want it (e.g. GitHub pages) while HackathonManager lives in an isolated, consistent environment.

HackathonManager makes use of a few different third-party services & Ruby gems:

• Devise + MyMLH (authentication & attendee identity)
• Sidekiq (background jobs)
• SendGrid (email)
• Amazon S3 (resume storage)
• Chartkick (management UI charts)
• Blazer (custom SQL queries, analytics, and charts)
• Doorkeeper (authentication via OAuth for API usage)

Deploy HackathonManager for your hackathon »

Documentation is available at https://coderit.org/hackathon-manager/

Docs are maintained as markdown files in the docs/ folder, with the website configuration & tooling stored in website/.

Doc & website changes are auto-built and deployed via Travis CI once merged into master.

Releases are automatically generated by semantic-release using commit messages.

Commit messages should follow the standard type(scope): subject format. For example:

• feat: Improve form typography
• deploy(heroku): Ensure db:migrate is run after each deploy
• fix: Support HTTPS in questionnaire portfolio URL

For more information, see semantic-release's how does it work.

GitHub issues and pull requests welcome!

All documentation is easily editable using the GitHub UI. Click the "Edit" button at the top of any documentation page to get started.

If there's a new feature you're looking to implement, please file an issue to open discussion on the feature before starting work or opening a pull request.

1. Setup Ruby + MySQL for local development

If you don't already have Ruby + MySQL set up, see this guide by GoRails for pointers.

• Select your computer's operating system & version
• If given the choice, use rbenv -- this will ensure a clean, sustainable Ruby dev environment
• SQLite and PostgreSQL steps are optional

2. Clone the repo

$ git clone [email protected]:codeRIT/hackathon-manager
$ cd hackathon-manager

3. Install dependencies

$ bundle install

4. Setup databse

$ bin/rails db:setup

5. Start up the server

$ bin/rails s  # short for bin/rails server

6. Visit http://localhost:3000/apply, create an account, and complete an application

7. In another bash window, promote your user to a director

$ cd hackathon-manager
$ bin/rails c  # short for bin/rails console
# Wait for the console to start...
Loading development environment (Rails 5.1.1)
irb(main):001:0> User.last.update_attribute(:role, :director)

8. Visit http://localhost:3000/manage and set up the hackathon as needed

See https://coderit.org/hackathon-manager/ for docs on regular hackathon setup

• 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.
• Guard - Automatically runs tests based on the files you edit. bundle exec guard
• Coverage - Test coverage can be manually generated via the bin/rails coverage:run command. Results are then made available in the coverage/ directory.
• Sidekiq - Run background jobs (such as emails) and view active & completed jobs. Sidekiq is automatically started with Docker - a dashboard is available at http://localhost:3000/sidekiq (also available in production).

The gem is available as open source under the terms of the MIT License.