the project compiles fine, the database is created, the server is running smoothly, frontend works fine.
i'm using local parity with this config:
[parity]
chain = "spec.json"
[footprint]
pruning = "archive"
tracing = "on"
i tried both master and production branches.
the problem: the database is not populated, nothing is being indexed.

@banteg run heroku local
make sure you have redis also installed
@banteg The database is populated with a series of workers that need to be scheduled. Easiest way is to dedicate a dyno to each worker in heroku.
Here is a list of workers that need to be scheduled to start indexing blocks:
web = bin/start-pgbouncer-stunnel mix phx.server
balances = bin/start-pgbouncer-stunnel mix scrape.balances 1000000
blocks = bin/start-pgbouncer-stunnel mix scrape.blocks 1000000
internal_transactions = bin/start-pgbouncer-stunnel mix scrape.internal_transactions 10000
receipts = bin/start-pgbouncer-stunnel mix scrape.receipts 10000
scheduler = bin/start-pgbouncer-stunnel mix exq.start scheduler
worker = bin/start-pgbouncer-stunnel mix exq.start
Thanks for your answers. I think that readme should be updated accordingly.
@acravenho can you provide a good documentation on how to run an explorer?
@banteg @rstormsf I'm in the process of updating readme. I will have it done by Monday.
Indexer has been rewritten in #162. This bug and setup instructions to fix it are obsolete. Open an new issue you have problems using new indexer on master.