Operator IPFS onboarding: run your own Kubo as preferred content source #14
No reviewers
Labels
No labels
feature request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rhelwig/DecentSite!14
Loading…
Reference in a new issue
No description provided.
Delete branch "rhelwig/operator-ipfs-onboarding"
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?
Makes running your own Kubo (like the ronhelwig.com VPS node) the obvious default for every DecentSite operator, and makes it easy to publish it as the site's preferred content source.
Admin
apps/admin/src/operator-onboarding.tschecklist (no network calls).DECENT_SITE_DOCS_URLoverrides the docs base for forks.Docs
docs/DEPLOY.md: new section "Your own IPFS node and preferred content source": install Kubo,Gateway.NoFetch, a read-only nginx/Caddy gateway (GET /ipfs/ only, never RPC 5001), port 4001, adding the gateway and multiaddr as preferred sources, checking pins after publish, an optional second Kubo node or Pinning Service API provider (token stays on the Kubo machine), and why public gateways (rate limits, notice pages) are a fallback only. The durable path is the owner's gateway plus the hash check.docs/INSTALL.md: short pointer after the Kubo step.docs/SPECS.md: records the operator default under Preferred content sources.docs/IMPLEMENTATION-PLAN.md: progress entry. A follow-up for later is an Admin probe that the published gateway really serves a pinned CID.Tests
tests/operator-onboarding.test.ts: card visibility, checklist states, escaping, and the docs-URL override.No Dash spent, no Platform writes, no device installs. Branched off
main(745c57e). It doesn't touch PR #12. If #12 merges first, expect at most a trivial conflict indocs/DEPLOY.md/IMPLEMENTATION-PLAN.md.