-
Notifications
You must be signed in to change notification settings - Fork 16
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
Clarify variables #476
Clarify variables #476
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
For example, this command initializes the DAL node with the address of a local `octez-node` instance on port 8732 and stores data in the default DAL node directory (`~/.tezos-dal-node`): | ||
|
||
```bash | ||
octez-dal-node config init --endpoint http://127.0.0.1:8732 --attester-profiles="$MY_ADDRESS" | ||
octez-dal-node config init --endpoint http://127.0.0.1:8732 \ | ||
--attester-profiles=tz1QCVQinE8iVj1H2fckqx6oiM85CNJSK9Sx |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Optional: consider using ellipses to avoid having such big and concrete hashes:tz1...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Clarify a few places where we use variables without explaining what they are. We can assume that $HOME and $PATH are defined, but if I use $MY_ACCOUNT that should have been explicitly defined.