-
Notifications
You must be signed in to change notification settings - Fork 26
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
Dockerize the development environment #576
Conversation
You need to install correct dependencies and set env variables. It depends on the network- eg if you want to run the dapp on goerli test network you need to use
If you want to run the dapp against your local chain it's more complicated because you have to deploy all contracts to your local chain and link dependencies. I believe @beaurancourt is working on setting up all environments(deploying necessary contracts, setting up nodes, setting up bitcoin server, running dapp) locally. |
thanks @r-czajkowski !! @beaurancourt is there a branch somewhere? I'm more than happy to just contribute to your stuff instead of duplicating effort :) |
Here's the base layer: keep-network/local-setup#156 There's also https://github.com/keep-network/local-setup/tree/build-keep-core which is my WIP branch for getting keep-core to work. The main thorn right now is that in order for the light relay to do it's job, we need to use bitcoin signet instead of bitcoin regtest, and getting that to work has been a lot of yak shaving. I hit the same UI bug you did above; so the UI stuff I did isn't valuable yet. My goal here is to have the UI and keep-core both plugged into local bitcoin signet and local geth with all of the relevant contracts deployed! |
Ok, after making the changes to I've also updated the README. I think this is now ready for review - it's certainly suitable to be used for basic front end dev. Not all functionality can be tested though because it doesn't hook into the Keep Local Setup that @beaurancourt mentioned. @cygnusv Would appreciate you checking this branch out and making sure that it works for you too. |
@theref I believe this error is happening because you didn't put your infura api key inside the .env
You have to put it in a place of EDIT: we might want to put tha in the README file too |
I changed the env variables when running locally, just didn't commit them because then my infura api key would be public. As I said, it's intermittent, and seems to be to do with the wallet that I use (Frame is dodgy, metamask seems fine) |
This still requires a lot of system resources, beware!
No description provided.