Stop committing JSON configuration to repo #20

Closed
opened 2025-10-10 15:05:00 -04:00 by sirdog3355 · 0 comments
sirdog3355 commented 2025-10-10 15:05:00 -04:00 (Migrated from github.com)

Rightfully pointed out by SierraKomodo is that the benefits of using json for configurable values is defeated if the json is committed to the repository with real values. At that point it doesn't make sense to parse the json: I should just use global variables.

I would like to keep things configurable, so I need to decouple the configuration files from the repo.

Additionally, I should try to condense some of the json files into one, instead of having so many.

Rightfully pointed out by SierraKomodo is that the benefits of using json for configurable values is defeated if the json is committed to the repository with real values. At that point it doesn't make sense to parse the json: I should just use global variables. I would like to keep things configurable, so I need to decouple the configuration files from the repo. Additionally, I should try to condense some of the json files into one, instead of having so many.
Sign in to join this conversation.
No description provided.