AaronFiore/btcpayserver-docker
1
0
Fork 0
Code Activity

Add BTCPAY_UPDATE_CLEAN environment option

Browse Source 
This commit provides a less-intrusive pruning of all images after
running an update.

Ideally, there would be a better prune filter but that appears to
require more granular tracking of images; including
btcpayserver/docker-compose-generator (which only pulls from latest).

This option should suffice for the time being.
This commit is contained in:
Aaron Fiore
2025-11-14 17:00:20 -08:00
parent af3d32e5c7
commit bf518660c7
4 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
README.md
View File

@@ -114,6 +114,7 @@ Check out this video if you're interested in learning more about setting up [BTC
* `BTCPAY_ENABLE_SSH`: Optional, gives BTCPay Server SSH access to the host by allowing it to edit authorized_keys of the host, it can be used for managing the authorized_keys or updating BTCPay Server directly through the website. (Default: false)
* `BTCPAYGEN_DOCKER_IMAGE`: Optional, Specify which generator image to use if you have customized the C# generator. Set to `btcpayserver/docker-compose-generator:local` to build the generator locally at runtime.
* `BTCPAY_IMAGE`: Optional, Specify which btcpayserver image to use if you have a customized btcpayserver.
* `BTCPAY_UPDATE_CLEAN`: Clean (prune) all old BTCPayServer images after an update. WARNING: also removes all non-BTCPayServer images! (default: true)
* `BTCPAYGEN_EXCLUDE_FRAGMENTS`: Semicolon-separated list of fragments you want to forcefully exclude (eg. `litecoin-clightning`)
* `TOR_RELAY_NICKNAME`: If tor relay is activated with opt-add-tor-relay, the relay nickname
* `TOR_RELAY_EMAIL`: If tor relay is activated with opt-add-tor-relay, the email for Tor to contact you regarding your relay