New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Make it easier to keep secrets.env up to date #220

Open

madwort opened this issue Mar 1, 2024 · 0 comments

Assignees

Contributor

madwort commented Mar 1, 2024 •

edited

Loading

on initial setup, we copy in secrets-template.env, but after that we don't do anything
it would be good to give some feedback to the user if there are keys missing due to new keys being added to the template but not to the production file

The text was updated successfully, but these errors were encountered:

madwort self-assigned this

# for free to join this conversation on GitHub. Already have an account? # to comment