Nethserver-collabora CODE testing and discussion

mark_nl · September 24, 2018, 10:52am

Found some info, seems you need a key file even if ssl is disabled i.e HTTP is used:

LibreOffice/online/blob/master/wsd/README#L185


      
          
              openssl req -sha256 -new -key key.pem -out csr.pem
          
              # change "unique_subject = yes" to "unique_subject = no" in demoCA/index.txt.attr
              # otherwise you'll get the following error:
              #   failed to update database
              #   TXT_DB error number 2
          
              openssl ca -keyfile private/ca.key.pem -cert ca.cert.pem -extensions usr_cert -notext -md sha256 -in csr.pem -out cert.pem
          
          HTTPS is the default. HTTP-only mode can be enabled with --disable-ssl
          configure option.
          
          If you plan to hack on loolwsd, you probably want to familiarize
          yourself with loolwsd's --o:num_prespawn_children switch, and the 'connect'
          test program.
          
          For interactive testing, you can use the 'connect' program. It accepts
          "commands" from the protocol on standard input.

Also managed to build loolwsd from source but it’s not working yet, curl pit seems to be setting up the jail chroot in a proper way. This is done quite unconventional by running loolwsd-systemplate-setup script at install (%post):

github.com

LibreOffice/online/blob/3.3.1-final/loolwsd-systemplate-setup

#!/bin/bash

test $# -eq 2 || { echo "Usage: $0 <chroot template directory for system libs to create> <LO installation directory>"; exit 1; }

# No provision for spaces or other weird characters in pathnames. So sue me.

CHROOT=$1
INSTDIR=$2

test -d "$INSTDIR" || { echo "No such directory: $INSTDIR"; exit 1; }

mkdir -p $CHROOT || exit 1

CHROOT=`cd $CHROOT && /bin/pwd`
INSTDIR=`cd $INSTDIR && /bin/pwd`

cd / || exit 1

(
# Produce a list of file names, one per line, that will be copied

This file has been truncated. show original

Need to figure out what it does…

pagaille · December 20, 2018, 8:52pm

Hey @mrmarkuz, did I say thank for that module ?

I successfully installed it using the manual installation following your first post but recently upgraded to NC 15, which broke the installation. Now I get a white page when I create or open a document.

I tried to install your nethserver-collabora module but same result.

The admin page leads to NC’s usual file page, like if there is a redirect.

In Apache’s access_log I see 500 errors when acceding to the richdocumentsapp (when opening a document file).

Do you observe this behaviour as well ?
Matt

mrmarkuz · December 20, 2018, 11:47pm

First, thanks for testing!

I think I could reproduce it. Fresh install worked but updating is a problem.
After updating CODE from 3.4 to 4.0 the updated /etc/loolwsd/loolwsd.xml (including the new paths to collabora 6 instead of 5.3) is saved as loolwsd.xml.rpmnew but loolwsd continues working with the old loolwsd.xml and that leads to the white screen.

Workaround until I can provide an updated module, I’ll update the wiki too.

mv /etc/loolwsd/loolwsd.xml /etc/loolwsd/loolwsd.xml.old
mv /etc/loolwsd/loolwsd.xml.rpmnew /etc/loolwsd/loolwsd.xml`
signal-event nethserver-collabora-update

As you use a new default config file, you have to set the password again, see the wiki

I couldn’t reproduce this one, do you use a vhost for nextcloud?

pagaille · December 21, 2018, 4:04am

Everything working, THANKS

Indeed. Using the “real” server name worked.

danb35 · January 12, 2019, 11:51am

Curious if this is currently installing CODE 4.0–document editing using the mobile client apps would be a big win.

mrmarkuz · January 12, 2019, 11:54am

Yes, it should use the newest one from collabora repo.

danb35 · January 12, 2019, 1:50pm

Cool, once 7.6 hits the subscription repo I’ll give it a try.

Why does the wiki call for yum install nethserver-nextcloud as a separate step? Seems it’d be simpler to just have it as a Requires: for nethserver-collabora.

mrmarkuz · January 12, 2019, 2:18pm

You are right, it’s the same with onlyoffice.
The intention was to be extra flexible and have the possibility to have them on separate machines.

danb35 · January 12, 2019, 2:22pm

Ah, that does make some sense too–hadn’t thought about that scenario.

dnutan · January 12, 2019, 2:24pm

Or if other applications supporting Collabora CODE are integrated in the future.

giacomo · January 14, 2019, 9:33am

We have a testing machine running collabora integrated with Nextcloud.
It’s not rock solid, but it works for simple documents.

An alpha release it’s in my agenda since long time, let’s see if now it is stable enough

I hope also webtop will use it. Ehi @webtop_team any news on it?

pagaille · January 14, 2019, 11:47am

That’s also my experience : ok for small documents but even integrating a picture or two leads to annoying display and functional bugs. Much better than nothing though.

I wish a full HTML5 editor even with less features (except collaborative editing which is a must) exists.

danb35 · January 14, 2019, 11:50am

Have you tried OnlyOffice as well? It seems to deal well with more complex documents.

giacomo · January 15, 2019, 7:47am

Probably OnlyOffice works a little better, but it can’t be installed on NS without replacing the default nodejs stack.

danb35 · January 15, 2019, 1:52pm

…or just installing the nethserver-onlyoffice module?

mrmarkuz · January 15, 2019, 1:57pm

Onlyoffice wiki recommends to install a newer nodejs now:

https://wiki.nethserver.org/doku.php?id=onlyoffice#install_nodejs_repo

You may disable spellchecker or use higher nodejs version to not have high CPU load, see Nextcloud Onlyoffice Nodejs and npm version

danb35 · January 15, 2019, 2:00pm

Ah, that’s what I get for skimming.

mrmarkuz · January 15, 2019, 2:04pm

Do you see a problem here?

IIRC some of my howtos recommend installing newer nodejs too.

giacomo · January 15, 2019, 2:11pm

Yes: we should not replace RHEL stack otherwise we loose all the security updates.

To use a newer nodejs version, we should use SCL. But I didn’t try onlyoffice with it.

mrmarkuz · January 15, 2019, 6:26pm

@LayLow already tried that here, but the onlyoffice documentserver requires nodejs and rh-nodejs8 conflicts with nodejs.
It seems to be a known bug: 1637922 – Conflict when installing alongside stock NodeJS 6 on EL7