Scheduling tool for Gaspard de Coligny school

This is a tool used for a school's parental board organising some events during the year, and trying to get volunteers to help during that event. The tool was orginally written by Yvan Cottyn, and later maintained by Vincent Mouton.

The current version of the tool is a caveman-migration from the original tool: just rewriting some code untill the entire thing worked again.

There's still a lot of work left to get this properly rewritten.

How it works

• Define basic event settings (its name, the date, ...) using the /settings route (that route is currently behind a username/password combo which is hard-coded)
• Define postjes which is the actual job (the bar, the kitchen, cleaning, ...)

Handy commands

Precompile assets: rake assets:precompile Precompile assets for production: RAILS_ENV=production bundle exec rake assets:precompile Run a specific db migration: rake db:migrate:up VERSION=20191010150325 Generate a new db migration file: rails generate migration TheNameOfYourMigrationGet the current db version:heroku rake db:version Get the current herokue db version:heroku rake db:versionGet a list of all migrations run against the db:rake db:migrate:status`

Need to fix

• Get the entire application working again (some things like config, destroy and purge everything don't work)
• Maybe we need to add it to the overview for visual reference
• Search & filter applications and volunteers
• Allow editing Volunteers, they sometimes make mistakes
• Remove the hard coded authentication on the back-end (yes, this repo contains a password, lol, but it's not mine)
• Maybe check the SIGTERM issue, caused by dyno sleeping, maybe use the at_exit see here and here
• Get that PROCFILE fixed and use puma?
• Give the back-end some bootstrap love
• Rename some models to English (from dutch): postjes, for example; also some params like klas, leerling, ...
• Remove redundant pieces of code, including all old assets (css, js, ...)
• Some UX changes are needed too (the schedule is still bare bones and maybe not so easy to use)
• Sort volunteers/applications by last added, descending
• Add a print stylesheet
• Upgrade heroku stack
• Table header should be fixed to top
• Replace the original Jdc2 module/namespace name
• Also allow some mass editing of volunteers
• Add a honeypot
• Get it to work with SASS and a build flow (note: not needed as the assets:precompile seems to be a task on heroku)
• Also Heroku requires pre-compiled assets? How can we add this to a deploy flow, with capistrano? (note: not needed as the assets:precompile seems to be a task on heroku)
• Look at the current ruby and see if it needs rewriting to new more modern concepts
• Add (unit) tests
• Move the entire concept from one setting defining the event (and having to destroy everything for any subsequent new event), to being able to schedule multiple events
• HTML e-mail
• Check this entire thing against multiple devices (now it's more of bootstrap-gives-me-responsiveness-by-default-so-i-wont-test)
• Work on accessibility
• Complete the docs (as if I'll ever get so far...)
• Get things like AirBrake configurable or something
• The migrations are really a pita, when they run it always claims some columsn already exist, lets fix those, maybe delete them all from the codebase and test if we can setup this thing from the onset?
• Also: add installation instructions