Everything pertaining to sending and receiving email, except for manual emails (like sending and receiving from [email protected], [email protected], which is explained in ‣).
Email assets, including fonts, are hosted on the static bucket.
Automated platform mail (auth, chat, feature, newsletter) sends from [email protected] via Resend. The Supabase Edge Function secret is GENERAL_EMAIL_ADDRESS.
.org. BIMI and similar programs are currently too expensive. See this Resend article for more.There are a few types of emails:
They are each explained in detail below.
All of these email types are sent by Resend, designed and rendered in React Email, and available on the repo under supabase/functions.
These functions have not been designed for local use, since they all rely on real user data and user triggers. An .env.example and .env.local for RESEND_API_KEY and SEND_EMAIL_HOOK_SECRET can be added, though, if that becomes a desired feature. Those env variables need to also be set as secrets on Supabase’s edge functions dashboard, under the Secrets page.
Any changes to edge functions must be deployed like so:
supabase functions deploy function-name --no-verify-jwt
You’ll need Docker running locally to make this work. Apparently that won’t be necessary for much longer. Don’t edit functions directly on the Supabase dashboard as it has no version control.
These are platform-related emails: ones that are to do with the running of Peels. There are two types of core emails: