## Right now the volumes are just added in a commented out state but if the end
## user would prefer to add volumes to their own usage cases all they will need
## to do is uncomment what they require and then build the container using docker-compose.yml
## Volumize the wallets in a separate location for backup purposes may be unnecessary.
# VOLUME /data/.local/share/lbry/lbryum/wallets
# VOLUME /data/.local/
## If the config ends up needing it's own volume it should be located here.
# VOLUME /etc/lbry/conf.py
## Downloaded blobs will be in their own separate volume for keeping backups of critical secrets and data separate from backups of potentially massive blob files.
## TODO: Decide if this next step is ideal or if it would be samrter to run as root to assert volume permissions on launch for improved container statelessness.
## Setting this entrypoint should mean that you can `docker exec lbrynet commands`
## and you should be able to control the daemon's CLI this way. There is an
## alternative method we could use here where we have an entrypoint shell script which could be a bit smarter.
## An docker-entrypoint should eventually be created and installed into the container $PATH with a config install script that checks for the existance of a config.py and if it exists don't install docker envvars established elsewhere.
## If the container doesn't detect a conf.py file however have it install a fresh copy into /etc/lbry/conf.py and run that from a fresh copy from somewhere sensible.
