Skip to content

docs: clarify open vs NoFetch gateway recipes#11382

Open
lidel wants to merge 1 commit into
masterfrom
docs/gateway-recipes-fetch-model
Open

docs: clarify open vs NoFetch gateway recipes#11382
lidel wants to merge 1 commit into
masterfrom
docs/gateway-recipes-fetch-model

Conversation

@lidel

@lidel lidel commented Jul 2, 2026

Copy link
Copy Markdown
Member

Moves the gateway recipes into gateway.md and puts the main choice up front: run an open gateway that fetches any CID (and needs content blocking and a takedown path) or serve only the content you host with Gateway.NoFetch=true.

Gateway recipes now lead with the decision that matters most for a
public gateway: does it fetch any CID from the network, or serve only
content the node already hosts? They move from the config reference into
the gateway guide, where operators look for them.

- gateway.md: new "Gateway recipes" section (serve-only-your-own-content
  via NoFetch, open recursive gateway, and subdomain/path/DNSLink URL
  styles as linkable sub-headings), a table of contents, and fixes to the
  Directories ordering and the /ipns/ subdomain redirect example; public
  gateways point to the public-utilities and checker pages and the
  self-hosting guide instead of naming hosts
- config.md: recipes replaced by a pointer to the gateway guide
- content-blocking.md: suggest an allowlist (NoFetch) over reactive
  denylist whack-a-mole
@lidel lidel requested a review from a team as a code owner July 2, 2026 00:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant