Delivery Domain

By default, a blog is hosted through the app domain subdirectory: https://<app-domain>/blog/<subdomain>

You can configure a Delivery Domain to serve blogs from subdomains of a given domain instead. For example, on our cloud, blogs are hosted at *.hyvorblogs.io.

Why use a delivery domain?

For most cases, we recommend using the default method of hosting blogs through the app domain /blog/*. A Delivery Domain is recommended in one specific scenario: your Hyvor Blogs instance hosts blogs for various users, and you want to keep their content isolated on separate subdomains to ensure proper content segregation.

Delivery Domain is a different feature from Custom Domains. Delivery Domain concerns the default hosting method for a blog, while any blog may or may not set up its own custom domain.

Configuring a Delivery Domain

Add DELIVERY_URL environment variable:

DELIVERY_URL=https://delivery.domain

Then, configure a DNS record to point all subdomains of your delivery domain to your server:

A   *.delivery.domain   1.2.3.4

Finally, configure your server to terminate TLS for your delivery domain. This requires a wildcard certificate for *.delivery.domain, which may require a DNS-01 challenge for issuance.

Full architecture:

*.delivery.domain
    ↓
Reverse Proxy (HTTPS, Port 443)
    ↓
Hyvor Blogs Container (HTTP, Port 80)