Every configuration through environment variables? #17

Closed
opened 2022-09-15 16:33:40 +00:00 by emacsen · 2 comments
emacsen commented 2022-09-15 16:33:40 +00:00 (Migrated from gitlab.com)

Should configuration be replaced with environment variables controlling everything?

ie
CHECK_HTTP_SIGNATURE_VERIFICATION=1

CHECK_HTTP_SIGNATURE_VERIFICATION_WEIGHT=10
...

or is this too much?

Should configuration be replaced with environment variables controlling everything? ie `CHECK_HTTP_SIGNATURE_VERIFICATION=1` `CHECK_HTTP_SIGNATURE_VERIFICATION_WEIGHT=10` ... or is this too much?
emacsen commented 2022-09-15 16:33:48 +00:00 (Migrated from gitlab.com)

changed the description

changed the description
emacsen commented 2022-10-18 18:55:19 +00:00 (Migrated from gitlab.com)

This now basically exists though there was no explicitly changeover.

This now basically exists though there was no explicitly changeover.
emacsen (Migrated from gitlab.com) closed this issue 2022-10-18 18:55:19 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
babka/activitycolander#17
No description provided.