osem-fcy/README.md

67 lines
2.5 KiB
Markdown
Raw Normal View History

2014-04-10 12:09:21 +02:00
[![Build Status](https://travis-ci.org/openSUSE/osem.svg?branch=master)](https://travis-ci.org/openSUSE/osem)
2014-04-09 17:05:34 +02:00
[![Code Climate](https://codeclimate.com/github/openSUSE/osem.png)](https://codeclimate.com/github/openSUSE/osem)
2014-04-09 17:27:17 +02:00
[![Coverage Status](https://coveralls.io/repos/openSUSE/osem/badge.png)](https://coveralls.io/r/openSUSE/osem)
[![Security Status](https://hakiri.io/github/openSUSE/osem/master.svg)](https://hakiri.io/github/openSUSE/osem/master)
2013-10-30 17:55:29 +01:00
#OSEM
The Open Source Event Manager. An event management tool tailored to Free and Open Source Software conferences.
2012-09-22 00:40:18 -07:00
2014-04-08 21:02:10 +02:00
## Install OSEM
You can run rails apps in different modes (development, production). For more information
about rails and what it can do, see the [rails guides.](http://guides.rubyonrails.org/getting_started.html)
2013-08-15 16:51:57 +02:00
2014-04-08 21:02:10 +02:00
### Run OSEM in development
2013-10-30 17:55:29 +01:00
1. Clone the git repository to the directory you want Apache to serve the content from.
```
git clone https://github.com/openSUSE/osem.git
```
2. Install all the ruby gems.
```
bundle install
```
2014-04-08 21:02:10 +02:00
3. Install ImageMagick from your distribution repository
4. Generate secret key for devise and the rails app with
```
rake secret
```
Look at config/config.yml.example.
5. Copy the sample configuration files and adapt them
2013-10-30 17:55:29 +01:00
```
cp config/config.yml.example config/config.yml
cp config/database.yml.example config/database.yml
```
2014-04-08 21:02:10 +02:00
6. Setup the database
2013-10-30 17:55:29 +01:00
```
2014-04-08 21:02:10 +02:00
bundle exec rake db:setup
2013-10-30 17:55:29 +01:00
```
2014-04-08 21:02:10 +02:00
7. Run OSEM
2013-10-30 17:55:29 +01:00
```
2014-04-08 21:02:10 +02:00
rails server
2013-10-30 17:55:29 +01:00
```
2014-04-08 21:02:10 +02:00
8. Visit the APP at
2013-10-30 17:55:29 +01:00
```
2014-04-08 21:02:10 +02:00
http://localhost:3000
2013-10-30 17:55:29 +01:00
```
2014-04-08 21:02:10 +02:00
9. Sign up, the first user will be automatically assigned the admin role.
2013-10-30 17:55:29 +01:00
2014-04-08 21:02:10 +02:00
### Run OSEM in production
We recommend to run OSEM in production with [mod_passenger](https://www.phusionpassenger.com/download/#open_source)
and the [apache web-server](https://www.apache.org/). There are tons of guides on how to deploy rails apps on various
base operating systems. Check Google ;-)
2013-10-30 17:55:29 +01:00
2014-04-08 21:02:10 +02:00
## Documentation
OSEM is extensively (some would say maniacally ;-) documented. You can generate a nice HTML documentation with ''rdoc''
2013-10-30 17:55:29 +01:00
```
2014-04-08 21:02:10 +02:00
bundle exec rdoc --op doc/app --all -f fivefish app
xdg-open doc/app/index.html
2013-10-30 17:55:29 +01:00
```
2014-04-09 01:37:59 +02:00
## Testing
We are using [rspec](http://rspec.info/)+[capybara](http://jnicklas.github.io/capybara/)+[factory girl](https://github.com/thoughtbot/factory_girl) to build test suite. You *should* run it continuously when you are developing, via:
2014-04-09 01:37:59 +02:00
```
bundle exec guard
2014-04-09 01:37:59 +02:00
```
This uses [spring](https://github.com/rails/spring) to provide a
[fast feedback loop for the red/green cycle](http://bitzesty.com/blog/2013/05/enable-tdd-with-faster-ruby-on-rails-stack-reloading/).