Conversation
|
| - **PostgreSQL Database** supporting wallet proxy and CCDScan | ||
| - **pgAdmin** on port 8432 for database management | ||
| - **Web Server** on port 7020 for PLT token metadata | ||
| - **ZK Verifier Backend** on port 7017 |
There was a problem hiding this comment.
Are these all mandatory? What if someone with limited storage wants to install only node and bare minimum infra?
| .. code-block:: console | ||
|
|
||
| cd concordium-misc-tools/genesis-creator | ||
| cargo run -- generate --config ./examples/genesis9.toml |
There was a problem hiding this comment.
What if I have installed the genesis creator? I have it in my system cause run local chain with Docker image guide asked me to. now I have it but cant use it to generate. The feeling is like I have to clone the code and proceed, if thats the case why we have it executable. I feel like we just need this generate command with a toml file. and you are already sharing it above. Can we update this section with something like either clone repo and get the toml file from there or create one and feed the generate with that configuration? somthing copy and paste? or maybe we can just mention, executable genesis-creator is not enough on its own
bogacyigitbasi
left a comment
bogacyigitbasi
left a comment
There was a problem hiding this comment.
Overall document is well constructed. In general its looking good but I find it difficult to navigate between different pages. Also the page showing the node build was also not reflecting how to install dependencies, if we want people to follow the instructions here one by one, we may either internalize that section or at least add how to install those dependencies for each OS type (might be an overkill - TBD later)
| .. code-block:: console | ||
|
|
||
| cd concordium-misc-tools/genesis-creator | ||
| cargo run -- generate --config ./examples/genesis9.toml |
There was a problem hiding this comment.
It requires concordium-rust-sdk as a dependency, we mention that user should install and manage the rust dependencies from here but that page doesnt explicitly mention the rust-sdk.
There was a problem hiding this comment.
maybe clone it with --recurse-submodules
|
|
||
| .. code-block:: console | ||
|
|
||
| stack build |
There was a problem hiding this comment.
perhaps cd in the node first?
| Step 4: Build and run the node | ||
| ============================== | ||
|
|
||
| Here we describe how to build and run the `node <https://github.com/Concordium/concordium-node/tree/main/concordium-node#building-the-node>`_ and setting up a local network. |
There was a problem hiding this comment.
I followed the new page for node build and run. just wanted to raise this discussion point, I dont feel like asking people to visit many different pages to complete a process we explain here. it is several times back and forth. Cant we embed some from there to here in this section?
There was a problem hiding this comment.
Also another problem is, we ask people to install the dependencies but dont tell how? This is really demanding too much energy.
2 participants
Purpose
Replace the outdated "Run a local chain" article with a restructured version that reflects the two available approaches: Docker images via concordium-local-stack (recommended) and building from source (advanced).
Changes
index.rstintro article explaining use cases and linking to both approachesrun-local-chain-docker.rstpointing to theconcordium-local-stackrepo (single source of truth)run-local-chain-source.rstwith the advanced source-build guideChecklist
hard-to-understand areas.
CLA acceptance
By submitting the contribution I accept the terms and conditions of the
Contributor License Agreement v1.0
link: https://developers.concordium.com/CLAs/Contributor-License-Agreement-v1.0.pdf
I accept the above linked CLA.