-
Notifications
You must be signed in to change notification settings - Fork 29
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
Deploy dApp on IPFS #53
Comments
Yesterday I have met @RachBLondon from 3Box. They have been developing a wrapper to easily use IPFS. |
@christianbrb I was thinking for a while if we could possibly leverage IPFS for the backup/restore of the user data. Thank you for the links, I will have a look. I think at some point I was looking into deploying to IPFS and it didn't seem like much work to actually integrate the deployment in our CI workflow. |
How to automatically deploy it on IPFS: https://medium.com/coinmonks/automated-deploy-to-ipfs-and-ens-12bae2f40302? |
Thanks @christianbrb I will have a look. |
I would say that using the ENS part is probably not feasible since automating this requires to pass the private key controlling the domain to the CI server configuration. I don't think we want to do that. As an alternative, from a quick read, I can see that there is ipns and DNSLink. So we could use something like that for people to always find the latest deployment of the light client dApp |
I am not sure if this is possible yet but I am just noting it as a point to research. We should look if it is possible to use ENS through IPNS so that we don't have to update ENS everytime a deployment happens. |
Afaik, https://mesa.eth.link/ and http://openswap.eth.link/ do it this way, maybe this could serve as an example. |
Description
Acceptance criteria
Tasks
Story Points
Why do this?
We want to ensure the dApp is always accessible in a decetralized way.
The text was updated successfully, but these errors were encountered: