Jumubase is a tool for organizers of Germany's largest youth music competition – Jugend musiziert, or "Jumu" in short. The software powers jumu-nordost.eu, a competition hub for German schools across Europe.
The application serves two main audiences:
- Jumu participants and their families, friends and teachers; they can sign up for a contest, edit their information, and check schedules and results without a user account.
- Jumu organizers on both local and global level, who can manage contest data, enter results and print contest-related material. The permissions for this are granted via personal user accounts.
- Clone this codebase
- Install PostgreSQL, e.g. through the provided
docker-compose.ymlfile or Postgres.app
- Install dependencies with
- Install JS dependencies with
cd assets && npm install
- Create, migrate and seed the local database with
- Start Phoenix endpoint with
Then, point your browser to
Ensure the following environment variables are made available to the app:
DATABASE_URL– Set automatically e.g. on Heroku when provisioning a database.
POOL_SIZE– Depends on how many database connections are allowed by the plan. Leave some room for occasional one-off
mixtasks such as migrations.
SECRET_KEY_BASE– Can be generated using
PHAUXTH_TOKEN_SALT– Can be generated in IEx using
Many schemas / data structs in this app are inextricably linked with the "Jugend musiziert" competition. The following list serves as a brief explanation to those unfamiliar with the domain:
A user of the software, identified by their email and password.
An institution, typically a school, that can host contests.
A location where performances take place. Every host has at least one, but often several stages.
A single- or multi-day event during which performances take place. Besides its associated host, it includes a season (= competition year) and a round.
A set of constraints for participating in a contest. Each category is designed either for solo or ensemble performances and mandates what pieces can be performed, as well as a min/max duration that depends on the performance's age group.
A manifestation of a category when offered within a particular contest. This schema exists to hold additional constraints: Some contests might offer a category only for certain age groups, or not at all.
A musical entry taking place within a contest category, at a given time and venue. It is associated with an age group calculated from the birth dates of the soloist or ensemblists (but not accompanists).
A single participant's contribution to a performance. It holds the participant's instrument and role (i.e. soloist, ensemblist or accompanist, the first two being mutually exclusive). It also stores its own age group, which for accompanists can differ from the performance's age group. Each appearance is awarded points by the jury, and a certificate is given to its participant afterwards.
A person appearing in one or more performances within a contest.
A piece of music presented during a performance. It holds information on the composer or original artist, as well as a musical epoch.
Some Jumu-related data (such as rounds, roles, genres, and category types) is unlikely to change much over time and therefore hard-coded into the
JumuParams module. Parameters that are likely to change, or not meant for the public eye, are stored as environment variables instead.
Phauxth is used for user authentication. Users can be associated with one or several hosts, typically for the reason of being employed there and acting as local organizers. They can only manipulate resources "belonging" to those hosts.
Apart from local organizers with their host-based access rights, there are global organizers who organize the 2nd round hosted somewhere abroad in round-robin fashion, inspectors who may access certain data for statistical purposes, and admin users with full privileges.
Jumubase is published under the MIT License.