Skip to content
FEMNET

Domains and email

Which addresses point where, and how transactional email is sent.

IT teamDone in: Server3 steps
  1. 1

    Domains

    The API currently runs at femnet-api.duckdns.org, served by Caddy on the VPS, which obtains HTTPS certificates automatically. The learner app and hub each have their own domain; whenever a domain changes, update the backend's allowed hosts and CORS settings (see Manage settings and secrets).

  2. 2

    Frontend API address

    Each frontend is built with NEXT_PUBLIC_API_BASE_URL pointing at the API, for example https://femnet-api.duckdns.org/api/v1. Changing the API domain means rebuilding both frontends.

  3. 3

    Email

    The backend sends sign-in codes, verification codes and certificate emails. Set RESEND_API_KEY to send through Resend, or set the DJANGO_EMAIL_* values for another SMTP provider. Set DJANGO_DEFAULT_FROM_EMAIL to an address on a domain verified with the provider.

    Tip: If no email settings are set, the backend uses the console backend: emails, including codes, only appear in docker compose logs drf and never reach users.

Related how-tos