Use private url on service role / allow client-server url separation

[ilnytskyi]

Types of changes

• [ ] Bug fix (a non-breaking change which fixes an issue)
• [x] New feature (a non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

Allow separation of public / private url for service role. For situations where supabase and client app hosted on same machine SSR side code can go to supabase via localhost.

SUPABASE_URL=https://my.api.domain/
SUPABASE_LOCAL_URL=http://localhost:8000/

config

  runtimeConfig: {
    supabase: {
      url: process.env.SUPABASE_LOCAL_URL,
    },
    public: {
      supabase: {
        url: process.env.SUPABASE_URL,
      },
    }
  }

maybe public client can also leverage this approach for SSR scenario.

Checklist:

• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [ ] I have added tests to cover my changes (if not applicable, please state why)

[netlify[bot]]

👷 Deploy request for n3-supabase pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	06882b1cefc57903cc26542470e107bb9984d337