Generic festival app with specific festivals as flavors:

• Party.San Open Air
• Spirit Festival

Place .env file in the root directory.

flutter pub run flutter_launcher_icons:main

Run in the app for a specific festival in development mode as follows:

./scripts/run_dev.sh --flavor=[spirit|party_san] [--year=<YEAR>] [--build=<BUILD>] [--release]
# or
./scripts/run_dev.sh -f=[spirit|party_san] [-y=<YEAR>] [-b=<BUILD>] [-r]
# e.g.
./scripts/run_dev.sh -f=spirit -y=2019 --release
# To install the app
./scripts/run_dev.sh -f=party_san -y=2022 -c=install

• --flavor/-f is required to specify the festival
• --year/-y is needed to prepare the asset folder and download the correct data for the given year. This is required on the first build and between flavor switches.
• --build/-b defaults to dev if omitted
• --release runs the app in release mode

Build the production apk for a specific festival as follows:

./scripts/build_prod.sh [spirit|party_san] [<YEAR>]
# e.g.
./scripts/build_prod.sh spirit 2019
./scripts/build_prod.sh party_san

• The second parameter is optional and used to prepare the asset folder and download the correct data for the given year. This is required on the first build and between flavor switches.

Prepare the assets for a specific festival as follows:

./scripts/prepare_assets.sh [spirit|party_san] <YEAR>
# e.g.
./scripts/prepare_assets.sh party_san 2019

• The second parameter is required and used to prepare the asset folder and download the correct data for the given year.

There is also a helper script to switch to the newest version of a festivals:

./scripts/switch.sh [spirit|party_san]
# e.g.
./scripts/switch.sh party_san

• This script should be updated as soon as a new year is available for a festival.

• Update initial bands.json and schedule.json
• Update display_font.tff if necessary
• Update flyer in android/app/src/<festival>/res/drawable/flyer.jpg
• Update infos if necessary:
  • HTML for FAQs, shuttle plan etc
  • Styling for htmls: font + colors
• Update config.dart:
  • festivalId
  • start and end date
  • Update history entries
  • Update font reference if necessary
  • Update weather info if necessary
  • Update stage alignment if necessary
• Possibly change default year in switch.sh script
• Update colors in theme.dart if necessary

We use mockito for creating mocks in our tests. Since the introduction of null safety in dart, mockito requires code generation to generate mocks. You can update these mocks by running

flutter pub run build_runner build

Tests can be executed by running

flutter test