d11n
I couldn't find a way to do so via docker-compose and further customizing the fragment. Maybe the better option would be to integrate electrs as a proper BTCPay fragment itself...
I remember we discussed adding those options, but went for the simplest approach which can then be extended with custom wrapper scripts. Free to open it up for dicussion again...
As said, I'm not opposing oppening it up for discussing — especially since I also use that functionality. Meanwhile, here's my wrapper script: ```bash #!/bin/bash BACKUP_FILE=/var/lib/docker/volumes/backup_datadir/_data/backup.tar.gz BACKUP_DIR=/root/backups cd /root/btcpayserver-docker ./btcpay-backup.sh...
Hmm, good point, I haven't tried either — I think the cert creation just fails without interupting the setup and it'll try again later.
I think the problem starts already with us not knowing that the Cloudflare fragment is being used there and that the address hence might need adaptation. This will be more...
@NicolasDorier Can we maybe use the [real IP header](https://github.com/btcpayserver/btcpayserver-docker/blob/master/docker-compose-generator/docker-fragments/opt-add-cloudflared.yml#L10) value for this? Otherwise we could use the presence of the `CLOUDFLARE_TUNNEL_TOKEN` env value as a hint to discard the clearnet...
Cloudflare only handles requests to port 80 (http) and 443 (https), not anything beyond that. For Lightning peer connections you will need port 9735, which does not work with Cloudflare.
It seems to be possible to open up other ports as well, at least if I understand this doc correctly. Can someone check whether or not this allows to circumvent...
@dstrukt Sure, go ahead. We might also want to add a short info note there, that simply adding the labels already attaches them to the address seen above. That was...
@dstrukt this is the custom CSS on the level of individual payment requests, pull payments, etc. I think it's rather confusing to have this additional option and imho it's simply...