Repository navigation
[Owner decision needed] docs: staging license domain guidance contradicts the Deployment Helper store page - #2589
Merged
Su (sushmangupta) merged 3 commits intoOct 23, 2026
Conversation
…ployment Helper (draft, owner decision) Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Developer Docs healthcheckStatus: Completed with |
Developer Docs healthcheckStatus: Running. |
Daniel Kirkland (d-kirkland)
marked this pull request as ready for review
October 20, 2026 08:03
Su (sushmangupta)
requested review from
Soner (shyim)
and removed request for
Soner (shyim)
October 23, 2026 06:57
Contributor
📢 Developer Announcement RecommendationRecommendation: ❌ No Announcement Recommended No developer announcement signals were detected.
|
Su (sushmangupta)
approved these changes
Oct 23, 2026
Su (sushmangupta)
deleted the
fix/docs-license-domain-staging-contradiction-draft
branch
October 23, 2026 11:34
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
Owner confirmation needed. This PR applies one possible resolution. The platform source cannot decide which is right, so please confirm the rule with the Account/Store owners before merging.
maingive opposite guidance for the Shopware Account license domain of a staging environment:creating-a-staging-instance.mdsays: "You should still use your live domain inShopware Account > License Domainto avoid licensing issues."store.mdsays "What does change per environment is the license domain" and listsstaging.example.comfor staging anddev.example.comfor dev, withSHOPWARE_STORE_LICENSE_DOMAIN="staging.example.com" # stagingin the example.core.store.licenseHostto the Store. Which domains the Shopware Account accepts, and whether a staging instance may use the live domain or must register its own, is a Store/Account policy outside the repositories.Options for the owner
store.md. This is what the diff in this PR does.store.mdL63-L64 and L76 must be changed to use the live domain in all environments, and the sentence "Set up multiple domains in your Shopware Account if you need them" (L67) revisited.Nothing in this PR is a verified fact about the Account policy.
Platform context (supporting only, does not decide the policy)
In the platform source, a Shopware Account can list several license domains, each verified separately (
FirstRunWizardService::getLicenseDomainsandverifyLicenseDomainat L229-L253), and each installation uses the one domain set incore.store.licenseHost(including for matching purchase tokens,MatchesLicenceDomain). The source does not say whether a staging or dev instance should use its own domain or the live one; that is for the Account/Store owners to decide.Related links
creating-a-staging-instance.mdL42-L44deployment-helper/store.mdL59-L76v6.7.15.1:StoreRequestOptionsProvider.phpL23 (CONFIG_KEY_STORE_LICENSE_DOMAIN = 'core.store.licenseHost') and L101-L103 (returns the configured string); the same mechanism exists atv6.6.10.29andv6.5.8.19.mainonly;v6.6andv6.5are not affected.Checklist
PageRefreferences where relevant. (The new relative link was resolved from the page's folder.).gitbook.yamlif pages were moved, renamed, or deleted. (N/A).wordlist.txt(and sorted it) if spellcheck flags new legitimate terms. (No new words.)Notes
🤖 Generated with Claude Code