📄️ CI/CD
Overview
📄️ Click ops
Whilst the majority of our infra is defined in code, there are some instances where things have been done manually. This is documented here.
📄️ Cloudflare
Any changes to these workers should be done in the linked file(s) and should not be done via console unless it's for testing a change before propogating it to source code.
📄️ Hecter
Overview
📄️ Infrastructure As Code
We use AWS SAM to write our infrastructure as code. Our SAM templates have been written in a consistent way across all our stacks, to make it easier for new services/stacks to follow a blueprint. This document outlines these best practices and coding guidelines to adhere to when writing our infra as code, as well as general CF tips.