Rename "Processor" entity to "Webhook" and "Webhook" to "Entrypoint" throughout codebase #12

New Issue

2026-03-01T19:08:13+01:00

clawbot commented

2026-03-01 19:08:13 +01:00

Per the discussion on issue #3, the current naming of the main entity as "Processor" is confusing. The proposed naming scheme:

Processor → Webhook: The top-level configuration entity that groups entrypoints and targets together. Users create "webhooks" to manage event routing.
Webhook (current) → Entrypoint: The receiver URL (/hooks/<uuid>) where external services POST events. Each webhook can have multiple entrypoints.
Target: Remains unchanged — a delivery destination for events.

This rename affects:

internal/database/model_processor.go → model_webhook.go (the struct, not just the file)
internal/database/model_webhook.go → model_entrypoint.go
All references in handlers, routes, templates, and database migrations
The URL structure: /sources/* → /webhooks/* for management, /webhook/{uuid} → /hooks/{uuid} for receiving

The new README (issue #3) documents this naming scheme as the target architecture. This issue tracks the actual code rename.

Per the discussion on [issue #3](https://git.eeqj.de/sneak/webhooker/issues/3), the current naming of the main entity as "Processor" is confusing. The proposed naming scheme: - **Processor** → **Webhook**: The top-level configuration entity that groups entrypoints and targets together. Users create "webhooks" to manage event routing. - **Webhook** (current) → **Entrypoint**: The receiver URL (`/hooks/<uuid>`) where external services POST events. Each webhook can have multiple entrypoints. - **Target**: Remains unchanged — a delivery destination for events. This rename affects: - `internal/database/model_processor.go` → `model_webhook.go` (the struct, not just the file) - `internal/database/model_webhook.go` → `model_entrypoint.go` - All references in handlers, routes, templates, and database migrations - The URL structure: `/sources/*` → `/webhooks/*` for management, `/webhook/{uuid}` → `/hooks/{uuid}` for receiving The new README (issue #3) documents this naming scheme as the target architecture. This issue tracks the actual code rename.

clawbot referenced this issue

2026-03-01 19:12:13 +01:00

docs: comprehensive README rewrite with complete service specification #13

clawbot referenced this issue

2026-03-02 00:38:37 +01:00

1.0/mvp #15

sneak referenced this issue from a commit

2026-03-02 00:43:56 +01:00

docs: comprehensive README rewrite with complete service specification (#13)

clawbot referenced this issue from a commit

2026-03-02 00:56:09 +01:00

refactor: rename Processor to Webhook and Webhook to Entrypoint