-[ActionCables](https://guides.rubyonrails.org/action_cable_overview.html) with [Redis](https://redis.io/) backend
-[ActionCable](https://guides.rubyonrails.org/action_cable_overview.html) with [Redis](https://redis.io/) backend
-[Devise](https://github.com/heartcombo/devise) for authentication
-[SolidQueue](https://github.com/rails/solid_queue) for background jobs
## Dev environment
The project comes with a devcontainer for VSCode and compatible editors. Simply open the project folder in Code (or using `devcontainer open <path>`) and after a few seconds, a suitable container should be ready.
Run `bin/dev` in the integrated terminal to start the dev webserver and the tailwind watch job (see `Procfile.dev` for details). Access your local rescheduled at http://127.0.0.1:3000.
Run `bin/dev` in the integrated terminal to start the dev webserver and the tailwind watch job (see `Procfile.dev` for details). Access your local re:scheduled at http://127.0.0.1:3000.
## Secrets
...
...
@@ -46,25 +51,79 @@ The application requires some secrets, as of writing these include:
You can supply the secrets by running `rails credentials:edit` or pass them as environment variable in upper case (e.g. `FILEDROP_USER`).
## Preparation for an event
## User and Role Management
tbd.
The application uses a role-based access control system with the following main roles:
-`admin`: Full system access
-`events_admin`: Can manage conferences and related resources
-`shift_coordinator`: Can manage session assignments