As the latest tag is not defined (which is the default tag), you may get an error like this:
docker: Error response from daemon: manifest for libreoffice/online:latest not found
To avoid that problem, use full reference (with an existing tag) like this: openoffice/online:master
Thats batshit crazy, Libre limit LOOL to 10 Docs and 20 connections, like the 20 connections just sort of puts a perspective on this.
Why the feck would you want a connection to a document platform if you donāt have a document open!!!
Sightseeing! Dayout! Or maybe your just a fan of making TCP connections!
Even with the new upgrade?
For the docker to work you have to manually copy your certs within the docker and edit the loolwds.html file
By the way it looks that after the update to Libreoffice5.1.3 I can now successfully build my image. it took almost 6 hours, but i was able to compile it in Debian Jessy and Ubuntu 16.04 on my two VMs, now am going to try the rest of the configurations. Iāll update once is done.
@Nemskiller tested and trust his findings, its there prerogative but just seems at odds with The Document Foundation stated goals.
Ignore my hyperbole, just frustation as has been an advocate of LOOL for a long time now, its taken far to long and just see this as further hurdles to adoption.
Nextcloud needs the document app back in 11 as for some the ability to edit documents lan side means the restriction of 10 documents far outweighs the advantages of LOOL.
The documents app and lool need to be offered as parallel apps or the use of Nextcloud effectively hits the same restrictions.
This would be great. So, you compiled LO 5.1.3. after pulling from github just like the OP documented? Or did you have to tweak something (like firebird)?
Do you think the 10 doc, 20 connection restriction might have been put in place to temporarily keep a server from crashing with many people using it in the development process? Maybe they forgot to remove or mention how to change it when released? Maybe that setting is simply in a configuration file not yet documented that simply needs changed?
It makes sense to have settings like that to keep a production server from getting out of control. Maybe they set it low to test those settings, and forgot about telling people how to increase the limits.
I donāt really think so. In the market there is as for right now 2 main options for office documents.
Microsoft Office 365
Google Apps
And they both have a price, i think that CODE is a way to spread the news about a new market competitor.
Collabora Online
Let users play with it, if you may call it that way, so they can compete with the other 2 private cloud solutions, reaching potential clients that already have started taking over their cloud infrastructure.
Later in time, who knows when, it may become free of charge, as in free beer, but i donāt see it as a near future.
So right now, i would suggest to stick with your copy of LibreOffice 5 and keep from there, that at the end is what you are using on CODE.
So, did CODE get us all excited, yes, is it a production product, no.
My thought about it is that, i didnāt think they will just hand over a project that has been developed for around 5 years with no direct sponsorship from the public.
I run a business myself and i understand where they are coming from, but i donāt prise the lack of information in the first place.
I completely agree and its Collaboraās prerogative, but actually its untrue about public support unless you are talking about the 30% of the code that Collabora have contributed. 30% of what you say is true.
Irrespective of that in Nextcloud 11 it does put Nextcloud in an extremely funny position, of not having a document viewer that can even scale into a modest workgroup, unless you stick with PDF.
@Ark74 Sure, but Iām not going to assume. Did they document, or announce anything that says they are trying to impose limitations? If you find something that announces the limitation, then I will believe you. I plan on compiling a copy myself in a couple days, and if a limitation isnāt announced by then; Iāll just look for a setting.
Its hardcoded and proved by many in the forum already, you can try compiling the code, but it doesnāt work, as proved by many in the forum already.
The release is neither opensource or unrestricted and the only working form is a docker binary with restrictions.
The fact you can not find details of this restriction is actually worse and casts doubt on the whole honesty and offering of Collabora Code. It is not what it says on the tin.
It comes up with a big message when you try more than 10 documents, there are no settings as the admin console is not part of code.
I can confirm that it works.
Many do not differ between Collabora and Onlineoffice.
I am fed up with the ā¦ (not yet documented)ā¦
I am working on install-script that will do all the work on Ubuntu 16.04.
I believe it will be ready to use in 2-3 days.
@husisusi, an install-script will be great! Another question: I have some problems with Letsencrypt certificates because I want deploy Nexcloud + Collabora in private lan and Letsencrypt need a public domain. Someone know a solution with openssl selfsigned certificates?