Deployment

GitHub

All code is stored in Git repositiories in club specifc accounts. Code pushed to GitHub triggers either:

• Cloudflare to deploy the commit, or
• GitHub Actions to build the commit into a container and push it to the revelant Container registry.

GitHub actions are also used for:

• backup of Cloudflare D1 databases
• webhook triggered from Strapi to rebuild and deploy a club website

Each club has its own Cloudflare account which is used for:

1. Domain registration and management, DNS and domain specific rules
2. Cloudflare Workers which in turn can use KV storage, D1 database, R2 object storage, Observability logs and Analytics Engine
3. Cloudflare Turnstile as CAPTCHA replacement

All Sveltekit applications and the bespoke Hono servers are deployed on Cloudflare.

1. App platform is used to automatically deploy the application from its container registry, supported by its PostgreSQL Managed Database Service and S3 storage.
2. Droplets (Linux-based virtual machines) are currently used the routes database servers, as they have persistent storage which allows use of local SQLite database. VM require more work the managed platforms to set up, update, maintain, monitor and, in the rare event of a catastrophic crash, manually restart. Techonolgies which need configuring include:

1. Spaces is used to provide the S3 storage needed to load, store or backup files, documents and images use.
2. PostgreSQL Managed Database Service is used to support
3. Container Registry and Firewalls are used to support the above.

Others

Archive Storage provides as a seperate low cost S3 storage to back up all content in the S3 Standard Storage.

is used by some clubs as an alternative to Digital Ocean PostgreSQL Managed Database Service

Amazon Simple Email Service is used to send emails from the web servers.

is used by one club as an alternative to AWS SES.

is used for Card payments

is used for Direct Debit payments