Note: Local deployment can experience all the functions of VoceSpace, but it cannot be accessed on the public network. If you need public network deployment, please refer to:
The following is the basic configuration of vocespace. You need to copy this configuration and specify it when starting the container
The defaul "key": "devkey", "secret": "secret" works well, however, if you want to improve security and stability, feel free to generate a key/secret pair from your hosted livekit-server.
(Optional) How to get key and secret?
your.ip: User host machine IP address, you can use ifconfig | grep inet to view
In this example 192.168.31.138 is your host machine IP, redis can directly use localhost
For detailed Docker installation instructions or problems with installation, please refer to:
If you are a freshman and unfamiliar with the command line, we recommend that you install Docker Desktop.
In the following installation, if you are using MacOS or Windows, we will guide you to install Docker Desktop.
VoceSpace contains two images:
privoce/vocespace:latestprivoce/vocespace:latest_armSo you need to know your current server architecture to make a choice, see: help-View your own Linux architecture
-p 3000:3000: Map the container's port 3000 to the host's port 3000.-v ${PWD}/vocespace.conf.json:/app/vocespace.conf.json: Map the configurationDocker ce: If on Linux, you can use docker ps to view the process, then visit your_ip:3000 in the browser to view the started application, and then use docker logs <container_id> to view the log
Docker desktop: Observe the output after the container is started. When the output is Ready on http://ip:3000, it means that the local deployment has been completed
VoceSpace needs to rely on livekit-server to build webrtc and other related services
When using cloud servers, such as Alibaba Cloud, Tencent Cloud, Google Cloud, etc., you need to configure security groups/firewalls for the server, etc.
| port | type | ingress/egress | allow ip |
|---|---|---|---|
| 3000 | tcp | ingress | 0.0.0.0/0 Ipv4 |
| 3000 | tcp | egress | 0.0.0.0/0 Ipv4 |
| 7880 | tcp | ingress | 0.0.0.0/0 Ipv4 |
| 7881 | tcp | ingress | 0.0.0.0/0 Ipv4 |
| 80 | tcp | ingress | 0.0.0.0/0 Ipv4 |