-
Notifications
You must be signed in to change notification settings - Fork 356
fix: mount notification email templates #4755
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
fix: mount notification email templates #4755
Conversation
Pull Request Test Coverage Report for Build 21510440398Details
💛 - Coveralls |
|
@sweatybridge sorry for the tag, would you mind taking a look at this as well? A couple of users are stuck on it. Also, kind of related: supabase/supabase#41860 (comment), its about how paths are parsed where auth templates need paths to start with Lines 697 to 710 in 3fe548f
|
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
When running
supabase start, only auth email templates were mounted in kong and configured in auth service.Notification email templates were ignored.
What is the new behavior?
Notification email templates are now mounted in Kong, and the required env vars for notification templates are configured in the auth service.
Additional context
Note for maintainers:Before testing, please do one of the following:- downgrade togotrue:v2.183.0, or- restart the auth container after runningsupabase startSee #4668 for more details.