What to install the Collabora online on our local and try with WOPI browser editing

Dear Team,

I want to install the Collabora online server on-premises, for doing this do we need a licence to have? or I can i install the Docker version on a windows VM?

Hi @chiranjeevi.yadav welcome to collabora online forum

I want to install the Collabora online server on-premises, for doing this do we need a licence to have? or I can i install the Docker version on a windows VM?

No licence key is needed to install and evaluate — CODE is the free build: docker pull collabora/code. The supported Collabora Online uses a key and a different image (registry.gitlab.collabora.com/collabora-online/docker).

The server is Linux-only; there’s no Windows build. Docker Desktop/WSL2 is fine for a first look, but use a Linux VM for anything beyond that.

For WOPI browser editing, quickest route is to point CODE at an existing host (Nextcloud, ownCloud, OpenCloud, Seafile). For your own app, follow the step-by-step tutorial at sdk.collaboraonline.com. You’ll need HTTPS in front of coolwsd, and your WOPI host allowed in coolwsd.xml.

To advise properly: which WOPI host, roughly how many concurrent users, and is this an evaluation or production?

On the licence itself whther your use needs a subscription , especially for commercial use, is a commercial/legal question we can’t answer on the community forum. Please contact sales@collaboraoffice.com.

Thanks Darshan,

We install the Collabaro - CODE on our Linux vm, we have built WOPI host, for testing the browser editing document and now we need to set the editor with below changes. Please help us, how to get the editor as per our business rules.

Basically, we don’t want the end-users to have below options on the ribbon. So I listed the against each menu, what we need to exclude.

  1. File —> Print
    —> Download
    —> Repair
    —> Security label
    —> Signature
    —> Properties

  2. Insert —> QR and Barcode

  3. References —> update All

  4. Review —> comment
    —> Record
    —> Compare
    —> Accesibility Check

  5. Fomat —> Theme

  6. View —> Status Bar
    —> Dark Mode

  7. Help

Note: I am happy to share the coolwsd.xml file if required.

Thanks

Hi @chiranjeevi.yadav,

Before going further: CODE is the free community build meant for home users and evaluation. If this is going into business use, please contact sales@collaboraoffice.com first if you haven’t already.

On your question: this isn’t a coolwsd.xml setting, so no need to share it. All of this is done from your WOPI host.

In your CheckFileInfo response (server enforced, use these where they exist):

  • Print: “DisablePrint”: true
  • Download: “DisableExport”: true
  • Repair: “HideRepairOption”: true
  • Record and Compare: “HideChangeTrackingControls”: true

For the rest, send postMessages to the editor iframe after you get App_LoadingStatus with Document_Loaded:

const send = (MessageId, Values) =>
frame.postMessage(JSON.stringify({ MessageId, SendTime: Date.now(), Values }), ‘*’);

[‘.uno:SetDocumentProperties’, ‘.uno:Signature’, ‘.uno:SecurityLabel’,
‘.uno:InsertQrCode’, ‘.uno:UpdateAll’, ‘.uno:InsertAnnotation’,
‘.uno:AccessibilityCheck’, ‘.uno:ThemeDialog’]
.forEach(id => send(‘Hide_Command’, { id }));

send(‘Hide_Button’, { id: ‘showstatusbar’ });
send(‘Hide_Button’, { id: ‘toggledarktheme’ });
send(‘Hide_NotebookTab’, { id: ‘Help’ });

Note that postMessage hiding is UI only. Print and download are the ones that need real blocking, which is why those use the Disable* flags.

Docs: Making sure you're not a bot! and Making sure you're not a bot!

Thanks Darshan,

We are currently conducting an on-premises Proof of Concept (POC) with Collabora Office in our development environment. If it work well for our business users, and both our procurement and cybersecurity teams are aligned to proceed with the purchase based on this.

To help us finalize this process, please assist us in successfully completing the POC. Once the purchase is finalized, we plan to roll out the installation to our other environments.