DayFront
github.com
Spec sheet
- What it does
- DayFront is a self-hosted web interface for calendars and tasks stored on an existing CalDAV server.Read 5 Oct 2026 · github.com
- Purpose
- DayFront is an open-source, self-hosted web interface for calendars and tasks stored on an existing CalDAV server.Read 12 Oct 2026 · github.com
- Deployment
- The maker documents Docker, Docker Compose, and Unraid deployment, with published container images for AMD64 and ARM64 hosts.Read 12 Oct 2026 · github.com
- Integrations
- DayFront connects to standards-compliant CalDAV servers and supports read-only external iCalendar subscriptions.Read 5 Oct 2026 · github.com
- License
- DayFront is available under the MIT License.Read 5 Oct 2026 · github.com
- Authentication
- DayFront supports a shared configured CalDAV account or a login mode that prompts each visitor for their own CalDAV credentials.Read 12 Oct 2026 · github.com
- Authentication modes
- It supports a shared configured CalDAV account or individual visitor sign-in using CalDAV credentials.Read 5 Oct 2026 · github.com
- CalDAV compatibility
- It uses standard CalDAV and WebDAV discovery to connect to standards-compliant CalDAV servers.Read 12 Oct 2026 · github.com
- Calendar sync
- two_wayRead 22 Sep 2026 · github.com
- Calendar views
- It offers month, week, day, and agenda views, with visibility controls and colors for multiple calendars.Read 12 Oct 2026 · github.com
- Compatibility
- CalDAV implementations vary in optional features and edge-case behavior, and the project welcomes compatibility reports and fixes.Read 5 Oct 2026 · github.com
- Compatibility limit
- CalDAV implementations vary in optional features and edge-case behavior, and the maker invites compatibility reports.Read 12 Oct 2026 · github.com
- Credential handling
- The CalDAV URL, credentials, and authorization header stay in the API process; the browser receives public UI settings and calendar display metadata.Read 5 Oct 2026 · github.com
- Data storage
- DayFront stores no calendar data locally; its only persistent input is the YAML configuration containing the CalDAV connection.Read 5 Oct 2026 · github.com
- Events
- It supports timed, all-day, multi-day, and recurring events, plus editing a series or a single recurrence.Read 12 Oct 2026 · github.com
- External calendars
- External iCalendar subscriptions are read-only; enabled feeds are fetched server-side and cached in memory.Read 12 Oct 2026 · github.com
- Intended audience
- The project describes itself as open source and ready for self-hosted deployment.Read 5 Oct 2026 · github.com
- License and status
- The repository states that DayFront is MIT-licensed and that version 1.0 is stable and ready for self-hosted deployment.Read 12 Oct 2026 · github.com
- Maker location
- The maker's GitHub profile lists Montreal, Quebec, Canada.Read 12 Oct 2026 · github.com
- Notable limitation
- External iCalendar subscriptions are read-only and configured in YAML; their list has no environment-variable equivalent.Read 5 Oct 2026 · github.com
- Search and themes
- The interface includes event search with optional fuzzy matching and keyboard navigation, plus light and dark themes.Read 12 Oct 2026 · github.com
- Security boundary
- The CalDAV origin is administrator-configured, credentials remain in the API process, and the maker recommends HTTPS before external exposure.Read 12 Oct 2026 · github.com
- Session security
- In login mode, credentials are encrypted with AES-256-GCM and stored in an HttpOnly, SameSite=Strict cookie inaccessible to frontend JavaScript.Read 12 Oct 2026 · github.com
- Storage
- DayFront stores no calendar data locally; its only persistent input is the YAML configuration containing the CalDAV connection.Read 12 Oct 2026 · github.com
- Tasks
- It supports dated and undated CalDAV tasks, recurring tasks, subtasks, priorities, and completion workflows.Read 12 Oct 2026 · github.com
Where Specifiction places it
- Calendar apps#161 of 1947.5