import this
ce067db401
* initialise nym node pages * new TOC flow and archive section * vps setup page draft * syntax fix * syntax fix * syntax fix * add ulimit setup * initialise nym-node page * add ports * syntax edit * syntax edit * add flags * add setup, run and bonding pages * add info * syntax edit * add configuration page * syntax fix * syntax fix * add vps troubleshooting * add vps troubleshooting * create nyx configuration page * add quickflow * add quickflow * add quickflow * add quickflow * add quickflow * add quickflow * syntax fix * syntax fix * move vps setup to configuration * syntax fix * syntax fix * syntax fix * edit points * finish nym-node setup.md page * new connnectivity configuration - page finished * finish proxy and landing page guide * finish nymvisor update * finish performance testing upgdate * finish faq pages update * fix troubleshooting * fix troubleshooting * fix manual-upgrade * finish introduction page * update introduction * update summary * correct all links * update graphs * update cmdruns * syntax edit and spellcheck * updated mdbook plugins * mdbook update * update modules * remove redundant * fix version cmdrun * removed smoosh-faw to archive * syntax fix * attempt to update mdbook admonish * try dirty workaround hack * try dirty workaround hack * try dirty workaround hack * try dirty workaround hack * try dirty workaround hack * try dirty workaround hack * try dirty workaround hack * try dirty workaround hack * try dirty workaround hack * address review comments * address review comments * address review comments * PR ready to merge
Nym Documentation
Documentation for the Nym privacy platform built using the mdBook docs framework.
Documentation can be viewed at https://nymtech.net/docs
Contributing
Contributions to our documentation are very welcome. Please work on your contribution in either a feature/<feature-name> or chore/<chore-name> branch from master and target your pull request at master.
Since these docs autogenerate command output and import docs from binaries in target/release on build make sure you're branching off of master when making your branch.
Changes merged to master will be autodeployed to the production site.
Contributing a new translation
To contribute tranlsations in a new language, please get in touch via Matrix or Discord.
Variables
There are some variables that are shared across the entire docs site, such as the current latest software version.
Variables are denoted in the .md files wrapped in {{}} (e.g {{wallet_release_version}}), and are located in the book.toml file under the [preprocessor.variables.variables] heading. If you are changing something like the software release version, minimum code versions in prerequisites, etc, check in here first!
Diagrams
Most diagrams are simply ascii. Copies are kept in /diagrams/ for ease of reproducability. Created using textik.
Importing files and auto-generated command output
Example files are inserted as per normal with mdbook.
Some binary command outputs are generated using the cmdrun mdbook plugin.
Building
When working locally, it is recommended that you use mdbook serve to have a local version of the docs served on localhost:3000, with hot reloading on any changes made to files in the src/ directory.
You can find other commands in the mdBook CLI tool docs.
I tried to edit files in theme/ and they aren't taking effect / mdbook serve causes a looping reload on file changes after changing fields in [preprocessor.theme] config
Looping reload is a known issue with the mdbook-theme preprocessor used for the table of contents and layout of these docs. As outlined in the mdbook-theme readme one way to mitigate this is to set turn-off = true under [preprocessor.theme]. This means that mdbook serve or mdbook watch ignores changes to the theme/ directory, which is the source of the looping reload. If you have changed or commented out this line, reintroduce it to remove the looping reload. If you are trying to edit the theme of the docs and want to apply the change, see here for more info on how to remove the block, change the theme, and reintroduce the block.
Checking the mdBook version
To check the version of mdBook installed on your system, you can use the mdbook --version command. This will print the version number of mdBook installed on your system in the terminal.
The latest release of the binary of the pre-compiled binaries can be found on GitHub.