A collaborative rostering app for self-organized teams.

You might need to install some CLI tools first:

• Node >= 16.x and NPM
• Quasar CLI
• Icon Genie CLI
• Cordova CLI

npm install

To run the app, you need to create .env files in the project root directory. You can create and name them according to your needs. However, there are some .env files required for the most common purposes:

• .env for production builds (default)
• development.env for development builds

Some environment variables provide specific or sensitive information that are used at runtime, others are used at build time for building, signing, notarizing or uploading the app. Here is a list of commonly used environment variables in this project.

Starting the app in development mode requires valid https certificates for localhost. This is necessary as some Web APIs are only available in secure contexts and the development environment should be as close as possible to the production app. To achieve this, you need to install mkcert first. mkcert is a simple tool for making locally-trusted development certificates. After the installation follow these steps:

0. Run mkcert -install to setup a local root CA on your development machine once
1. In this project"s root directory, run mkcert -cert-file localhost.pem -key-file localhost-key.pem localhost 127.0.0.1 ::1 to create the certificate and key. We strongly recommend that you add your development machines IP addresses to that list after ::1 before running the command. The IP addresses will be used by Cordova to access the app in development mode from external test devices, simulators and emulators. You can add further domain names as well in case you need them. Two files will be created in the project directory named localhost-key.pem and localhost.pem. In case your IP address changes, you need to recreate certificate and key, otherwise your Cordova app will freeze on launch.
2. You will need to install and trust your local rootCA.pem file on every external test device. You find that file in the folder printed by running mkcert -CAROOT. To install your rootCA.pem file in the simulator drag & drop the rootCA.pem file onto the running simulator. Check in Settings App under "General > About > Certificate Trust Settings" if it is trusted.

For further guidance on mkcert we recommend reading these articles or it"s GitHub Readme.

Finally we are ready to run the app in development mode!

Developing for iOS and Android requires some initial installation and configuration on your development system, so before you start you want to follow this guide to setup Cordova. After that check our own notes for Cordova configuration which includes our learnings about building on the latest versions of macOS.

You will also need to create the file src-cordova/build.json which includes required configuration to build the app for iOS and Android.

For debugging including hot-code reloading, error reporting, etc.

npm run dev web

The following commands will launch RoaringRoster in development mode for debugging on a locally connected device or if none is connected on installed simulators or emulators:

npm run dev ios

npm run dev android

You can connect the Safari or Chrome developer tools on your computer to your device, simulator or emulator for debugging.

npm run dev electron

The installed build behaves closer to a production build, but is still debuggable.

npm run device ios

npm run device android

Please read our Contributing Guide.

To learn more about changing the app configuration and user interface, see the Quasar documentation. You might also want to familiarize with the app"s architecture using Vue.js.

To build RoaringRoster for testing and production use, see our guide on how to build and publish the app.