gateway-registry
List of Public IPNS-Link Gateways (by ipns-link)
ipns-link
Expose local http-servers (web-apps) through IPNS-Link (by ipns-link)
gateway-registry | ipns-link | |
---|---|---|
2 | 10 | |
4 | 31 | |
- | - | |
0.0 | 0.0 | |
over 1 year ago | about 2 years ago | |
Shell | ||
MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
gateway-registry
Posts with mentions or reviews of gateway-registry.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-11-11.
-
Optional end-to-end encryption
We have decided to implement, in near future, an optional SSL/TLS passthrough mode at least for the registered public gateways. HTTPS requests made using this mode, cannot be inspected by the gateways, making the Browser to Origin route end-to-end encrypted.
-
A few notes on IPNS-Link-Gateways and www.ipns.live
This is our ofiicial public gateway registry. You shall find all public IPNS-Link-Gateways we know of here.
ipns-link
Posts with mentions or reviews of ipns-link.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-07-09.
-
Serve a service/port on IPFS instead of content, ngrok decentralized alternative?
I saw this project, IPNS-Link, that seems promising, but I wasn't able to make it work yet and seems to require specialised IPNS-Link gateways, they can't use just any IPFS gateway, and their freely available gateways seem to be all down rn, so I'd probably have to host my own gateway anyways.
-
is it possible ipfs host a php website?
You might wanna take a look at ipns-link.
-
Introducing IPNS-Link
Install and run a free and open-source app on your local server (the Pi in your case), following this easy tutorial.
-
Open call for developers
We welcome you to implement the IPNS-Link project, especially the Gateway, in a proper server-side language - be it Go, JS, Rust, Ruby, Python - whatever you are good at. The existing prototype, in the spirit of playful experimentation, has been rather hurriedly hacked in Bash 🙈. Thankfully, it works! But of course, we need to evolve.
-
A few notes on IPNS-Link-Gateways and www.ipns.live
Loading an ipns-link-exposed website for the first time might take a while. This is because the Gateway has to locate your site and peer with its host node. Subsequent requests for the site, however, are served faster because the Gateway maintains persistent peering with the site's host node.
-
IPNS-Link
Here's an overview and a quick-start tutorial. And here's a prototype gateway.
-
Exposing http-server (web app) using IPNS
The static blue background is missing. This might happen due to the following. The background is embedded in the html and sourced from a root-relative URL. Now, being a path-gateway, ipns-link.herokuapp.com requires the Referer header (with absolute URL) in the http request, so that it can resolve the PeerID when requested a relative path without the /ipns/PeerID prefix. Although the Gateway wants a complete referrer URL, the embedded tags may override it with a different ReferrerPolicy. If overridden in this way, the Gateway can't resolve the PeerID and fails. NOTE: this problem WILL GO AWAY once the IPNS-Link-GATEWAY supports wildcard subdomains, hopefully in the near future. Then, there wouldn't be any dependence on the Referer or cookie or server-side cache for resolving root-relative URLs, and everything would work as intended. Subdomain Gateway has always been the end-goal, but due to the lack of a domain I went with a path-gateway for prototyping.
What are some alternatives?
When comparing gateway-registry and ipns-link you can also consider the following projects:
ipns-link-gateway - Access http-servers (web-apps) exposed using IPNS-Link
torsocks - Library to torify application - NOTE: upstream has been moved to https://gitweb.torproject.org/torsocks.git
Go IPFS - IPFS implementation in Go [Moved to: https://github.com/ipfs/kubo]
specs - Technical specification for IPNS-Link
contribute - Contribute to IPNS-Link
crumb-show-hn - A simple Show HN client in Crumb.