Education Outside the Classroom Helper is a Rails app for helping teachers organize class trips, without lots of paperwork. It is currently unfinished.
The eotc-helper app will allow authorized users (teachers and above) to create trips. This will involve a form for trip specification, as well as a notification system to automatically notify the EOTC coordinator, the Board of Trustees, and lower-level associated accounts (students in associated groups or classes).
The app will be built around a user model, with accounts of differing privilege levels.
- Students can subscribe to notifications and comment on trips
- Teachers can create trips
- BoT members and the EOTC coordinator can remove, edit, and approve trips
All accounts have the privileges of lesser accounts. Accounts can only be escalated to higher permission levels by the System Administrator. Anyone can register a student account.
We are currently organizing a public chatroom for discussion.
This app runs on Ruby 2.3 with Rails 5.2.0. Other dependency information is available in the Gemfile. To install all dependencies, run
gem install bundler and then
bundle install. Further, the app requires a database. See the Database Creation section below.
Databases in Development
In the development phase, it is recommended to use SQLite. This does not require a command to create its database, but to use it, you must set the environment variables
This must be run every terminal session. Alternatively, for a permanent solution:
To run the Rails server, run
rails server. Should this fail, run
bin/rails server. Remember that you must be in the eotc-helper directory.
There are three supported database packages: SQLite, mysql, and postgresql. To switch between them, set the
$DB environment variable. If the environment variable is not set, the default database is
postgresql. To use a database package, it must be installed.
To create the database, run
To initialize the database, run
To run the test suite, use
rake --trace db:migrate test
This sets the environment to a testing environment, and executes the tests. This script is automatically exected by our Continuous Integration software (currently Travis CI).
For deployment, it is recommended to use PostgreSQL, as it is most suited to the deployment phase. To create the production database, use:
You must also set the environment variables:
export DB=postgresql # not necessarily needed,
# but good practice to
# overwrite potential
# previous values
Running a production server is currently impossible.
This README would normally document whatever steps are necessary to get the application up and running.
Things you may want to cover:
x Ruby version - 2.3 with Rails 5.2.0
x System dependencies
x Configuration (?)
x Database creation
x Database initialization
x How to run the test suite
Services (job queues, cache servers, search engines, etc.)
x Deployment instructions