audius-protocol
audius-protocol copied to clipboard
[WIP] Hackathon staging mode
Description
Tests
Monitoring - How will this change be monitored? Are there sufficient logs / alerts?
My thoughts so far,
We use files like discovery-provider-1.sh to manage configs, and config.json is for private keys and the like
We should have something like audius-compose set-env discovery-provider-1 similar to how we have audius-cli to set individual configs to these *.sh files.
We should have stage and prod configs in one place (audius-docker-compose) to avoid redundancy of configs in multiple places.
I suggest we have something like
audius-compose load-env <type of node> [prod|stage (default stage)] [replica number to set (default 1)]
That pulls these configs and writes the configs to the same *.sh file.
This has been resolved in follow up PRs