remove resync service and run vdb command from foreground in startup_script

This commit is contained in:
Ian Norden 2020-03-23 12:12:04 -05:00
parent 8b7ecee4ec
commit a5fc994c79
2 changed files with 6 additions and 30 deletions

View File

@ -65,28 +65,6 @@ services:
- "127.0.0.1:8080:8080"
- "127.0.0.1:8081:8081"
resync:
depends_on:
- db
build:
context: ./../../
cache_from:
- alpine:latest
- golang:1.12.4
dockerfile: ./dockerfiles/super_node/Dockerfile
args:
USER: "vdbm"
CONFIG_FILE: ./environments/superNodeETH.toml
environment:
VDB_COMMAND: "resync"
IPFS_INIT: "true"
IPFS_PATH: "/root/.eth_resync/.ipfs"
DATABASE_NAME: "vulcanize_public"
DATABASE_HOSTNAME: "db"
DATABASE_PORT: 5432
DATABASE_USER: "vdbm"
DATABASE_PASSWORD: "password"
graphql:
restart: always
depends_on:

View File

@ -49,19 +49,17 @@ fi
# If IPFS initialization was successful
if [[ $? -eq 0 ]]; then
echo "Beginning the vulcanizedb super node process"
./vulcanizedb ${VDB_COMMAND} --config=config.toml 2>&1 | tee -a vulcanizedb.log &
echo "Running the VulcanizeDB process"
./vulcanizedb ${VDB_COMMAND} --config=config.toml
else
echo "Could not initialize IPFS."
exit 1
fi
# If Vulcanizedb startup was successful
# If VulcanizeDB process was successful
if [ $? -eq 0 ]; then
echo "Super node successfully booted"
echo "VulcanizeDB process ran successfully"
else
echo "Could not start vulcanizedb super node process. Is the config file correct?"
echo "Could not start VulcanizeDB process. Is the config file correct?"
exit 1
fi
tail -f vulcanizedb.log