Handover

Centralised Handover with OAuth2, using Laravel 10. Created by Daniel L. (1352906) and Matan B. (1375048). An extra special thanks to VATSIM UK's open source core system which helped us on the right track with this one.

Prerequisites

Docker (Recommended)

• A Docker environment to deploy containers. We recommend Portainer.
• MySQL database to store data.
• Preferably a reverse proxy setup if you plan to host more than one website on the same server.

In the instructions where we use docker exec, we assume your container is named handover. If you have named it differently, please replace this.

Manual (Unsupported)

If you don't want to use Docker, you need:

• An environment that can host PHP websites, such as Apache, Ngnix or similar.
• MySQL database to store data.
• Comply with Laravel 10 Requirements
• Manually build the composer, npm and setting up cron jobs and clearing all caches on updates.

Setup and install

To setup your Docker instance simply follow these steps:

1. Pull the ghcr.io/vatsim-scandinavia/handover:v3 Docker image
2. Setup your MySQL database (not included in Docker image)
3. Configure the environment variables as described in the CONFIGURE.md
4. To ensure that users will not need to log in after each time you re-deploy or upgrade the container, you need to create and store an application key in your environment and setup a shared volume.

   docker exec -it handover php artisan key:get
   docker volume create handover_storage

   Copy the key and set it as the APP_KEY environment variable in your Docker configuration and bind the volume when creating the container with handover_storage:/app/storage.
5. Start the container in the background.
6. Setup the database.

   docker exec -it --user www-data handover php artisan migrate

7. Setup a crontab outside the container to run * * * * * docker exec --user www-data -i handover php artisan schedule:run >/dev/null every minute. This patches into the container and runs the required cronjobs.
8. Bind the 8080 (HTTP) and/or 8443 (HTTPS) port to your reverse proxy or similar.

Refer to the CONFIGURE.md for information about theming text, colors and logos.

Updating

After recreating the docker container, remember to run the migration to make sure your database is up to date.

docker exec -it --user www-data handover php artisan migrate

Adding OAuth Clients

Add your client auth token with

docker exec -it --user www-data handover php artisan passport:client

Skip with ENTER when asked to assign to specific user. Name the client something descriptive as it's shown to the user and add the callback URL. The generated ID and Secret can now be used from other OAuth2 services to connect to Handover.

Updating Data Protection Policy

When you update your DPP, you should make all users explicitly accept the new policy again. To do this, follow these steps:

1. Update the date and url to DPP in your environment variables.
2. If needed, update the DPP simplified version according to the configuration manual
3. Reset all user's accepted_privacy variable in database with

   docker exec -it --user www-data handover php artisan reset:acceptedprivacy

4. To make sure everyone needs to login again, delete the sessions:

   docker exec -it --user www-data handover sh -c 'rm -rf /app/storage/framework/sessions/*'

Present automation

The only job the cron has automated today is daily member check and pull freshest data from VATSIM

OAuth Credentials

• Method: Authorization Code

• Client ID: Usually a short id number

• Client Secret: String of hash you generated earlier

• Authorization Endpoint: /oauth/authorize

• Token Endpoint: /oauth/token

• User Information Endpoint: /api/user

• Login Callback: /login

Contribution and conventions

Contributions are much appreciated to help everyone move this service forward with fixes and functionalities. We recommend you to fork this repository here on GitHub so you can easily create pull requests back to the main project.

In order to keep a collaborative project in the same style and understandable, it's important to follow some conventions:

GitHub Branches

We name branches with feat/name-here or fix/name-here for features or fixes, for example feat/new-api or fix/login-bug