Usage:
./manage.sh -n <network> -a <action> <optional args>
-n|--network: [ mainnet | testnet | mocknet ]
-a|--action: [ start | stop | logs | reset | upgrade | import | export | bns ]
optional args:
-f|--flags: [ signer,proxy ]
export: combined with 'logs' action, exports logs to a text file
ex: ./manage.sh -n mainnet -a start -f proxy
ex: ./manage.sh -n mainnet -a start -f signer,proxy
ex: ./manage.sh --network mainnet --action start --flags proxy
ex: ./manage.sh -n mainnet -a logs export
./manage.sh -n <network> -a start./manage.sh -n <network> -a restart./manage.sh -n <network> -a start -f signer./manage.sh -n <network> -a restart -f signer./manage.sh -n <network> -a start -f proxy./manage.sh -n <network> -a restart -f proxy./manage.sh -n <network> -a stop./manage.sh -n <network> -a export
./manage.sh -n <network> -a logs # check logs for completion
./manage.sh -n <network> -a restart./manage.sh -n <network> -a import
./manage.sh -n <network> -a logs # check logs for completion
./manage.sh -n <network> -a restart./manage.sh -n <network> -a logsThis will create a log file in ./exported-logs for every running service.
Note that each time you run this command the log files will be overwritten.
./manage.sh -n <network> -a logs export./manage.sh -n <network> -a pullSome of the data in ./persistent-data/<network> is owned by root, so this will need to run with sudo privileges.
sudo ./manage.sh -n <network> -a resetStore legacy BNS data to ./persistent-data/bns-data
This step is required if the env var BNS_IMPORT_DIR is uncommented
./manage.sh bns