@tboernert Thanks for starting this thread.
We are also looking for a CalDAV solution similar to the Calendso tool @tiredofit shared. This solution would be a scheduling frontend for the public to use to request appointments based on the availability of our staff’s Kopano Calendars. We like how “availability” is shown when booking a meeting with suggested times that work for all attendees. Maybe the public calendar could follow a similar layout/function? We would definitely prefer a native Kopano addition supporting CalDAV. I can throw $500 in as a bounty if that will help support the development. Would love to see a public facing calendar added.

Hi @gutschy,

the primary language of this forum is english. Please translate your question so that other users can benefit of it as well.

Hi @fbartels ,
thanks for not calling me a complete idiot. Of course using ssh. I’m not a server guy but done a few things with some raspberries. To my apologize, I would like to say that I’ve been more on the arduino track in the last two years.

greetings,
gutschy

THX, will test in a few moments.
Cheers
W.

Thanks to all for your help, now I’m in. I’ve done a new installation with “debian 9 64 bit” and everything looks fine. Now we will see. :)

Hi @odix67,

in general we adopted semantic versioning for our software a while ago, which specifies when a new tag should be major, minor or patch.

The mix of versions in Core can be explained in the following way:

8.7 is the current stable for all customers 9.x is part of Kopano One and brings a nice licensing component, Kopano One is the recommended installation for new customers because of the new licensing component users upgrading from 8.7 need to convert their subscription key, which requires some more automation to provide a smooth transition 11.x is the head of our main development branch

@odix67 said in Version numbering for community version, Kopano One and Kopano core:

btw. are there any plans in the near future for a replacement of the current WebApp ?

Yes, the idea is still to replace WebApp with new web applications designed as so called Progressive Web Apps (PWA), which make use of OIDC and a RestAPI to communicate with the Kopano backend.

Weird, judging from past occurrences I would guess that more likely the build process if broken than that this is a conscious decision to only support limited operating systems? I have no clue though.

I don’t think it’s a problem for your upgrade, I would disable the kopano services with systemd, then upgrade ubuntu 18.04 => 20.04 and then install the new packages (via a local repository is probably the best way). This should overwrite the old ones and sort out dependencies. Or you make a list of all kopano packages and remove them before upgrading (config and database will stay unless you “purge” instead of “remove”).

If you need old packages for ubuntu 18.04 PM me, i have
core-11.0.1.101.a68bc0f-Ubuntu_18.04-amd64.tar.gz from Apr 21
which is likely the last one that was offered here for download (i download 18.04 and 20.04 core archives weekly with a script if there are new versions, this is the most recent 18.04 version my script downloaded)

You can configure multi tenant mode of the Kopano server by following these steps.

KCCONF_SERVER_ENABLE_HOSTED_KOPANO=YES
KCCONF_LDAP_LDAP_COMPANY_TYPE_ATTRIBUTE_VALUE=kopano-company

Also, I am using Cloudways managed hosting and I have done this process through their platform which is much easier.

@fbartels Thank you very much for your time! Now I see what I can do.
Kind regards,
Andreas

@ebroch and @Sinux a statement can be found here https://forum.kopano.io/topic/3738/packages-and-services-available-under-new-locations

If your database is only used on this host, you may also use:

skip-external-locking skip-name-resolve

57 connections is not a whole lot, I would not limit that anyway - the default is 150.
“query_cache_size” and “query_cache_limit” with InnoDB are a difficult topic - it is usually better to set “0”.

You may also use multiple buffer pools for better concurrency with:

innodb_buffer_pool_instances

I usually match my number of cpu cores with the number of buffer pools and io-threads.
The overall buffer pool size is calculated “innodb_buffer_pool_instances” * “innodb_buffer_pool_size”.

Why are you increasing “innodb_lock_wait_timeout” ?

More is not always better…

@boospy
It seams you did not change all references from “repo.z-hub.io” to “download.kopano.io”.

@fbartels But the wiki is at z-hub.io, right? This post links to the wiki using z-hub.io: https://forum.kopano.io/topic/3615/z-push-2-6-2-final-release

@junglemarc like I have written before I would suggest you to use Kopano One. You can find instructions for Kopano One and Ubuntu 20.04 at https://kb.kopano.io/display/WIKI/Kopano+One+on+Ubuntu+20.04+-+quick+installation+instructions.

The repo configuration that you can download in the portal is for the individual products, but for new installation we recommend to use Kopano One. If you still want to use the individual repositories you can still configure them manually. Instructions for that can be found at https://kb.kopano.io/display/WIKI/Configure+repositories and https://documentation.kopano.io/kopanocore_administrator_manual/installing.html#installing-kopano-core-through-the-kopano-package-repositories

Nevertheless I notified our internal it that this wizard seems to miss the ability to select Ubuntu 20.04.

@fbartels you are correct.

I did a reboot on the server, and it did wonders.

kopano-search, kopano-server processes not as cpu hungry anymore.

The search function has been good past week.

Case closed :P

Marc

@meyca said in Stable version is at 8 - why have nightlies version 11?:

And when will the current release fix for a memory exhaustion issue forwarded to the community and the other versions?

Changes are done first in the master branch (the one branch where you can downloads nightly binary builds of) and are from there backported/cherry-picked to the relevant release branches (8.x, 9.x, …).

The specific change was first introduced in the master branch in https://stash.kopano.io/projects/KC/repos/kopanocore/commits/512457466b87039c6a8d25887fdaca6173619546 and then picked into the 8.7 release branch for the 8.7.20 release as https://stash.kopano.io/projects/KC/repos/kopanocore/commits/2ddd63cd55e236f382124ee2b6d7f41b12986848.