feat(docs): add infrastructure guide and restart docker instructions

fix(docs): fix correct order for telegram bot notifications

Author: fassko

docs/fassets/guides/1-deploy-fassets-agent.mdx

@@ -8,6 +8,8 @@ authors: [fassko]
 keywords: [fassets, xrp, btc, doge flare-network, flare-network]
 ---
 
+import RestartDocker from "./_restart_docker.mdx";
+
 The FAssets system by Flare enables non-smart contract tokens like BTC and XRP to interact trustlessly with smart contracts on the Flare network, unlocking their use in DeFi applications. It achieves this through collateralized minting, utilizing [Flare Data Connector (FDC)](/fdc/overview) and [Flare Time Series Oracle (FTSO)](/ftso/overview) for secure cross-chain functionality.
 
 Agents in the FAssets system facilitate the minting and redemption of FAssets by providing over-collateralized assets and managing transactions securely. A liquidator in the FAssets system monitors agent's collateralization levels to ensure the system's security and trustlessness.
@@ -227,13 +229,7 @@ docker compose --profile cli run user-bot info --fasset FASSET
 
 To restart and update the FAssets agent, run the following commands:
 
-```bash
-docker compose down
-git pull
-docker compose pull
-docker compose --profile cli run agent-bot listAgents --fasset FXRP
-docker compose up -d
-```
+<RestartDocker />
 
 ## Access the Agent Frontend
 

docs/fassets/guides/7-telegram-bot-notifications.mdx

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 6
+sidebar_position: 7
 slug: telegram-bot-notifications
 title: Telegram Bot Notifications
 description: Set up a Telegram bot to receive notifications

docs/fassets/guides/8-infrastructure.mdx

@@ -0,0 +1,78 @@
+---
+sidebar_position: 8
+slug: infrastructure
+title: FAssets Agent Infrastructure
+description: Configuring the FAsset Bot to Use Custom Infrastructure
+tags: [intermediate, fassets, bitcoin, dogecoin]
+authors: [fassko]
+keywords: [fassets, xrp, btc, doge flare-network, flare-network]
+---
+
+import RestartDocker from "./_restart_docker.mdx";
+
+By default, the FAsset bot operates on Flare infrastructure.
+This guide explains how to configure it to utilize your own infrastructure for enhanced performance and reliability.
+
+## Prerequisites
+
+- Running an RPC node https://dev.flare.network/run-node/rpc-node
+- Configure FTSO data provider https://dev.flare.network/run-node/ftso-data-provider
+- Configuring FDC attestation provider https://dev.flare.network/run-node/fdc-attestation-provider
+- Setting up DAL https://github.com/flare-foundation/data-availability
+
+## Setting Up
+
+1.  Update `config.json`
+
+    Update the `config.json` file to include your own URLs for the data access layer, RPC, and verifier.
+
+    Replace the following URLs with your own:
+
+        - Substitute the Data Availability Layer URL with the URL for your Data Access Layer.
+        - Update the Songbird RPC URL with your RPC endpoint.
+        - Replace your verifier URL with your verifier endpoint.
+
+    ```json
+    {
+      "dataAccessLayerUrls": [
+        "Data Availability Layer URL",
+        "https://sgb-data-availability.flare.network"
+      ],
+      "rpcUrl": "Songbird RPC URL",
+      "fAssets": {
+        "FXRP": {
+          "indexerUrls": [
+            "Verifier URL",
+            "https://fdc-verifiers-mainnet.flare.network/verifier/xrp"
+          ]
+        }
+      }
+    }
+    ```
+
+2.  Update `secrets.json`
+
+    Ensure your API keys are correctly set in the `secrets.json` file:
+
+    ```json
+    {
+      "indexer": ["Your API key", "Flare API key"],
+      "data_access_layer": ["Your API key", "Flare API key"],
+      "native_rpc": "your Songbird API key"
+    }
+    ```
+
+    Replace the following: - Substitute your API key with your own custom API key(s) for indexers and data access layers. - Replace your Songbird API key with your RPC API key.
+
+    :::warning
+
+        The API keys must align with the corresponding URLs in dataAccessLayerUrls and indexerUrls. For example, the first API key in indexer should match the first verifier URL in indexerUrls.
+
+        Currently, only a single RPC URL is supported.
+        Multiple RPC URLs are not supported yet.
+
+3.  Restart Docker Containers
+
+    After updating the configuration files, make sure to restart the Docker containers to apply the changes.
+
+    <RestartDocker />

docs/fassets/guides/_restart_docker.mdx

@@ -0,0 +1,7 @@
+```bash
+docker compose down
+git pull
+docker compose pull
+docker compose --profile cli run agent-bot listAgents --fasset FXRP
+docker compose up -d
+```