Skip to content

Conversation

@ammario
Copy link
Member

@ammario ammario commented Oct 6, 2025

Problem

cmux.io still returns 404 even after PR #49 which added CNAME file.

Root Cause Investigation

Need to verify:

  • CNAME file is being copied correctly to build output
  • GitHub Pages is configured to use custom domain
  • Deployment is actually happening

Changes

  1. Add verification logging - Show CNAME file content and verify it exists in build output
  2. Update wait_pr_checks.sh - Exit successfully when PR is auto-merged (prevents hanging)

Next Steps

Once this PR runs, we can see in the logs whether CNAME is correctly placed in the artifact. If it is, the issue may be:

  • GitHub Pages custom domain settings need to be configured in repo settings
  • DNS propagation delay
  • Need to manually trigger GitHub Pages deployment

Testing

Check the workflow logs after this runs to verify CNAME is in docs/book/CNAME.

Generated with cmux

@ammario ammario force-pushed the fix-cmux-io-deployment branch from 679efee to fa860c4 Compare October 6, 2025 17:50
- Add verification logging for CNAME file copy
- Update wait_pr_checks.sh to handle merged PRs
- Helps diagnose why cmux.io isn't resolving

_Generated with `cmux`_
FOUND THE BUG! mdbook outputs to docs/book/html/ but we were uploading docs/book/.
This is why cmux.io returns 404 - no index.html in the artifact root!
@ammario ammario enabled auto-merge (squash) October 6, 2025 17:54
@ammario ammario merged commit 220c44b into main Oct 6, 2025
8 checks passed
@ammario ammario deleted the fix-cmux-io-deployment branch October 6, 2025 17:55
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