6 Commits

Author	SHA1	Message	Date
clawbot	43c22a9e9a	feat: implement per-webhook event databases ... Split data storage into main application DB (config only) and per-webhook event databases (one SQLite file per webhook). Architecture changes: - New WebhookDBManager component manages per-webhook DB lifecycle (create, open, cache, delete) with lazy connection pooling via sync.Map - Main DB (DBURL) stores only config: Users, Webhooks, Entrypoints, Targets, APIKeys - Per-webhook DBs (DATA_DIR) store Events, Deliveries, DeliveryResults in files named events-{webhook_uuid}.db - New DATA_DIR env var (default: ./data dev, /data/events prod) Behavioral changes: - Webhook creation creates per-webhook DB file - Webhook deletion hard-deletes per-webhook DB file (config soft-deleted) - Event ingestion writes to per-webhook DB, not main DB - Delivery engine polls all per-webhook DBs for pending deliveries - Database target type marks delivery as immediately successful (events are already in the dedicated per-webhook DB) - Event log UI reads from per-webhook DBs with targets from main DB - Existing webhooks without DB files get them created lazily Removed: - ArchivedEvent model (was a half-measure, replaced by per-webhook DBs) - Event/Delivery/DeliveryResult removed from main DB migrations Added: - Comprehensive tests for WebhookDBManager (create, delete, lazy creation, delivery workflow, multiple webhooks, close all) - Dockerfile creates /data/events directory README updates: - Per-webhook event databases documented as implemented (was Phase 2) - DATA_DIR added to configuration table - Docker instructions updated with data volume mount - Data model diagram updated - TODO updated (database separation moved to completed) Closes #15	2026-03-01 17:06:43 -08:00
clawbot	f21a007a3c	feat: add entrypoint/target management controls (closes #25) ... Add toggle (activate/deactivate) and delete buttons for individual entrypoints and targets on the webhook detail page. Each action is a POST form submission with ownership verification. New routes: POST /source/{id}/entrypoints/{entrypointID}/delete POST /source/{id}/entrypoints/{entrypointID}/toggle POST /source/{id}/targets/{targetID}/delete POST /source/{id}/targets/{targetID}/toggle	2026-03-01 16:38:14 -08:00
clawbot	2606d41c60	fix: cascade soft-delete for webhook deletion (closes #24) ... When deleting a webhook, also soft-delete all related deliveries and delivery results (not just entrypoints, targets, and events). Query event IDs, then delivery IDs, then cascade delete delivery results, deliveries, events, entrypoints, targets, and finally the webhook itself — all within a single transaction.	2026-03-01 16:37:21 -08:00
clawbot	7f8469a0f2	feat: implement core webhook engine, delivery system, and management UI (Phase 2) ... - Webhook reception handler: look up entrypoint by UUID, verify active, capture full HTTP request (method, headers, body, content-type), create Event record, queue Delivery records for each active Target, return 200 OK. Handles edge cases: unknown UUID → 404, inactive → 410, oversized → 413. - Delivery engine (internal/delivery): fx-managed background goroutine that polls for pending/retrying deliveries and dispatches to target type handlers. Graceful shutdown via context cancellation. - Target type implementations: - HTTP: fire-and-forget POST with original headers forwarding - Retry: exponential backoff (1s, 2s, 4s...) up to max_retries - Database: immediate success (event already stored) - Log: slog output with event details - Webhook management pages with Tailwind CSS + Alpine.js: - List (/sources): webhooks with entrypoint/target/event counts - Create (/sources/new): form with auto-created default entrypoint - Detail (/source/{id}): config, entrypoints, targets, recent events - Edit (/source/{id}/edit): name, description, retention_days - Delete (/source/{id}/delete): soft-delete with child records - Add Entrypoint (/source/{id}/entrypoints): inline form - Add Target (/source/{id}/targets): type-aware form - Event Log (/source/{id}/logs): paginated with delivery status - Updated README: marked completed items, updated naming conventions table, added delivery engine to package layout and DI docs, updated column names to reflect entity rename. - Rebuilt Tailwind CSS for new template classes. Part of: #15	2026-03-01 16:14:28 -08:00
clawbot	7bbe47b943	refactor: rename Processor to Webhook and Webhook to Entrypoint ... The top-level entity that groups entrypoints and targets is now called Webhook (was Processor). The inbound URL endpoint entity is now called Entrypoint (was Webhook). This rename affects database models, handler comments, routes, and README documentation. closes #12	2026-03-01 16:01:44 -08:00
sneak	1244f3e2d5	initial	2026-03-01 22:52:08 +07:00