b0VIM 9.0 {c ^`h timdaub kazoo ~timdaub/Projects/attestate/docs/source/configuration.rst utf-8
U3210 #"! U tp ad 4 K
b
e
d
L
v * A ` D C + * ``IPFS_HTTPS_GATEWAY`` describes the host that IPFS extraction requests are made against. A list of publicly accessible IPFS gateways can be found `here `_. * ``EXTRACTION_WORKER_CONCURRENCY`` is the number of simultaneous requests the extraction worker will make against ``RPC_HTTP_HOST``. It must be an integer value and it cannot be smaller than `1`. * ``DATA_DIR`` is the directory that stores all results from extraction and transformation of the crawler. It must be set to a file system path (relative or absolute). * ``RPC_API_KEY`` is the API key for the host extraction requests are made against. It must be set if an Ethereum full node was provisioned behind an HTTP proxy that requires a bearer token authorization via the HTTP ``Authorization`` header. In this case, the header is structurally set as follows: ``Authorization: Bearer ${RPC_API_KEY}``. * ``RPC_HTTP_HOST`` describes the host that Ethereum JSON-RPC extraction request are made against. It must be set to an URL to an Ethereum full node's JSON-RPC endpoint that starts with ``https://``. ``ws://`` or ``wss://`` prefixes are currently not supported. We support URLs that include the API's bearer token as is the case with, e.g., Infura or Alchemy. to run: The following environment variables are **required** for ``@attestate/crawler`` before an invoking command. already been set in, e.g., the ``.env`` file can be overwritten by passing them ``proces* ``IPFS_HTTPS_GATEWAY_KEY`` is the API key for the host IPFS extraction requests are made against. It must be set if an IPFS node was provisioned behind an HTTP proxy that requires a bearer token authorization via the HTTP ``Authorization`` header. In this case, the header is structurally set as follows: ``Authorization: Bearer ${IPFS_}``. * ``IPFS_HTTPS_GATEWAY`` describes the host that IPFS extraction requests are made against. A list of publicly accessible IPFS gateways can be found `here `_. * ``EXTRACTION_WORKER_CONCURRENCY`` is the number of simultaneous requests the extraction worker will make against ``RPC_HTTP_HOST``. It must be an integer value and it cannot be smaller than `1`. * ``DATA_DIR`` is the directory that stores all results from extraction and transformation of the crawler. It must be set to a file system path (relative or absolute). * ``RPC_API_KEY`` is the API key for the host extraction requests are made against. It must be set if an Ethereum full node was provisioned behind an HTTP proxy that requires a bearer token authorization via the HTTP ``Authorization`` header. In this case, the header is structurally set as follows: ``Authorization: Bearer ${RPC_API_KEY}``. * ``RPC_HTTP_HOST`` describes the host that Ethereum JSON-RPC extraction request are made against. It must be set to an URL to an Ethereum full node's JSON-RPC endpoint that starts with ``https://``. ``ws://`` or ``wss://`` prefixes are currently not supported. We support URLs that include the API's bearer token as is the case with, e.g., Infura or Alchemy. to run: The following environment variables are **required** for ``@attestate/crawler`` before an invoking command. already been set in, e.g., the ``.env`` file can be overwritten by passing them ``process.env`` object. However, if necessary, environment variables that have variables from a ``.env`` file in the project root into Node.js's `_ to automatically load environment ``@attestate/crawler`` internally uses `dotenv --------------------- Environment Variables purpose is to serve as a reference for all configurable options. Attestate's crawler comes with plenty of configuration options. This page's Compared to other tools that may help you replicate Ethereum state locally, ============= Configuration