New media branch #37
Open
New media branch #37
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tings for leaf file types.
… for these in our relay panel stats.
…ith stats db as sql is easier to update and query
- Add SubscriptionTier struct with data_limit and price fields - Update RelaySettings struct to include subscription_tiers field - Modify settings handlers to process subscription tiers data - Update viper config to handle subscription tiers storage - Ensure proper JSON serialization/deserialization of tier data
…date - Enhanced function to conditionally create a new kind 411 event if there are changes in . - Passed as a parameter to and related route handlers. - Improved configuration update logic and comparison checks for to minimize unnecessary kind 411 creation.
…date - Enhanced updateRelaySettings function to conditionally create a new kind 411 event if there are changes in subscription_tiers. - Passed store as a parameter to updateRelaySettings and related route handlers. - Improved configuration update logic and comparison checks for subscription_tiers to minimize unnecessary kind 411 creation.
…only update kind 764/888
- Updated createNIP88EventIfNotExists and createOrUpdateNIP88Event functions to include dynamic 'subscription_tier' tags based on values retrieved via Viper configuration. - Implemented type assertions and error handling for retrieving and parsing 'subscription_tiers' from configuration. - Ensured consistent tagging for tiers, including data limits and prices, with improved error logging for type conversions and assertions.
…ers when the relay runner needs to make an adjustment to the tier prices it will take too much effort changing all the kind 888 to reflect this change so if we just update it on kind 411 then subscribers can pull the updated pricing fron 411
Adds functionality to retrieve subscriber information by Bitcoin address. This method supports transaction processing by allowing lookup of subscriber details when processing incoming Bitcoin payments. - Implements GetSubscriberByAddress in GormSubscriberStore - Returns complete subscriber record including npub for payment processing - Handles both 'not found' and general database error cases
|
Is there a reason why we have a new sqlite database specifically for subscriber information? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.