This repo is used as an example/guide when facilitating internal workshops relating to Source Control, CI/CD, Infrastructure as Code, Cloud, Serverless etc.

This repo is intended to showcase a simple example of how app and serverless infrastructure codebases can be housed together and managed from a single repository.

The services deployed and managed by this repo (eg. in GitHub, Terraform Cloud and Cloudflare) incur no cost - they are free to run.

This repo is manages both the infrastructure and application codebases for the www.jaseblenner.com landing page

Our (web) application Next.JS/React codebase is housed in the ./app/ folder - any changes to this codebase on the main branch will trigger a production deployment against the Cloudflare Pages Project named wwwjaseblennercom - for this reason, the main branch has branch protection enabled.

In addition to this, Cloudflare automatically invokes deployment checks prior to a PR being marked available to merge.

Note: Cloudflare Pages in conjunction with our custom domain provides transparent management and automation of SSL/TLS certificates removing a large chunk of management overhead if managing certs ourselves.

Any changes made to any other branch will trigger a development deployment against the same Cloudflare Pages Project

Our infrastructure code is housed in the root (top level) of the repository. Any changes to this codebase on the main branch will trigger a speculative terraform plan against the Terraform Cloud workspace of the same name as a VCS connection has been configured on the Terraform Cloud Workspace. Note that all changes to main must be merged by way of an approved PR.

Local basic pre-commit and linting checks (mainly for terraform) have been configured in the .pre-commit-config.yaml file - note that there is a dependency to have the required pre-commit linters and dependencies installed locally for these to run successfully. Example only. A better way to do this would be to leverage GitHub Actions to perform these.

The ./.github/CODEOWNERS file is used to define individuals or teams that are responsible for code in a repository.

• Next JS / React
• Terraform Workspaces / VCS
• Cloudflare Pages
• Cloudflare DNS
• GitHub pre-commit
• GitHub CODEOWNERS