feat(docs): new node operator documentation #3
Conversation
Create README.md for staging network setup, detailing configuration files and public keys. Introduce network-nodes.csv with initial validator node information.
Introduced a comprehensive guide to configuring Kwil node operators, covering database, performance, network, and peer configurations. Updated README with step-by-step instructions for setting up a TSN node, deploying it, and optionally becoming a validator.
outerlook
changed the title
Renamed Kwil Node Operator to TSN Node and updated configuration instructions accordingly. Added details on specifying the genesis file and other network configurations.
Update the staging network nodes CSV to include a new column for node CometBFT ID.
Replaced `--config` with `--root-dir` in the deployment command.
|
@outerlook do we need to specify anything related to the download of prerequisites? When can we review this PR? |
|
I would like to merge this PR if there is nothing else we can add at this stage. And if something will be reported, we can add it later. |
|
Alright! Im in transit now, I'd just do a final check while testing. However, we can create an issue later if I find any |
|
Oh wait, there are conflicts. I'll resolve them soon |
# Conflicts: # configs/network/staging/network-nodes.csv
There was a problem hiding this comment.
Hey @outerlook,
Overall, I think this looks pretty good. In my opinion, the main area for improvement is making the instructions clearer about the correct P2P address a new node operator should use when setting up their peer nodes.
For some reason, I could not sync a node using the domain names; however, I could sync a node using the current tsn nodes' IP addresses.
Once we resolve the domain name versus IP address question, we can proceed with setting up our node in Kwil's cloud account and adding that node as a validator.
|
@KwilLuke |
Moved custom PostgreSQL setup instructions and peer configuration to more appropriate sections for better readability. Updated example commands to include persistent peers configuration, ensuring consistency and clarity in the documentation.
Expanded the setup section to include specific commands for generating initial configuration using `kwil-admin`. Improved clarity by defining the Truflation Stream Network and updating labels accordingly.
|
Thank you for the comments @KwilLuke, I highly appreciate them! Just some of these conversations are pending now. about the domain issue: - staging.node-2.tsn.truflation.com
+ staging.node-2.tsn.test.truflation.comnow they are fixed. related to trufnetwork/node#446 |
Description
Solved Friction Points
Related Problem
How Has This Been Tested?