Document all possible config keys
See original GitHub issueDescribe the problem you’d like to have solved
I stumbled on the AUTH0_EXCLUDED_CONNECTIONS configuration property and it really helped me use this library better. But I really found it by accident. I’d like all config options to be documented.
Describe the ideal solution
Document all config options in the README (or a linked MD file)
Issue Analytics
- State:
- Created 3 years ago
- Reactions:11
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Reference - Web.config application keys
AppSettings keys are stored in the /configuration/appSettings section. The following setting categories are available:.
Read more >git-config Documentation - Git
A list of all available configuration variables can be obtained using the git help --config command. OPTIONS. --replace-all. Default behavior is to replace...
Read more >Configuration basics - AWS Command Line Interface
This section explains how to quickly configure basic settings using the config and credentials files that the AWS Command Line Interface (AWS CLI)...
Read more >Example: Configure policy configuration keys
Run setup using the --optionsFile argument. Customize all other options as appropriate for your needs. $ bin/setup demo \ --adminUsername admin ...
Read more >Understand Azure App Configuration key-value store
It's a common practice to organize keys into a hierarchical namespace by using a character delimiter, such as / or : . Use...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

At the bare minimum, create a public JSON schema. This is good for the project as well since it can be used for validation. Considering the absolute neglect of the issues in the project, it’s hard to see it happening anytime soon, though.
This has been addressed with the addition of documentation to this project, including a Configuring the Deploy CLI page. Please check it out and create PRs with any suggested alterations. Thanks for everyone’s patience!