docs(cdn): update domain ownership instructions and clarify DNS challenge configuration#2368
Open
Renaud Hager (renaudhager) wants to merge 3 commits into
Open
docs(cdn): update domain ownership instructions and clarify DNS challenge configuration#2368Renaud Hager (renaudhager) wants to merge 3 commits into
Renaud Hager (renaudhager) wants to merge 3 commits into
Conversation
Developer Docs healthcheckStatus: Completed with |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the Shopware PaaS CDN custom-domain documentation to improve the logical ordering of DNS setup steps, separating domain ownership TXT record creation into its own step and clarifying the relationship between an application FQDN and the base domain used for the challenge record.
Changes:
- Moved domain ownership TXT record instructions into a dedicated “Step 3: Domain ownership”.
- Clarified the domain vs. FQDN example to make the challenge record target explicit.
- Shifted “Create Domain in PaaS” later in the step sequence to reflect the new ordering.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+130
to
+134
| ### Step 3: Domain ownership - Create a `TXT` record to prove domain ownership: | ||
|
|
||
| ```dns | ||
| _shopware-challenge.<domain> IN TXT "shopware-challenge=<organization id>" | ||
| ``` |
Comment on lines
+154
to
156
| ### Step 4: Create Domain in PaaS | ||
|
|
||
| Once DNS records are configured and propagated, create the domain using the CLI: |
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
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
Restructures the custom domain setup guide in the PaaS CDN docs to fix the step ordering. The domain ownership TXT record instructions were previously bundled into Step 1 (DNS records), but verification (Step 2) logically comes before proving ownership. This moves the TXT record creation into its own dedicated step after DNS propagation is verified.
Changes
Moved the domain ownership TXT record instructions out of Step 1 into a new Step 3: Domain ownership, pushing "Create Domain in PaaS" to Step 4.
Clarified the domain-vs-FQDN example: now spells out that for an application FQDN of myshop.example.com, the domain is example.com (org ID abc123), making the relationship between the application hostname and the challenge record explicit.
Related links
Checklist
PageRefreferences where relevant..gitbook.yamlif pages were moved, renamed, or deleted..wordlist.txt(and sorted it) if spellcheck flags new legitimate terms.Notes