Skip to content
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

doc multi-file constants format #261

Conversation

alexandratran
Copy link
Contributor

Pull Request Description

Add documentation for multi-file config file format.

Fixed Issue(s)

fixes #259

@alexandratran alexandratran requested a review from mbaxter March 19, 2021 04:52
@CLAassistant
Copy link

CLAassistant commented Mar 19, 2021

CLA assistant check
All committers have signed the CLA.

Copy link
Member

@NicolasMassart NicolasMassart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approval to come once url points to master

docs/Reference/CLI/CLI-Syntax.md Outdated Show resolved Hide resolved
@@ -1809,3 +1813,4 @@ or clear your weak subjectivity settings.
[weak subjectivity period]: ../../Concepts/Weak-Subjectivity.md
[BeaconScan chain explorer]: https://beaconscan.com/ws_checkpoint
[load new validators without restarting Teku]: ../../HowTo/Load-Validators-No-Restart.md
[MainNet resources directory]: https://github.com/ConsenSys/teku/tree/master/util/src/main/resources/tech/pegasys/teku/util/config/mainnet
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure it's a good idea to link to these resources here - they're slated to move in the near future and we could easily forget to update docs

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have a nightly link check, so no risks we forget to update if they are broken.
But then if you think it will move soon we can either point to a better resource, if there's a stabler one, or include the examples directly in the doc, but then we will need you to tell us as soon as we need to update them. No solutions is perfect.
I don't think we should point to the root of the Teku repos, even if it will hopefully not change, as it will be too hard for users to find the files from there.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The canonical place to look for config definitions is the eth2.0 spec repo here. Various testnet configs can be found here.

I'm not sure how helpful it is to include links - I think just explaining that you can use a single file, or split them up in a directory with subfiles named phase0 or altair is really all the detail I was trying to convey.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the idea to have a link to example when we talk about config files. It helps having a quick understanding of the content and capabilities. Your links are nice imo. @ConsenSys/protocol-pliny what do you think?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pliny recommends keeping the link.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use one of @mbaxter 's link then, they are closer to the source of truth and should not move too much.

Predefined network configuration.
Accepts a predefined network name, or file path or URL to a YAML configuration file or directory.
Directories must hold a `phase0.yaml` file and can hold an optional `altair.yaml` file.
See the [MainNet resources directory] for an example.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd suggest just cutting this line. Can't think of a resource to link to that is guaranteed to be stable and correct.

@NicolasMassart NicolasMassart requested a review from a team March 22, 2021 17:53
@alexandratran alexandratran merged commit 582823f into Consensys:master Mar 25, 2021
@alexandratran alexandratran deleted the 259_doc_multi_file_constants_format branch April 6, 2021 05:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Doc multi-file format for constants
4 participants