Skip to content

Suggestion: Consistency on API KEY Environment variable #17

Description

@gwpl

Problem:
API_KEY environment variable may conflict with other "API_KEYs" environment variables, for projects using multiple APIs.

For consistency across opensource snippets of code made by community, could you in your opensource repositories and documentation propose some standard?

E.g. SPEECHMATICS_API_KEY or sth like that environment variable to :

  • reduce risk of conflict with other APIs , snippets, code examples etc variables
  • make maintanance (of config files .ENV etc or debugging and seeing this environment variable and immediately knowing from where it comes from and if it's properly used in production) easier?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    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