Deploy docs version 0.11.8 (#1885)

* create docs version 0.11.8

* add former docs redirects

docs/docusaurus.config.js

@@ -58,6 +58,25 @@ const config = {
         highlightSearchTermsOnTargetPage: true,
       },
     ],
+    [
+      "@docusaurus/plugin-client-redirects",
+      {
+        redirects: [
+          {
+            from: "/config",
+            to: "/configuring",
+          },
+          {
+            from: "/installing-on-gcp",
+            to: "/running-on-gcp",
+          },
+          {
+            from: "/updating_node",
+            to: "/updating",
+          },
+        ],
+      },
+    ],
   ],
 
   themeConfig:

docs/package.json

@@ -16,6 +16,7 @@
   },
   "dependencies": {
     "@docusaurus/core": "3.2.1",
+    "@docusaurus/plugin-client-redirects": "3.2.1",
     "@docusaurus/preset-classic": "3.2.1",
     "@easyops-cn/docusaurus-search-local": "^0.40.1",
     "@mdx-js/react": "^3.0.0",

docs/versioned_docs/version-0.11.8/_config-options.md

@@ -0,0 +1,48 @@
+<!-- This file is generated automatically. Any manual modifications will be overwritten. -->
+
+| Config Option | Default Value | Description |
+| - | - | - |
+| `cn-core-contract-address` |  | Custom network core contract address |
+| `cn-feeder-url` |  | Custom network feeder URL |
+| `cn-gateway-url` |  | Custom network gateway URL |
+| `cn-l1-chain-id` |  | Custom network L1 chain id |
+| `cn-l2-chain-id` |  | Custom network L2 chain id |
+| `cn-name` |  | Custom network name |
+| `cn-unverifiable-range` | `[]` | Custom network range of blocks to skip hash verifications (e.g. `0,100`) |
+| `colour` | `true` | Use `--colour=false` command to disable colourized outputs (ANSI Escape Codes) |
+| `config` |  | The YAML configuration file |
+| `db-cache-size` | `8` | Determines the amount of memory (in megabytes) allocated for caching data in the database |
+| `db-max-handles` | `1024` | A soft limit on the number of open files that can be used by the DB |
+| `db-path` | `juno` | Location of the database files |
+| `eth-node` |  | WebSocket endpoint of the Ethereum node. To verify the correctness of the L2 chain, Juno must connect to an Ethereum node and parse events in the Starknet contract |
+| `grpc` | `false` | Enable the HTTP gRPC server on the default port |
+| `grpc-host` | `localhost` | The interface on which the gRPC server will listen for requests |
+| `grpc-port` | `6064` | The port on which the gRPC server will listen for requests |
+| `gw-api-key` |  | API key for gateway endpoints to avoid throttling |
+| `gw-timeout` | `5` | Timeout for requests made to the gateway |
+| `http` | `false` | Enables the HTTP RPC server on the default port and interface |
+| `http-host` | `localhost` | The interface on which the HTTP RPC server will listen for requests |
+| `http-port` | `6060` | The port on which the HTTP server will listen for requests |
+| `log-level` | `info` | Options: trace, debug, info, warn, error |
+| `max-vm-queue` | `2 * max-vms` | Maximum number for requests to queue after reaching max-vms before starting to reject incoming requests |
+| `max-vms` | `3 * CPU Cores` | Maximum number for VM instances to be used for RPC calls concurrently |
+| `metrics` | `false` | Enables the Prometheus metrics endpoint on the default port |
+| `metrics-host` | `localhost` | The interface on which the Prometheus endpoint will listen for requests |
+| `metrics-port` | `9090` | The port on which the Prometheus endpoint will listen for requests |
+| `network` | `mainnet` | Options: mainnet, sepolia, sepolia-integration |
+| `p2p` | `false` | EXPERIMENTAL: Enables p2p server |
+| `p2p-addr` |  | EXPERIMENTAL: Specify p2p source address as multiaddr |
+| `p2p-feeder-node` | `false` | EXPERIMENTAL: Run juno as a feeder node which will only sync from feeder gateway and gossip the new blocks to the network |
+| `p2p-peers` |  | EXPERIMENTAL: Specify list of p2p peers split by a comma. These peers can be either Feeder or regular nodes |
+| `p2p-private-key` |  | EXPERIMENTAL: Hexadecimal representation of a private key on the Ed25519 elliptic curve |
+| `pending-poll-interval` | `5` | Sets how frequently pending block will be updated (0s will disable fetching of pending block) |
+| `pprof` | `false` | Enables the pprof endpoint on the default port |
+| `pprof-host` | `localhost` | The interface on which the pprof HTTP server will listen for requests |
+| `pprof-port` | `6062` | The port on which the pprof HTTP server will listen for requests |
+| `remote-db` |  | gRPC URL of a remote Juno node |
+| `rpc-call-max-steps` | `4000000` | Maximum number of steps to be executed in starknet_call requests. The upper limit is 4 million steps, and any higher value will still be capped at 4 million |
+| `rpc-cors-enable` | `false` | Enable CORS on RPC endpoints |
+| `rpc-max-block-scan` | `18446744073709551615` | Maximum number of blocks scanned in single starknet_getEvents call |
+| `ws` | `false` | Enables the WebSocket RPC server on the default port |
+| `ws-host` | `localhost` | The interface on which the WebSocket RPC server will listen for requests |
+| `ws-port` | `6061` | The port on which the WebSocket server will listen for requests |

docs/versioned_docs/version-0.11.8/configuring.md

@@ -0,0 +1,102 @@
+---
+title: Configuring Juno
+---
+
+# Configuring Juno :gear:
+
+Juno can be configured using several methods, with the following order of precedence:
+
+1. [Command line parameters (flags)](#command-line-params)
+2. [Environment variables](#environment-variables)
+3. [Configuration file](#configuration-file)
+
+## Command line params
+
+Juno can be configured directly on the command line by prefixing `--` to each option name:
+
+```bash
+./build/juno --http --http-port 6060 --http-host 0.0.0.0
+```
+
+When using Docker, append the command line parameters after the image name to configure Juno:
+
+```bash
+docker run nethermind/juno --http --http-port 6060 --http-host 0.0.0.0
+```
+
+:::tip
+Command line parameters override [environment variables](#environment-variables) and [configuration file](#configuration-file).
+:::
+
+## Environment variables
+
+Juno can be configured through environment variables by prefixing the variable names with `JUNO_` and using the configuration options in [SCREAMING_SNAKE_CASE](https://en.wiktionary.org/wiki/screaming_snake_case) format.
+
+To set the `http`, `http-port`, and `http-host` configurations, Juno should be run in this format:
+
+```bash
+JUNO_HTTP=true JUNO_HTTP_PORT=6060 JUNO_HTTP_HOST=0.0.0.0 ./build/juno
+```
+
+When using Docker, start Juno using the `-e` command option:
+
+```bash
+docker run \
+  -e "JUNO_HTTP=true JUNO_HTTP_PORT=6060 JUNO_HTTP_HOST=0.0.0.0" \
+  nethermind/juno
+```
+
+:::tip
+Environment variables rank second in configuration precedence. [Command line parameters](#command-line-params) override environment variables.
+:::
+
+## Configuration file
+
+Juno can be configured using a [YAML](https://en.wikipedia.org/wiki/YAML) file:
+
+```yaml title="Sample YAML File" showLineNumbers
+log-level: info
+network: mainnet
+http: true
+http-port: 6060
+metrics: true
+metrics-port: 9090
+```
+
+To run Juno with a configuration file, use the `config` option to specify the path of the configuration file:
+
+```bash
+# Standalone binary
+./build/juno --config <CONFIG FILE PATH>
+
+# Docker container
+docker run nethermind/juno --config <CONFIG FILE PATH>
+```
+
+:::info
+By default, Juno looks for the configuration file in the `$XDG_CONFIG_HOME` directory.
+:::
+
+:::tip
+Configuration file rank third in configuration precedence. [Command line parameters](#command-line-params) and [environment variables](#environment-variables) override configuration file.
+:::
+
+## Configuration options
+
+To list all available command line options, you can use the `--help` parameter:
+
+```bash
+# Standalone binary
+./build/juno --help
+
+# Docker container
+docker run nethermind/juno --help
+```
+
+Below is a list of all configuration options available in Juno, along with their default values and descriptions:
+
+```mdx-code-block
+import ConfigOptions from "./_config-options.md";
+
+<ConfigOptions />
+```

docs/versioned_docs/version-0.11.8/faq.md

@@ -0,0 +1,125 @@
+---
+title: Frequently Asked Questions
+---
+
+# Frequently Asked Questions :question:
+
+<details>
+  <summary>What is Juno?</summary>
+
+Juno is a Go implementation of a Starknet full-node client created by Nethermind to allow node operators to easily and reliably support the network and advance its decentralisation goals. Juno supports various node setups, from casual to production-grade indexers.
+
+</details>
+
+<details>
+  <summary>How can I run Juno?</summary>
+
+Check out the [Running Juno](running-juno) guide to learn the simplest and fastest ways to run a Juno node. You can also check the [Running Juno on GCP](running-on-gcp) guide to learn how to run Juno on GCP.
+
+</details>
+
+<details>
+  <summary>What are the hardware requirements for running Juno?</summary>
+
+We recommend running Juno with at least 4GB of RAM and 250GB of SSD storage. Check out the [Hardware Requirements](hardware-requirements) for more information.
+
+</details>
+
+<details>
+  <summary>How can I configure my Juno node?</summary>
+
+You can configure Juno using [command line parameters](configuring#command-line-params), [environment variables](configuring#environment-variables), and a [YAML configuration file](configuring#configuration-file). Check out the [Configuring Juno](configuring) guide to learn their usage and precedence.
+
+</details>
+
+<details>
+  <summary>How can I update my Juno node?</summary>
+
+Check out the [Updating Juno](updating) guide for instructions on updating your node to the latest version.
+
+</details>
+
+<details>
+  <summary>How can I interact with my Juno node?</summary>
+
+You can interact with a running Juno node using the [JSON-RPC](json-rpc) and [WebSocket](websocket) interfaces.
+
+</details>
+
+<details>
+  <summary>How can I monitor my Juno node?</summary>
+
+Juno captures metrics data using [Prometheus](https://prometheus.io), and you can visualise them using [Grafana](https://grafana.com). Check out the [Monitoring Juno](monitoring) guide to get started.
+
+</details>
+
+<details>
+  <summary>Do node operators receive any rewards, or is participation solely to support the network?</summary>
+
+Presently, running a node does not come with direct rewards; its primary purpose is contributing to the network's functionality and stability. However, operating a node provides valuable educational benefits and deepens your knowledge of the network's operation.
+
+</details>
+
+<details>
+  <summary>How can I view Juno logs from Docker?</summary>
+
+You can view logs from the Docker container using the following command:
+
+```bash
+docker logs -f juno
+```
+
+</details>
+
+<details>
+  <summary>How can I get real-time updates of new blocks?</summary>
+
+The [WebSocket](websocket#subscribe-to-newly-created-blocks) interface provides a `juno_subscribeNewHeads` method that emits an event when new blocks are added to the blockchain.
+
+</details>
+
+<details>
+  <summary>Does Juno provide snapshots to sync with Starknet quickly?</summary>
+
+Yes, Juno provides snapshots for both the Starknet Mainnet and Sepolia networks. Check out the [Database Snapshots](snapshots) guide to get started.
+
+</details>
+
+<details>
+  <summary>How can I contribute to Juno?</summary>
+
+You can contribute to Juno by running a node, starring on GitHub, reporting bugs, and suggesting new features. Check out the [Contributions and Partnerships](/#contributions-and-partnerships) page for more information.
+
+</details>
+
+<details>
+  <summary>I noticed a warning in my logs saying: **Failed storing Block \{"err": "unsupported block version"\}**. How should I proceed?</summary>
+
+You can fix this problem by [updating to the latest version](updating) of Juno. Check for updates and install them to maintain compatibility with the latest block versions.
+
+</details>
+
+<details>
+  <summary>After updating Juno, I receive **error while migrating DB.** How should I proceed?</summary>
+
+This error suggests your database is corrupted, likely due to the node being interrupted during migration. This can occur if there are insufficient system resources, such as RAM, to finish the process. The only solution is to resynchronise the node from the beginning. To avoid this issue in the future, ensure your system has adequate resources and that the node remains uninterrupted during upgrades.
+
+</details>
+
+<details>
+  <summary>I receive **Error: unable to verify latest block hash; are the database and --network option compatible?** while running Juno. How should I proceed?</summary>
+
+To resolve this issue, ensure that the `eth-node` configuration aligns with the `network` option for the Starknet network.
+
+</details>
+
+<details>
+  <summary>I receive **process \<PID\> killed** and **./build/juno: invalid signature (code or signature have been modified)** while running the binary on macOS. How should I proceed?</summary>
+
+You need to re-sign the binary to resolve this issue using the following command:
+
+```bash
+codesign --sign - ./build/juno
+```
+
+</details>

docs/versioned_docs/version-0.11.8/hardware-requirements.md

@@ -0,0 +1,23 @@
+---
+title: Hardware Requirements
+---
+
+# Hardware Requirements :computer:
+
+The following specifications outline the hardware required to run a Juno node. These specifications are categorised into minimal and recommended requirements for different usage scenarios.
+
+## Minimal requirements
+
+- **CPU**: At least 2 cores
+- **RAM**: 4GB or more
+- **Storage**: 250GB or more (SSD recommended; note: storage needs will grow over time)
+
+## Recommended requirements
+
+- **CPU**: High-performance CPU with 4 or more cores
+- **RAM**: 8GB or more
+- **Storage**: High-performance SSD with at least 250GB to accommodate future growth
+
+:::tip
+We intend the above specifications as a guideline. The minimal requirements support basic node operations, and the recommended settings ensure optimal performance and scalability for future needs.
+:::