Skip to content

feat: AWS Amplify build spec + deployment docs for docs.grith.ai#2

Merged
djf73 merged 1 commit into
mainfrom
feat/amplify-deploy
May 18, 2026
Merged

feat: AWS Amplify build spec + deployment docs for docs.grith.ai#2
djf73 merged 1 commit into
mainfrom
feat/amplify-deploy

Conversation

@djf73
Copy link
Copy Markdown
Collaborator

@djf73 djf73 commented May 18, 2026

Summary

Closes P1 #5 in work/findings/launch-readiness-followup-2026-05-18.md. The docs site has existed for months but docs.grith.ai is not deployed anywhere (HTTP 000, DNS doesn't resolve).

Per your instruction, this wires up AWS Amplify (same provider as grith.ai). The PR is the code half — amplify.yml + setup docs. The console-side half (connecting the repo, adding the custom domain) is your ~5 minutes of clicking; the README walks through it step-by-step.

What's in this PR

amplify.yml (new)

Single-app build spec — grith-docs is a static Next.js export, not a monorepo wrapper. Mirrors the grith-website pattern minus the env-var injection (the docs site has no runtime secrets).

preBuild:    nvm install 22 / npm ci
build:       npm run build      # gen:llms → next build → gen:pagefind
baseDirectory: out
cache:       node_modules + .next/cache

README.md — new "Deployment to docs.grith.ai" section

  • Table of canonical Amplify settings
  • One-time console steps: connect GitHub repo, pick main, confirm auto-detected build spec, add custom domain, point CNAME, ACM provisions TLS
  • Ongoing-operations notes: push-to-deploy on main, optional PR previews, log location

Verified

  • python3 -c 'import yaml; yaml.safe_load(open("amplify.yml"))' parses.
  • npm run build end-to-end clean locally: 146 pages indexed by Pagefind, search index written to out/pagefind/.
  • After merge — you connect the GitHub repo to Amplify per the README, deployment runs, custom domain docs.grith.ai resolves with valid TLS. Then we close P1 #5 in the audit followup.

Your next steps (post-merge)

  1. AWS Amplify console → Create new app → Host web appGitHub.
  2. Authorise the AWS Amplify app on the grith-ai org (one-time).
  3. Pick grith-ai/grith-docs, branch main.
  4. Confirm Amplify auto-detected amplify.yml.
  5. Save + deploy. First build ~3-5 min.
  6. Domain management → Add domain → docs.grith.ai. Amplify gives you a CNAME target.
  7. Add the CNAME in your DNS provider for docs.grith.ai.
  8. ACM auto-provisions TLS once DNS resolves.

🤖 Generated with Claude Code

Closes P1 #5 in ../grith/work/findings/launch-readiness-followup-
2026-05-18.md. The docs site source has existed for months but
docs.grith.ai is not deployed anywhere (HTTP 000, DNS doesn't
resolve). The audit flagged the missing deploy CI as the gating
item; the user's preference is to host on AWS Amplify, matching
grith.ai.

amplify.yml at the repo root: single-app build spec (the docs site
is a static Next.js export, no monorepo wrapper needed). preBuild
sets Node 22 and runs `npm ci`; build runs `npm run build` which
chains gen:llms → next build → gen:pagefind. baseDirectory is `out/`
where Next emits the static tree and Pagefind appends its search
index under out/pagefind/. No environment variables are needed —
the docs site has no runtime secrets.

README.md gains a "Deployment to docs.grith.ai" section with:
- a table of the canonical Amplify settings,
- one-time setup steps for the AWS Amplify console (connect GitHub,
  pick branch, confirm auto-detected build spec, add custom domain,
  point CNAME),
- ongoing-operations notes (push-to-deploy on main, preview-build
  toggle, log location).

Verified locally:
- `python3 -c 'import yaml; yaml.safe_load(open(\"amplify.yml\"))'` parses.
- `npm run build` succeeds end-to-end: 146 pages indexed by Pagefind,
  search index written to out/pagefind/.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@djf73 djf73 merged commit 7126e93 into main May 18, 2026
1 check passed
@djf73 djf73 deleted the feat/amplify-deploy branch May 18, 2026 16:33
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