-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can "server_url" be a link with a path? #5
Comments
@NicolasDorier if you need anyone to test things just give me a shout. |
Yes, it should work alright. But note that Lightning Publisher also uses the checkout page provided by Lightning Charge as an iframe, which I guess would add more complexity on your side? Of the Charge-based Lapps I wrote, only Lightning Publisher and nanotip rely on the embedded checkout page. The other Lapps display payments information on their own and rely solely on the API. |
well it seems easy for me to steal as long as I can put them in any path I want. |
Then yes, you can. Note that you have two configurable URLs: |
Any news @NicolasDorier on the publisher mods? |
no, have not start working on the API in btcpay |
@pieman64 it is done, please try https://twitter.com/BtcpayServer/status/1076025576845017088 |
Thanks @NicolasDorier I will switch my node from LND to c-lightning in the coming days and try it out. |
@pieman64 check https://www.youtube.com/watch?v=ZbM3jcxau0o Closing this issue |
Thanks @NicolasDorier we set it up a few days ago on our site after following developments in the BTCpay Slack channel. |
Very cool :D |
@NicolasDorier never thought of that. We simply added Publisher to an article we had written previously. I am following this issue btcpayserver/btcpayserver#50 in the hope that ERC tokens will be available at some point in the future. |
@shesek I plan to integrate lightning-charge to BTCPay as an option.
But, because we don't want to require users to open new ports, we use URL rewriting on nginx. (like https://btcpay.example.com/clightning-charge/btc/)
Will this work fine with wordpress lightning publisher?
The text was updated successfully, but these errors were encountered: