Running Standalone in Docker
If you wish to run Token Indexer locally as a standalone product, the easiest way is to run it using Docker. Images are periodically published to the GitLab registry:
Image Name | Meaning |
|---|---|
registry.gitlab.com/tezos-dappetizer/token-indexer-app:latest | Latest stable release (recommended) |
registry.gitlab.com/tezos-dappetizer/token-indexer-app:master | Latest build from master |
To run Token Indexer locally, you can use a Docker command like:
docker run -it --network=host \
-e DB_HOST=localhost \
-e DB_PORT=5432 \
-e DB_USERNAME=yourusername \
-e DB_PASSWORD=yourpassword \
-e DB_DATABASE=postgres \
-e DB_SCHEMA=token_indexer \
registry.gitlab.com/tezos-dappetizer/token-indexer-app:latest
The individual environment variables that can be passed to the container are explained below.
Variable Name | Meaning | Default |
|---|---|---|
TEZOS_NODE_URL | Tezos node RPC | https://mainnet-tezos.giganode.io |
IPFS_GATEWAY | Custom IPFS gateway | None (uses public gateways) |
DB_HOST | PostgreSQL hostname | localhost |
DB_PORT | PostgreSQL port | 5432 |
DB_USERNAME | PostgreSQL username | postgres |
DB_PASSWORD | PostgreSQL password | postgrespassword |
DB_DATABASE | PostgreSQL database name | postgres |
DB_SCHEMA | PostgreSQL schema name | indexer |
METADATA_UPDATE_PARALLELISM | Maximum concurrent jobs fetching token metadata | 100 |
SKIP_GET_METADATA | Completely skips fetching contract and token metadata if set to true | false |
INDEX_FROM_BLOCK_LEVEL | Level of the first block to be indexed (assumes that previous blocks don't contain any relevant token data) | 889027 |
Last modified 1yr ago