Document Cloudflare Pages DNS and 1Password deploy credentials - #1
Open
Sean Future (seanfuture) wants to merge 1 commit into
Open
Document Cloudflare Pages DNS and 1Password deploy credentials#1Sean Future (seanfuture) wants to merge 1 commit into
Sean Future (seanfuture) wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
developers.enterprisecrm.com(CNAME to Pages, not Netlify)Test plan
enterprise-api-docs-9s9)developers.enterprisecrm.comNote
Low Risk
Documentation-only changes with no runtime, auth, or infrastructure code impact.
Overview
Updates
DEPLOY_CLOUDFLARE.mdso deploy setup and production DNS are explicit for Cloudflare Pages.The one-command publish section now documents 1Password (Engineering → Cloudflare API Token) and
modules/setup-1p.jsonas the preferred credential path, with env vars still listed as a fallback.A new Custom domain DNS (required) section specifies that
developers.enterprisecrm.commust CNAME toenterprise-api-docs-9s9.pages.dev(proxied), not Netlify, including a table of record settings. It calls out SSL cipher mismatch / 522 when DNS still targetsenterprise-api-docs.netlify.app, and notes waiting for the Pages custom domain to show Active after DNS changes.Reviewed by Cursor Bugbot for commit 852700a. Bugbot is set up for automated code reviews on this repo. Configure here.