-
Notifications
You must be signed in to change notification settings - Fork 558
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: config file #3042
docs: config file #3042
Conversation
Visit the preview URL for this PR (updated for commit b2f8eaa): https://ignitesrvc-d--pr3042-docs-config-b2a80wds.web.app (expires Wed, 09 Nov 2022 12:47:44 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 60382552e86c69890c026e09478220ea153394a8 |
Not documenting the |
Is there intention to merge these changes? It looks good to do so 👍. |
How about we merge and I'll create an issue for this? The validator home doesn't work for me and we are not sure about the keyring. Might as well publish the updated guide and add some information later on. |
Oh, there is a conflict with one file to be resolved |
Visit the preview URL for this PR (updated for commit 4d6f46c): https://igntservices-docs--pr3042-docs-config-qk7dho6i.web.app (expires Fri, 18 Nov 2022 17:06:11 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 95379efd94dd497aaa37c2d0354e6e2cafca5ec5 |
tysm @fadeev. Will merge once we open that issue you mentioned. |
@aljo242 @jeronimoalbi added a note about |
Extremely useful changes to the docs, awesome! |
Co-authored-by: Thomas Bruyelle <[email protected]>
Co-authored-by: Jerónimo Albi <[email protected]>
* docs: config file * build section * faucet and genesis * validators section * add a note about the home perty in validators * wrap at 80 chars * update config * Update docs/docs/kb/03-config.md Co-authored-by: Thomas Bruyelle <[email protected]> * fix: key pair generated outside of Ignite * Update docs/docs/kb/03-config.md Co-authored-by: Jerónimo Albi <[email protected]> Co-authored-by: Alex Johnson <[email protected]> Co-authored-by: Thomas Bruyelle <[email protected]> Co-authored-by: Jerónimo Albi <[email protected]>
Updating to
v1
and switching to a more descriptive format.The problem I have with existing config documentation is that it's table-based. Even though I authored this, I always had issues with using it to remind myself what's available in the config file.
Instead of tables, I think it should be a mix of YAML examples ready to be copy-pasted and a rich plain-text description of all edge-cases and features.