Files
mfahampshire cf3fd00350 Max/crates io prep v2 (#6270)
* - standardise versions for all nym-sdk workspace dependencies
- prepend sqlx-pool-guard with 'nym-'

* Test remove nym-api from deps

* Add oneliner to client_pool doc comments

* Add note to commented out docs.rs link in sdk

* remove nym-api from script

* add publishing file

* bring non-binary / contract / tools into workspace version

* added more info to publishing.md

* make deps workspace version

* remove uploaded sphinx-types crate from script

* remove erroueously included ignore-defaults

* add zeroise to feature

* chore: Release

* add topology to batch

* more cargo versioning

* more cargo versioning - wasm utils

* more cargo versioning - wasm utils

* Add publish=false to manifest for cargo workspaces / crates.io
publishing exclusion

* remove script now switched to manifest based exclusion

* rename import based on rename of contracts-common dep

* Making workspace versions for publication + removing unnecessary crates
from publication

* Remove OOD info from publishing sdk guide

* rename contract imports + remove package

* temp commit: continuing with removal of path from cargo manifest and
replacing with workspace version import for publication

* continuing with cargo.toml updates

* dryrun only erroring on known version problem crates

* remove old published-crates file

* Minor comment change

* remove default features warning

* Additional info on workspace dep comment re publish list

* Add missing description to cargo.toml

* Fix missing feature flags

* Add missing descriptions

* Fix remaining path import

* Add workspace repo / homepage / documentation links to cargo.toml files

* remove workspace version from excluded crate

* Remove todo descriptions

* Minor comment change

* add homepage etc

* move from bls git import to nym_bls_fork crate

* Modify rest of imports from path to workspace import, excluding binaries

* add directory/homepage info

* fix cargo fmt

* add notes to gitignore

* better solution to contracts/ experiment

* wasm -> nym_wasm crate renaming

* fix fatfinger

* add metadata to ecash cargo.toml

* stub publishing guide

* fix misrevolved netlink- version

* Fixes and block publication of rebase re: LP

* first pass @ workflows
2026-01-19 13:19:45 +00:00
..
2026-01-19 13:19:45 +00:00
2024-12-11 16:30:17 +00:00

Nym Docs v2

This is v2 of the nym docs, condensed from various mdbooks projects that we had previously.

These docs are hosted at nymtech.net/docs.

Doc projects

docs/pages/ contains several subdirs, each hosting a subsection of the docs:

  • network contains key concepts, cryptosystems, architecture.
  • developers contains key concepts for developers, required architecture, and Rust/Typescript SDK docs.
  • operators contains node setup and maintenance guides.

Local development

Dependencies

Our prebuild script relies on the following:

Otherwise make sure to have node installed.

Binary dependencies

If you don't want/need build our binaries in Rust localy you can download them from latest Release page on github into target/release in root of this repo. {'nym-node', 'nym-api', 'nymvisor'}

Make them executable

chmod +x target/release/*

Serve Local (Hot Reload)

pnpm i
pnpm run dev

Open http://localhost:3000.

Build

pnpm run build

The static output will be in ./out;

Contribution

  • If you wish to add to the documentation please create a PR against this repo, with a patch against develop.

Scripts

  • There are several autogenerated command files for clients and binaries. These are generated with generate:commands, which runs the autodoc rust binary, moves the files to their required places, and then if there is an update, commits them to git. This is for remote deployments.
  • Python scripts TODO

Autodoc

autodoc is a script that generates markdown files containing commands and their output (both command and --help output). For the moment the binaries and their commands are manually configured in the script.

CI/CD

TODO

This is a monorepo and components that make up Nym as a system are licensed individually, so for accurate information, please check individual files.

As a general approach, licensing is as follows this pattern: