Custom Domains

By default, your roster lives at apps.ngit.com.au/<your-slug>/rosters/. You can also serve it from your own subdomain (e.g. apps.yourclub.com.au/rosters/ or rosters.yourclub.com.au) for a cleaner URL and stronger branding.

What you get

• Volunteers see your domain, not ngit.com.au.
• The embed widget can be served from your domain too.
• The admin login lives at the same domain (apps.yourclub.com.au/admin).
• Magic-link emails point to your domain.

What you need

• A domain you control (e.g. yourclub.com.au).
• Access to your DNS provider's dashboard (or your web person can do it).
• About 5 minutes for the DNS change, plus 5-15 minutes for it to propagate.

How it works

Cloudflare hosts NGIT Apps. To point your subdomain at our worker, you add a single CNAME record at your DNS provider:

Name:    apps     (or rosters, or whatever subdomain you want)
Type:    CNAME
Target:  apps.ngit.com.au
TTL:     auto / default
Proxy:   orange cloud (if your DNS is also on Cloudflare)

Then NGIT registers the hostname as a Cloudflare Worker Custom Domain via the API. SSL is provisioned automatically.

Setup steps

1. You (club admin): add the CNAME record at your DNS provider. Wait a couple minutes for it to propagate (test with dig apps.yourclub.com.au).
2. Email NGIT (support@ngit.com.au) with the new hostname.
3. NGIT (master admin): opens Configure on your club, enters the hostname in Custom domain, clicks Save. The worker calls Cloudflare to register the binding and provisions an SSL cert (takes about 30 seconds).
4. Verify: visit https://apps.yourclub.com.au/admin in your browser. You should see your branded admin login.

Multi-app subdomains (advanced)

If you ever want a second NGIT app on the same hostname (e.g. apps.yourclub.com.au/events alongside apps.yourclub.com.au/rosters), the master admin can use Configure → Advanced → Provision a new module hostname to register a module_routes entry. Don't worry about this until you actually have a second app.

Common gotchas

• CNAME conflicts with existing DNS records: if you have an A or AAAA record for apps, it clashes. Delete it first; CNAMEs cannot coexist with other records on the same name.
• DNS not propagated yet: the worker registration will fail with "hostname not pointing here". Wait 5 minutes and retry.
• SSL cert pending: occasionally the cert takes a few minutes to issue. Visit the URL and reload; if it shows a cert warning, give it 5 more minutes.
• Old rosters.X.com.au hostname: legacy. Still 301-redirects to apps.X.com.au/rosters/. New clubs go straight to apps.*.

Removing a custom domain

Tell NGIT. They'll clear it via the master admin Configure panel. Your club's roster falls back to apps.ngit.com.au/<your-slug>/rosters/. No data loss.