Skip to content

Site: also serve copper.exowatt.com from Exowatt AWS - #190

Merged
collinrijock merged 1 commit into
forkfrom
site-aws
Nov 18, 2026
Merged

collinrijock merged 1 commit into
forkfrom
site-aws

Conversation

@collinrijock

Copy link
Copy Markdown
Collaborator

Serves site/ from Exowatt AWS at https://copper.exowatt.com, alongside GitHub Pages.

  • infra/site-aws.yml: CloudFormation stack copper-site (already created): private S3 copper-site-340752802981, CloudFront E2MR74IJVKSHAD (OAC, HTTPS redirect, HTTP/2+3, gzip/br, HSTS), deploy role gha-copper-site-deploy (GitHub OIDC, refs/heads/fork only; S3 on this bucket + invalidations on this distribution only). Same shape as exowatt-landing-page's prod stack.
  • .github/workflows/site.yml: new aws job after build on pushes to fork: s3 sync --delete (HTML always revalidated, assets 1h in browsers) then invalidate /*.
  • site/README.md: one line. site/index.html untouched.

The custom name goes live once Cloudflare has the ACM validation CNAME and copper CNAME → d1ms30564yaqk4.cloudfront.net (DNS only), then the stack is re-run with the cert. Until then the site already answers at https://d1ms30564yaqk4.cloudfront.net/.

infra/site-aws.yml is the CloudFormation stack (private bucket, CloudFront with OAC, deploy role trusted only for pushes to fork). site.yml gets an aws job that syncs site/ and invalidates the cache. Does not touch site/index.html.
@collinrijock
collinrijock merged commit 3994508 into fork Nov 18, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant