Build OnlyOffice from source code (2024-05)

Introduction

Onlyoffice is an online Office suite based on Web. It lets you to edit Microsoft Office documents such as docx, pptx, xlsx and other Open Document files such as odt, ods and odp.

In our Zimbra and Nextcloud SaaS service we offer Onlyoffice integration in order to view and edit documents. This article shows technically how to build OnlyOffice from the source code.

In addition to build OnlyOffice it will be modified to increase the default 20 simultaneous connections maximum limit to 99999 connections. It’s similar to an OnlyOffice without any limits. This is possible thanks to OnlyOffice AGPL license that let us to modify it.

This build has been possible thanks to bTactic I+D department.

Build instructions

Download

If you don’t have the technical expertise to build OnlyOffice yourself you can download our built packages from OnlyOffice v8.0.1.31-btactic release .

You are also advised to check our many services which include OnlyOffice integration such as Nextcloud and Zimbra. 

(Warning: This package is not an official OnlyOffice build. If you find problems with it do not seek help on OnlyOffice official forums/trackers. In any case do it if you have manage to reproduce them in the original source code or OnlyOffice original binary packages.)

Supported distros

The package should install fine on Debian 11.
The package might also work on other Debian/Ubuntu based distros.

Usage

Just use standard documentation on how to install official Ubuntu packages such as: https://helpcenter.onlyoffice.com/installation/docs-community-install-ubuntu.aspx

However do not add OnlyOffice package repository and when you are asked to install onlyoffice-documentserver package you should do instead::

sudo apt install /path/to/onlyoffice-documentserver_8.0.1-31-btactic_amd64.deb

5 thoughts on “Build OnlyOffice from source code (2024-05)”

    • I did my own builds with and without server parametre as I explain in the development blog ( onlyoffice-no-limit-2024-05.md) and they both lasted roughly 2 hours in Github Actions.
      There was not a build speed up as you describe.

      I kept the build all recipe that I was once advised it was going to be safer to build eveything (or in other words it should be less prone to not being able to be built).
      The day they manage to avoid to build entirely Qt just for qmake (or was it cmake?) we will save around 1 hour of build time (in my own 2 hours tests).

      Reply
      • I realized that there’s no escaping build of QT unfortunately. I get errors at least starting with x2t in FileConverter not being built if I skip make/make install of QT.
        However, I managed to reduce the build time to 85 minutes exactly (ran with `time ./onlyoffice-package-builder.sh …`), after a minor edit to `tools/linux/automate.py` in “build_tools”, basically removing “builder” and “desktop” from the “modules” array towards the end of the file (not only passing “server” to automate.py from Dockerfile).
        Try it and see for yourself.

        Next step would be to see how to use `tools/linux/use_system_qt.py` properly. I tried but failed, because I think I first need to install system qt (dev?) libs via deb packages. But the question is where to get them for obsolete ubuntu 16.04 image. 🙂

        Cheers

        Reply

Leave a Comment