-
Notifications
You must be signed in to change notification settings - Fork 15
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
Recast this as a node/baker/DAL tutorial #495
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
a889e49
to
52f1aec
Compare
Maybe we should also run an accuser then, to be complete? |
Also, we should just mention that it could be recommended to also run a signer, just referring to the doc for that (e.g. https://tezos.gitlab.io/user/key-management.html#signer). |
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.
I like the idea to also include the node in the picture, so we can go ahead and complete the scene
Co-authored-by: NicNomadic <148877430+NicNomadic@users.noreply.github.com>
|
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.
|
||
1. To run a baking daemon that connects to the DAL, start it as usual and pass the URL to your DAL node to it with the `--dal-node` argument: | ||
|
||
```bash | ||
octez-baker-PsParisC run with local node "$HOME/.tezos-node" my_baker --liquidity-baking-toggle-vote pass --adaptive-issuance-vote on --dal-node http://127.0.0.1:10732 | ||
``` | ||
|
||
Note that the command for the baker depends on the protocol version. | ||
This example uses the ParisC protocol, so the command starts with `octez-baker-PsParisC`. |
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.
Is there a way to use a variable here for the protocol suffix that gets instantiated by Docusaurus at build time, to avoid changing the tutorial at a protocol shift?
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.
There are a few ways to do this -- I'll add a note as part of our discussion about a list of to-dos for each protocol upgrade.
Co-authored-by: NicNomadic <148877430+NicNomadic@users.noreply.github.com>
Co-authored-by: NicNomadic <148877430+NicNomadic@users.noreply.github.com>
This tutorial is going to be the primary place we point people to for instructions about running a node:
tezos
user to run the services