fix: dynamic origin handling and updated redirect URLs for environmen…

[OlenaReukova]

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review on my code
• I have made corresponding changes to the documentation (if any were needed)
• My changes generate no new warnings or errors
• I have added tests that prove my fix is effective or that my feature works
• New and previously existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Description

**Relates #385 OR Closes #385 **

Instead of defaulting to http://localhost:3000/, the reset password email link should dynamically generate the correct URL based on the environment.

In the deployed version, the reset password email link should point to the actual domain of the website (e.g., https://your-deployed-domain.com/login/reset-password) instead of the localhost URL.

Code Update:

• Refactored origin detection to handle cases where the value is missing or undefined smoothly.
• Default to http://localhost:3000 for development mode.
• Dynamically set the origin for production using NEXT_PUBLIC_SITE_URL environment variable.

const headersList = await headers();
  let origin: string | null = headersList.get('origin') || null;

  if (!origin) {
    origin =
      process.env.NODE_ENV === 'development'
        ? 'http://localhost:3000'
        : process.env.NEXT_PUBLIC_SITE_URL || null;
  }

Configuration Update:

Updated config.toml to include additional production redirect URLs "https://**cool-creponne-3e1272.netlify.app/**", "https://cool-creponne-3e1272.netlify.app/login/reset-password" to ensure Supabase accepts them, preventing failed password reset flows due to unlisted URLs.

(Supabase Docs)

Files changed

• app/(auth)/login/forgot-password/page.tsx
• config.toml

UI changes

no UI changes

Changes to Documentation

No changes needed.

Tests

All previous tests passed during local development.

[netlify]

👷 Deploy request for cool-creponne-3e1272 pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	88ae7ff

[camelPhonso]

I have a theory that this needs to be sorted with some tweaks in supabase but I no longer have access because I'm not logged in with my old email account. Can someone reach out on discord and give me access on my personal email?

[OlenaReukova]

The console.log("Origin", origin) confirms that the origin value is fetched correctly during my tests, and no errors (e.g., null or unexpected results) occur. This makes me believe that the production deployment should work as expected, provided the server environment properly sets the origin header.