Re: [CalendarServer-users] MacPorts port of calendarserver

ration could be part of this. Should ccs-calendarserver’s Twisted TLS config be raised as an issue at https://github.com/apple/ccs-calendarserver/issues <https://github.com/apple/ccs-calendarserver/issues> ? > On Aug 8, 2019, at 11:31 PM, Glyph wrote: > > > >> On Aug 8,

[CalendarServer-users] MacPorts port of calendarserver

I've ported Apple Calendar and Contacts Server to MacPorts. See https://github.com/macports/macports-ports/pull/4978 This port is completely independent of Server.app, and uses an nginx reverse proxy for modern crypto and to isolate the backend server. I have it deployed and it’s working well.

[CalendarServer-users] MacPorts port of ccs-calendarserver

I've ported Apple Calendar and Contacts Server to MacPorts. See https://github.com/macports/macports-ports/pull/4978 This port is completely independent of Server.app, and uses an nginx reverse proxy for modern crypto and to isolate the backend server. I have it deployed and it’s working well.

[CalendarServer-users] APNS configuration for ccs-calendarserver

I have a working APNS service on a mail server and would like to configure a working ccs-calendarserver for APNS. I have all the valid APNS certificates and keys—both in my System Keychain and as pkcs12 and PEM files—but haven’t been able to figure out the right calendarserver configuration to

Re: [CalendarServer-users] End of life for FreeBSD port

We have a working port with 2.7 on MacPorts: https://github.com/macports/macports-ports/blob/master/net/calendar-contacts-server/Portfile This will continue to run on now-unsupported 2.7, but yes, it’s necessary to move this to Python 3 for long-term stability. I want to continue using

[CalendarServer-users] Calendarserver Patch for New APNS HTTP/2 Protocol?

Does anyone have a calendarserver patch that addresses the new APNS API requirement for HTTP/2? I just swapped in new APNS certificates and see in the calendarserver logs that APNS connections are no longer going through. The legacy APNS binary protocol was deprecated in November 2020:

[CalendarServer-users] Calendarserver Patch for New APNS HTTP/2 Protocol?

Does anyone have a calendarserver patch that addresses the new APNS API requirement for HTTP/2? I just swapped in new APNS certificates and see in the calendarserver logs that APNS connections are no longer going through. The legacy APNS binary protocol was deprecated in November 2020:

Re: [CalendarServer-users] Is this still Active?

I don’t know if calendarserver is, but I know there are still active ccs-calendarserver users. In spite of the fact that the repo has been archived and macOS Server discontinued, ccs-calendarserver still has the greatest functionality of open source caldav servers. I just updated my APNS

[CalendarServer-users] ccs-calendarserver Ventura Authentication Issue — Request for Pointers

I just migrated my server to Ventura, including a still-going-strong instance of ccs-calendarserver with APNS. All went smoothly, except for the issue that ccs-calendarserver is under Ventura is rejecting authentication to local accounts. I am confident that this is a new issue with macOS

Re: [CalendarServer-users] ccs-calendarserver Ventura Authentication Issue — Request for Pointers

method.}); I see that authentication in calendarserver.plist is reconfigurable: > > > > DirectoryService > > type > opendirectory > On Jan 1, 2023, at 9:12 AM, Steven Smith wrote: > > I just migrated my server to Ventur

Re: [CalendarServer-users] ccs-calendarserver Ventura Authentication Issue — Request for Pointers

I resolved this by using XML file-based authentication per https://www.calendarserver.org/QuickStart.html, and now have ccs-calendarserver running on macOS Ventura. > On Jan 1, 2023, at 12:32 PM, Steven Smith wrote: > > This issue is the disappearance of OpenDirectory because mac