Deploy build

[kulpreet]

Build a version of the demo and deploy it on IPFS. Once ready, we will publish it so that demo.chlu.io loads that build

[fazo96]

Looks like the build fails because of multiformats/js-cid#38

I'll see what the best workaround is

[fazo96]

We made a test build: http://ipfs.io/ipfs/Qmd3P3hmXxrwnT3zyon1JXkTZEmG5JctKBFyT8G5Vvp2he/

[fazo96]

So the build fails due to

@kulpreet I am looking at all the options to solve this. Here is what we can do:

Short Term:

• (we chose this in Production build workaround #41) use this ugly trick Revisit targeting ES6+ facebook/create-react-app#2108 (comment)
• (looks this this won't work until we use babel 7) finishing and merging Prebuilt module for webpack chlu-ipfs-support#19 then importing that build instead of the babel transpiled sources
• finishing and merging Fix Uglify not minifying js-ipfs libraries #28, but this is only in case the others don't work because it requires ejecting
• load IPFS stuff using script tags

Long Term:

react-scripts 2.0 will use uglify-es instead of uglify solving this problem completely. The change is already implemented in the alpha, it will also support targeting older browsers which will take care of compiling subdependencies of ipfs automatically facebook/create-react-app#3815

Looks like the alpha works, but new issues show up:

• transform-runtime breaks under ordering of generator functions and class babel/babel#5655
• @jest-environment node not working in v22 jestjs/jest#5119

[kulpreet]

• setup subdomain demo
• dns link to server demo from ipfs hash
• provide a deploy script - which npm run deploy - which runs ipns publish and voila

[fazo96]

The IPFS ID of the node we are running on EC2 is QmYkctX9Wg5g2mBD8mnnNiCQE5toy3RqAkmzAmGEXY4dVU

this means that dnslink=/ipns/QmYkctX9Wg5g2mBD8mnnNiCQE5toy3RqAkmzAmGEXY4dVU is what needs to be stored into the TXT record for the domain. The A records need to point to IPFS gateway(s) reachable on port 80, we can use the public ones without any issues (check dig +short gateway.ipfs.io for IP addresses).

When we want to update the demo we just need to publish a new version using IPNS from the EC2 and that's it. We can backup the private key so that we don't risk losing access to making new publications.

When I was making the first build I created chlu.ydns.eu to try out the dnslink functionality, and it still works even though it's an old build and does not use IPNS or HTTPS

@kulpreet can you set up the domains and the dnslink? I can work on the deploy script in the meantime

Another thing to consider: we need to use hashHistory I think. I'll make a couple of tests to see if browserHistory works but I suspect it won't

[fazo96]

New build: https://ipfs.io/ipfs/QmawsKKMeLy1mLQFh8YQaQnMV4GQQfr3GFzgvNuUeFc3sM

This is based on commit d994d1d from PR #52

Build has been IPNS published to https://ipfs.io/ipns/QmYkctX9Wg5g2mBD8mnnNiCQE5toy3RqAkmzAmGEXY4dVU

[fazo96]

New build: https://ipfs.io/ipfs/QmYsqputTd3v84nEDKkgTN34ePuM5CZxM49yCPh8Hv5MFA

This is based on master as of now with a small change that disables all rendezvous servers except ws-star-signal-2