Multi-tenant / redundant hosting (long-term) #90
Labels
No labels
area:ai
area:ci-cd
area:notifications
area:observability
area:public-pages
backlog
bug
duplicate
enhancement
help wanted
invalid
question
type:decision
type:feature
type:infra
type:maintenance
type:security
v1.0.1
v1.1.0
v1.2.0
v1.3.0
v2.0.0
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rbrooks/WeatherBot#90
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?
Would redefine scope - long-term possibility.
Beyond serving more users, a hosted/redundant deployment would help guarantee alerts still arrive if a single self-hosted host goes down (the availability angle the poller heartbeat, I-07, only detects). Almost certainly overkill for the current single-operator use, but worth holding as a direction if reach or resilience ever becomes a goal.
Filed from the 2026-07-17 codebase audit (
docs/.internal/report-2026-07-17.md), finding SCOPE-2.