Skip to content

Audit environment variables #177

@stevenbuccini

Description

@stevenbuccini

This is a:

  • bug
  • enhancement
  • feature-discussion

Enhancement

Description

Currently, we have a several environment variables in a .env file in the project. These variables mainly drive our database configuration. However, Heroku will inject its own "config vars" into the environment. By having these in two separate places (specifically the URLs for pulling the data from the Board of Elections), we increase the probability that folks will update the values in one place and not the other.

Implementation

Several options off the top of my head:

  • Use dotenv everywhere
  • Move values into src/config.js
  • Hard-code values into the appropriate places in the database configuration.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions