[WEB-1214-446] Move Yearn.finance CI/CD from aplify to IPFS

[yearn-linear-gh-sync[bot]]

the tldr: "make a github action to deploy and pin yearn.finance to IPFS every time the master branch gets updated

via github action, vercel, or fleek

we’re using AWS amplify which id like to change ASAP. for front end:

• Should deploy to IPFS so FE integrity can be independently verified
• CI/CD should be public so anyone/devs can easily review and fix build errors (right now only a couple people with AWS amplify access can debug)

[ghost]

I've started looking into this and will be testing out deployment soon in a fork. Is Yearn DNS on AWS Route 53? Also, is it only required for the master branch, or develop would be useful as well, linked to some subdomain, e.g. staging.yearn.finance?

[x48115]

Ideally:

• we use yearn.dev for develop branch builds
• we support pull request pull request previews (previously it was pr-123.yearn.dev)

we want to move away from amplify:

• to avoid vendor lock-in
• we want there to be transparency around builds/logs/CI/CD

[willianpaixao]

Hi @x48115 is there anyone working on this issue?

[xgambitox]

Hi @willianpaixao , this repo has been deprecated in favor of new frontend. You can take a look at the repo here https://github.com/yearn/yearn.fi

[willianpaixao]

Hey @xgambitox thanks for the quick reply. I'll take a look at the new repo now, but regardless, would be nice to make explicit in this repo's README it's been deprecated.