Self-host operational plumbing: notifications and backups #21
Labels
No labels
burndown-2026-06
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/infrastructure#21
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally filed by @coilysiren on 2026-05-22T08:25:56Z - https://github.com/coilysiren/infrastructure/issues/247
Problem - Two operational layers every homelab needs.
Notifications: ntfy (self-hosted push, great for scripts and the daily routines), Gotify, Apprise (fan-out library).
Backups: Restic, Kopia, Borg. Raid is not a backup. Anything stateful on the cluster needs one.
Recommendation: ntfy for push, it would slot directly into the daily routines. Restic or Kopia for backups.
Origin: homelab chat sweep, 2026-05-21.
Iceboxed in the 2026-05-29 backlog burn-down: self-host notifications/backups options survey. Reopen anytime if it becomes real.