Sync-in installation within openmediavault Compose

[Stephan-P]

[EDIT] Long exploration thread below. Skip to ANSWER.

Following up on @Fogia-f who couldn't find a way, I am making another attempt to bring the Sync-in installation under the wings of the openmediavault Docker Compose.

For this I am following along these steps:

• Download and unzip sync-in-compose.zip on your PC
• Open openmediavault workbench - Services - Compose - Files
• Create a new Compose file called "sync-in-docker"
• Open the compose.yml from the zip file and copy its contents into the OMV Compose File editor
• (Open the environments.yml from the zip file, use an online yaml-env converter and paste the result in the Environment variable pane of the OMV Compose File editor)
• Save the newly created compose file for now
• Use Winscp to SSH into OMV's /appdata/sync-in-docker
• Copy the full contents of the downloaded zip file in there
• Continue following the steps in the Sync-in installation guide: Winscp edit environments.yaml with default secrets, db username and db password
• Return to the OMV workbench - Services - Compose - Files
• Edit compose file sync-in-docker
• (Put a # in front of the line - ./environment.yaml as this should be taken over by the Evironment variables now)
• Continue following the steps in the Sync-in installation guide: database url, data storage, admin credentials
• Save the compose file and pull and up the container
• (Potential issue? Docker prefixes the network name with the container name: sync-in_sync_in_network)
• Failure to open http://local-server-ip:8080

Compose:

REMOVED

Environment:

REMOVED

Log:

time="2026-05-29T16:56:45+02:00" level=warning msg="The \"z\" variable is not set. Defaulting to a blank string."
sync-in  | Waiting for database to be ready...
sync-in  | Database connection attempt 1/30...
...
sync-in  | Database connection attempt 17/30...
mariadb  | 2026-05-29 14:55:37+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.8.7+maria~ubu2404 started.
sync-in  | Database connection attempt 18/30...
...
sync-in  | Database connection attempt 30/30...
sync-in  | Error: Timeout waiting for database after 30 attempts:
sync-in  | Database check failed: Missing configuration: "environment.yaml" not found, or no variables beginning with "SYNCIN_" are set.
sync-in  | Waiting for database to be ready...
sync-in  | Database connection attempt 1/30...
...

Missing configuration: "environment.yaml" not found
So my intended alternative route via environment variables in environment.env is not working. Something is hardcoded for "environment.yaml"?
@johaven can you confirm this? And does this mean that I have have reached a cul-de-sac in my attempt and need to fall back to the manual installation outside openmediavault Compose?

Is this the only issue, or is the renamed network sync-in_sync_in_network also playing up?

What's this warning message at the first line of the log? It also pops up if I remove the line
- TZ=${{ tz }} # omv system time zone
from the compose.

EDIT: PART OF LOG CUT

[Stephan-P]

With the environment.yaml re-instated with the same content as the environment.env:

    volumes:
      - ./environment.yaml:/app/environment/environment.yaml
      - ./data:/app/data
      - desktop_releases:/app/static/releases:ro

The log looks less problematic:

time="2026-05-29T17:28:07+02:00" level=warning msg="The \"z\" variable is not set. Defaulting to a blank string."
mariadb  | 2026-05-29 15:27:05+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.8.7+maria~ubu2404 started.
mariadb  | 2026-05-29 15:27:05+00:00 [Warn] [Entrypoint]: /sys/fs/cgroup///memory.pressure not writable, functionality unavailable to MariaDB
mariadb  | 2026-05-29 15:27:05+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
mariadb  | 2026-05-29 15:27:05+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.8.7+maria~ubu2404 started.
mariadb  | 2026-05-29 15:27:06+00:00 [Note] [Entrypoint]: MariaDB upgrade not required
mariadb  | 2026-05-29 15:27:06 0 [Note] Starting MariaDB 11.8.7-MariaDB-ubu2404 source revision e7d1202da30b7707185dc9b55af4693d1e3e4f60 server_uid xzUHW9xRVkFOAl6QLepZZ8Khe0U= as process 1
mariadb  | 2026-05-29 15:27:06 0 [Note] InnoDB: Compressed tables use zlib 1.3
mariadb  | 2026-05-29 15:27:06 0 [Note] InnoDB: Number of transaction pools: 1
mariadb  | 2026-05-29 15:27:06 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
mariadb  | 2026-05-29 15:27:06 0 [Warning] mariadbd: io_uring_queue_init() failed with EPERM: sysctl kernel.io_uring_disabled has the value 2, or 1 and the user of the process is not a member of sysctl kernel.io_uring_group. (see man 2 io_uring_setup).
mariadb  | create_uring failed: falling back to libaio
mariadb  | 2026-05-29 15:27:06 0 [Note] InnoDB: Using Linux native AIO
mariadb  | 2026-05-29 15:27:06 0 [Note] InnoDB: innodb_buffer_pool_size_max=8388608m, innodb_buffer_pool_size=128m
mariadb  | 2026-05-29 15:27:06 0 [Note] InnoDB: Completed initialization of buffer pool
sync-in  | Waiting for database to be ready...
sync-in  | Database connection attempt 1/30...
...
sync-in  | Database connection attempt 30/30...
sync-in  | Error: Timeout waiting for database after 30 attempts:
sync-in  | Database check failed: unknown escape sequence (4:26)
sync-in  | 
sync-in  |  1 | mysql:
sync-in  |  2 |   url: mysql://root:databas-password ...
sync-in  |  3 | auth:
sync-in  |  4 |   encryptionKey: "long-random-encryption-key"
sync-in  | ------------------------------^
sync-in  |  5 |   token:
sync-in  |  6 |     access:
sync-in  | Waiting for database to be ready...
sync-in  | Database connection attempt 1/30...
...

But still no Sync-in when opening http://server-ip:8080
ERR_CONNECTION_REFUSED

[johaven]

Yes, environment.yaml must be reachable from the server.

The mariadb and sync-in containers must be on the same network to communicate with each other.
That should be supported by the Docker Compose plugin (I think).

sync-in  | Database check failed: unknown escape sequence (4:26)

This error line looks strange.

Could you put your mysql.url value in quotes ?

[Stephan-P]

If the environment.yaml needs to remain in place, then there's no chance for me to elevate the installation proces to a higher (compose) level.

• Removed the environment variables from my compose definition
• Removed the # in front of the reference to the ./environment.yaml
• Put the mysql.url value in betwen quotes In the environment.yaml

No luck: http://server-ip:8080 results in ERR_CONNECTION_REFUSED

Openmediavault Compose:

REMOVED

Environment.yaml:

REMOVED

Log Docker UP:

time="2026-05-30T10:54:57+02:00" level=warning msg="The \"z\" variable is not set. Defaulting to a blank string."
 Network sync-in_sync_in_network Creating 
 Network sync-in_sync_in_network Created 
 Container mariadb Creating 
 Container mariadb Created 
 Container sync-in Creating 
 Container sync-in Created 
 Container mariadb Starting 
 Container mariadb Started 
 Container sync-in Starting 
 Container sync-in Started 

Log Sync-in:

time="2026-05-30T10:58:18+02:00" level=warning msg="The \"z\" variable is not set. Defaulting to a blank string."
...
sync-in  | Database connection attempt 30/30...
sync-in  | Error: Timeout waiting for database after 30 attempts:
sync-in  | Database check failed: unknown escape sequence (4:26)
sync-in  | 
sync-in  |  1 | mysql:
sync-in  |  2 |   url: "mysql://root:passphrase-with-hyphens...
sync-in  |  3 | auth:
sync-in  |  4 |   encryptionKey: "long-random-encryption-key"
sync-in  | ------------------------------^
sync-in  |  5 |   token:
sync-in  |  6 |     access:
sync-in  | Waiting for database to be ready...
sync-in  | Database connection attempt 1/30...
sync-in  | Database connection attempt 2/30...
REPEAT

• What is "The "z" variable is not set."? (It's only coming up with sync-in.)
• Could the OMV Compose prefix of the docker network name be an issue?
• I noticed that the database encryption key and database password are (partly) readable in the log.
• If I change these later on, will the old database be automatically removed from the system or do need to do that manually?
• In general, what happens with the database with every Docker UP - DOWN - UP cycle?

[Stephan-P]

Replaced all three secrets with less exotic keys and the first hurdles have been taken. Sync-in starts!

Summary of findings so far:

• environments.yaml cannot be converted into environment variables within compose or external .env file.
  Sync-in components require the yaml file and its contents to be in place.
  @johaven Maybe remove the section about environment variables from Installation manual, as it may give wrong impressions?
• Encryption keys must not contain backslashes as these are parsed as escape sequence.
  @johaven, Please add specifications for secret codes to docs.
• docker-compose.yaml should be adapted to prevent prefix to docker network name.
  @johaven, I suggest that name: sync_in_network be added to the network specification in docker-compose.yaml
• docker-compose.yaml can be imported/copied into openmediavault Compose.
• Once successfully UP, openmediavault Compose properly lists containers 'sync-in' and 'mariadb', as well as network 'sync_in_network' with these two containers bridged.
• The warning "The "z" variable is not set" disappeared from the Sync-in log.
  @johaven Would it be an idea to enhance the docs with an explanation about this warning?
• the folder appdata/sync_in_docker/data is empty, so I am not sure where the database and other volumes have gone to.

[Stephan-P]

Additional finding:

• Sync-in - User management show an additional user by name "sync-in-admin" including the quotation marks.
  @johaven Please add to Installation guide: Do not use double quotes when specifying INIT_ADMIN_LOGIN and INIT_ADMIN_PASSWORD. Best to not use any quotation marks at all and opt for one-word-name and one-word-password.

As this account including quotation marks was created before the one without, THIS IS THE ADMINISTRATOR account that cannot be deleted. How to overcome this? How to start all over again?

[EDIT] I managed to rename the account after which I was able to delete it.

[Stephan-P]

@johaven Could you give some more explanation about the volumes data and desktop_releases?
Are these for Sync-in internal use and if so, should I point them to corresponding subdirectories under /appdata/sync-in-docker/?
Or are these NAS Shares where the user files reside and should I point them to the NAS "data" share?

Also, when I'm logged in as the administrator and I click Files - Personal, then an English error message "Space path is invalid" briefly pops up. What does this mean?

[Stephan-P]

This is becoming a one man show....
TIL about the distinction between single and double quotes in yaml: https://www.yaml.info/learn/quote.html

[Stephan-P]

Question about error message within the Sync-in app: 'Space path is not valid' moved to separate thread

[Stephan-P]

After resolving the error message "Space path is not valid", my working configuration is below.
Next steps:

• Nginx reverse proxy
• webdav
• Collabora

After that I'll close this thread with a complete HOW-TO.

(reduced) Environment.yaml:

REMOVED

Openmediavault compose:

REMOVED

[Stephan-P]

Sync-in installation guide (so far) published at openmediavault forum

[johaven]

Maybe remove the section about environment variables from Installation manual, as it may give wrong impressions?

We added a note here about the minimum environment variables needed to run the server without using environment.yaml: here

Please add specifications for secret codes to docs.

We reviewed the examples and added single quotes to prevent certain special characters from being interpreted.

I suggest that name: sync_in_network be added to the network specification

Indeed, this seems to have an impact on some integrations. The docker-compose configuration has been updated accordingly.

The warning "The "z" variable is not set" disappeared from the Sync-in log.

The Sync-in Docker Compose setup does not define a TZ environment variable.

Please add to Installation guide: Do not use double quotes when specifying INIT_ADMIN_LOGIN and INIT_ADMIN_PASSWORD

In the next release, SYNCIN_* variables will also support surrounding single quotes; surrounding double quotes are already supported. INIT_ADMIN_LOGIN and INIT_ADMIN_PASSWORD will support either matching single or double quotes. Only the outer quotes are removed; the inner value remains unchanged. The documentation will include a note explaining this behavior.

[Stephan-P]

We added a note here about the minimum environment variables needed to run the server without using environment.yaml: here

If this minimum set of environment variables is used for initial setup and at a later stage changes are made in environment.yaml, which will have precedence?

[Stephan-P]

Only the outer quotes are removed; the inner value remains unchanged. The documentation will include a note explaining this behavior.

This is important for OMV compose, as this may enclose variables into (double) quotes. Running a Compose Check looking out for instances of double double quotes or /escape sequences within double quotes seems crucial.

[johaven]

If this minimum set of environment variables is used for initial setup and at a later stage changes are made in environment.yaml, which will have precedence?

Environment variables take precedence over environment.yaml. This is a generic and widely adopted configuration behavior across applications: environment variables override file-based settings. Therefore, later YAML changes only apply to values not already overridden by environment variables.

[johaven]

What needs to be understood is that environment.yaml is optional. As long as the minimum required environment variables are present in the environment, the server can start and run without environment.yaml.

[Stephan-P]

After a week of study and contemplation, today is my "let's try to integrate Collabora (CODE) behind external proxy" day.
I've got Nginx Proxy Manager (NPM) already running on my NAS, so 'behind external proxy' it must be.

Two additional variables set in environment.yaml

Sync-in environment.yaml

    collabora:
      enabled: true
      externalServer: https://collabora.MYDOMAIN.TLD

Nothing much changed in

Sync-in compose

---
# Date: 2026-06-13
# Installation instructions from https://sync-in.com/docs/setup-guide/docker/
# Compose file derived from https://raw.githubusercontent.com/Sync-in/server/refs/heads/main/docker/docker-compose.yaml

# include:
#  - ./config/nginx/docker-compose.nginx.yaml             # Using Nginx Proxy Manager, so DO DO NOT INSTALL an additional nginx
#  - ./config/collabora/docker-compose.collabora.yaml     # Install this separately, not included
#  - ./config/onlyoffice/docker-compose.onlyoffice.yaml   # Install this separately, not included
#  Enable next line when applications.appStore.repository in environment.yaml is set to 'local'
#  - ./config/sync-in-desktop-releases/docker-compose.sync-in-desktop-releases.yaml  

name: sync-in
services:
  sync_in:
    image: syncin/server:2
    container_name: sync-in
    restart: always
    environment:
      - PUID=${{ uid:"appuser" }}           # omv user appuser
      - PGID=${{ gid:"users" }}             # omv usergroup users
      - TZ=${{ tz }}                        # omv system time zone
      - INIT_ADMIN=true
      - INIT_ADMIN_LOGIN=ADMIN-USER1      # If needed, USE 'single quotes' so as to prevent including "Double quotes" in name
      - INIT_ADMIN_PASSWORD=ADMIN-PASSWORD2   # If needed, USE 'single quotes' so as to prevent parsing /escape sequences
    ports:
      - 8080:8080                           # External port:Internal port as defined in envirenment.yaml
    volumes:
      # IMPORTANT: environment.yaml is required for sync-in internal workings
      - ./environment.yaml:/app/environment/environment.yaml
      # - data:/app/data                    # Default configuration (Docker volume)
                                            # Recommended configuration (host directory)
      - ${{ sf:"data" }}/sync-in:/app/data  # omv share 'data'/sync-in:internal dataPath as defined in environment.yaml
                                            # Location for desktop releases if appStore is set to local in environment.yaml
      - ${{ sf:"data" }}/sync-in/desktop_releases:/app/static/releases:ro
    depends_on:
      - mariadb
    logging:
      driver: json-file
      options:
        max-size: 25m
        max-file: 5
    networks:
      - sync_in_network
      - web-proxy

  mariadb:
    image: mariadb:11
    container_name: mariadb
    restart: always
    command: --innodb_ft_cache_size=16000000 --max-allowed-packet=1G
    environment:
      MYSQL_ROOT_PASSWORD: DATABASE-PASSWORD    # also referred to in mysql.url in environment.yaml
      MYSQL_DATABASE: sync_in
    volumes:
      - mariadb_data:/var/lib/mysql
    networks:
      - sync_in_network

networks:
  sync_in_network:
    name: sync_in_network                   # IMPORTANT: Prevent automatic prefixing of the docker network name
    driver: bridge
  web-proxy:
    external: true

volumes:
  data:
  mariadb_data:
  desktop_releases:

Based upon the Sync-in-docker/config/collabora/compose file plus some suggestions coming from the Collabora Installation guide

Collabora CODE compose

name: collabora
services:
  code:
    container_name: collabora
    image: collabora/code
    restart: always
    environment:
      - PUID=${{ uid:"appuser" }}          # omv user appuser
      - PGID=${{ gid:"users" }}            # omv usergroup users
      - TZ=${{ tz }}                       # omv system time zone
      - user=${{ uid:"appuser" }}          # omv user appuser
      - username=ADMIN-USER2           # If needed, USE 'single quotes' so as to prevent including "Double quotes" in name
      - password=ADMIN-PASSWORD2         # If needed, USE 'single quotes' so as to prevent parsing /escape sequences
      - dictionaries=de_DE en_GB en_US fr_FR nl
                                           # extra_parms copied from sync-in collabora compose
      - extra_params=--o:ssl.enable=false --o:ssl.termination=false --o:logging.disable_server_audit=true --o:admin_console.enable=false
    ports:
      # - 9980:9980                          # Standard port redirection
      - '[::1]:9980:9980'                  # IPv6 port redirection as suggested by CODE Installation guide
    tty: true
    cap_drop:                              # capabilities drop copied from sync-in collabora compose
      - ALL
    cap_add:                               # capabilities add copied from sync-in collabora compose
      - SYS_CHROOT
      - SYS_ADMIN
      - FOWNER
      - CHOWN
    logging:
      driver: json-file
      options:
        max-size: 25m
        max-file: 5
    networks:
      - sync_in_network                    # join sync-in external network
      - web-proxy                          # join web-proxy external network

networks:
  sync_in_network:
    external: true
  web-proxy:
    external: true

Opening https://SERVER-IP:9980 returns OK, so CODE appears to be experiencing no issues.

Nginx Proxy Manager configurations:

For Sync-in:

For Collabora (based upon Sync-in nginx collabora config:

Sync-in is accessible via https://sync-in.MYDOMAIN.TLD and appears to be functioning alright.

Questions:

1. Docker UP for Collabora gives a warning: time="2026-06-13T14:00:29+02:00" level=warning msg="The \"pd\" variable is not set. Defaulting to a blank string.", which I don't understand. I guess I need to ask the Collabora Forum about expecting a variable pd?
2. I know that Collabora configurations may need to be made in a file /etc/coolwsd/coolwsd.xml but I cannot find this on my openmediavault system. Any ideas as to where to look, or better; are there ways to force the location of this file similar to - ./data:/app/data
3. Opening a file from within Sync-in, an attempt is made to open Collabora and the following error message is displayed: Oops there is a problem connecting to Collabora Online Development Edition (CODE): SecurityError: Failed to construct WebSocket: An insecure WebSocket connection may not be initiated from a page loaded over HTTPS. Any suggestions related to this?
4. Did I miss something important from sync-in-docker/config/nginx/nginx.conf that I should add to the NPM configuration?

Any support will be much appreciated.

[Stephan-P]

FRABJOUS DAY!!!

I'm in Collabora!!!
I am able to open files and changes are properly saved.

Magic moment

I decided to change the extra_params in the collabora-compose and everything fell into place

One warning remaining

I still get a warning when Collabora is started. See Collabora Forum.

@johaven, @Fogia-f, I think I can complete that guideline now.
@johaven shall I write that guideline here at the end of this long thread, or shall I close this thread and start a new one?

[johaven]

@Stephan-P => You can publish your tutorial here: awesome-sync-in

[Stephan-P]

@johaven styling issue: shall I put the different files in attachments or in code style in the tutorial as done above?

[johaven]

You need to create Markdown files and follow this guide: https://www.markdownguide.org/basic-syntax/

Edit: This is the language used here.

[Stephan-P]

I experienced a second stumbling related to a random password, this time with Collabora.
My random password value held a substring '$pd', which gave cause to the warning message "The "pd" variable is not set. Defaulting to a blank string."
Changing the $ for an S solved the issue.

So besides '/', '$' is also a special character that should not be used in password values. What else?
What is it with random character passwords that break the parsing of compose.yaml files?

[Stephan-P]

Sync-in Server on openmediavault 8

Openmediavault (OMV) is an open-source network attached storage (NAS) solution based on Debian Linux.
Sync-in is an open-source platform to store, share, collaborate, and sync files.
Among many other features, Sync-in includes WebDAV integration, as well as collaborative documents editing through integrations with Collabora Online and OnlyOffice. Openmediavault offers a wide range of network storage related services, as well as Kubernetes and Compose plugins for installing containerized apps.

This guide describes the steps towards installing Sync-in Server and Collabora Online as separate docker containers on an openmediavault 8 system, using its Docker Compose plugin as well as Nginx Proxy Manager (NPM) to expose the private network Web services to the internet.

Background

The Sync-in Server installation guide describes an elaborate hands-on process of downloading the latest release, issuing curl commands, modifying the configuration file 'envrionment.yaml', modifying the file 'compose.yaml' and issuing commands, all of which not being my cuppa tea.
As no Sync-in compose file is offered, I set towards attempting to integrate this process into openmediavault Compose. I had hopes of incorporating the 'environment.yaml' into compose environment variables, but alas that will not do, as Sync-in components will require access to this file during the setup process. As a result, this guide will involve some manual steps, as well as editing the Sync-in configuration file 'environment.yaml'.

Prerequisites

• An openmediavault 8 NAS set up and running
  • With Docker Compose plugin installed
  • With Nginx Proxy Manager docker container installed and running
• Remote access to the NAS using Filezilla or WinSCP

Outline of steps

1. Installation of Sync-in docker using Compose
2. Proxy Host configuration for Sync-in using NPM
3. Installation of Collabora Online docker using Compose
4. Proxy Host configuration for Collabora Online using NPM

---

1. Installation of Sync-in docker using Compose

• Download the latest 'sync-in-compose.zip' from Sync-in server releases to your PC
• Also download the full Sync-in 'environment.dist.yaml' configuration template
• Open your openmediavault workbench - Services - Compose - Files
• Create a new Compose file called 'sync-in-docker'
• Copy the contents of the 'docker-compose.yaml' from the zip file into the OMV Compose File editor
• Save the newly created compose file for now
• Compose will now have created a folder '/appdata/sync-in-docker' with some files
• Use Filezilla/WinSCP to remote access this folder '/appdata/sync-in-docker'
• Copy the contents of the downloaded 'sync-in-compose.zip' in there, which will result in the following structure:

/appdata/sync-in-docker/
├── config
│ ├── collabora
│ │ └── docker-compose.collabora.yaml
│ ├── nginx
│ │ ├── collabora.conf
│ │ ├── docker-compose.nginx.yaml
│ │ ├── nginx.conf
│ │ └── onlyoffice.conf
│ ├── onlyoffice
│ │ └── docker-compose.onlyoffice.yaml
│ └── sync-in-desktop-releases
│ ├── docker-compose.sync-in-desktop-releases.yaml
│ └── update.sh
├── docker-compose.yaml
└── environment.yaml

• (Much of this will not be used, but does offer a nice reference)
• Skipping the default minimal setup and going full whammy right away;
  open the file 'environment.yaml' and replace its full contents with that of the downloaded 'environment.dist.yaml'
• Search for the following items and edit these ALL_CAPS valueas with your own (random generated) ones:

...
mysql:
  url: 'mysql://root:ALPHANUMERIC_DB_KEY@mariadb:3306/sync_in'
...
auth:
  encryptionKey: 'ALPHANUMERIC_ENCRYPTION_KEY'
  token:
    access:
      secret: 'ALPHANUMERIC_ACCESS_KEY'
    refresh:
      secret: 'ALPHANUMERIC_REFRESH_KEY'
...
applications:
  files:
    dataPath: /app/data     # Sync-in internal data path. Needs to be exposed to SMB share in Compose
...
    sampleDocuments: [opendocument, microsoft]
...
    collabora:
      enabled: true
      externalServer: https://collabora.YOUR-DOMAIN.TLD
...

• Return to the OMV workbench - Services - Compose - Files
• Edit the compose file 'sync-in-docker' as follows, changing the ALL_CAPS credentials for your own:

include:
#  - ./config/nginx/docker-compose.nginx.yaml             # Not installed, as we'll be using Nginx Proxy Manager (NPM)
#  - ./config/collabora/docker-compose.collabora.yaml     # To be installed separately, not included
#  - ./config/onlyoffice/docker-compose.onlyoffice.yaml   # To be installed separately, not included
#  Enable the next line when applications.appStore.repository in environment.yaml is set to 'local'
#  - ./config/sync-in-desktop-releases/docker-compose.sync-in-desktop-releases.yaml  

name: sync-in
services:
  sync_in:
    image: syncin/server:2
    container_name: sync-in
    restart: always
    environment:
      - PUID=${{ uid:"appuser" }}           # omv user 'appuser'
      - PGID=${{ gid:"users" }}             # omv usergroup 'users'
      - TZ=${{ tz }}                        # omv system time zone
      - INIT_ADMIN=true
      - INIT_ADMIN_LOGIN=SYNC-IN-ADMIN      # AVOID $, / or other special characters that may trigger undesired parsing
      - INIT_ADMIN_PASSWORD=SYNC-IN-PASS    # AVOID $, / or other special characters that may trigger undesired parsing
    ports:
      - 8080:8080                           # External port:Internal port as defined in environment.yaml
    volumes:
      - ./environment.yaml:/app/environment/environment.yaml  # IMPORTANT: environment.yaml is required for sync-in internals
      - ${{ sf:"data" }}/sync-in:/app/data  # omv share 'data'/sync-in:internal dataPath as defined in environment.yaml
                                            # Location for desktop releases if appStore is set to local in environment.yaml
      - ${{ sf:"data" }}/sync-in/desktop_releases:/app/static/releases:ro
    depends_on:
      - mariadb
    logging:
      driver: json-file
      options:
        max-size: 25m
        max-file: 5
    networks:
      - sync_in_network
      - web-proxy                           # Common docker bridge network re. Nginx Proxy Manager 

  mariadb:
    image: mariadb:11
    container_name: mariadb
    restart: always
    command: --innodb_ft_cache_size=16000000 --max-allowed-packet=1G
    environment:
      MYSQL_ROOT_PASSWORD: ALPHANUMERIC_DB_KEY    # Same ALPHANUMERIC_DB_KEY as in mysql.url in environment.yaml
      MYSQL_DATABASE: sync_in
    volumes:
      - mariadb_data:/var/lib/mysql
    networks:
      - sync_in_network

networks:
  sync_in_network:
    name: sync_in_network                   # IMPORTANT: Prevent automatic prefixing of the docker network name
    driver: bridge
  web-proxy:                                # Common docker bridge network re. Nginx Proxy Manager 
    external: true

volumes:
  data:
  mariadb_data:
  desktop_releases:

• Save the compose file
• Compose Check for issues, Compose Pull and Compose UP

If all is well, Sync-in should be accessible through http://YOUR-SERVER-IP:8080 using above ADMIN credentials.

2. Proxy Host configuration for Sync-in

• Open your Nginx Proxy Manager (NPM) instance
  Note: NPM and Sync-in share the same docker bridge network 'web-proxy', so we can reference Sync-in by its container name
• Create a new Proxy Host:
  • Details:
    • Domain name: sync-in.YOUR-DOMAIN.TLD
    • Scheme: http
    • Forward hostname/IP: sync-in
    • Forward port: 8080
    • Option: Block common exploits
    • Option: Websockets support
  • SSL:
    • SSL Certificate: sync-in.YOUR-DOMAIN.TLD
    • Option: Force SSL
    • Option: HTTP/2 Support
    • Option: HSTS enabled
• Save

If all is well, Sync-in will now be accessible as well through https://sync-in.YOUR-DOMAIN.TLD.

3. Installation of Collabora Online docker using Compose

• Open your openmediavault workbench - Services - Compose - Files
• Create a new Compose file called 'collabora' with the following contents:

name: collabora
services:
  code:
    container_name: collabora
    image: collabora/code
    restart: always
    environment:
      - PUID=${{ uid:"appuser" }}          # omv user 'appuser'
      - PGID=${{ gid:"users" }}            # omv usergroup 'users'
      - TZ=${{ tz }}                       # omv system time zone
      - user=${{ uid:"appuser" }}          # omv user 'appuser'
      - username=COLLABORA-ADMIN           # AVOID $, / or other special characters that may trigger undesired parsing
      - password=COLLABORA-PASSWORD        # AVOID $, / or other special characters that may trigger undesired parsing
      - dictionaries=de_DE en_GB en_US es_ES fr_FR it nl pt_BR pt_PT ru
                                           # extra_parms (adapted from sync-in collabora compose)
      - extra_params=--o:ssl.enable=false --o:ssl.termination=true --o:logging.disable_server_audit=true --o:admin_console.enable=true
      - domain=collabora.YOUR-DOMAIN.TLD
    ports:
      - 9980:9980                          # Standard port redirection
    tty: true                              # keep the container running, equivalent to -t command line option
    cap_drop:                              # capabilities drop (as per sync-in collabora compose)
      - ALL
    cap_add:                               # capabilities add (as per sync-in collabora compose)
      - SYS_CHROOT
      - SYS_ADMIN
      - FOWNER
      - CHOWN
    logging:
      driver: json-file
      options:
        max-size: 25m
        max-file: 5
#    volumes:                                # IMPORTANT: TO BE UNCOMMENTED LATER ON
#      - ./coolwsd/coolwsd.xml:/etc/coolwsd/coolwsd.xml:rw  # mount local copy of coolwsd.xml config file
    networks:
      - sync_in_network                    # Common docker bridge network re. Sync-in
      - web-proxy                          # Common docker bridge network re. Nginx Proxy Manager

networks:
  sync_in_network:
    external: true
  web-proxy:
    external: true

• Save the compose file
• Compose Check for issues, Compose Pull and Compose UP

The following steps are neccessary to make a copy of the docker internal Collabora configuration file into a location that is better accessible. For this the Collabora docker container needs to be UP.

• Use Filezilla/WinSCP to remote access OMV's /appdata/collabora
• Create a subfolder ‘coolwsd’
• Use the context menu option “Static Custom Commands” - “Enter” and paste the command:
  docker cp collabora:/etc/coolwsd/coolwsd.xml ./coolwsd/coolwsd.xml
• Check if the file /appdata/collabora/coolwsd/coolwsd.xml is in place
• Ambitious people can get their hands dirty with advanced Collabora configuration. I didn't find anything appealing.
• With /appdata/collabora/coolwsd/coolwsd.xml in place, Filezilla/WinSCP can be closed

Return to your openmediavault workbench - Services - Compose - Files

• Docker Compose DOWN collabora
• Open the collabora compose file and remove the # comment marks in front of the following two lines:

   volumes:
     - ./coolwsd/coolwsd.xml:/etc/coolwsd/coolwsd.xml:rw  # mount local copy of coolwsd.xml config file

• Make sure that all indents are consistent, as this is a requirement for compose.yaml files
• Save the compose file
• Compose Check for issues and Compose UP

4. Proxy Host configuration for Collabora

• Open your Nginx Proxy Manager (NPM) instance
  Note: NPM and Collabora share the same docker bridge network 'web-proxy', so we can reference collabora by its container name
• Create a new Proxy Host:
  • Details:
    • Domain name: collabora.YOUR-DOMAIN.TLD
    • Scheme: http
    • Forward hostname/IP: collabora
    • Forward port: 9980
    • Option: Block common exploits
    • Option: Websockets support
  • Custom Locations:
    • /browser/
      • Scheme: http
      • Forward hostname/IP: collabora
      • Forward port: 9980
    • /hosting/
      • Scheme: http
      • Forward hostname/IP: collabora
      • Forward port: 9980
    • /cool/
      • Scheme: http
      • Forward hostname/IP: collabora
      • Forward port: 9980
  • SSL:
    • SSL Certificate: collabora.YOUR-DOMAIN.TLD
    • Option: Force SSL
    • Option: HTTP/2 Support
    • Option: HSTS enabled
• Save
• In the NPM Proxy Hosts list you can click the newly created host 'collabora' and it will open with a mere 'OK', indicating its status.
  Collabora in itself is a quiet servant ;-)

If all is well, you can now create new OpenDocument or Microsoft Office files in Sync-in and open them in Collabora Online.

Result

Sync-in and Collabora Online are now installed as separate docker containers in openmediavault 8 Compose and proxied and SSL-terminated by Nginx Proxy Manager.
The two containers can be managed from Compose. Take note that Collabora is dependant upon sync_in_network, meaning that Collabora can only be UP-ed after Sync-in, and Sync-in cannot be DOWN-ed if Collabora is still up.
Therefor observe the following UP-DOWN cycle:

1. UP Sync-in
2. UP Collabora
3. DOWN Collabora
4. DOWN Sync-in

[johaven]

You can fork the repository and open a pull request, just like with any other repository.

[Stephan-P]

I thought that you'd have fixed something, so I tried and failed again this morning:

[johaven]

I thought it was written in large enough print :) The standard procedure is to fork, create a branch, and submit a pull request, just like with other repositories. To speed things up, I've given you permission to post directly.

[Stephan-P]

Thanks for inviting me. That'll remove a barrier.
The screenshots tell (in the left bottom corner) that "An unexpected error occurred" while I was attempting to fork. Coupled with the other pair of screenshots saying "Uploads are disabled", I figured that there may be something off in the configuration of this new repo.

[johaven]

This is actually the expected GitHub workflow. Since you’re not the owner of the repository and don’t have write access, you can’t push changes directly to it. Instead, you need to fork the repository, make your changes in your fork, and then open a pull request for review.

That’s exactly the same process you already follow on sync-in/server when you submit translation updates.