Package Details: collabora-online-server-nodocker_es 6.4.11-1

Git Clone URL: https://aur.archlinux.org/collabora-online-server-nodocker.git (read-only, click to copy)
Package Base: collabora-online-server-nodocker
Description: None
Upstream URL: https://www.collaboraoffice.com/code/
Licenses: MPL
Submitter: theYinYeti
Maintainer: theYinYeti
Last Packager: theYinYeti
Votes: 11
Popularity: 1.02
First Submitted: 2017-10-13 20:12
Last Updated: 2021-10-05 06:58

Required by (0)

Sources (120)

Pinned Comments

theYinYeti commented on 2018-01-04 08:33

About upstream: 1º Upstream does not maintain past versions of packages, so I have no choice but to follow new releases. 2º Upstream does not advertise minor/patch releases. These are the reasons why the PKGBUILD is made to adapt itself the best it can to the current upstream situation, whatever it is. If an incompatible change occurs, do not hesitate to mark the package as “obsolete”: I will get notified, and fix the the package as soon as my free time allows. Cheers :-)

Latest Comments

1 2 3 4 5 Next › Last »

9-r commented on 2021-10-12 09:54

@andrej: the nginx and apache configs you mention are just tls-reverse-proxy examples and should work outside of docker as well. collabora-office can establish encrypted connection by itself if configured correctly and supplied with certs, so it depends on your setup if you need use these examples.

nexcloud-systemd-timers just runs the cron jobs required by nextcloud and has nothing to do with collabora-office.

The package does not require nextcloud because it just supplies the online document editing functionality independently from nextcloud and can be used with other cloud file storage systems as well.

For differences between collabora and libreoffice consulting the search engine of your choice should answer the question.

andrej commented on 2021-08-22 01:20

Is there an ArchWiki page for this? I could only find this short chapter on the Nextcloud page, which is not very informative. For example, can the Apache and Nginx configuration from the Docker chapter be applied also in the non-Docker case? Which of the other tips and instructions apply? (Should one install nextcloud-systemd-timers etc.?)

The package dependencies are also a bit of a mystery. For example, why doesn’t this depend on nextcloud from community? That looks concerning, because it’s unclear to what extent it can share an existing nextcloud configuration without too much duplication + hassle.

On the same topic: How is this package related to libreoffice-online? IIUC, libreoffice-online (in its vanilla form) is just a server serving a HTML5 office suite without any cloud access / online editing, which can store files on the end users’ local disks. Does CODE / Collabora reuse / depend on LOOL or not? Or does it contain a modified version of it?

Can the CODE functionality be configured (perhaps in a somewhat more modular way) using a combination of nextcloud and libreoffice-online?

celogeek commented on 2021-03-14 23:29

Hi, I've got trouble with capabilities on loolforkit and loolmount.

Here what I do to manually fix the permission issues:

setcap cap_chown,cap_fowner,cap_sys_chroot,cap_mknod=ep /usr/bin/loolforkit
setcap cap_sys_admin=ep /usr/bin/loolmount

this even works in a systemd-nspawn system.

I see some permission already there for loolforkit. it seems to needed chown also. And loolmount need admin for mount/umount.

mqs commented on 2021-02-26 13:47

@theYinYeti, you should be able to strip all the makedependencies that are already in base-devel and base, as those can be assumed as installed for all packages.

Specifically, that means you can drop bzip2, coreutils, gawk, grep, gzip, sed, systemd, tar, util-linux, xz (see base). libcap and curl are also transitively included via iputils and libelf.

The only thing that is left then is fontconfig.

To be clear, I am only referring to the makedeps array, not any content within e.g. _upstream_equiv, I have no clue about that :D

theYinYeti commented on 2020-12-16 07:45

@electricprism: I admit this package is somewhat unusual. It is however not too far from the Linux/Unix standard because /opt is a standard location for software that is not installed from official packages. I can’t change that: it is not built from source, but instead build from a .DEB packaging targeted at Debian.

As for TLS, since it is a complicated subject (even when using the ACME protocol), I think it is best to leave TLS termination to Nginx or HAProxy. Users still can setup TLS by themselves, though; I just won’t.

Last but not least, thank you for notifying me of the missing systemd dependency! That’s the problem with this package: I always have to catch-up with what is going on upstream…

9-r commented on 2020-12-09 12:27

@electricprsim: At least Unknown dependency: systemd can be fixed by adding systemd = systemd to _upstream_equiv

electricprism commented on 2020-12-05 09:11

This has been quite the rabbit hole.

It would be nice if someday this package could follow standard arch style for webapps: /usr/share/webapps [and] /etc/webapps

I am wondering if there is a problem in configuration with letsencrypt with user lool not having access to /etc/letsencrypt/live/...

I am also wondering if libreoffice-online is supposed to be a dep? Or does the package provide it? If so maybe it should conflict.

Lots of trouble getting this to work, please help, thank you.

Edit: When I try to wget the tarbuild, and make it manually I get:

makepkg -s

Unknown dependency: systemd

Edit 2: I was able to temporarily bypass the problem and setup the CODE server -- which requires manually downloading the package and unpacking to ../nextcloud/apps/

https://apps.nextcloud.com/apps/richdocumentscode/releases?platform=20#20

I would like to use this package but for now it's nice to have a temp fix even if less a performant appimage.

genofire commented on 2020-11-08 08:03

_upstream_equiv for openssh-client = openssh still not fixed.

Also hardcoded path from opt/collaboraoffice6.2/ to opt/collaboraoffice6.4/ needs be changed

9-r commented on 2020-06-26 09:48

The latest version (4.2.4) requires the addition of openssh-client = openssh to _upstream_equiv in PKGBUILD. Otherwise an "unknown dependency" error will stop the build

theYinYeti commented on 2020-05-24 10:25

@hecsa: I suppose you’re using an AUR helper. The “helper” you chose must have some shortcomings, and is probably trying to install all packages that got built.

On my PC, with yay as an helper, only the base package is installed, and the build directory contains the other packages in case I want to install them.

And of course, you can always not use an helper, and just use curl, makepkg, and pacman.