[Backend] — Missing CORS Configuration for Production

[Olowodarey]

Description:
CORS is not properly configured in main.ts. The application needs proper CORS settings for production with specific allowed origins.

Technical Requirements:

1. Configure CORS with environment-specific origins
2. Set proper allowed methods and headers
3. Configure credentials handling
4. Add preflight caching
5. Document CORS policy

Acceptance Criteria:

• CORS configured per environment
• Allowed origins from env variables
• Credentials handling correct
• Preflight caching enabled
• Documentation complete

[Amizeey]

@Amizeey has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

I’m interested in working on this issue because it sits at the intersection of system reliability and developer experience—areas I care about deeply. Issues around package management, upgrades, and environment consistency can quietly slow teams down or introduce hard-to-debug problems. Fixing them not only improves stability but also makes the workflow smoother for everyone who depends on the tool.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Amizeey to this issue.

[Mkalbani]

@Mkalbani has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Hi maintainers, can I work on this. I've worked on a similar work. Thank you.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Mkalbani to this issue.

[Ugasutun]

@Ugasutun has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Hi, I’d like to work on this issue.

I understand the goal is to properly configure CORS in main.ts for production by defining environment-specific allowed origins, setting appropriate methods and headers, handling credentials correctly, and enabling preflight caching. I can implement a clean, configurable setup using environment variables and ensure it’s secure and aligned with best practices.

I’ll also document the CORS policy clearly and verify behavior across environments to ensure everything works as expected.

I’m comfortable working with backend configuration and security, and I’ll make sure the implementation is robust, flexible, and easy to maintain.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ugasutun to this issue.

[Emmo00]

@Emmo00 has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

i would love to work on this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Emmo00 to this issue.

[drips-wave]

Congratulations, @Ugasutun! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @Ugasutun: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊