Skip to content

Collapse duplicated environment configuration into a single source of truth #233

Description

@phertyameen

Description
The project currently defines two separate sets of environment variables for what is conceptually the same thing: a backend base URL and an API credential. Each set is consumed by a different one of the competing API clients described in Issue 1. This duplication makes local setup confusing (which variable actually matters?) and makes it easy for a deployment to configure one set correctly while leaving the other unset or stale.

Why this matters
Configuration drift like this is a common source of "works on my machine" bugs, since whichever client happens to be imported determines which environment variable is actually read.

Acceptance criteria

  • - There is exactly one environment variable for the backend base URL and one for the API credential, used everywhere.
  • - The .env.example file and any setup documentation are updated to reflect the single set of variables.
  • - No component or module reads from the old, now-removed variable names.
  • Priority: Medium - a hygiene and reliability issue rather than a functional break, but it directly enables a clean version of Issue Consolidate the three competing API client implementations into one #228.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions