-
Notifications
You must be signed in to change notification settings - Fork 7
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
Stop relying exclusively on Infura for IPFS #200
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, it works when I specify my private IPFS node :D
In regards to the fallback; I have set it up to work with Infura as a fallback. You just need to set the REACT_APP_IPFS_INFURA_PROJECT_ID
and REACT_APP_IPFS_INFURA_SECRET_KEY
environment variables.
Two comments:
-
We are missing the check for whether it's able to connect to the IPFS node. Perhaps a notification with something like "unable to connect to the specified IPFS node, will use Infura" if it can not connect?
-
I think we should stick with one kind of model, now, we have different modals for updating the pinning service and updating the IPFS node.
I added a commit where we remove Infura as a fallback and instead spin up an IPFS node in the browser. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
closes #27
FYI: #27 (comment)
UI