-
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
Updating for agent0 and various cleanup #118
Conversation
profiles: | ||
- "service-bot" | ||
command: | | ||
/bin/sh -c "sleep 1; python scripts/checkpoint_bots.py --pool-check-sleep-blocks 30 --infra" |
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.
kinda curious why we need the sleep?
@@ -1,4 +1,3 @@ | |||
version: "3.9" |
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.
good stuff, the warning irks me🤘
@@ -15,7 +14,7 @@ services: | |||
profiles: | |||
- "data" | |||
working_dir: /app/ | |||
command: /bin/sh -c "python scripts/run_data_analysis.py" | |||
command: /bin/sh -c "python scripts/run_analyze_data.py" |
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.
no sleep here... do we need it?
POSTGRES_PASSWORD: password | ||
POSTGRES_USER: admin | ||
POSTGRES_DB: postgres_db | ||
POSTGRES_DB: agent0_db |
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.
do we wanna pull these from the .env
file instead of redefining them here?
@@ -1,5 +1,5 @@ | |||
POSTGRES_USER=admin | |||
POSTGRES_PASSWORD=password | |||
POSTGRES_DB=postgres_db | |||
POSTGRES_DB=agent0_db |
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.
nit: if we expect to have more than one db present on the postgres instance, we might want to indicate that by changing the env variables in the .env
file.... for example
# .env
AGENT0_POSTGRES_USER=admin
AGENT0_POSTGRES_PASSWORD=password
AGENT0_POSTGRES_DB=agent0_db
MY_POSTGRES_USER=me
MY_POSTGRES_PASSWORD=yo
MY_POSTGRES_DB=my_db
then in the compose file....
environment:
POSTGRES_PASSWORD: $AGENT0_POSTGRES_PASSWORD
POSTGRES_USER: $AGENT0_POSTGRES_USER
POSTGRES_DB: $AGENT0_POSTGRES_DB
might need to pass as args rather than env vars since I'm not sure if .env
vars will be interpolated but hopefully the gist makes sense
echo " --postgres : Runs a postgres db container for storing data." | ||
echo " --data : Runs the data framework, querying the chain and writing to postgres." | ||
echo " --service-bot : Runs checkpoint bot and invariance check bots on the chain." | ||
echo " --random-bot : Runs random bots on the chain." |
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.
kinda confused as to what a "random" bot is in this case...
setup_env
.setup_env
.