Multi-service routing config + wire Planka native Apprise integration #64

New Issue

Open

opened 2026-07-16 18:44:11 +00:00 by jared · 0 comments

jared commented

2026-07-16 18:44:11 +00:00

Owner

Card comments carried over:

(2026-07-13) Apprise API wrapper gem created in ~/dev/ruby-gems. Blocker cleared.

(2026-07-13) Apprise API server deployed on OVH and verified (Forgejo server-ovh-prod-01-main #1): service Up, authenticated /json/urls check 200. Credentials incl. API key confirmed in credvault at ovh-prod/apprise/prod/api-key (matches live server). Blocker (1) cleared.

(2026-07-13) Blockers now tracked in their owning projects: (1) Apprise server deploy + credentials/API key -> Forgejo server-ovh-prod-01-main issue #1; (2) Apprise API wrapper gem -> ruby-gems Planka board card #1818429983199069556. Both instructed to comment here when done. Remaining local blocker: os-notify design pass (hitl card in Backlog).

(2026-07-12) 2026-07-12: Blocked — depends on (1) the os-notify design pass (hitl card, still in Backlog: notification etiquette / pull-beats-push policy must be settled first), (2) the Apprise API server deploy + client gem, both still in Review awaiting sign-off, and (3) service tokens (Discord/Telegram/Bark/HA/Zoom) that only you can provision. Suggest relabeling from afk-ready, or moving to Waiting behind the os-notify design card.

NOTE (2026-07-16): the "wire Planka native Apprise integration" half is obsolete per ADR-0042 (Planka decommissioned); the multi-service Apprise routing config half survives.

Migrated 2026-07-16 from Planka board cc-os, column Waiting (ADR-0042, change retire-planka-git-issues-only).

ADR-024 expansion. (1) Routing conventions: Apprise tags per purpose (urgent/afk-done/property/clients), which service(s) each tag fans out to, quiet hours. (2) Point Planka's built-in Apprise notification support at the same server so board events and agent notifications converge. (3) Add remaining services: Discord, Telegram, Bark, Home Assistant, Gnome, Zoom. --- Card comments carried over: > (2026-07-13) Apprise API wrapper gem created in ~/dev/ruby-gems. Blocker cleared. > (2026-07-13) Apprise API server deployed on OVH and verified (Forgejo server-ovh-prod-01-main #1): service Up, authenticated /json/urls check 200. Credentials incl. API key confirmed in credvault at ovh-prod/apprise/prod/api-key (matches live server). Blocker (1) cleared. > (2026-07-13) Blockers now tracked in their owning projects: (1) Apprise server deploy + credentials/API key -> Forgejo server-ovh-prod-01-main issue #1; (2) Apprise API wrapper gem -> ruby-gems Planka board card #1818429983199069556. Both instructed to comment here when done. Remaining local blocker: os-notify design pass (hitl card in Backlog). > (2026-07-12) 2026-07-12: Blocked — depends on (1) the os-notify design pass (hitl card, still in Backlog: notification etiquette / pull-beats-push policy must be settled first), (2) the Apprise API server deploy + client gem, both still in Review awaiting sign-off, and (3) service tokens (Discord/Telegram/Bark/HA/Zoom) that only you can provision. Suggest relabeling from afk-ready, or moving to Waiting behind the os-notify design card. NOTE (2026-07-16): the "wire Planka native Apprise integration" half is obsolete per ADR-0042 (Planka decommissioned); the multi-service Apprise routing config half survives. --- Migrated 2026-07-16 from Planka board cc-os, column Waiting (ADR-0042, change retire-planka-git-issues-only).