Markus Petzsch

I think the main problem was the way Zeus handled our combined QR code including a lnurl. They seem to have fixed that. That the lnurl doesn't get shown as...

If someone needs a test QR Code: https://btcpay.host/apps/2sZfhihthmnaGAUbtu84xCprDPcj/pos

[decoded](https://lnurl.fiatjaf.com/codec/) the lnurl and got this URL: https://btcpay.host/BTC/UILNURL/pay/app/2sZfhihthmnaGAUbtu84xCprDPcj/herbal-tea this gives me the following JSON: ```json { "callback":"https://btcpay.host/BTC/UILNURL/pay/i/4zx8fA99kyspYfZi87pqFj", "metadata":"[[\"text/plain\",\"Paid to petzsch's kitty (Order ID: JYyciymvLP9wZnKF6f96Vk)\"]]", "tag":"payRequest", "minSendable":2757000, "maxSendable":2757000, "commentAllowed":0, "nostrPubkey":"cd0ed24fdaf5efed5f4cd80fd36c0734ae32670bcbe8fdd5ddbad272a063d305", "allowsNostr":true...

It is indeed possible to setup Che on k3s. You just need to make sure that you don't deploy traefik when setting up the manager/server: `curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC="server...

Still waiting for my employer to provide me with 2 new VPS for setting Che+k3s up again on a clean install. While doing so, I'll document my steps taken. And...

I might have the wrong perspective about the local path storage provider: But it gave me quite a bit of headache with it's placement constraints (I think that's what they...

might be related: https://github.com/btcpayserver/btcpayserver-docker/issues/716

The transaction list now seems to work. Not quite sure what I did wrong there. Leaving this issue open for the strange Network cost line in the payment confirmation.

back to draft: changes to https://github.com/btcpayserver/btcpayserver-docker/pull/873 will reduce the amount of docs needed for this.

giving up on the lnbits fragment and therefore closing this.