So it is entirely possible to remove the 20 connections limit in the Community Document Server (CDS).
However there seems to be a bit of a ‘gotcha’. This is my, probably incomplete, understanding of what I have observed so please do comment if you have better knowledge or experience or can see a way around it.
CDS installs as a Nextcloud (NC) app using the same OnlyOffice (OO) Connector app as full OO but with the server entry pointing to the app instead of the OO separate server.
This means that CDS is using the same resources and database as NC
The problem is that the OO engine (used by CDS) works by writing every keystroke made while editing to the database (oc_documentserver_changes in the case of CDS). Periodically the changes get written back to the file and flushed from the db.
This means that if you have 20 users all typing away there can be a massive load on the MySQL server and this may slow down everything else in NC.
With full OO you are running it as a separate process using a separate database which should mean it works slightly better even if it is on the same host. And this probably explains why they recommend installing OO on a completely separate machine.
SO although you can increase the users easily in CDS, you might not want to.
Anyone else seen this effect.