# Download and Environment Preparation

US3SYNC provides two deployment methods: "General Deployment" and "UHOST Image Launch". Users can choose to deploy the US3SYNC service via "General Deployment" or "UHOST Image Launch" based on their existing resources. The general deployment solution is as follows:

## Runtime Environment

- **Linux:**
- CentOS 7.0 and above (check with `cat /etc/redhat-release`)
- Ubuntu 16.04 and above (check with `cat /etc/issue`)

US3SYNC depends on the telnet, expect, and rsync commands. Ensure these commands are pre-installed. For systems using yum as the package manager, install them with the following command:

```bash
yum install -y telnet expect rsync
```

## Download and Unzip

```bash
wget -O US3SYNC.tgz "https://ufile-release.cn-bj.ufileos.com/US3SYNC/v1.10.5/US3SYNC.tgz"
tar xzf US3SYNC.tgz
cd ./US3SYNC
```

## Start the Master Service

```bash
./console.sh start
# Set the cache service listening port:
Please set cache service listening port [9000]:
# Set the cache service password:
Please set cache service password [user-passwd]:
# For cloud hosts bound to EIP, use 0.0.0.0 as the IP address
Please set web service listening address [0.0.0.0:443]:
# Internal communication address should not be exposed to the public network. Use the machine's internal IP.
Please set internal communication listening address [x.x.x.x:8080]:
# Set the number of retries for errors:
Please set retry count for errors [10]:
# Set the username for web login:
Please set web login username [root]:
# Set the password for web login:
Please set web login password [passwd]:
US3SYNC start success!
# View the master service status:
./console.sh show
# Stop the master service:
./console.sh stop
# Verification:
# Check if the process is running correctly:
./console.sh show
```

## Add Worker Nodes

1. After the service starts, open the following address in a browser:

https://<web service listening IP>:<web service listening port>/

**Note:** When deploying the migration service using a cloud host, use the EIP here instead of 0.0.0.0.

2. Log in to the page using the username and password set during startup.

3. Add worker nodes with reference to the node creation interface instructions. Each node requires a unique working path. If the path does not exist, the corresponding directory will be created automatically.

**Note:** It is recommended to use the intranet IP.