1239: Replace the low-resolution diagrams with the high-resolution ones
Before Width: | Height: | Size: 43 KiB After Width: | Height: | Size: 167 KiB |
Before Width: | Height: | Size: 285 KiB After Width: | Height: | Size: 191 KiB |
Before Width: | Height: | Size: 49 KiB After Width: | Height: | Size: 187 KiB |
Before Width: | Height: | Size: 22 KiB |
BIN
.gitbook/assets/components/aquarius_deployment.png
Normal file
After Width: | Height: | Size: 177 KiB |
Before Width: | Height: | Size: 54 KiB After Width: | Height: | Size: 216 KiB |
Before Width: | Height: | Size: 33 KiB After Width: | Height: | Size: 126 KiB |
@ -281,7 +281,7 @@ $ curl localhost:9200
|
||||
|
||||
Aquarius supports indexing multiple chains using a single instance to serve API requests and one instance for each chain that must be indexed.
|
||||
|
||||
<figure><img src="../.gitbook/assets/components/aquarius_deployment.jpg" alt=""><figcaption><p>Aquarius deployment - multiple chains indexing</p></figcaption></figure>
|
||||
<figure><img src="../.gitbook/assets/components/aquarius_deployment.png" alt=""><figcaption><p>Aquarius deployment - multiple chains indexing</p></figcaption></figure>
|
||||
|
||||
The following deployment templates could be used for guidance. Some parameters are [optional](https://github.com/oceanprotocol/aquarius) and the template could be adjusted based on these considerations. Common cases are the deployments for one/multiple Ethereum networks:
|
||||
|
||||
|