Add template: peach.build.hosting#1339
Open
grega91 wants to merge 2 commits into
Open
Conversation
|
✅ JSON Filename Check Passed |
|
✅ JSON Schema Validation Passed |
Linter OK
|
| Level | Code | Note |
|---|---|---|
| info | DCTL1029 | template does not have syncPubKeyDomain |
PR Description Check PassedAll required sections are filled in correctly. Details |
pawel-kow
requested changes
Jul 8, 2026
| "version": 1, | ||
| "logoUrl": "https://www.peach.build/peach-logo.svg", | ||
| "description": "Connects your domain to your published Peach experience (www CNAME to Peach's edge; SSL is issued automatically).", | ||
| "variableDescription": "No variables — the record targets Peach's fixed customer CNAME endpoint.", |
Member
There was a problem hiding this comment.
Re-consider using syncPubKeyDomain.
Yes, the template has no variables but still some providers require it by policy and the templates need to be updated.
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.
Description
New template for Peach (peach.build), a 3D web-experience builder. A single static
CNAME points the customer's
wwwhost at our Cloudflare-for-SaaS endpoint(
domains.peach.build); TLS certificates are issued automatically on our side.The service is live; discovery and the sync apply flow are implemented per spec.
Type of change
How Has This Been Tested?
<providerId>.<serviceId>.jsonlogoUrlis actually served by a webserverChecklist of common problems
syncPubKeyDomainis set — justification for omission: the template contains novariables and a single static CNAME record pointing at the provider's fixed customer
endpoint. Applying it is byte-identical to creating the same public record manually, it
grants no access on the Peach side (attaching a domain to content additionally requires
authenticated ownership of that content in our platform, verified independently of DNS),
and no user data flows through the apply URL. We're happy to add signed requests in a
follow-up version if preferred.
warnPhishingis not set alongsidesyncPubKeyDomainsyncRedirectDomainis set whenever the template usesredirect_uriin the synchronous flow (N/A —redirect_urinot used)txtConflictMatchingModeis set on every TXT record that must be unique (N/A — no TXT records)hostlabel (N/A — no variables)hostfield to create a subdomain (N/A — no variables)%host%does not appear explicitly in anyhostattributeessentialis set toOnApplyon records the end user may need to modify or remove without breaking the template (N/A — the single CNAME is the service; removing it is intentional disconnection)Online Editor test results
Editor test link(s):
Test peach.build/hosting example.com/@
Test peach.build/hosting example.com/shop