Improvements for Nethserver-Collabora

Note : you still need to set it up as described in README.rst
EDIT: above applies to version nethserver-collabora-0.1.2-1.ns7.noarch not the wip-package

To get rid of most additional steps to configure nethserver-collabora and make it more stable at updates is what this "TLC"efffort is about. :grinning:

1 Like

Well, tried the first round yesterday, but found out that probably the droplet I created was too small in RAM. Will retry in some hours :slight_smile:

1 Like

same for me, someone has a clue ?

As @mrmarkuz mentioned above it seems to be a upstream bug in the richdocuments netxtcloud app

2 Likes

In the CODE repo there’s only version 6.0 and 6.4. I’d like to get some dictionaries for our version 6.2. I don’t understand because 6.2 should be LTS from what I saw here.

Install code repo:

sudo yum-config-manager --add-repo https://www.collaboraoffice.com/repos/CollaboraOnline/CODE-centos7

EDIT:

Version 6.4 working here with dictionaries.

Collabora is named like collaboraofficebasis6.4* whereas the dictionaries are named like

yum install collaboraoffice6.4-dict-en collaboraoffice6.4-dict-de collaboraoffice6.4-dict-es

1 Like

Did not take a possible LTS version in to consideration, i’ll gues it for collabora-subscribtion users (or build it yourself).
Did two brief update tests from 6.0 > 6.2 > 6.4 and one 6.0 > 6.4, it did not break but did only basic functional tests.
If this makes it to release i’d propose to include CODE/collabora office 6.4 in the nethforge repo.

1 Like

Fully agree :+1:

3 Likes

IMHO it is ready to go through the development/audit cycle

@giacomo do you prefer I open an issue in Nethserver/dev for this (or not),
asking because it is a nethforge module.

2 Likes

I’d say yes, it will help you tracking the progress. I we will add the forge tag to the issue :slight_smile:

2 Likes

Does this apply to all services in the (update) event ?:

event_services($event, qw(
               httpd reload
               loolwsd restart
));

Goal is to set/check the WopiUrl after httpd reload

EDIT Sorry RTFM:
https://docs.nethserver.org/projects/nethserver-devel/en/latest/events.html#order-of-implicit-actions

1 Like

this is the goal indeed action 91 will be triggered after the services restart

1 Like

Updated another server, worked without issues. :clap:

2 Likes

With the last commit nethserver-collabora works like intended;

The default wopiUrl (collabora.server_domain) created on installation needs to be resolvable. :thinking:

Included it in the /etc/hosts template, can not think of a cleaner method.

1 Like

I updated a Nethserver at work with Collabora 6.4 because there were problems with formattings and it worked and solved the format issues in first tests.

1 Like

Can some of you review the changes made in the PR on github?

To make a bit of a quiz: found one bogus IF statement myself…

cc/ @Amygos

Like to have “special permission” from @giacomo or @davidep on the Add default collabora WopiUrl to server-hostnames part…

2 Likes

You now have write access to repo so you can merge and request for review.
I will take a look to it, but it will require a little time.

In the meanwhile, @stephdl could you please take a look?

1 Like

Take your time :grinning:
As long as needed, I’m not in a hurry.

Pinged here because could not add reviewers and need some auditing going on in time. :yum:

1 Like

Will do it asap, currently in holidays but interested mainly because I installed it recently.

Either next week or sooner if possible.

3 Likes