Supabase config.toml: run local dev with Resend SMTP while keeping config synced with remote
I’m working with Supabase and its config.toml file.
This file is generated when running supabase init, but it also reflects the remote project configuration — I can see this because when I run supabase link I get a diff between the local config.toml and the remote config.
This led me to think the intended workflow is:
1. Modify config.toml locally.
2. Test it locally.
3. Push it to remote using supabase config push.
However, I’m having an issue with authentication.
When running Supabase locally:
• If I configure the auth.smtp section the same way it’s configured on the remote project (I’m using Resend as the SMTP provider) and restart Supabase, calling supabase.auth.signUpWithOtp returns a 500 error.
• If instead I configure Inbucket (and set it in auth.smtp in config.toml), it works locally — but then I can’t push config to remote, because it would overwrite the remote SMTP settings with Inbucket.
What I want:
• Have the same configuration locally and remotely.
• Use the actual SMTP provider (Resend) even in local development, so I can test the real authentication flow before deploying.
1 Reply
What does the logs say about the 500 error? first you need to find the cause of that and then it will be easier to debug. Also not sure why you would use up your Resend credits to test locally, when there is inbucket/mailpit.