Skip to content

Implement environment specific controls #114

Closed
campb303 opened this issue Nov 4, 2020 · 1 comment
Closed

Implement environment specific controls #114

campb303 opened this issue Nov 4, 2020 · 1 comment
Assignees
Labels
feature-request Request for functionality that has not already been implemented

Comments

@campb303
Copy link
Collaborator

campb303 commented Nov 4, 2020

Several pieces of the project need some settings changed to move from development to production. Both the Python codebase through gunicorn and Flask and the React frontend through node's process.env package support reading logic from .env files.

To avoid needless issues when changing environments and to allow environment secrets to be stores outside of version control, environment file reading support should be integrated into the project.

This can start with webserver configuration as described in this article.

@campb303 campb303 added the feature-request Request for functionality that has not already been implemented label Nov 4, 2020
@campb303 campb303 added this to the v1 milestone Nov 4, 2020
@campb303 campb303 self-assigned this Nov 4, 2020
@campb303
Copy link
Collaborator Author

This was implemented in #15 using Python's dotenv library. Closing.

Sign in to join this conversation on GitHub.
Labels
feature-request Request for functionality that has not already been implemented
Projects
None yet
Development

No branches or pull requests

1 participant