Conversation
| @@ -1 +1,2 @@ | |||
| REACT_APP_ETH_NETWORK_WEB_SOCKET_ADDRESS=ws://eth-tx-node.default.svc.cluster.local:8546 No newline at end of file | |||
| REACT_APP_ETH_NETWORK_WEB_SOCKET_ADDRESS=ws://eth-tx-node.default.svc.cluster.local:8546 | |||
There was a problem hiding this comment.
Should this filename match the truffle network name?
There was a problem hiding this comment.
Yep exactly. Good catch. The main idea is to keep consistent with the keep-dev and keep-test. What do you think about this? Or maybe we should create a new environment variable dedicated to the dapp?
| @@ -1 +1,2 @@ | |||
| REACT_APP_ETH_NETWORK_WEB_SOCKET_ADDRESS=ws://eth-tx-node.default.svc.cluster.local:8546 No newline at end of file | |||
| REACT_APP_ETH_NETWORK_WEB_SOCKET_ADDRESS=ws://eth-tx-node.default.svc.cluster.local:8546 | |||
| REACT_APP_ETHERSCAN_DEFAULT_URL='https://etherscan.io/address/' No newline at end of file | |||
There was a problem hiding this comment.
This won't play nicely against the private network.
There was a problem hiding this comment.
Fine that it's here, just wanted to call it out.
There was a problem hiding this comment.
Possibly leave a comment.
|
Another thought - should we rename |
Agree. I thought about it. I'll update also in the circleci config. |
|
@sthompson22, |
Thanks for asking, right now it's |
Evnets subscirpiton works well without the websocket provider
.env files are not needed anymore. The default ehterscan address can be returned from the custom funcion.
|
Thanks for going through these updates. I'm going to take it for a spin in |
|
To give a bit of color on my naming recommendation in the last comment This allows us to be consistent around the naming pattern prefix Not super relevant now but say we create some new dapp for Keep, we call it "operations" in this example. Using the format above that would give us:
Benefit here is that it binds deployed applications that are of the same breed, sort of like labeling "frontend" and "backend", in a more specific way. Anywho I'm not firm on this, just wanted to explain my thought process on the original suggestion. Just fine with it as-is |
|
ah right Sloan. I missed it. I'll update |
We've removed all of the .env files, so there's nothing to copy anymore.
|
I had to do some surgery to get a To get this out to Ropsten, if it's not coupled with a contract deployment we'll need to do something similar. |
|
@nkuba @r-czajkowski Thanks again ya'll for getting this put together. I've run through a deployment to |
| export const OPERATOR_CONTRACT_NAME_EVENTS = 'eventKeepRandomBeaconOperatorContract' | ||
|
|
||
| export const ETHERSCAN_DEFAULT_URL = 'https://etherscan.io/address/' | ||
| export const ETHERSCAN_DEFAULT_URL = 'https://ropsten.etherscan.io/address/' |
There was a problem hiding this comment.
Please remember about handling it per environment in a follow-up PR.
Depends on: #1438
Closes: #1400
test build
New configs are deployed to
keep-dev, available @ http://keep-dapp-token-dashboard.default.svc.cluster.local/ (behind the VPN)