Skip to content

add VibeHost, VibeHost Custom Domain#1369

Open
sangnekk wants to merge 1 commit into
Domain-Connect:masterfrom
sangnekk:add-vibehost.vn-hosting
Open

add VibeHost, VibeHost Custom Domain#1369
sangnekk wants to merge 1 commit into
Domain-Connect:masterfrom
sangnekk:add-vibehost.vn-hosting

Conversation

@sangnekk

Copy link
Copy Markdown

Description

New template for VibeHost (vibehost.vn) — a Vietnamese web-hosting provider.
The template adds a single A record pointing the customer's domain (apex or
subdomain via the host parameter) to the IPv4 address of their VibeHost
hosting node (%ip%). Used by the "Custom Domain" feature so customers can
connect their own domain with one click instead of editing DNS manually.

Type of change

Please mark options that are relevant.

  • New template
  • Bug fix (non-breaking change which fixes an issue in the template)
  • New feature (non-breaking change which adds functionality to the template)
  • Breaking change (fix or feature that would cause existing template behavior to be not backward compatible)

How Has This Been Tested?

Please mark the following checks done

  • Template functionality checked using Online Editor
  • Template file name follows the pattern <providerId>.<serviceId>.json
  • resource URL provided with logoUrl is actually served by a webserver

Checklist of common problems

Mark all the checkboxes after conducting the check. Comment on any point which is not fulfilled.
See Template Quality Guidelines for details and rationale on each rule.

  • syncPubKeyDomain is set — this is mandatory; omitting it requires explicit justification in the PR description or the PR will be rejected
  • warnPhishing is not set alongside syncPubKeyDomain — the two must not appear together
  • syncRedirectDomain is set whenever the template uses redirect_uri in the synchronous flow
  • no TXT record contains SPF content ("v=spf1 ...") — use the SPFM record type instead
  • txtConflictMatchingMode is set on every TXT record that must be unique per label or content prefix (e.g. DMARC) — N/A, template has no TXT records
  • no variable is used as a bare full record value (e.g. @ TXT "%foo%") unless necessary — prefer @ TXT "service-foo=%foo%"; if bare, justify in the PR description — %ip% as A-record pointsTo is the standard pattern for custom-domain hosting templates (each hosting node has its own IPv4), same as e.g. approximated.app.arecord.json
  • no bare variable is used as the full host label — the non-variable parts are fixed to limit misuse (e.g. %dkimkey%._domainkey, not %dkimhost%); if bare, justify in the PR description — host is fixed @
  • no variable is used in the host field to create a subdomain — use the host parameter or multiInstance instead
  • %host% does not appear explicitly in any host attribute
  • essential is set to OnApply on records the end user may need to modify or remove without breaking the template (e.g. DMARC) — N/A, the single A record IS the service; users manage it through VibeHost

Online Editor test results

Editor test link(s):
Test vibehost.vn/hosting example.com/@

Test vibehost.vn/hosting example.com/bot

@sangnekk sangnekk force-pushed the add-vibehost.vn-hosting branch from e14d761 to f17b037 Compare July 11, 2026 12:10
@github-actions

Copy link
Copy Markdown

JSON Filename Check Passed

@github-actions

Copy link
Copy Markdown

JSON Schema Validation Passed

@github-actions

Copy link
Copy Markdown

PR Description Check Passed

All required sections are filled in correctly.

Details
  OK  Type of change: 1/4 checkboxes ticked
  OK  How Has This Been Tested?: all 3 checkboxes ticked
  OK  Checklist of common problems: 10/10 checkboxes ticked
  OK  Online Editor test results: 2 link(s) found
  OK  Template coverage: all 1 template(s) covered
Labels to remove: Checklist of common problems not complete, Forged editor links, PR description incomplete, Test links missing

PR description check PASSED

@github-actions

Copy link
Copy Markdown

Linter OK

vibehost.vn.hosting.json

Level Code Note

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