BilldDesk Pro

BilldDesk Pro is a cross-platform remote desktop control solution similar to ToDesk or Sunflower. You can use it to control computers and Android devices from a web browser, a desktop client, or an Android device.

Quick Start

• Web Experience: Visit https://desk.hsslive.cn for a quick trial.
• Client Download: Download the official client from https://desk.hsslive.cn/#/download.

Key Capabilities

• Cross-Platform Control: Web/Desktop controlling Desktop/Android, and Android controlling Desktop/Android (Desktop/Web is view-only).
• Advanced Features: Supports multi-screen operation, file transfer (bidirectional), clipboard synchronization, resolution synchronization, and remote Wake-on-LAN (WOL).
• Performance Modes: Includes 'Office' mode (low frame rate to save bandwidth) and 'Gaming' mode (high frame rate priority).
• Mouse Modes: Supports using the controller's mouse, the controlled device's mouse (for FPS games), and an 'Intelligent Mouse' mode.

To set up a local Redis instance, use redis:7.0. You must provide custom configuration files (redis.conf and users.acl) from the project root to your local directory before starting the container.

1. Prepare directories: Create conf and data directories in your local Redis path.
2. Copy config: Copy /docker/redis/conf/redis.conf and users.acl from the project root to your local conf directory.
3. Run the container: Map the local data and configuration files into the container.

# 1. Pull the image
docker pull redis:7.0

# 2. Start the container (Assumes local directories and config files are prepared)
LOCAL_DOCKER_RESIS_PATH=/Users/huangshuisheng/Desktop/docker/redis \
&& docker run -d \
-p 6379:6379 \
--name billd-desk-redis \
-v $LOCAL_DOCKER_RESIS_PATH/data:/data \
-v $LOCAL_DOCKER_RESIS_PATH/conf/redis.conf:/etc/redis/redis.conf \
-v $LOCAL_DOCKER_RESIS_PATH/conf/users.acl:/etc/redis/users.acl \
redis:7.0 redis-server /etc/redis/redis.conf

To set up a local MySQL instance for BilldDesk, follow these steps to pull the image, extract the default configuration, and run the container with custom settings.

1. Pull the image: Use mysql:8.0.
2. Extract configuration: Create a temporary container to copy the /etc/my.cnf file to your local machine. Ensure the local directory exists before running the copy command.
3. Run the container: Start the container using a volume mapping for both the configuration file and the data directory.

# 1. Pull the image
docker pull mysql:8.0

# 2. Copy configuration to local (Ensure $LOCAL_DOCKER_MYSQL_PATH/conf exists)
LOCAL_DOCKER_MYSQL_PATH=/Users/huangshuisheng/Desktop/docker/mysql \
DOCKER_MYSQL_TMP=`docker run -d mysql:8.0` \
&& docker cp $DOCKER_MYSQL_TMP:/etc/my.cnf $LOCAL_DOCKER_MYSQL_PATH/conf \
&& docker stop $DOCKER_MYSQL_TMP \
&& docker rm $DOCKER_MYSQL_TMP

# 3. Start the container with custom config and data mapping
LOCAL_DOCKER_MYSQL_PATH=/Users/huangshuisheng/Desktop/docker/mysql \
&& docker run -d \
-p 3306:3306 \
--name billd-desk-mysql \
-e MYSQL_ROOT_PASSWORD=mysql123. \
-v $LOCAL_DOCKER_MYSQL_PATH/conf/my.cnf:/etc/my.cnf \
-v $LOCAL_DOCKER_MYSQL_PATH/data:/var/lib/mysql/ \
mysql:8.0

To implement a multi-to-one remote control scenario (multiple controllers controlling a single client), follow this message-based workflow:

1. Initiate Connection: The controller client must click connect and send the billdDeskStartRemote message.
2. Handle Connection on Controlled Client: The controlled client listens for the billdDeskStartRemote message and performs the following logic:
   • If no stream exists: Call the native interface to acquire the stream.
   • If a stream exists: Call updateWebRtcRemoteDeskConfig to initiate the WebRTC handshake process (Offer/Answer).
3. Manage Permissions: By default, all users connected to the remote session can perform operations. You may implement logic to switch between 'Control Mode' and 'Observation Mode'.
4. Terminate Session:
   • When a controller disconnects, it must not affect other active connections.
   • The controlled client should only display the 'Remote Connection Disconnected' status once all connected users have disconnected.