Config: Refactor and thoroughly document configuration system. - #516
Merged
Merged
Conversation
Member
Author
|
approved on dc by avery |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR unifies our existing FOUR (!!!) config files into one single JSONC file. The switch to JSONC also allowed me to create a thoroughly-documented example config file, which should demystify self-hosting a bit. It's still very annoying because of all the third-party services that need to be set up, but I want to cut most of those out pretty soon.
config.json,env.js,admin.json, and.envall intoconfig.jsonc.example.config.jsoncto guide people setting up an instance through the process.Note
This PR does create a dependency on
jsonc-parser, but it's a very widely used package so I'm not super concerned.