`--expected-shred-version` is another knob for users to get wrong and is
documentation that can get stale due to cluster restarts. Turns out
it's also generally not required anymore either because:
1. The cluster entrypoint can always be expected to be using the correct
shred version, and that shred version will be adopted by the new node
(earlier this was not the case when the `solana-gossip spy` node on
mainnet-beta.solana.com:8001 ran with shred version 0)
2. On a cluster restart, `--expected-bank-hash` is a much stronger
assertion that the validator is starting from the correct place (and
didn't exist when `--expected-shred-version` was first recommended)
* fix: ignore unknown fields in more RPC responses
* Remove mdbook infrastructure
* Delete gitattributes and other theme related items
Move all docs to /docs folder to support Docusaurus
* all docs need to be moved to /docs
* can be changed in the future
Add Docusaurus infrastructure
* initialize docusaurus repo
Remove trailing whitespace, add support for eslint
Change Docusaurus configuration to support `src`
* No need to rename the folder! Change a setting and we're all good to
go.
* Fixing rebase items
* Remove unneccessary markdown file, fix type
* Some fonts are hard to read. Others, not so much. Rubik, you've been
sidelined. Roboto, into the limelight!
* As much as we all love tutorials, I think we all can navigate around a
markdown file. Say goodbye, `mdx.md`.
* Setup deployment infrastructure
* Move docs job from buildkite to travic
* Fix travis config
* Add vercel token to travis config
* Only deploy docs after merge
* Docker rust env
* Revert "Docker rust env"
This reverts commit f84bc208e807aab1c0d97c7588bbfada1fedfa7c.
* Build CLI usage from docker
* Pacify shellcheck
* Run job on PR and new commits for publication
* Update README
* Fix svg image building
* shellcheck
Co-authored-by: Michael Vines <mvines@gmail.com>
Co-authored-by: Ryan Shea <rmshea@users.noreply.github.com>
Co-authored-by: publish-docs.sh <maintainers@solana.com>
