Skip to main content

​
Domain map

​
DNS records

Add the following records at the domain provider (where muzemus.online was purchased). Exact record types depend on the provider; the values below are the standard forms.
Firebase apex IPs: Firebase Hosting serves the apex domain via the two A records above. If the provider requires a single value, use 151.101.1.195 and add the second record if supported. Firebase will show the exact records to add when you connect the domain in the Firebase console — prefer those values over this table.

​
Custom domain setup (one-time, per service)

​
Firebase Hosting (landing, production, staging)

  1. In the Firebase console, open Hosting and add the domain to the relevant site:
    • muzemus.online → site muze-mus-landing
    • app.muzemus.online → site muze-mus
    • stage.muzemus.online → site muze-mus-stage
  2. Firebase shows the DNS records to add (the A/CNAME records above).
  3. Add the records at the domain provider, then click Verify in Firebase.
  4. Wait for propagation (minutes to a few hours), then Firebase provisions the TLS certificate automatically.

​
Render (production and staging API)

  1. Render’s free plan does not support custom domains. Upgrade each backend service to Starter (or higher).
  2. In the Render dashboard, open the service → Settings → Custom Domains.
  3. Add api.muzemus.online (production service) and stage-api.muzemus.online (staging service).
  4. Add the CNAME records above at the domain provider.
  5. Render provisions the TLS certificate automatically.

​
Mintlify (user guide and architecture docs)

  1. In the Mintlify dashboard, open the site → Settings → Custom domain.
  2. Add doc.muzemus.online (user guide) and system.muzemus.online (architecture).
  3. Add the CNAME records above at the domain provider.
  4. Mintlify verifies the record and provisions TLS.

​
Fallback: staying on the free Render plan

If the backend services remain on the free plan, the API custom domains will not resolve. In that case, point the frontend at the .onrender.com URLs instead: Update frontend/.env.production / frontend/.env.staging accordingly and redeploy. The BETTER_AUTH_URL and FRONTEND_ORIGIN values on the Render services must match the frontend origin actually in use.

​
Verification

After DNS propagates:
Each should return the target from the domain map. Then confirm HTTPS: