fix: Adjusted the existing Supabase service image to allow redirect links in emails to follow the SITE_URL…

[justserdar]

… custimisation via SITE_URL env. Fix provided by Fiend & Darren, solution fix reproduced and tested by hum+.

Issues

Redirect links in Supabase e-mail is based on the SERVICE_FQDN_SUPABASEKONG, this can be wrong at times, this modification takes in the SITE_URL for the e-mail links.

Changes & Fix

• supabase-db:
  ports:
  - "5432:5432" # Addition
• Changed FQDN_SUPABASE_URL=${FQDN_SUPABASE_URL} to GOTRUE_SITE_URL=${SITE_URL}

[djsisson]

@justserdar please remove mapping ports to host, this should not be the default, it will break if it is already in use.

Generally mapping ports to the host should generally not be used, there are much more secure options to do this.

[justserdar]

@djsisson I understood this fixes parts of supabase that doesn't work. I can remove the ports but then what would be the actual fix?

[djsisson]

@justserdar the fix should be to make the publicly available option work for supabase, but if a user wants to expose their db to the host, then they can manually alter the compose file themselves.
As i said it is terrible security practice to even do this.

[Geczy]

@justserdar the fix should be to make the publicly available option work for supabase, but if a user wants to expose their db to the host, then they can manually alter the compose file themselves. As i said it is terrible security practice to even do this.

what are the more secure methods to do this?

[justserdar]

@djsisson I got this feedback from a community member called Fiend on discord. He told me you offered this solution for his supabase setup in a support thread. However if it's not advised (exposing ports), any advice going forward?

I'll change the PR after I tested a new solution.