-
Notifications
You must be signed in to change notification settings - Fork 0
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
Fill/review contracts value in config #2
Comments
hey @aminlatifi we need to pull someone in who has an overview of the giveconomy to review this |
I think bot sections can be managed by the devops team. Other values can be crossed checked with https://www.notion.so/giveth/Deployment-52935e6579034f1b940bbef161e82229?pvs=4 |
ok thanks I was looking for that. |
Thank you @aminlatifi - I update https://github.com/Giveth/giveconomy-monitoring/blob/main/src/config/production.ts according to the Deployment page in Notion (no changes) and set the new address for givpower-bot (updated for all three chains to correct value) ... maybe someone can do another quick check, but it should be fine now |
@aminlatifi can you review? :) |
Alert system is running now - looks good to me! I uncommented Gnosis and op configs, doublechecked against notion deployments and updated the bod address |
@geleeroyale Two points:
|
It's super important to fill the giveconomy monitoring configuration with all and the latest values of related contracts.
I have entered values, so it's needed someone to review them.
Also, I am sure the bot section is not filled for every chain. I deliberately didn't fill them in to make this issue later and get other related guys involved in this project.
giveconomy-monitoring/src/config/develop.ts
Lines 91 to 95 in 88a229d
To brief:
Note that the develop.ts and production.ts can be same. The only difference is that the production.ts will be used if
NODE_ENV=production
is set in .env. Also, the graphql schema would not fetch by API. Running in develop mode would be fine so.The text was updated successfully, but these errors were encountered: