This is the code of hacken.in, an event calendar for geeks in and around Cologne, Berlin and Munich. If you want to help us in extending the calendar to your city, please contact us in our Google Group.
When you want to add an event to hacken.in please check with the following guidelines:
- Currently we only feature events in Ruhr area plus BIG events in Europe
- The following topics are allowed:
- Programming (in any language)
- Nerd-Culture (like Star Wars, Ponies, Gaming, Comics...)
- Software Development Methods and Software Engineering
- Electronics and Robots
If you want to work on the Project, follow the steps described here:
- Fork the Project
- Check out your fork
cdinto the directory, install the bundler gem and run
- Now create a database config:
cp config/database.yml_example config/database.yml
- The example config requires MySQL including a database and a user
- More information on the database config
- Create the Devise & Omniauth configuration
cp config/initializers/devise.rb_example config/initializers/devise.rband edit the keys
- Now run
rake db:migrateto setup your database
- To run your application locally you can now use
- Now visit http://localhost:3000 in your webbrowser and you are ready to go!
If you want to add Events to your local page, you need an administrator:
- Now you can log in with your new administrator ;)
Pow is a really comfortable way to run the application on your machine. You can learn everything about it here.
If you are in the project directory, you can start Guard with
This will offer you the following comfortable features:
- Pow: Pow will get restarted automatically when necessary.
- Bundler: Bundler will run, when the Gemfile changes server running
- Specs: If you make changes to a spec or an application file, the according spec will be run and you will get feedback.
Hacken.in is developed in a test-driven way using Rspec and FactoryGirl. If you want to contribute to the project always add tests for your added functionality. If you find a bug it would be really helpful if you add a regression test that displays this misbehaviour. Even better: Fix it afterwards ;)
See CONTRIBUTING.md for details