Skip to content
This repository has been archived by the owner on Jan 25, 2022. It is now read-only.

Add in a config.secrets.* file #2

Open
mikeschinkel opened this issue Nov 6, 2018 · 0 comments
Open

Add in a config.secrets.* file #2

mikeschinkel opened this issue Nov 6, 2018 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@mikeschinkel
Copy link
Member

There is likely to be a need for a file with a single name that can be ignored by .gitignore that can contain passwords or API keys or whatever else that the site owner/developer feels should never be committed to version control.

The open question is, should secrets be loaded before environment overrides or should secrets override the environment config?

@mikeschinkel mikeschinkel added the enhancement New feature or request label Nov 6, 2018
@mikeschinkel mikeschinkel self-assigned this Nov 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant