-
Notifications
You must be signed in to change notification settings - Fork 416
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
High-level explainer of Gateways, in an IPFS context. #246
Comments
LGTM |
Also note via @yusefnapora: Gateway is great for playing well with the outside world, but you're really only getting part of the full IPFS goodness. Let's emphasize gateway as a gateway drug ;) |
Update: @olizilla may have some material he wrote to onboard folks that could be used as initial source material! |
There is also a short section on HTTP Gateways I wrote at https://docs.ipfs.io/guides/guides/addressing/#http-gateways which could be reused/expanded into a dedicated article about Gateways. I believe it is important to recognize three types of HTTP gateways:
DNSLink gateway is useful for "private/personal" hosting and the other two are more like "public" service (here is a community list of public ones). Happy to provide context/help/call with anything related to this. |
see also local gateway (localhost:8080) vs public/shared gateway (example.org) vs the canonical public gateway (ipfs.io) |
I'll tackle this one… |
The bounty list from the first post is this thread is not accessible :/ |
@bertrandfalguiere - can you view this? https://github.com/ipfs/devgrants/projects/1#column-7126098 |
Also, important to incorporate documentation on writable gateways which is here: https://discuss.ipfs.io/t/writeable-http-gateways/210 |
Here is the condensed version of the onboarding doc for the gateways for the IPFS Infra team https://gist.github.com/olizilla/81cee26ffa3ae103e4766d2ae0d2f04b |
How's your progress going @EricLScace? Anything I can help out with? |
See branch https://github.com/EricLScace/ipfs-docs-v2/tree/issue%2393 for WIP. Just getting rolling at this point and have material yet to integrate over the next days. I'll be in touch if I get stumped and cannot get help. |
Great stuff, I'm glad you've got enough to get moving. Yeah post in here if you need a hand. |
@EricLScace -- what can we do to help unblock this? Do you have an ETA for materials for review? |
@EricLScace -- update? If we don't hear from you by Wednesday 12 Feb, we'll open this up to other contributors instead. Thank you! |
Sorry, I’m just wrapping up another project on Feb 12. I’ll be back on this immediately thereafter.
… On Feb 10, 2020, at 09:05, Jessica Schilling ***@***.***> wrote:
@EricLScace -- update? If we don't hear from you by Wednesday 12 Feb, we'll open this up to other contributors instead. Thank you!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Hey @EricLScace - let us know if you're still working on this, otherwise we can open it back up to other contributors. |
Yes still working. |
Do you have a planned ETA? I've been working on an FAQ I'd love to add to a basic description once that's ready. |
Let’s open this back up to other contributors. @bertrandfalguiere - is this something you might be interested in picking up? |
...as "when not to deplay a gateway" Ref #93
Manual section numbering :-( Ref #93
...and some minor wording edits. Ref #93
Reassigning to @EricLScace. |
Add example To do: provide defense mechanism Ref #93
Move temporarily into new folder Ref #93
How's this going @EricLScace? I can see you've added a bunch of commits recently, that's great! Anything I can help out with, or are you still working on things? |
Still working :-)
I have a checklist of stuff to work through, and will be more consistent about making end-of-day work-in-progress PRs on a branch named issue#93.
… On 2020 Apr 17, at 15:10 , Johnny ***@***.***> wrote:
How's this going @EricLScace <https://github.com/EricLScace>? I can see you've added a bunch of commits recently, that's great! Anything I can help out with, or are you still working on things?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <https://github.com/ipfs/docs/issues/93#issuecomment-615464831>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABTYUQVZZ7L62KHWOTI4AXDRNDATDANCNFSM4FMDYFWQ>.
|
Good stuff! Looking forward to reading everything once it's done. |
This issue has a bounty!
Successfully closing this issue by producing a production-ready piece of documentation can earn you not only the undying love of the IPFS community — it can net you a financial reward. See the current list of bounty issues and their values here.
The need in brief
A high-level explainers of what gateways are in an IPFS context.
At the Berlin developer summit, we decided gateways were important to write a concept doc about. Here was the original draft:
Some concerns:
Host
header.Deliverable
A concise, high-level description of this IPFS concept. It should answer the following, supplemented whenever possible by diagrams, videos and/or code examples:
Content should take the form of a Markdown document, supplemented by diagrams as embedded images. File locations should be as follows:
Guidelines
The text was updated successfully, but these errors were encountered: