new pages

Author: JukLee0ira

docs/subnet/install_guide/exposing_services.md

@@ -0,0 +1,22 @@
+---
+title: Exposing Subnet Services and Frontend
+---
+
+# Exposing Subnet Services and Frontend
+After starting the subnet, you need to start the servers. To allow outside users or services to access the services on the server, you need to expose the following ports. Here are the steps:
+
+Update the following parameters in `common.env`, replacing `<YOUR_SERVER_IP>` with your actual server IP address or domain name:
+```bash
+VITE_SUBNET_URL=http://<YOUR_SERVER_IP>:5213
+VITE_SUBNET_RPC=http://<YOUR_SERVER_IP>:8545
+```
+
+Modify the ports in `docker-compose.yml` as follows:
+```yaml
+  relayer:
+    ports:
+      - '0.0.0.0:5215:5215'
+  frontend:
+    ports:
+      - "0.0.0.0:5214:5214"
+```

docs/subnet/install_guide/launch_subnet.md

@@ -60,59 +60,6 @@ title: Launch a Subnet
 
   <!-- 6. (Optional) if you deployed Subswap, check out the usage here: -->
 
-### Multiple Machines Deployment
-
-To deploy a subnet with multiple machines , access the Deployment Wizard in your browser and follow these steps:
-
-1. Select "Custom Subnet" and click the button:
-   ![Custom Subnet](<../img/custom_subnet.png>)
-
-2. Configure the subnet options as per your requirements and fill in the details:
-   ![Configureuration](<../img/configuration.png>)
-
-3. Click the `Submit` button. You should see a success message:
-   ![success message](<../img/success_message.png>)
-
-4. Return to the Deployment Wizard page ,continue with [Deployment Wizard](launch_subnet/#deploy-with-wizard-ui) step 2,click the `Start` button.
-   ![click_start](../img/click_start.png)
-
-5. Copy the generated files `subnetX.env`, `docker-compose.yml`, and `genesis.json` to the other machines (ensure you modify the paths as necessary).
-   You need to copy and move the following files:
-   ![files_to_copy](../img/files_to_copy.png)
-
-6. Edit the `generated/docker-compose.yml` file, removing the subnet's network configuration (**except for the subnet configuration on machine1, which is the machine where you ran `start.sh`**).
-   ![delete_docker_net](../img/delete_docker_net.png)
-
-7. On `machineX`, place the `subnetX.env`, `docker-compose.yml`, and `genesis.json` files in the same directory. Then, use the following commands to start the corresponding subnet:
-   ```bash
-   export HOSTPWD=$(pwd)
-   docker compose --profile machineX pull;  
-   docker compose --profile machineX up -d;
-   ```
-   ![multi_machine_deploy](../img/multi_machine_deploy.png)
-
-8. Back in the Deployment Wizard, you can monitor the number of peers in the Status column on the left, or use the script `generated/scripts/check-peer.sh` to confirm if the multi-machine deployment was successful:
-
-   ![Status](<../img/status.png>)
-
-## Exposing Subnet Services and Frontend
-
-Update the following parameters in `common.env`, replacing `<YOUR_SERVER_IP>` with your actual server IP address or domain name:
-```bash
-VITE_SUBNET_URL=http://<YOUR_SERVER_IP>:5213
-VITE_SUBNET_RPC=http://<YOUR_SERVER_IP>:8545
-```
-
-Modify the ports in `docker-compose.yml` as follows:
-```yaml
-  frontend:
-    ports:
-      - "0.0.0.0:5214:5214"
-```
-
-Visit the Deployment Wizard and restart the subnet and services in the Deployment Wizard to apply these settings.
-
-
 <!-- ## Removing Subnet
 
 ### Shutdown Subnet

docs/subnet/install_guide/multi_machines_deployment.md

@@ -0,0 +1,39 @@
+---
+title: Multiple Machines Deployment
+---
+
+# Multiple Machines Deployment
+
+To deploy a subnet with multiple machines, you need to follow the first two steps of [Deploy With Wizard UI](../launch_subnet/#deploy-with-wizard-ui), pull and run the `start.sh` script, access the Deployment Wizard in your browser, and follow these steps:
+
+1. Select "Custom Subnet" and click the button:
+   ![Custom Subnet](<../img/custom_subnet.png>)
+
+2. Configure the subnet options as per your requirements and fill in the details:
+   ![Configureuration](<../img/configuration.png>)
+
+3. Click the `Submit` button. You should see a success message:
+   ![success message](<../img/success_message.png>)
+
+4. Return to the Deployment Wizard page ,continue with [Deployment Wizard](../launch_subnet/#deploy-with-wizard-ui) step 2,click the `Start` button.
+   ![click_start](../img/click_start.png)
+
+5. Copy the generated files `subnetX.env`, `docker-compose.yml`, and `genesis.json` to the other machines (ensure you modify the paths as necessary).
+   You need to copy and move the following files:
+   ![files_to_copy](../img/files_to_copy.png)
+
+6. Edit the `generated/docker-compose.yml` file, removing the subnet's network configuration (**except for the subnet configuration on machine1, which is the machine where you ran `start.sh`**).
+   ![delete_docker_net](../img/delete_docker_net.png)
+
+7. On `machineX`, place the `subnetX.env`, `docker-compose.yml`, and `genesis.json` files in the same directory. Then, use the following commands to start the corresponding subnet:
+   ```bash
+   export HOSTPWD=$(pwd)
+   docker compose --profile machineX pull;  
+   docker compose --profile machineX up -d;
+   ```
+   ![multi_machine_deploy](../img/multi_machine_deploy.png)
+
+8. Back in the Deployment Wizard, you can monitor the number of peers in the Status column on the left, or use the script `generated/scripts/check-peer.sh` to confirm if the multi-machine deployment was successful:
+
+   ![Status](<../img/status.png>)
+

mkdocs.yml

@@ -108,6 +108,8 @@ nav:
       - Introduction: ./subnet/index.md
       - Deployment Guide: 
         - Launch a Subnet: ./subnet/install_guide/launch_subnet.md
+        - Multi-Machines Deployment: ./subnet/install_guide/multi_machines_deployment.md
+        - Exposing Services: ./subnet/install_guide/exposing_services.md
         - Configs Explanation: ./subnet/install_guide/config_explanation.md
         - Common Issues and Troubleshooting: ./subnet/install_guide/common_issues.md
         - FAQ: ./subnet/install_guide/faq.md