Collabora Online Development Edition (CODE)

[msbt]

Would be nice to have the option to chose if it's going to be installed alongside nextcloud or not, since it will probably hog a lot of resources. Did you make progress installing it? I was testing that repo and couldn't get it to work either.

[nebulon]

Yeah the idea would be to only start the collabora process, if the nextcloud addon is enabled. Will see if that is easy to detect.

[saglagla]

@nebulon said in Collabora Online Development Edition (CODE):

Yeah the idea would be to only start the collabora process, if the nextcloud addon is enabled. Will see if that is easy to detect.

Oh, it would be nice !

@nebulon said in Collabora Online Development Edition (CODE):

For anyone interested in collabora, are there any use-cases currently outside of the nextcloud binding? If not, then we consider to just bundle it pre-installed with the nextcloud package. This would be probably most convenient for most users. Please let us know, if there are concerns about this.

For a first approach, the stand alone part would be intresting in a first time. Then, a integration in the NextCloud container could be intresting.

[nebulon]

Yes, after consideration, we might first go with a standalone approach as we don't want to pull in too much into the nextcloud package, which we then have to support forever. This would mean one has to install the collabora app on its own domain and put that domain into the nextcloud's plugin configuration dialog. That is also more aligned to how the nextcloud plugin works anyways. Still hoping to figure out how we can whitelist Cloudron domains at https://github.com/makayabou/install-nextcloud-collabora/blob/master/loolwsd.xml#L74 out of the box, to avoid further configuration burden.

I have collabora working now as a standalone app already, just needs final touch ups.

[msbt]

That's very nice to hear @nebulon! Is it also possible to use one Collabora installation with multiple Nextcloud installations?

[nebulon]

We have released an initial package for CODE in the store, which works together with the NextCloud plugin (as the WOPI host)
It has to be installed as a separate app, to avoid the risk of pulling too much into the NextCloud app itself.
I tried to make it rather self-describing how it is to be used and added a small UI to configure it. Maybe it can support other apps besides NextCloud in the future. Also unfortunately I was not able to make it work with multiple NextCloud instances, if someone has successfully done that, please let me know.

Any feedback welcome.

[msbt]

Thanks for the update and the good work. Unfortunately I'm still getting "Unauthorized WOPI host. Please try again later and report to your administrator if the issue persists."

I've installed the CODE app, added the nc domain in the gui and activated the collabora app and added the CODE url in there. Am I missing something?

edit: Log says "Aug 05 15:41:31 wsd-00016-00042 2018-08-05 15:41:31.511409 [ websrv_poll ] WRN WOPI host did not pass optional access_token_ttl| wsd/FileServer.cpp:608"

[nebulon]

One thing I could think of is, that in the nextcloud app, you have to use https://code.domain.com and as it currently stands inside the code ui you have to remove the https:// part. Is that causing your issue? I should improve that regardless though.

[msbt]

Ah right, that did the trick! So to recap:

Enter the Nextcloud url without https:// in the Cloudron Collabora app. After that I tested both, CODE url with and without https:// in NC, there it doesn't seem to matter, so there's that

Cheers!

[necrevistonnezr]

This post is deleted!

[msbt]

@necrevistonnezr you need to click on the office app, login with your cloudron credentials and add the nextcloud url in there (without https://)

[msbt]

@nebulon I just tried adding several domains to collabora and it seems to be working. You just need to seperate them with a pipe, like
nc1.domain1.com|nc2.domain2.com
can you confirm that?

[nebulon]

@msbt ah that could very well be true, the input field actually allows a regexp. I will see if I can make that input a bit more user friendly and maybe pre-setup the value with *.domain.com for the Cloudron, as that might be the most common use-case.

[necrevistonnezr]

@msbt said in Collabora Online Development Edition (CODE):

@necrevistonnezr you need to click on the office app, login with your cloudron credentials and add the nextcloud url in there (without https://)

Thanks! I had missed that step indeed. Works now.

[nebulon]

I pushed a new version which gives more details on the domain setup. It also mentions how to use it for more than one domain.

[FTLAUDMAN]

This is like Christmas for me, guys. Thank you!! Works perfectly for me so far. Full implementation in less than 5 minutes. By far the easiest way to setup Collabora, anywhere.

[uiharu]

Thank you so much. This is amazing!

[saglagla]

It's really amazing ! Thank you guy's !

[necrevistonnezr]

If you now add Fulltext Search (https://forum.cloudron.io/post/1596), Cloudron's Nextcloud package would be unparalleled, I think....

[ruihildt]

@nebulon I have suggestions for improvements, where is the best place to write those?