Indexer Configuration
- Below you will find a list of CLI configuration options that can be used to configure either the Fuel indexer service, the standalone Fuel indexer GraphQL API service, or both.
- For those who prefer to use a configuration file, you can check out the default service configuration file, which also shows the default values used for these configuration options.
Usage
Using the fuel-indexer
binary
./fuel-indexer [options]
Using the fuel-indexer-api-server
binary
./fuel-indexer-api-server [options]
Options
-c
--config
- Path to the configuration file.
-m
--manifest
- Path to manifest file from which initial indices will be loaded
Fuel node: The node running the Fuel client implementation.
--fuel-node-host
- IP of the Fuel node
--fuel-node-port
- Port of the Fuel node
GraphQL API: The endpoint at which GraphQL queries will be processed. This is context dependent. If using the
fuel-indexer
binary, these options apply to the GraphQL service run in that binary. If using thefuel-indexer-api-server
binary, these options will apply to that service.
--graphql-api-host
- IP at which to bind the GraphQL server
--graphql-api-port
-
Port at which to bind the GraphQL server
-
--run-migrations
-
Whether to run the migrations on the GraphQL API's connected database
Postgres: Standard Postgres connection options.
--postgres-host
- Postgres host
--postgres-port
- Postgres port
--postgres-username
- Postgres username
--postgres-password
- Postgres password (redacted from logging)
--postgres-database
- Postgres database
SQLite: An alternative database implementation using standard SQLite connection options
--sqlite-database
- Path to SQLite database