From 4d160762aeef531208f8cf6094a0e58a9e7d53ec Mon Sep 17 00:00:00 2001 From: Peter Stone Date: Sun, 20 Sep 2026 07:57:36 +0000 Subject: Add .ics calendar feed support MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit doot reads Google Calendar through a service account, by calendar ID. That cannot consume an .ics URL, and it cannot see a calendar subscribed to inside a personal Google account either, because Google does not allow re-sharing a subscribed calendar. Published schedules — sports fixtures, school terms, bin collections — are distributed almost exclusively as .ics, so none of them could be added at all. Feeds are now fetched on the normal calendar refresh and merged into calendar_events alongside Google events, so the timeline, widget and everything downstream keep seeing one list and needed no changes. Failure handling is deliberately asymmetric. A Google error is still returned as an error, unchanged, so an outage there surfaces. A single failing feed is recorded against that feed and skipped, because one dead URL should not take the whole calendar down — and last_error is shown in settings, since a feed that has quietly stopped resolving otherwise looks identical to a team with no games left. The parser handles what real feeds actually contain: line unfolding, CRLF and LF, UTC / TZID / VALUE=DATE times, and escaped text. Two details worth naming: a TZID time is wall-clock in that zone, and reading it as UTC would put a 1:15pm Pacific kickoff on the timeline at 1:15pm local — wrong by the offset but entirely plausible-looking. And non-calendar content is a hard error rather than zero events, because an HTML error page from a moved feed URL is the common failure and "no events" reads as success. RRULE is deliberately unsupported: every schedule feed this targets expands recurrence itself, one VEVENT per fixture, and a correct expansion is a large amount of subtle code. A recurring event appears once rather than wrongly. Settings gains an add/enable/disable/remove UI. webcal:// links are accepted and rewritten, since that is how feeds are usually advertised. 16 parser tests, 5 store tests. Verified against the real Seattle Seahawks feed: 21 events, all with valid times. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_018AwnALZL6bD4VBtATDVv3B --- web/templates/partials/ics-feeds.html | 43 +++++++++++++++++++++++++++++++++++ web/templates/settings.html | 26 +++++++++++++++++++++ 2 files changed, 69 insertions(+) create mode 100644 web/templates/partials/ics-feeds.html (limited to 'web') diff --git a/web/templates/partials/ics-feeds.html b/web/templates/partials/ics-feeds.html new file mode 100644 index 0000000..4ee1ad6 --- /dev/null +++ b/web/templates/partials/ics-feeds.html @@ -0,0 +1,43 @@ +{{define "ics-feed-list"}} +
+ {{if .Feeds}} + {{range .Feeds}} +
+
+
+ {{.Name}} + {{if not .Enabled}}(off){{end}} +
+
{{.URL}}
+
+ {{if .LastError}} + Failed: {{.LastError}} + {{else}} + {{.EventCount}} events · last checked {{.LastFetched}} + {{end}} +
+
+
+ + +
+ +
+ {{end}} + {{else}} +

+ No calendar feeds yet. Paste an .ics or webcal:// link below — published + schedules (sports fixtures, school terms, bin collections) are almost + always distributed this way. +

+ {{end}} +
+{{end}} diff --git a/web/templates/settings.html b/web/templates/settings.html index 8a72287..1156ef5 100644 --- a/web/templates/settings.html +++ b/web/templates/settings.html @@ -215,6 +215,32 @@ + +
+

Calendar Feeds (.ics)

+

+ Subscribed calendars fetched directly by doot. Google Calendar is read + through a service account, which cannot see calendars you subscribe to + in your own account — so published schedules go here instead. +

+ + {{template "ics-feed-list" .}} + +
+ + + +
+
+ {{template "sync-log" .SyncLog}}
-- cgit v1.2.3