Files
plm-electrumx/.env.example
T
davideandClaude Sonnet 5.5 419ff90859 Docker: keep data in ~/.plm-electrumx (bind mount) instead of named volumes
db/ is the database, ssl/ the certificate; ELECTRUMX_DATADIR, PLM_UID and
PLM_GID configure it like the node's ~/.palladium. The entrypoint fails with a
clear message if a data directory is not writable.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-10-22 15:38:04 +02:00

23 lines
946 B
Bash

# Copy to .env (never commit it). RPC credentials of the node: rpcuser/rpcpassword (or an rpcauth user)
# in ~/.palladium/palladium.conf.
PLM_RPC_USER=username
PLM_RPC_PASSWORD=change-me
#CACHE_MB=1200
#REPORT_SERVICES=tcp://electrum.example.com:50001
#ELECTRUMX_TCP_PORT=50001
# Data directory of the host: db/ (database) and ssl/ (certificate). Create it first: mkdir -p ~/.plm-electrumx/db ~/.plm-electrumx/ssl
#ELECTRUMX_DATADIR=~/.plm-electrumx
# owner of the data directory, if it is not user 1000
#PLM_UID=1000
#PLM_GID=1000
# SSL (port 50002): on by default, self-signed certificate generated once and kept in ssl/ of the data directory.
#SSL_ENABLED=true
# name (or IP) of the server, written in the generated certificate
#SSL_HOSTNAME=electrum.example.com
#ELECTRUMX_SSL_PORT=50002
# your own certificate (paths inside the container; mount the files, see DEPLOY.md):
#SSL_CERTFILE=/certs/fullchain.pem
#SSL_KEYFILE=/certs/privkey.pem