Pulls in a schedule of games for the latest team and creates google calendar events (optionally inviting teammates to the event).
You must set up you config files, vendor files, and install dependencies.
To set up the configuration, create a config folder with the following files.
config.yml: application-wide config. Seeconfig.yml_samplefor expected valuesemails.txt: return-delimited list of emails to add as guest to the eventscredentials.json: google calendar credentials. Check out gcal quickstart for how to get this filetoken.json: google calendar auth token. This file is automatically generated and must be deleted if/when scopes change
This utility uses Chrome as the webdriver. If an outdated driver is detected, a new one will be installed into /vendor
and you will need to re-run the utility. You may need to manually run it once if the quarantine flag fails to be
removed. Additionally, until latest is specified as the webdriver filename, you will need to manually update your env
config.
Google Calendar events need to have a valid auth token stored in config/token.json. Once the token expires, remove the
file and run the utility again. It will prompt for auth in a web browser and automatically store the newly generated
token.
Game info is locked behind a secure portal. To log in, credentials must be specified. While hard-coded strings can be specified, credentials can be pulled from 1Password via CLI. See here on how to get started. Once the CLI is enabled in 1password, you will be able to copy the secret reference and store that in the YML config.
Dependencies can be installed with poetry install.
Once your environment is set up, call run.py