Today, Collabora releases version 1.8, which brings an upgrade to LibreOffice 5.1 as well as some statusbar features for Writer and Calc.
Improvements
The new release is based on LibreOffice 5.1 which fixes a large number of small rendering issues and is a bit faster and more stable overall.
In feature news, the Statusbar has been updated. It shows a word-count in writer and Calc gained the quick statusbar 'sum" functionality, among other things. On top of that, security and bugfixes are included in this release so we strongly recommend upgrading!
Go get it!
You can get your own Online Office setup by following our extensive instructions on our website. Docker has a built-in upgrade process which you can do by pulling again, stopping the current image, removing it and starting the new one:
grab new docker image: docker pull collabora/code
List docker images: docker ps
from the output you can glean the Container ID of your Collabora Online docker image.
stop and remove the Collabora Online docker image: docker stop CONTAINER_ID
docker rm CONTAINER_ID
start the new one: docker run -t -d -p 127.0.0.1:9980:9980 -e "domain=cloud\.nextcloud\.com" --restart always --cap-add MKNOD collabora/code
Shouldn’t docker pull docker pull be docker pull collabora/code ??
Edit:
root@hostname:~# docker pull docker pull
"docker pull" requires exactly 1 argument(s).
See 'docker pull --help'.
Usage: docker pull [OPTIONS] NAME[:TAG|@DIGEST]
Pull an image or a repository from a registry
VS
root@hostname:~# docker pull collabora/code
Using default tag: latest
latest: Pulling from collabora/code
512b11b31aa9: Already exists
a3ed95caeb02: Already exists
Digest: sha256:97f2303ee682b5c31b9a545f77244aab572333d4fa4dc604ba0c817bffe15a18
Status: Image is up to date for collabora/code:latest
I have a different setup, maybe you have an idea:
Collabora Container exposes now TCP 9980.
My Docker runs on a different machine than Nextcloud. Both hosted at the same provider.
So, I wanted to install the stuff using ACME as shown in the Video of Jos. But the config changed (ports), I guess and I do not know, which installation mode is needed regarding the reverse proxy and ACME.
Any link I can refer to?
@enoch85 I know, reason is I already have that implemented in the auto install. But if its not a must then I’d rather leave it out since using snakeoil is a lot more fail proof then using letsencrypt.
It works without any issues at all. It would be asy to adopt to Apache as well. Just change the secure settings and different headers in the virtual host file.
@enoch85 It is because of the letsencrypt part in the script. If the user doesn’t have 443 forwarded or apache2 is still running the cert wont be created.
I’ll have a look later tonight. Used your previous version I think so I’d be comfortable with it I guess.
@ezraholm50 Yeah, didn’t think of the 443 thing. Apache is easy, just stop it before the cert is generated.
We could at least ask the user if they want to get a real cert, then we could use the script we already use, and just change the domains to several instead of just one. We are aiming for the best possible solution here.
Point is, that I can configure the collabora plugin in Nextcloud and I can jump to the Documents-Section where I can see possible editable docs, but as soon as I want to open a doc the request times out.
@lebernd: So on the docker side there is no Apache needed at all? When looking at the config for the virtual host, it seems it wanted to have its own subdomain as of: <VirtualHost *:443> ServerName docker.example.com:443
I really do not understand, why I need a new virtual host on the right side with its own subdomain. Does the proxy need this? … well, would be my first working Apache proxy…
Did you solve the problem you had referring to you post in the chat mentioned?
Right, no additional apache on the docker side needed.
Just configure the ssl-proxy.conf as mentioned in the tutorial and replace the localhost entrys with the IP of the server where docker container get exposed.
Actually, it was my first working proxy too
No, I didn’t get rid of the 20 seconds with the docker image. But the tutorial to extract the files is pretty good.
Yeah, I just tried the test server and I agree with your assessment. On the one hand, you can technically click on and do everything. On the other, you often have to scroll to get interface elements onscreen.
Ah well. I look forward to the day when either Collabora has a mobile interface, or the NC client can do full 2 way sync, so I can use a local app to edit documents. Until then, I guess I’ll just use the one way sync, and occasionally manually re-upload the edited files.
Still, Collabora is an impressive step forward for the free software world! I’m looking forward to being part of it’s evolution…