Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add remote backend mode from bifrost-gateway #88

Closed
lidel opened this issue Feb 14, 2024 · 0 comments · Fixed by #117
Closed

Add remote backend mode from bifrost-gateway #88

lidel opened this issue Feb 14, 2024 · 0 comments · Fixed by #117
Labels
effort/hours Estimated to take one or several hours P1 High: Likely tackled by core team if no one steps up

Comments

@lidel
Copy link
Member

lidel commented Feb 14, 2024

Filling here so we don't forget, upstream details in ipfs/boxo#576.

Once we have block / car backends in boxo/gateway, it will be easy to add config flag to rainbow which disables libp2p stack and only uses delegated retrieval via HTTP (trustless gateway + delegated routing).

I think the basic configuration options would be:

  • RAINBOW_REMOTE_BACKEND with list of URLs of trustless gateways
  • RAINBOW_REMOTE_BACKEND_MODE=block|car where block is implicit default (if not set)
@lidel lidel changed the title Port remote backend mode from bifrost-gateway Add remote backend mode from bifrost-gateway Feb 14, 2024
@aschmahmann aschmahmann added P1 High: Likely tackled by core team if no one steps up effort/hours Estimated to take one or several hours labels Feb 20, 2024
This was referenced Apr 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort/hours Estimated to take one or several hours P1 High: Likely tackled by core team if no one steps up
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants