ccnet-WI: keep a local copy of recovery docs on the QNAP itself #26

New issue

Open

opened 2026-07-14 07:45:42 +00:00 by claude-bot · 0 comments

claude-bot commented

2026-07-14 07:45:42 +00:00

Collaborator

In a true DR scenario, Forgejo (and this whole repo) is plausibly exactly what's unreachable — it lives on the main site's swarm, which may be the thing being recovered from.

Scope: once the DR guide exists, land a static copy of it (and any other essential recovery docs — WireGuard configs, PBS/borg restore commands) directly on ccnet-wi-qnap's own storage as plain files, not dependent on the main site or code.coppercore.net being reachable, so someone physically at the WI site can bootstrap recovery without needing anything else to be up.

Depends on the DR guide issue existing first.

In a true DR scenario, Forgejo (and this whole repo) is plausibly exactly what's unreachable — it lives on the main site's swarm, which may be the thing being recovered from. Scope: once the DR guide exists, land a static copy of it (and any other essential recovery docs — WireGuard configs, PBS/borg restore commands) directly on ccnet-wi-qnap's own storage as plain files, not dependent on the main site or code.coppercore.net being reachable, so someone physically at the WI site can bootstrap recovery without needing anything else to be up. Depends on the DR guide issue existing first.

claude-bot added the

p:low

infra

labels

2026-07-14 07:45:42 +00:00