2019-09-23 15:46:28 +02:00
|
|
|
This doc is about the Docker container for "flowee/bitcore".
|
|
|
|
|
|
|
|
|
|
Other Docker containers [in this repo](../README.md)
|
|
|
|
|
|
|
|
|
|
The Bitcore-proxy container requires both a flowee/hub and a flowee/indexer
|
|
|
|
|
to connect to for its backing data store. The advantage is that containers
|
|
|
|
|
for bitcore-proxy stay simple and small. No need for any volumes (storage).
|
|
|
|
|
|
|
|
|
|
As detailed in the [generic readme](../README.md), it is known to work that
|
|
|
|
|
you port-forward the API on services like *the Hub* and *Indexer* for
|
|
|
|
|
others to connect to it by nothing but the hosts network address. Either a
|
|
|
|
|
DNS entry, or a direct IP address. Use this in the *FLOWEE_HUB* env var
|
|
|
|
|
below.
|
|
|
|
|
|
|
|
|
|
A simple setup example:
|
|
|
|
|
|
|
|
|
|
docker run -e FLOWEE_HUB=192.168.1.2 -d -p 3000:3000 \
|
|
|
|
|
-e FLOWEE_INDEXER=192.168.1.2 flowee/bitcore-proxy
|
|
|
|
|
|
|
|
|
|
### Available options (env-vars)
|
|
|
|
|
|
2019-10-06 15:20:41 +02:00
|
|
|
* FLOWEE_INDEXER *The hostname or IP and optionally port to connect to the Indexer
|
|
|
|
|
(see [Indexer](../indexer/README.md) container)*
|
2019-09-23 15:46:28 +02:00
|
|
|
|
|
|
|
|
* FLOWEE_HUB *The hostname or IP and optionally port to connect to the Hub
|
2019-10-06 15:20:41 +02:00
|
|
|
(see [hub](../hub/README.md) container)*
|
2019-09-23 15:46:28 +02:00
|
|
|
|
|
|
|
|
* FLOWEE_LOGLEVEL *allows you to change the log-level. Recognized options
|
|
|
|
|
are info, quiet or silent*
|
|
|
|
|
|
