Deploy Apprise API server + provision credentials (API key) in credvault #1

Closed
opened 2026-07-13 17:51:44 +00:00 by jared · 1 comment
Owner

What to do

  1. Deploy the Apprise API server on this host (docker-compose design already exists — see the cc-os board card "Deploy Apprise API server on OVH (docker-compose)", Done column, for the design/spec).
  2. Provision/update credentials for the service, including the API key, in credvault (via the credential-management flow) so clients (the ruby apprise-client gem, os-notify, Planka's native Apprise integration) can authenticate.

On completion — unblock cc-os

The cc-os card "Multi-service routing config + wire Planka native Apprise integration" is blocked on this deploy. When done, comment on that card so cc-os knows the blocker cleared:

os-backlog card-comment --card 1816115942841648992 --text "Apprise API server deployed on OVH; credentials incl. API key in credvault. Blocker cleared."

Discoverer: /home/jared/dev/cc-os, session 22ebd341-5b0f-4b9e-a959-e700a866f331, 2026-07-13. Multi-service notification routing in cc-os is blocked on the Apprise server being live with credentials provisioned.

## What to do 1. Deploy the Apprise API server on this host (docker-compose design already exists — see the cc-os board card "Deploy Apprise API server on OVH (docker-compose)", Done column, for the design/spec). 2. Provision/update credentials for the service, including the API key, in credvault (via the credential-management flow) so clients (the ruby apprise-client gem, os-notify, Planka's native Apprise integration) can authenticate. ## On completion — unblock cc-os The cc-os card "Multi-service routing config + wire Planka native Apprise integration" is blocked on this deploy. When done, comment on that card so cc-os knows the blocker cleared: os-backlog card-comment --card 1816115942841648992 --text "Apprise API server deployed on OVH; credentials incl. API key in credvault. Blocker cleared." -------- **Discoverer:** /home/jared/dev/cc-os, session 22ebd341-5b0f-4b9e-a959-e700a866f331, 2026-07-13. Multi-service notification routing in cc-os is blocked on the Apprise server being live with credentials provisioned.
Author
Owner

Verified complete 2026-07-13: Apprise API server running at ~/services/apprise (caronc/apprise, docker compose, bound to tailnet 100.100.43.95:8901 + localhost only). API key stored in credvault at ovh-prod/apprise/prod/api-key and confirmed matching the live server; authenticated /json/urls check returns 200. Unblock comment posted on cc-os card 1816115942841648992. Note: /status reports STORE_PERMISSION_ISSUE (config lock is on, so persistent-store writes are blocked by design — benign for current usage).

Verified complete 2026-07-13: Apprise API server running at ~/services/apprise (caronc/apprise, docker compose, bound to tailnet 100.100.43.95:8901 + localhost only). API key stored in credvault at ovh-prod/apprise/prod/api-key and confirmed matching the live server; authenticated /json/urls check returns 200. Unblock comment posted on cc-os card 1816115942841648992. Note: /status reports STORE_PERMISSION_ISSUE (config lock is on, so persistent-store writes are blocked by design — benign for current usage).
jared closed this issue 2026-07-13 18:14:40 +00:00
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: jared/server-ovh-prod-01-main#1
No description provided.