bal-server/bal-pusher.env

29 lines
1.1 KiB
Bash

RUST_LOG=info
BAL_PUSHER_DB_FILE=/home/bal/bal.db
BAL_PUSHER_BITCOIN_COOKIE_FILE=/home/bitcoin/.bitcoin/.cookie
BAL_PUSHER_REGTEST_COOKIE_FILE=/home/bitcoin/.bitcoin/regtest/.cookie
BAL_PUSHER_TESTNET_COOKIE_FILE=/home/bitcoin/.bitcoin/testnet3/.cookie
BAL_PUSHER_SIGNET_COOKIE_FILE=/home/bitcoin/.bitcoin/signet/.cookie
BAL_PUSHER_ZMQ_LISTENER=tcp://127.0.0.1:28332
BAL_PUSHER_SEND_STATS=true
WELIST_SERVER_URL=http://welist.bitcoin-after.life
#
#The service for registering times requires signing the time with the key associated with the SSL certificate in use by Willexecutor. Once the first time is registered, it will be possible to update the
#certificate for your domain (for example using Certbot) and continue to use the old key to sign the times.
#
# EXAMPLE
# $ cp /etc/letsencrypt/live/we.bitcoin-after.life/privkey.pem /home/bal/privkey.pem
# $ sudo chown bal:bal /home/bal/privkey.pem
# $ sudo chmod 400 /home/bal/privkey.pem
# $ ls -l /home/bal/privkey.pem
# -r-------- 1 bal bal 241 31 oct 12.00 privkey.pem
#
#
SSL_KEY_PATH=/home/bal/privkey.pem
#your server domain. do not add https or final / only domain.
BAL_SERVER_URL="we.bitcoin-after.life"