Stand-Alone Intranet Deployment Guide

This guide covers the deployment steps for the LarkXR Stand-Alone version on an **intranet** (local network) environment. In this setup, both the management node and rendering node run on a single GPU server within the same local network.

## Prerequisites

Before deploying, ensure the following are ready:

1. A GPU server with the environment prepared. Refer to [Environment Preparation](https://docs.paraverse.cc/doc/215/) for details.
2. The LarkXR stand-alone package downloaded and extracted. Refer to [System Components](https://docs.paraverse.cc/doc/239/) for the download link. It is recommended to extract to a drive root directory (e.g., `D:\larkxr`). The path must not contain Chinese characters.
3. All required system ports are available and not in use. If any port is occupied, perform port modification before proceeding.

## Required Ports

| Protocol | Port | Purpose |
|---|---|---|
| TCP | 8181 | Frontend page (nginx) and backend interface |
| TCP | 8182 | Backend page nginx forwarding |
| TCP | 8184 | Management service |
| TCP | 3306 | MySQL database |
| TCP | 6379 | Redis cache |
| TCP | 8089 | Sync and proxy service |
| TCP | 10002 | WebSocket communication |
| TCP | 10003 | Internal rendering server communication |
| TCP | 10004 | Rendering server SSL |
| UDP | 10011-10040 | Audio and video communication |

## Deployment Steps

1. **Open the deployment directory** - Navigate to the extracted LarkXR folder and double-click `LarkXRLauncher.exe`.
2. **Configure the management node** - Open the configuration management node panel. Enter the local IPv4 address of the machine. Enable **Start on Boot** if desired. Other configuration items can remain at their defaults.
3. **Configure the rendering node** - Open the configuration rendering node panel and enter the same local IPv4 address.
4. **Save and start services** - Click Save, then start the service. If any pop-up dialogs appear during startup, click **Cancel** to dismiss them.
5. **Access the backend** - Once all services have started, open a browser and go to `http://<IP>:8182`. The default login credentials are:
   - **Username:** `admin`
   - **Password:** `123456`
6. **Verify deployment** - Log in to the backend and check the resource monitoring panel. A successfully deployed node should appear as registered.