fedocal

#23 Desktop or CLI client
Closed: Invalid by ryanlerch. Opened by pingou.

Closed: Invalid
Reopen Issue

In the long term it might be cool if we have a cli or desktop client for fedocal.

This might need, more work on the API (beside all the work on the client).

Given that we provide standard calendar feeds, is a separate app a real need?

Thinking about this a bit more, should we consider refactoring the application into a separate front-end and back-end?

back-end: Manage the DB of events and editing; Send emails; create a new complete static .ics file after every edit.

front-end: read and display static .ics files; serve .ics urls for other clients; aggregation, and sub-calendaring, etc. as referenced in tickets like #53 and #161. This would also solve #156 as .ics files could always be complete with negligible load.

fedocal has been migrated to Fedora Forge.

this ticket has also been migrated, please continue over at

https://forge.fedoraproject.org/apps/fedocal/issues/23

Metadata Update from @ryanlerch:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.