Skip to content

Move hardcoded API endpoints and tokens to environment configuration #21

Description

@dipak0000812

Summary

Some backend configuration values appear to be hardcoded directly in source files, including API endpoints and related tokens.

Examples observed:

  • OSDG endpoint configured in backend/app.py
  • Aurora endpoint configured in backend/aurora_api.py

Why this matters

  • Endpoint changes require source code edits and redeployment
  • Harder to manage different environments (local / staging / production)
  • Configuration values are better handled outside the codebase

Suggested direction

  • Move these values to environment variables
  • Add a .env.example / setup template
  • Read values at runtime using configuration helpers

I’d be happy to work on this if it sounds useful.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions