JAMS (Jam Administration and Management System)

JAMS has primarily been built for use by the Northern Ireland Raspberry Jam, but is generic enough to be used by anyone planning events in a similar structure like other raspberry jams, coder dojos and many more.

At its core, it is an event administration and management system which allows planners to create event schedules, manage volunteer attendance and signup for any workshops running in the schedule. It also allows attendees to sign up to workshops.

Current Features

• OAuth 2.0 SSO support
• Role based access control
  • Zero Trust policy
• Interactive drag and drop schedule planner
• Workshop creation and management
  • File management with ability to edit .md files
  • File versioning and ability to restore old versions
• Volunteer Attendance for each event
• Volunteer Signup for which workshops they will help in on the schedule
  • This is an interactive grid with live updates
• Attendee management with ability to add local attendees
• Eventbrite integration for various areas
  • Events
  • Attendees
    • You can configure what gets imported from your forms
• Public schedule page
• Extensive logging viewable within the app
• Dark mode...

A core feature to this system is that a lot of the pages have live updating built into them. As someone adds workshops to the schedule, it live updates for everyone. This is the same for the Volunteer attendance, signups, and attendee pages

All planned and currently in development features can be seen in the GitHub project attached to this repo.

If you have any feature requests or bugs, feel free to open a discussion, create an issue, contact me or if you want, open a Pull Request.

Software Stack

• Server - Python
  • Flask
  • Flask SqlAlchemy
• DB - PostgreSQL
• File Storage - MinIO
• Front end:
  • HTML
  • CSS
  • TypeScript (compiled into JavaScript)

Running JAMS

Jams has been developed with docker in mind. You can use the example docker compose and .env files in the docker folder. Once you have filled out the compose file with your settings, it should set everything up for you. The default user that it creates will be AdminAccount with the password admin. You should change this.

If running in production at scale, it is recommended to run this behind a reverse proxy that can handle SSL for you. Personally I use Traefik for this.

Custom config

The provided docker compose file includes containers for Postgres and MinIO. However if you want to run your own DB and file storage, you can.

The database has to be PostgreSQL. If doing this, you will need to add an environment variable in the jams-web container called DATABASE_URL. This will look like this:

DATABASE_URL=postgresql://username:password@address:port/jams-main

As for file storage, any S3 API compatible system should work, but this has not been tested. For that you will need to add another environment variable in the jams-web container called MINIO_ENDPOINT. This will look like this:

MINIO_ENDPOINT=address:port

I strongly recommend against doing these if you are running them on an external server to jams-web. This is because it is currently configured to use http as it is just over the docker network. I'll update this README if this changes in the future

Screenshots

Schedule Planner:

Eventbrite Settings:

Authentication sources Settings:

Add Event page (edit is very similar):

Edit Workshops page (add is very similar):

Volunteer Attendance:

Volunteer Signup:

Events Page:

I have not shown all the pages that are like events. Ones like Workshops, Attendees, etc... These are all very similar. A table with data and some actions

And for those who for some reason like light more, all pages support both dark and light mode. Here is the Schedule planner as an example: