Skip to content

ci: fail when dist/ does not match a clean rebuild - #1

Merged
CameronBrooks11 merged 1 commit into
masterfrom
chore/dist-drift-check-and-deploy-docs
Aug 25, 2026
Merged

ci: fail when dist/ does not match a clean rebuild#1
CameronBrooks11 merged 1 commit into
masterfrom
chore/dist-drift-check-and-deploy-docs

Conversation

@CameronBrooks11

Copy link
Copy Markdown
Member

Apache serves the committed dist/ and the server never runs a build, so src/
and dist/ drifting apart is invisible in production.

The existing Verify output step checks the seven pages exist — not that they
match what src/ would produce. A stale dist/ passes it. This adds a real
git diff --exit-code -- dist/ check after the build.

The sibling cameronbrooks-net site, built from the same template, ran 20 months
behind master before anyone noticed. This repo is in better shape — dist/
currently reproduces exactly, so the check passes from the start.

Also adds a Deployment section to the README covering the manual pull, the
rebuild-and-commit requirement, and the server posture set on 2026-08-25:
key-only SSH, fail2ban, and 443 pinned to Cloudflare ranges. It calls out
specifically that port 80 must stay open — certbot uses the apache
authenticator (HTTP-01), so restricting it breaks renewal up to 90 days later
with no warning.

README.md and ci.yml were already outside the Prettier globs CI checks, and were
not Prettier-clean before this change either. Left alone rather than reformatted,
to keep the diff to the actual change.

Apache serves the committed dist/ and the server never runs a build, so
src/ and dist/ drifting apart is invisible in production. The existing
"Verify output" step checks the seven pages exist, not that they match
what src/ would produce, so a stale dist/ passes.

A sibling site on the same template ran 20 months behind master before
anyone noticed. This repo's dist/ currently reproduces exactly, so the
check passes from the start.

README gains a Deployment section: the manual pull, the
rebuild-and-commit requirement, and the server's posture -- key-only
SSH, fail2ban, 443 pinned to Cloudflare ranges, and specifically that
port 80 must stay open while certbot validates over HTTP-01.
@CameronBrooks11
CameronBrooks11 merged commit ca37b7d into master Aug 25, 2026
1 check 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