-
-
Notifications
You must be signed in to change notification settings - Fork 371
Paid extensions #2229
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
Paid extensions #2229
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## dev #2229 +/- ##
==========================================
- Coverage 59.17% 58.81% -0.36%
==========================================
Files 60 60
Lines 9036 9133 +97
==========================================
+ Hits 5347 5372 +25
- Misses 3689 3761 +72 ☔ View full report in Codecov by Sentry. |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as resolved.
This comment was marked as resolved.
|
Great idea ! If the payment is dependant on the version as in the video that means that hotfixes for it are also behind a paywall ? |
|
interesting issue. I think its possible that once paid, you get access to all future updates. |
|
If the extension does not contain pay_link and the user has already paid for the previous version then this update is for free. So let's say extension 1.0 and extension 2.0 have pay_links and versions 1.1, 1.2, 2.1 and 2.2 don't. In that case you need to pay only for the major version update, but not for minor version updates. At least that is how I understand this feature is implemented. |
|
@arbadacarbaYK @prusnak regarding the
Those this ☝️ answer your concerns? |
|
|
@motorina0 ah yes. That is even better. Love this! |
Summary
Add support for paid extensions.
It is now possible for extension developers to require payment for their extension.
When an admin user wants to install an extension, it will be prompted with a request for payment. The payment can be made:
install_paid_extension.mov
Features:
pay_linkfield, see description here.pay_link(no need to pay again for a new release install)pay_link, thus requiring a new payment to install themServe the extension file:
https://raw.githubusercontent.com/lnbits/lnbits-extensions/paid_extensions/extensions.json2 sats(basic features), the next 3 have a cost of5 sats(premium)Test Scenarios
Prerequisites: configure the repo for the paid extension (see above description).
Retry Install