From 05309678075a2bc9694edc9b77d82d40757ff0b2 Mon Sep 17 00:00:00 2001 From: mfahampshire Date: Fri, 10 Apr 2026 11:01:20 +0000 Subject: [PATCH] Fix broken redirects & links. (#6660) --- documentation/docs/next.config.js | 40 ++++++++++++++++++- .../docs/pages/operators/changelog.mdx | 2 +- .../docs/pages/operators/faq/general-faq.mdx | 2 +- .../pages/operators/nodes/validator-setup.mdx | 4 +- .../performance-and-testing/gateway-probe.mdx | 2 +- .../ns-api-deployment.mdx | 4 +- 6 files changed, 46 insertions(+), 8 deletions(-) diff --git a/documentation/docs/next.config.js b/documentation/docs/next.config.js index d4be16bd92..45e93e4089 100644 --- a/documentation/docs/next.config.js +++ b/documentation/docs/next.config.js @@ -1120,7 +1120,7 @@ const config = { // --- Rust SDK: deleted mixnet example subpages --- { - source: "/docs/developers/rust/mixnet/examples/:path*", + source: "/docs/developers/rust/mixnet/examples/:path+", destination: "/docs/developers/rust/mixnet/examples", permanent: true, basePath: false, @@ -1178,6 +1178,44 @@ const config = { basePath: false, }, + // --- Directory index redirects (directories without index pages) --- + { + source: "/docs/developers/typescript/bundling", + destination: "/docs/developers/typescript/bundling/bundling", + permanent: false, + basePath: false, + }, + { + source: "/docs/developers/typescript/examples", + destination: "/docs/developers/typescript/examples/mix-fetch", + permanent: false, + basePath: false, + }, + { + source: "/docs/developers/typescript/playground", + destination: "/docs/developers/typescript/playground/mixfetch", + permanent: false, + basePath: false, + }, + { + source: "/docs/developers/typescript/api", + destination: "/docs/developers/typescript/api/sdk", + permanent: false, + basePath: false, + }, + { + source: "/docs/developers/clients", + destination: "/docs/developers/clients/socks5", + permanent: false, + basePath: false, + }, + { + source: "/developers/rust/importing", + destination: "/docs/developers/rust/importing", + permanent: true, + basePath: false, + }, + // --- APIs: flattened structure --- { source: "/docs/apis/ns-api/mainnet", diff --git a/documentation/docs/pages/operators/changelog.mdx b/documentation/docs/pages/operators/changelog.mdx index a8c7d178f1..24a04cb6d1 100644 --- a/documentation/docs/pages/operators/changelog.mdx +++ b/documentation/docs/pages/operators/changelog.mdx @@ -5419,7 +5419,7 @@ bind_address = '0.0.0.0:9000' ### Tooling -* [Nym Harbourmaster](https://https://harbourmaster.nymtech.net/) has now several new functionalities: +* [Nym Harbourmaster](https://harbourmaster.nymtech.net/) has now several new functionalities: - Tab for Mixnodes - Tab with Charts - New columns with: *Moniker (node description)*, *DP delegatee*, *Accepted T&Cs* - also part of a new category đŸŧ😀 diff --git a/documentation/docs/pages/operators/faq/general-faq.mdx b/documentation/docs/pages/operators/faq/general-faq.mdx index 57271c1c17..ede465867d 100644 --- a/documentation/docs/pages/operators/faq/general-faq.mdx +++ b/documentation/docs/pages/operators/faq/general-faq.mdx @@ -10,7 +10,7 @@ lastUpdated: "2026-02-01" ## Nym Network -To see different stats about Nym Network live, we recommend you to visit [Nym Harbourmaster](https://harbourmaster.nymtech.net) and dynamic [Nym token page](https://nym.com/about/token). +To see different stats about Nym Network live, we recommend you to visit [Nym Harbourmaster](https://harbourmaster.nymtech.net) and dynamic [Nym token page](https://nym.com/token). ### Is there an explorer for Nym Mixnet? diff --git a/documentation/docs/pages/operators/nodes/validator-setup.mdx b/documentation/docs/pages/operators/nodes/validator-setup.mdx index 8b7c3a8ac3..5de5779bba 100644 --- a/documentation/docs/pages/operators/nodes/validator-setup.mdx +++ b/documentation/docs/pages/operators/nodes/validator-setup.mdx @@ -11,7 +11,7 @@ import { AccordionTemplate } from 'components/accordion-template.tsx'; > - the [Nym platform](https://github.com/nymtech/nym), written in Rust. This contains all of our code except for the validators. > - the [Nym validators](https://github.com/nymtech/nyxd), written in Go & maintained as fork of [wasmd](https://github.com/CosmWasm/wasmd) -The validator is a Go application which implements it's functionalities using [Cosmos SDK](https://v1.cosmos.network/sdk). The underlying state-replication engine is powered by [CometBFT](https://cometbft.com/), where the consensus mechanism is based on the [Tendermint Consensus Algorithm](https://arxiv.org/abs/1807.04938). Finally, a [CosmWasm](https://cosmwasm.com) smart contract module controls crucial mixnet functionalities like decentralised directory service, node bonding, and delegated mixnet staking. +The validator is a Go application which implements it's functionalities using [Cosmos SDK](https://docs.cosmos.network). The underlying state-replication engine is powered by [CometBFT](https://cometbft.com/), where the consensus mechanism is based on the [Tendermint Consensus Algorithm](https://arxiv.org/abs/1807.04938). Finally, a [CosmWasm](https://cosmwasm.com) smart contract module controls crucial mixnet functionalities like decentralised directory service, node bonding, and delegated mixnet staking. At present, our mainnet operates with a select group of reputed validators. We are not accepting new validators at this time. Any updates or changes to this policy will be promptly announced. @@ -307,7 +307,7 @@ nyxd keys add nyxd-admin ``` -Cosmos SDK offers multiple backends for securing your keys. Please refer to the Cosmos SDK [docs on available keyring backends](https://docs.cosmos.network/main/user/run-node/keyring#available-backends-for-the-keyring) to learn more +Cosmos SDK offers multiple backends for securing your keys. Please refer to the Cosmos SDK [docs on available keyring backends](https://docs.cosmos.network/sdk/v0.47/user/run-node/keyring#available-backends-for-the-keyring) to learn more While using the default settings, this will add keys for your account to your system's keychain and log your name, address, public key, and mnemonic. As the instructions say, remember to **write down your mnemonic**. diff --git a/documentation/docs/pages/operators/performance-and-testing/gateway-probe.mdx b/documentation/docs/pages/operators/performance-and-testing/gateway-probe.mdx index e7e717665f..7e2e41da44 100644 --- a/documentation/docs/pages/operators/performance-and-testing/gateway-probe.mdx +++ b/documentation/docs/pages/operators/performance-and-testing/gateway-probe.mdx @@ -7,7 +7,7 @@ import { VarInfo } from 'components/variable-info.tsx'; Nym Node operators running Gateway functionality are already familiar with the monitoring tool [Harbourmaster.nymtech.net](https://harbourmaster.nymtech.net). Under the hood of Nym Harbourmaster runs iterations of `nym-gateway-probe` doing various checks and displaying the results on the interface. Operators don't have to rely on the probe ran by Nym and wait for the data to refresh. With `nym-gateway-probe` everyone can check any Gateway's networking status from their own computer at any time. In one command the client queries data from: -- [`nym-api`](https://validator.nymtech.net/api/v1/gateways) +- [`nym-api`](https://validator.nymtech.net/api/v1/nym-nodes/described) - [`explorer-api`](https://mainnet-node-status-api.nymtech.cc/swagger/#/Gateways) - [`harbour-master`](https://harbourmaster.nymtech.net/) diff --git a/documentation/docs/pages/operators/performance-and-testing/ns-api-deployment.mdx b/documentation/docs/pages/operators/performance-and-testing/ns-api-deployment.mdx index 1444892e29..91e9e71258 100644 --- a/documentation/docs/pages/operators/performance-and-testing/ns-api-deployment.mdx +++ b/documentation/docs/pages/operators/performance-and-testing/ns-api-deployment.mdx @@ -171,7 +171,7 @@ If you have already run the API before, make sure to add the following to your s If you want to enable Gateway node probes and have the NS API store that data, you need to periodically run the `nym-node-status-agent`, authenticated with your `nym-node-status-api` instance. Authentication is to make sure that only the `-agent` you are operating (or others you trust) are submitting data to your API instance. #### Compile Gateway Probe -The `nym-node-status-agent` is a thin wrapper around the Gateway Probe binary which currently is in the NymVPN repo. `git checkout` to the most recent [release](https://github.com/nymtech/nym-vpn-client/releases), and compile the probe by following the [readme instructions](https://github.com/nymtech/nym-vpn-client/tree/develop/nym-vpn-core/crates/nym-gateway-probe). You will point the `-agent` at this binary when doing Probe testruns. +The `nym-node-status-agent` is a thin wrapper around the Gateway Probe binary which lives in the [Nym monorepo](https://github.com/nymtech/nym/tree/develop/nym-gateway-probe). Compile the probe by following the readme instructions there. You will point the `-agent` at this binary when doing Probe testruns. #### Generate Keypair ```shell @@ -316,7 +316,7 @@ function swarm() { local workers=$1 for ((i = 1; i <= workers; i++)); do - ${monorepo_root}/target/release/nym-node-status-agent run-probe --probe-path ~//nym-vpn-client/nym-vpn-core/target/debug/nym-gateway-probe & + ${monorepo_root}/target/release/nym-node-status-agent run-probe --probe-path ${monorepo_root}/target/release/nym-gateway-probe & done wait