fix docker-compose

pull/5228/head
zjb0807 3 years ago
parent a31c704bb3
commit 97050ab5b4
  1. 12
      docker-compose/README.md
  2. 2
      docker-compose/docker-compose-no-build-ganache.yml
  3. 2
      docker-compose/docker-compose-no-build-geth.yml
  4. 2
      docker-compose/docker-compose-no-build-hardhat-network.yml
  5. 2
      docker-compose/docker-compose-no-build-open-ethereum-nethermind.yml
  6. 2
      docker-compose/docker-compose.yml

@ -18,14 +18,14 @@ This command uses by-default `docker-compose.yml`, which build the explorer into
## Configs for different Ethereum clients
Also, the repo contains built-in configs for different clients without need to build the image
- Ganache: `docker-compose -d -f docker-compose-no-build-ganache.yml up -d`
- HardHat network: `docker-compose -d -f docker-compose-no-build-hardhat-network.yml up -d`
- Geth: `docker-compose -d -f docker-compose-no-build-geth.yml up -d`
- OpenEthereum, Nethermind: `docker-compose -d -f docker-compose-no-build-open-ethereum-nethermind up -d`
- Running only explorer without DB: `docker-compose -d -f docker-compose-no-build-no-db-container.yml up -d`. In this case, one container is created - for the explorer itself. And it assumes that the DB credentials are provided through `DATABASE_URL` environment variable.
- Ganache: `docker-compose -f docker-compose-no-build-ganache.yml up -d`
- HardHat network: `docker-compose -f docker-compose-no-build-hardhat-network.yml up -d`
- Geth: `docker-compose -f docker-compose-no-build-geth.yml up -d`
- OpenEthereum, Nethermind: `docker-compose -f docker-compose-no-build-open-ethereum-nethermind up -d`
- Running only explorer without DB: `docker-compose -f docker-compose-no-build-no-db-container.yml up -d`. In this case, one container is created - for the explorer itself. And it assumes that the DB credentials are provided through `DATABASE_URL` environment variable.
All of the configs assume, that the Ethereum JSON RPC is running at http://localhost:8545.
In order to stop launched containers, run `docker-compose -d -f config_file.yml down`, where replace `config_file.yml` with the file name of the config, which has been launched before.
You can play with the BlockScout environment variables, which are present at `./envs/common-blockscout.env`. The description of the environment variables are available in [the docs](https://docs.blockscout.com/for-developers/information-and-settings/env-variables).
You can play with the BlockScout environment variables, which are present at `./envs/common-blockscout.env`. The description of the environment variables are available in [the docs](https://docs.blockscout.com/for-developers/information-and-settings/env-variables).

@ -14,7 +14,7 @@ services:
blockscout:
depends_on:
- postgres
- db
image: blockscout/blockscout:${DOCKER_TAG:-latest}
restart: always
container_name: 'blockscout'

@ -16,7 +16,7 @@ services:
blockscout:
depends_on:
- postgres
- db
image: blockscout/blockscout:${DOCKER_TAG:-latest}
restart: always
container_name: 'blockscout'

@ -14,7 +14,7 @@ services:
blockscout:
depends_on:
- postgres
- db
image: blockscout/blockscout:${DOCKER_TAG:-latest}
restart: always
container_name: 'blockscout'

@ -16,7 +16,7 @@ services:
blockscout:
depends_on:
- postgres
- db
image: blockscout/blockscout:${DOCKER_TAG:-latest}
restart: always
container_name: 'blockscout'

@ -14,7 +14,7 @@ services:
blockscout:
depends_on:
- postgres
- db
image: blockscout/blockscout:${DOCKER_TAG:-latest}
build:
context: ..

Loading…
Cancel
Save