Proof of Concept: Web Calendar with Event Commands and Scheduling API

[Richc]

Overview

Build a proof-of-concept web-based calendar app for scheduling events, each with the ability to trigger custom commands (via HTTP requests) at start and end times. All events are managed through a backend API and stored persistently.

Requirements

• Web Interface: Calendar to add, edit, and delete events. Each event must define:
  • Start/end times
  • Command/payload to execute at start
  • Command/payload to execute at end
  • Target IP addresses/endpoints for each command
• Backend API:
  • Receive event data from frontend
  • Store events in a database (e.g. SQLite/PostgreSQL)
  • Dispatch HTTP requests to defined IPs at event boundaries
  • Operate as a background service on macOS (using launchd/LaunchAgent)
• Database: Store all event fields including scheduled commands, IP targets, times, and payloads reliably.
• Persistence: Must persist through user logouts, reboots, and system interruptions on macOS.

Deliverables

• Calendar web component skeleton (React, Vue, or similar)
• API definition and basic code for scheduling/command dispatching
• Database schema for event storage
• macOS persistent service example setup (LaunchAgent config/instructions)

Acceptance Criteria

• Users can create events with start/end commands and IP targets
• Events trigger commands on schedule using the API
• All data is reliably stored and background service persists
• Manual trigger and test callbacks for webhooks are provided for verification