[API] Creator Payout History#96
Closed
Skinny001 wants to merge 7 commits intoSubStream-Protocol:mainfrom
Closed
Conversation
|
@Skinny001 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Member
|
resolve conflicts |
- Add VideoTranscodingService with FFmpeg-based HLS transcoding - Support multiple resolutions (360p, 720p, 1080p) for adaptive streaming - Implement VideoProcessingWorker with Redis-based job queue - Create video upload and streaming API endpoints - Add IPFS and S3 storage integration for transcoded segments - Build adaptive bitrate streaming logic for connection-based quality selection - Update database schema for video metadata and transcoding results - Fix CI/CD pipeline with Node.js 20.11.0+ and FFmpeg support - Add comprehensive API documentation and test suite - Integrate with existing pay-per-second subscription system Resolves: Users on different internet speeds need smooth viewing experience
:wq :qw :qw :wq
Contributor
Author
@elizabetheonoja-art done |
Contributor
Author
done |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This pull request introduces several key improvements to the backend API, focusing on subscription and payout functionality, as well as database enhancements. The main updates include adding new API endpoints for subscription events and payouts, switching to the
better-sqlite3library for improved SQLite support, and expanding the database schema to better support subscriber tracking.API Enhancements:
/api/subscription/eventsendpoint to receive subscription events, with optional shared secret validation for security. The endpoint uses a newSubscriptionServicefor event handling. [1] [2]/api/payoutsendpoint to fetch creator payouts, utilizing the database for data retrieval. [1] [2]/api/creator/:id/statsendpoint to retrieve creator statistics, including a cached subscriber count.Database and Dependency Updates:
node:sqlitelibrary withbetter-sqlite3for database operations, improving performance and reliability. [1] [2]appDatabase.jsfor clarity and efficiency. [1] [2] [3] [4] [5] [6] [7] [8] [9]Schema and Data Model Improvements:
subscriptionstable to the database schema for tracking active and inactive subscriptions, including timestamps and wallet addresses.creatorstable includes asubscriber_countcolumn, supporting efficient subscriber count retrieval and caching.Other Cleanups:
index.jsfor a cleaner server startup.These changes lay the groundwork for more robust subscription tracking and payout management, while also modernizing the database layer for future scalability.
close #4