satoshiportal / esplora-deploy

esplora

Init docker swarm and overlay network, once

docker swarm init
docker network create --driver=overlay --attachable --opt encrypted esploranet

Do the following line only if data_bitcoin_mainnet doesn't already exist / isn't already mounted

cd ; mkdir data_bitcoin_mainnet ; sudo mount /dev/vdc data_bitcoin_mainnet/

Build the image -- if updating, remove all cached images

./build.sh

Start TLS manager (Let's Encrypt Companion) + Esplora

docker stack deploy -c docker-compose.yml esplora

Start Esplora outside of the docker-compose file

docker run -d --expose 80 --network=esploranet --name esplora -v /home/debian/data_bitcoin_mainnet:/data --rm --env-file esplora.env esplora bash -c "/srv/explorer/run.sh bitcoin-mainnet explorer"

esplora-deploy's Issues

Configs

NODE_ENV: production
BASE_HREF: base href for user interface (defaults to /, change if not served from the root directory)
STATIC_ROOT - root for static assets (defaults to BASE_HREF, change to load static assets from a different server)
API_URL:
CANONICAL_URL - absolute base url for user interface (optional, only required for opensearch and canonical link tags)
NATIVE_ASSET_LABEL - the name of the network native asset (defaults to BTC)
SITE_TITLE - website title for <title> (defaults to Block Explorer)
SITE_DESC - meta description (defaults to Esplora Block Explorer)
HOME_TITLE - text for homepage title (defaults to SITE_TITLE)
SITE_FOOTER - text for page footer (defaults to Powered by esplora)
HEAD_HTML - custom html to inject at the end of
FOOT_HTML - custom html to inject at the end of
CUSTOM_ASSETS - space separated list of static assets to add to the build
CUSTOM_CSS - space separated list of css files to append into style.css
NOSCRIPT_REDIR - redirect noscript users to {request_path}?nojs (should be captured server-side and redirected to the prerender server, also see PRERENDER_URL in dev server options)

Open-sourcing this

I think there is a lot of value in open-sourcing this tool.

1. For this to be included in Cyphernode. There isin't a reason for someone to have to run Cyphernode and Esplora separately if they want both.
2. To make it easier for people to use Esplora
3. To give back to blockstream for having done such a good job!

Looks like most of our configs are not in there. Any reason to keep it private ?