Autonnel v0.1.0
Get started

Domains

Bind multiple custom domains; mark primary; configure CDN domain.

Autonnel uses a multi-domain model: each domain is bound to your deployment and there is no intermediate “site” container. You manage domains from Settings → Domains.

Adding a domain

  1. Open Settings → Domains.
  2. Click Add domain.
  3. Paste the hostname, for example shop.example.com. Do not include a protocol or trailing slash.
  4. Click Save.

The new domain row is created with isPrimary: false unless it is the first domain on the deployment, in which case it is marked primary automatically.

Primary domain

Exactly one domain in the deployment can have isPrimary: true. All other domains redirect to the primary domain using a 301 response.

To change the primary domain:

  1. Click the domain you want to promote.
  2. Toggle Set as primary.
  3. Save. The previous primary domain is automatically demoted.

There must always be a primary domain. You cannot remove the primary domain without first designating another domain as primary.

DNS configuration

Autonnel does not manage DNS. You must point your domain to your deployment yourself.

For most hosting setups, add a CNAME record:

shop.example.com.  CNAME  your-autonnel-deployment.example.com.

If your hosting provider gives you an IP address rather than a hostname, use an A record instead.

After DNS propagates (typically a few minutes to a few hours depending on your TTL), the domain becomes live. There is no verification step in the OSS version.

TLS / HTTPS

Autonnel does not issue TLS certificates. You are responsible for terminating HTTPS at your infrastructure layer. Common approaches:

  • Cloudflare proxy — set the DNS record to proxied (orange cloud) and Cloudflare issues a certificate automatically.
  • Hosting provider cert manager — platforms like Fly.io, Railway, and Render provision certificates for custom domains from their dashboard.
  • Nginx + Certbot — for self-hosted deployments, use Certbot to issue Let’s Encrypt certificates and configure Nginx to terminate TLS before proxying to Autonnel.

Static asset domain

The static domain setting controls the base URL prepended to every S3 object key when generating a public asset URL.

If the static domain is left blank, the system attempts to derive a default by prepending static. to the root portion of your primary domain. For example, if your primary domain is shop.example.com, the derived static base would be https://static.example.com.

The static domain field lives in Settings → Storage, alongside the S3 bucket it prefixes, not in Settings → Domains. Set it explicitly if:

  • You are using a CloudFront distribution or Cloudflare cache as a CDN in front of your S3 bucket
  • Your S3 bucket public URL differs from the static. subdomain convention
  • You want all asset URLs to use a specific host for cache-control purposes

The value can be either a bare hostname (e.g., cdn.example.com) or a full URL with protocol (e.g., https://cdn.example.com). If you enter a bare hostname, https:// is prepended automatically.

Example:

If your R2 bucket is publicly accessible at https://pub-abc123.r2.dev, set the static domain to that value. All uploaded images will then resolve as https://pub-abc123.r2.dev/<object-key>.

If you put a Cloudflare cache zone in front, change the static domain to your Cloudflare zone URL instead.

Removing a domain

Click the trash icon next to any non-primary domain to remove it. The Domain row is deleted; no redirect is left in place. Visitors to that hostname will get a domain-not-configured error page until DNS is updated.

You cannot delete the primary domain. Reassign primary first.

Caveats

  • No wildcard domains in OSS — each subdomain requires its own Domain row. Wildcard support (e.g., *.example.com) is a SaaS-only feature.
  • No built-in domain verification — in the OSS version, adding a domain row does not verify that DNS is correctly pointed. Verification (including Cloudflare for SaaS integration) is available only in the managed SaaS version.
  • You cannot add the same hostname twice to the same deployment.
  • Redirects from non-primary to primary domains are handled by the Autonnel middleware. They are 301 permanent redirects. Some crawlers cache 301s aggressively — test before switching primary.