Expand Infra Docs with Advanced Config Options and Identity Verification via TOML (#62)

* Add TOML and advanced-config webpages to infra section and minor edits to existing sections.

* Update the Infra section of the index page for the docs. Begin adding content to the TOML page.

* Fix header levels (promote L3 -> L2) in many infra docs.

* Add webserver configuration and TOML file contents.

* Document the '[ORGANIZATION]' section for the TOML.

* Finish the identity page & minor updates/revisions on other pages for consistency.

* Add clustering.

* Document memory (rwdb) database.

* Remove erronious file

* Remove section header for 'Ledger Pinning'.

* Spell Xahau correctly :)

Co-authored-by: tequ <git@tequ.dev>

* proofread

Co-authored-by: tequ <git@tequ.dev>

* proofread

Co-authored-by: tequ <git@tequ.dev>

---------

Co-authored-by: tequ <git@tequ.dev>
Co-authored-by: Thomas Silkjær <thomas@inftf.org>
This commit is contained in:
J. Scott Branson
2025-10-21 11:19:16 -04:00
committed by GitHub
parent 77e3d8b001
commit 575598f42e
10 changed files with 270 additions and 28 deletions

View File

@@ -1,12 +1,12 @@
# Intro
# Thank You!
Public contributions to the documentation are welcome. When contributing, please help with consistency and clarity by adhering to the below guidelines.
### Disambiguation
* Strive for brevity and clarity. Avoid jargon and use a professional writing tone.
# Disambiguation
* Strive for brevity and clarity. Avoid jargon and use a professional writing tone. Adhere to standards, such as [RFC 2119](https://datatracker.ietf.org/doc/html/rfc2119).
* When referring to the software `xahaud`, use a lowercase "x" and include the 'd'. When referring to the broader `Xahau Network`, capitalize both terms and,if appropriate, subsequently use the capitalized term "the Network". Use the capitalized `Xahau` or the all caps abbreviation `XAH` when referring to the currency.
* Be mindful that this documentation is shared by a global community. Avoid culture-specific jargon or slang.
### Formatting
# Formatting
* Relative and absolute linking are both permitted. When changing the directory structure or renaming individual pages, use grep to ensure all links are updated. Header, footer, index page, navigation bar, and links on other pages all need to be updated manually.
* The use of second person ("you") is permitted.
* Individual webpages may be formatted using Markdown, HTML, CSS, and JavaScript in any combination. To the extent possible, favor style templates and avoid inline CSS.
@@ -15,5 +15,5 @@ Public contributions to the documentation are welcome. When contributing, please
* Use square brackets inside code snippets to offset user specific information, such as file names and paths. For example: `cd [/path/to/xahaud] && ./xahaud server_info`
* Wrap multi-line code examples in three backticks: "```".
### General Guidelines
# General Guidelines
* Include meaningful commit messages.