Why? Because the indexer tends to produce erroneous data when the git-hosted .envio/cache runs behind the present day (it leads to increasingly more CoinGecko API calls, which result in API rate limits being hit, etc.)
We could use GitHub actions-based cron jobs for redeploying to envio/analytics.
Why? Because the indexer tends to produce erroneous data when the git-hosted
.envio/cacheruns behind the present day (it leads to increasingly more CoinGecko API calls, which result in API rate limits being hit, etc.)We could use GitHub actions-based cron jobs for redeploying to
envio/analytics.