rainbow icon indicating copy to clipboard operation
rainbow copied to clipboard

A specialized IPFS HTTP gateway

Results 22 rainbow issues
Sort by recently updated
recently updated
newest added

On top of #111. Closes #88. This PR adds support for remote backends (as described in #88). I made it such that it is the most flexible as I could....

## Problem HTTP gateway requests for non-cached blocks can often take much longer than a couple of seconds. In fact, it's not uncommon for them to take ~60 seconds or...

This is GO version of https://github.com/ipfs-shipyard/service-worker-gateway/issues/72. We want rainbow to benefit from `/https` providers ([example](https://delegated-ipfs.dev/routing/v1/providers/bafybeigdyrzt5sfp7udm7hu76uh7y26nf3efuylqabf3oclgtqy55fbzdi)) and use them in addition to bitswap Ideally, we would be prioritizing HTTP retrieval over...

It would be advantageous if we have a debug endpoint where we can check the peering status. This can be especially useful if we're using seed-based automatic peering. The only...

Tracking issue to add flag (and env variable) to be able to configure the listen addresses. Right now we use the default ones. There was prior art in #59 but...

Tracking issue to add a flag (and environment variable) to allow overriding the bootstrappers for private deployments: https://github.com/ipfs/rainbow/pull/111#discussion_r1577097959

P2
dif/easy
effort/hours
help wanted
kind/enhancement

We want rainbow to be enough to do badbits handling at `ipfs.io` / `dweb.link`. If it is good enough for us, it will be good enough for people who self-host....

P1
dif/expert
effort/days

Caching on top of rainbow means we cannot effectively integrate the content-blocking layer as the cache would bypass it. If we can introduce an HTTP cache directly at the gateway...

need/triage

Filling here so we don't forget, upstream details in https://github.com/ipfs/boxo/issues/576. Once we have block / car backends in `boxo/gateway`, it will be easy to add config flag to rainbow which...

P1
effort/hours

## Problem Seems that we have hardcoded some settings related to delegated routing over HTTP - http client pool details [here](https://github.com/ipfs/rainbow/blob/19723fe3c522dba0daa861bf64f02dad30fde7e2/setup.go#L191-L196) - http router timeout [here](https://github.com/ipfs/rainbow/blob/19723fe3c522dba0daa861bf64f02dad30fde7e2/setup.go#L273) https://github.com/ipfs/rainbow/blob/19723fe3c522dba0daa861bf64f02dad30fde7e2/setup.go#L273 15s timeout on...

P2
need/triage