owned this note
owned this note
Published
Linked with GitHub
# IPFSOPS 2021-11-16 Native redirects for web apps on IPFS gateway
Event link: https://lu.ma/rxi6buve
Relevant github links:
* Proposal: native redirects config https://github.com/ipfs/go-ipfs/issues/7392
* Proposal: manifest file for the IPFS gateway: https://github.com/ipfs/go-ipfs/issues/6214
Attendees
* Cliff Brake
* Matt, Cloudflare
* JeffG, Fission
* James, Fission
* Lidel, Protocol Labs
* Boris
_Boris high level outline description -- let's make it so that any web app deployed to any IPFS gateway will just work, in a similar way as a Netlify or Vercel deploy_
Lidel
* Most people put UnixFS on IPFS
* Maps to the way websites work -- files in directories
* Subset of IPFS / IPLD
* Right now mainly fetch files
* More IPLD formats coming
* Special behavior for files and directories when they are fetched from HTTP gateway
* Many requests for CORS headers -- compromise defaults
* Add directory with website, can't control headers returned by gateway
* Redirects are one thing -- want to keep links working, have an SPA, sub-pages pointing at the same thing
* Other people add data -- don't like the content type, gateways do MIME sniffing, people need different data types -- e.g zip files with different stuff
* summarize: person who adds data to IPFS -- I should have some means of controlling, hinting to the gateway, if possible, I would like this and this behavior
* HTTP headers are a can of worms, security wise
* Want to have control over headers starting with a small subset -- eg location, control redirects
CI Pipelines controlled by some sysadmin
* config should be inside repo
* if I publish data on IPFS -- with the purpose of an HTTPS website, at minimum we should have a standard for hinting
* not just go-ipfs, part of http gateway spec -- spec and compliance tests
Tackle just redirects for now?
* manifest
* include redirects
Matt:
* redirects based on headers
Gateway specs
* priority for 2022
* want the spec / compliance
* implement the spec and you don't have to be running go-ipfs
* content type by magic go-lang sniffing
Implementing
* manifest
* redirects
Extract gateway code to stand alone library
Bikeshedding the spec
* especially the manifest
* PWAs -- specs for web app manifest
Manifest for PWAs vs building
What if we could ship some code with data
* eg WASM
* writing Lua scripts in nginx
* Netlify / Vercel already have serverless definitions as part of manifest
Cloudflare: PM Wesley is interested in for Web3
RFC for ipfs/specs repo!
Cloudflare Pages
* support Netlify redirects without custom logic
* from --> to
Next steps:
* @lidel to create area in ipfs specs repo for gateway, manifest
* DONE: https://github.com/ipfs/specs/issues/257
* Fission will commit developer time to implementation and help move process forward
* Cloudflare interested
* Talk to rest of IPFSOPS group and see who else is interested in contributing
* Bring examples of existing manifest formats
* Netlify, Vercel, CF Pages, Github Pages, Buildpacks.io static sites directives, etc.
###### tags: `ipfsops`, `ipfs`, `meeting`