Copy the structure of this repo for new repos deleting anything in app_data and re working config.ts

Manual

This will create a release and upload it to Google play console. The first time this is run users will need to upload the 'release_bundle' created in the action manually. It will only upload automatically once the first build as been uploaded.

• APP_CODE_BRANCH - the tag/branch for the code repository
• APP_ID - app id used in firebase and play store (generally international.idems.[DEPLOYMENT NAME])
• DEPLOYMENT_NAME - Name of app (use underscores)

using keytool -genkeypair -v -keystore [APP_ID] -keyalg RSA -keysize 2048 -validity 10000 -alias [ALIAS]

• ALIAS - Name of app (use hyphens)
• KEY_PASSWORD - random
• KEY_STORE_PASSWORD
• SIGNING_KEY - generated with tool
• GOOGLE_PLAY_SERVICE_ACCOUNT_JSON - Service account to access Google Play

Play console set up

config.android
config.api.db_name (to log data)
config.error_logging (glitch tip dsn added)

Manual

This will grab content from Sheets and create a PR with the changes

• PAT - Personal access token from GitHub in order to comit code and create a PR access to sheets via credentials (see https://developers.google.com/workspace/guides/create-credentials)
• GDRIVE_CREDENTIALS -
• GDRIVE_TOKEN -

config.google_drive 

Automatic - When new code is mergerd into main

This will create a web preview in Firebase

Automatic - When 'test - preview' is added to a PR

This will create a temporary web preview based on the PR branch. The URL will be added to the PR

See Deploy-firebase

Manual

Same as Deploy-firebase but uses FIREBASE_HOSTING_TARGET_RELEASE and is manually triggered

WIP

WIP