Euro-Office
Deployment and configuration of Euro-Office as an optional Docker Compose service.
Euro-Office is handled as an OnlyOffice-compatible editor by Sync-in.
📋 Prerequisites
⚠️ To enable Euro-Office integration, first make sure that the reverse proxy configuration is enabled.
⚡ Activation
Follow the steps below to enable Euro-Office with the Nginx reverse proxy.
Nginx configuration
In ./config/nginx/nginx.conf, uncomment the Euro-Office include at the end of the file:
include eurooffice.conf;
In ./config/nginx/docker-compose.nginx.yaml, ensure that the Euro-Office configuration is mounted in the Nginx container:
services:
nginx:
volumes:
- ./eurooffice.conf:/etc/nginx/eurooffice.conf
Docker Compose configuration
In docker-compose.yaml, uncomment the required Docker Compose files:
include:
- ./config/nginx/docker-compose.nginx.yaml
- ./config/eurooffice/docker-compose.eurooffice.yaml
Sync-in configuration
In environment.yaml, enable the Euro-Office integration:
applications:
files:
editors:
eurooffice:
# enable Euro-Office integration
enabled: true
# use the same secret as in docker-compose.eurooffice.yaml
secret: 'euroOfficeSecret'
Replace euroOfficeSecret with a secure value, then make sure it matches the one defined in
./config/eurooffice/docker-compose.eurooffice.yaml:
services:
eurooffice:
environment:
- JWT_SECRET=euroOfficeSecret
Do not enable onlyoffice and eurooffice at the same time unless this is intentional.
If both are enabled, Sync-in gives priority to onlyoffice.
docker compose up -d && docker compose restart nginx sync_in to apply the changes
🌐 Access
Sync-in and Euro-Office run in Docker containers and communicate via the Nginx reverse proxy.
It is essential to access the interface using either the server IP address or a properly configured domain name.
Accessing Sync-in via http://localhost or http://127.0.0.1 will prevent Euro-Office from working properly; documents will neither be displayed nor edited.