docs: add networks and environments guide - #1179
Merged
Merged
Conversation
Add a modular-docs assembly at /guides/networks-and-environments covering the four networks (undeployed, preview, preprod, mainnet): what each is for, a selection reference, a tabbed environment reference with endpoints and address prefixes, a connect procedure with an executed Vitest verification, funding and cost, and a mainnet preparation procedure with a readiness checklist. Reconcile docs/nodes/node-endpoints.mdx with the mainnet endpoints (it said only two test networks exist) and add the new route to pipelines-urls.json.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Summary
Errors per inputErrors in docs/guides/acquire-tokens.mdx
Errors in docs/guides/configure-providers.mdx
Errors in docs/guides/networks-and-environments.mdx
Errors in docs/guides/security-best-practices.mdx
Errors in docs/nodes/node-endpoints.mdx
Errors in docs/tutorials/bboard/bboard-cli-implementation.mdx
Errors in docs/tutorials/zk-loan/attestation-api.mdx
Errors in docs/tutorials/zk-loan/cli.mdx
Errors in sdks/official/midnight-js.mdx
Redirects per inputRedirects in docs/guides/acquire-tokens.mdx
Redirects in docs/guides/configure-providers.mdxRedirects in docs/guides/networks-and-environments.mdxRedirects in docs/guides/security-best-practices.mdxRedirects in docs/tutorials/bboard/bboard-cli-implementation.mdxRedirects in docs/tutorials/zk-loan/attestation-api.mdxRedirects in docs/tutorials/zk-loan/cli.mdxRedirects in sdks/official/midnight-js.mdx |
Rewrite the lead paragraphs of the networks and security guides so the concept/procedure/reference module taxonomy stays authoring vocabulary; readers see plain sections.
…ding Scope the setNetworkId sentence to what the SDK source actually does (only the contracts package reads the network ID at runtime, for address normalization and transaction building); apply the same fix to the configure-providers guide it was inherited from. Tighten the mainnet funding step to say Cardano reward address, matching RegistrationData in the cnight-observation pallet.
Fold midnight-local-network.mdx into the assembly as a Running a local network procedure (verified against a live local stack: node 1.0.0, indexer 4.3.3, proof server 8.1.0) and a troubleshooting reference that adds the indexer first-start race observed during verification. Drop the stale pinned-version tables in favor of standalone.yml, correct the funding menu text to match the tool source, repoint every inbound link, and redirect both old routes without creating chains.
Contributor
Author
|
Update: the Midnight local network guide is now merged into this assembly as the Running a local network procedure and Local network troubleshooting reference (see the updated PR description). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this adds
A new guide, Networks and environments (
/guides/networks-and-environments), built as a modular-docs assembly (concept, procedure, and reference modules in one page, same structure as/guides/security-best-practices). It gives the four networks (undeployed,preview,preprod,mainnet) a single home:testnet-02name no longer resolves.setNetworkIdplus endpoint wiring, thecreate-mn-appnetwork scripts, ending in a runnable Vitest verification.Also included, to close the mainnet contradiction the guide would otherwise inherit:
docs/nodes/node-endpoints.mdxno longer says only "two active test networks" exist; it now names Preview, Preprod, and Mainnet, gains a Mainnet RPC tab, and links to the new reference.Update: local network guide merged into the assembly
Per review direction,
docs/guides/midnight-local-network.mdxis now part of this guide rather than a separate page, completing the single user journey (understand > choose > set up locally > connect > fund > mainnet):midnight-node:1.0.0,indexer-standalone:4.3.3,proof-server:8.1.0); its Verification block is a real executed Vitest run againstlocalhost:9944/8088/6300.block number 1 not found(startup race) and latches on afterdocker start midnight-indexer.standalone.yml(they had drifted: the page said node 0.22.3 / indexer 4.0.1 / proof server 8.0.3; the tool pins 1.0.0 / 4.3.3 / 8.1.0), and its funding-menu text was corrected against the tool source ([3] Display wallets).vercel.jsonredirects/midnight-local-networkand/guides/midnight-local-networkdirectly to/guides/networks-and-environments(no chains).