IPFS 0.5 Meetup, 23 May 2020

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: IPFS and the JAMstack: How stakefish uses IPFS - Eric de Courtis

Description

JAMstack is a new way of building websites and apps that deliver better performance, higher security, lower cost of scaling, and a better developer experience by combining JavaScript, APIs and Markup. What does this mean for IPFS? Eric de Courtis of stakefish explains in this lightning talk from the 0.5 Release Meetup.

stakefish is the leading staking service provider for blockchain projects. Join their community to help secure networks and earn rewards. https://stake.fish/en/

For more information
- read the go-ipfs 0.5 release announcement: https://blog.ipfs.io/2020-04-28-go-ipfs-0-5-0/
- visit the project website: https://ipfs.io
- or follow IPFS on Twitter: https://twitter.com/IPFS

Sign up to get IPFS news, including releases, ecosystem updates, and community announcements in your inbox, each Tuesday: https://ipfs.us4.list-manage.com/subscribe?u=25473244c7d18b897f5a1ff6b&id=cad54b2230

A

Okay, so my name is Eric D, Curtis, I, work for steak, fish and I'm here to talk to you about how we use ipfs and the gem stack yeah. So who are we steak? Fish were one of the leading operators for validators for proof of steak blockchains. So token holders can stick with us to secure. You know, networks and reward. So we run a lot of proof of steak infrastructure.

A

Steak fish is a sister company to have two pools. So if two pool is handling the proof-of-work blockchains, okay, so maybe you've been wondering you know, how can I? How can we become? You know, ipfs native? How can we deploy a PFS and two onto our website and start using it?

A

So we went through that process and I'm here to basically tell you how we did it and to give you ideas on maybe the challenges or what is required in order to get that done so first, the first thing to realize is that you can't have any dynamic contact, obviously on the on the content, distribution layer. So if you want your website to be served entirely from my PFS, you have to separate out the api and the static content and jan is kind of like an architecture for doing that. Now.

A

There's many frameworks that work with this architecture and I'll be here to talk to you. So we use Gatsby and yeah. So that's basically it and white matters well, because if you don't split up those two things, then basically it's impossible to use. I get this other than to serve just a few static absence.

A

So steak fish is powered entirely by ipfs and it's ipfs native, so meaning we target ipfs. First, then we retrofit the normal web onto it. So you know the steak fish website, basically get statically compiled with fold, see I see pipeline that we through that pipeline. We weep in all the assets on tapenade and then we update a DNS link text record, so we have updated DNS so that basically it routes to the right. The latest version of the site, yeah so and then for the normal traffic.

A

It comes in through the web to an IP FS gateway. So it's not actually served by it's not like. We have a normal stack and then an IPF that stack and we we kind of like you know, maintain you know two different copies of this thing. We actually just deployed to ipfs, so you can see here the DNS link. What that might look like it's very simple I mean there's a sub domain here, you don't have to do it with a sub domain, but that's how we've done it.

A

It's more secure this way, because then you can delegate that sub domain and change the security on that yeah. So that's quite simple, so you can see here you can go through any gateway and our website basically loads and everything works. Just as you would expect anything that requires an API goes directly to the API through the normal. They can't go through I, pee FS, but all the static content here is through ipfs and there's no server-side rendering.

A

So you can see that and oops sorry yeah. So here's a kind of like a 1 million foot view of what what's actually happening there. So we have CloudFlare and when we commit via get goes to the CDI CD pipeline, we pin the data on pinata and then we update the the record on CloudFlare and all the issues normal HTTP requests go to the ipfs gateway and all the api calls go to the api cluster and that's pretty much it. It's a lot simpler and it's a lot cleaner and it works fairly.

A

Well then, you would imagine so anyway, if you would like to learn more about us feel free to reach out to us. If you, we would like to actually we'd like to contribute to the Wikipedia on ipfs project, because it I think that project needs a little bit of love and yeah. So if any developers are interested in in helping us with that, well we're hiring so feel free to send your resumes all right. Thanks a lot.