clarion

Call for Papers automation tool for OpenFest

Go to file

Petko Bordjukov 59a0cc482e Create a new Rails app called Clarion		2014-07-28 12:34:18 +03:00
app	Create a new Rails app called Clarion	2014-07-28 12:34:18 +03:00
bin	Create a new Rails app called Clarion	2014-07-28 12:34:18 +03:00
config	Create a new Rails app called Clarion	2014-07-28 12:34:18 +03:00
db	Create a new Rails app called Clarion	2014-07-28 12:34:18 +03:00
lib	Create a new Rails app called Clarion	2014-07-28 12:34:18 +03:00
log	Create a new Rails app called Clarion	2014-07-28 12:34:18 +03:00
public	Create a new Rails app called Clarion	2014-07-28 12:34:18 +03:00
test	Create a new Rails app called Clarion	2014-07-28 12:34:18 +03:00
vendor/assets	Create a new Rails app called Clarion	2014-07-28 12:34:18 +03:00
.gitignore	Create a new Rails app called Clarion	2014-07-28 12:34:18 +03:00
Gemfile	Create a new Rails app called Clarion	2014-07-28 12:34:18 +03:00
Gemfile.lock	Create a new Rails app called Clarion	2014-07-28 12:34:18 +03:00
README.rdoc	Create a new Rails app called Clarion	2014-07-28 12:34:18 +03:00
Rakefile	Create a new Rails app called Clarion	2014-07-28 12:34:18 +03:00
config.ru	Create a new Rails app called Clarion	2014-07-28 12:34:18 +03:00

README.rdoc

== README

This README would normally document whatever steps are necessary to get the
application up and running.

Things you may want to cover:

* Ruby version

* System dependencies

* Configuration

* Database creation

* Database initialization

* How to run the test suite

* Services (job queues, cache servers, search engines, etc.)

* Deployment instructions

* ...


Please feel free to use a different markup language if you do not plan to run
<tt>rake doc:app</tt>.