LarkSR3.3
3.3 Environment
Hardware Environment
CPU
Memory
GPU
Sound Card
Software Environment
Operating System
Chrome Browser
VC Runtime Library
DX Runtime
Text Editor
Virtual Sound Card Driver
Virtual Camera Driver
Virtual Handle Controller Driver
System Settings
Turn Off Antivirus and Firewall
Turn Off Application Running Notification
Setup Automatic Login
Set Never Sleep-Never Turn Off the Display
Using Dongle Settings
3D Program Adaptation
Program Adaptation Requirements
Installation and Deployment
System Components
Stand-Alone Version: File Structure Overview
Simple Cluster Version: Package Structure & Deployment Overview
Deployment in Detail
Stand-Alone Intranet Deployment Guide
Stand-Alone External Network Access Guide
Cluster Intranet Deployment Guide (Windows)
Cluster External Network Access Guide (Windows)
Cluster Intranet Deployment Guide (Linux Docker)
Cluster External Network Access Guide (Linux Docker)
Deployment Case Study
Edge Cluster Deployment: Multi-Location Case Study
LarkXR NAT
LarkXR Turn: Built-in TURN Proxy for Rendering Nodes
Nginx Reverse Proxy: Exposing LarkXR Cluster to External Network
Server Port Mapping: Exposing LarkXR Cluster via Port Forwarding
Advanced Cluster Deployment: High Availability and Multi-Master Setup
GPU dedicated server
GPU Dedicated Server: Rack Installation and Initial Setup
Operating System Compatibility and Precautions
Running LarkXR
Browser support
Browser Compatibility Guide
Front usage instructions
Language Support
Application Overview
Launching an Application
Video Interaction (Client Camera Passthrough)
Voice Interaction (Microphone Passthrough)
Live Streaming
Text Input Methods
Regional Detection and Latency-Based Routing
Resource Allocation Strategy
Virtual Joystick (Remote Pole) Settings
Mobile Touch Gesture Modes
Function menu
PC Client: Function Menu Guide
Mobile Client: Function Menu Guide
Exiting an Application
Backend usage instructions
Logging into the Management Backend
Data Center
Data Center: Resource Monitor
Data Center: Usage Statistics
Data Center: Client Error Log
Applications
Package Management
Package Overview
Add Package
Edit Package
Delete Package
Application Management
Applications
Add Applications
Share
Mouse Mapping
Noun Interpretation
Reserve Applications
Overview
Check Alive Function
Run Applications
Run Applications
Synchronization management
Synchronization Overview
Client List
SR Client Management
Group Management
Group management
System Settings
Access Authorization List
Workspace
Parameter Settings
License Type
No Operation Timeout
Storage Configuration
Safety Measurements
Region Setting
Custom Logo
Short Note
Port Mapping
Dispatch Policy
Current Limiting
Theme
Users
Change Password
change PWD
Port Forward
guides
Custom
App Index
EnterAppli
Server-side
Application Storage
Standalone
Local Storage
OSS Storage
AWS S3
Cluster
Local storage
OSS Storage
AWS S3
General Features
Disk Space
Sync
Set Max Sync Cnt
Feature Components
DataChannel
Additional Parameters
Smart Voice
video input
voice input
external physical controller
Interactive Mode
How to use
Use Front end
Interactive Mode Interface Integration
Security Settings
Feature Components
Redis
MySQL8
Database Monitoring(druid)
Change userName and PWD
Disable
HTTPS access
Windows
Linux Docker
App Auth
Workplace Access Encryption
SDK ID for encrypted secondary development
security setting
Use AppliList Page
IP Blacklist-Whitelist
Allow Cross-Origin
CORS
Cors For Upload
Frequently Asked Questions (FAQ)
Troubleshooting Common Issues
Update Log
product updates
-
+
首页
Local storage
## Configuration In the admin panel, click on: System Settings -> Parameter Settings -> Storage Type, and choose "Local Storage" (default is "Local Storage"). ## **Upload to the Main Node Application Storage** Local storage refers to storage on the management node. The uploaded application zip package is by default stored in the **appli** folder under the deployment directory. If you want to change the application storage location, open the configuration management of the LarkXR Central Service Manager and select **Application Save Path**. Changing the program save path will not affect the normal operation of the system. In the default simple cluster version installation package, the management node is not used for rendering, so the uploaded zip package will not be unpacked. ## Synchronize and Render Node Application Storage ### 1. Render Node Local Storage Application Once the application is saved, a synchronization record will be generated. Registered render nodes will immediately **pull the application locally and unzip it**. If the application is uploaded after the node is online, it will start actively **pulling the application locally and unzipping it** after about 2 seconds. By default, applications will synchronize to the **Larkxr-render/appli** directory. You can change the application synchronization directory and make multiple selections. The system will prioritize synchronizing to directories with more remaining disk space. If you need to change the storage directory, you can directly add a directory, but if you want to modify a directory, you will need to manually move the applications in that directory to the modified directory; otherwise, the applications in that directory will trigger synchronization. ### 2. Render Node Using Shared Storage When there are a large number of applications, you can choose NAS shared storage. In the render service startup manager, select the shared directory as the local synchronization path and modify the following configuration: 1. Make modifications in `larkxr-render/application.properties`. If multiple machines use the same shared disk (such as NAS), configure the list of node IP addresses that use the same shared disk, separated by commas: `pxy.storage.type.local.disk-share-node-list=` 2. Choose **a specific render node as the unique synchronization node** and add the following configuration in `larkxr-render/application.properties`: `pxy.sync.enable=true`
admin
2025年4月8日 14:59
转发文档
收藏文档
上一篇
下一篇
手机扫码
复制链接
手机扫一扫转发分享
复制链接
Markdown文件
Word文件
PDF文档
PDF文档(打印)
分享
链接
类型
密码
更新密码
有效期