Please note that all installation actions must be performed with root rights.
You can install all ONLYOFFICE Workspace Enterprise Edition components and modules at once. To do that run the following command:
bash workspace-enterprise-install.sh -md "yourdomain.com"
Where yourdomain.com
is your own domain that will be used for ONLYOFFICE Mail.
Your domain that will be used for maintaining correspondence must be valid and configured for this machine (i.e. it should have the appropriate A record in the DNS settings that points your domain name to the IP address of the machine where ONLYOFFICE Mail is installed).
In the command above, the "yourdomain.com"
parameter must be understood as a service domain for Mail Server. It is usually specified in the MX record of the domain that will be used for maintaining correspondence. As a rule, the "yourdomain.com"
looks like mx1.onlyoffice.com
If you do not have a domain name or simply want to install ONLYOFFICE Workspace Enterprise Edition for your local server, you can install it without ONLYOFFICE Mail. In case you plan to add it later, you will be able to do that from Control Panel.
For the ONLYOFFICE Workspace Enterprise Edition to be able to run the Docker service is necessary. The installation script will check if it is present on the computer and its version is not less than the minimal required. Otherwise the Docker will be installed or updated automatically.
Docker specifies Google DNS servers by default. If your
ONLYOFFICE Workspace Enterprise Edition server is not going to have access to the Internet, we recommend that you change the default Docker DNS address to the address of your local DNS server. To do that go to the
/etc/default/docker
file and change the IP address in the following line to the IP address of a DNS server in your local network:
docker_OPTS="--dns 8.8.8.8"
For the RPM based operating systems like CentOS:
- Create the
/etc/docker/daemon.json
configuration file with the following contents:
{ "dns" : [ "8.8.8.8" ] }
- Restart the Docker service:
sudo systemctl restart docker.service