Skip to content

feat: added a new provider peachify.ts#33

Merged
An0n-01 merged 2 commits intocinepro-org:devfrom
nischaldoescode:dev
Apr 29, 2026
Merged

feat: added a new provider peachify.ts#33
An0n-01 merged 2 commits intocinepro-org:devfrom
nischaldoescode:dev

Conversation

@nischaldoescode
Copy link
Copy Markdown
Contributor

Closes #31

Description

This PR merges the development branch into main, bringing significant enhancements to CinePro Core including a new streaming provider (Peachify).

Type of Change

  • 🐛 Bug fix (non-breaking change which fixes an issue)
  • 🌟 New feature (non-breaking change which adds functionality)
  • 📀 New provider (adding a new streaming source provider)
  • 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 📝 Documentation update
  • ♻️ Code refactoring (no functional changes)
  • 🎨 Style/formatting changes
  • ⚡ Performance improvement
  • 🔧 Configuration change

Related Issues

Closes #31

Changes Made

  • Did a Comeback at cinepro after long time, i would like to get welcomed greeted.

New Provider

  • Peachify Provider: Multi-server provider with AES-GCM decryption support and flexible source parsing

Code Quality

  • Standardized code formatting across all providers
  • Improved handling for aliased source fields
  • Enhanced parallel fetching across multiple servers

Provider Information

Peachify Provider

  • Provider Name: Peachify
  • Provider ID: peachify
  • Base URL: https://peachify.top
  • Content Types Supported:
    • Movies
    • TV Shows

Key Features:

  • Supports 6 different servers
  • Optional AES-GCM decryption for encrypted responses
  • Parallel server fetching for better reliability
  • Flexible parsing for aliased/messy source schemas
  • Multi-quality stream extraction
  • Subtitle support
  • Robust fallback handling

Provider Testing

Peachify Tested with:

  • Multiple movies and TV episodes
  • Successfully handles encrypted and non-encrypted responses
  • Works across all available servers

Test Results:

  • Peachify: Returns multiple sources across servers
  • All providers pass health checks
  • CI pipeline passing all checks

Checklist

General

  • My code follows the code style of this project
  • I have run npm run format to format my code
  • My code builds without errors (npm run build)
  • I have tested my changes locally
  • I have commented my code, particularly in hard-to-understand areas
  • My changes generate no new warnings or errors
  • I have read the CONTRIBUTING.md guidelines

Provider Checklist

  • Providers extend BaseProvider from @omss/framework
  • Providers have unique id and descriptive name
  • Providers declare correct capabilities (movies/tv support)
  • Implements getMovieSources() and/or getTVSources() correctly
  • All streaming URLs use this.createProxyUrl() for proxying
  • Includes proper error handling with diagnostics
  • Uses this.console.log() for logging (not console.log())
  • Includes appropriate headers via this.HEADERS
  • Returns standardized ProviderResult format
  • Provider files are in src/providers/ directory
  • Providers export classes properly for auto-discovery
  • Tested with multiple TMDB IDs for movies and/or TV shows
  • Works correctly with the proxy system
  • Handles edge cases (missing content, API errors)

Documentation

  • I have updated the README.md if necessary
  • I have added/updated comments in my code
  • I have documented any new environment variables
  • I have added examples if introducing new patterns

Screenshots (if applicable)

N/A - Backend/API changes only

Additional Context

Performance Impact

  • No performance impact
  • Performance improvement (parallel server fetching)
  • Potential performance concern

Details:

Peachify uses parallel requests across multiple servers and decrypts responses when required.

Breaking Changes

No breaking changes - all additions are backward compatible with existing infrastructure.

Dependencies

No new dependencies added:

  • Uses native crypto APIs for AES-GCM decryption

For Maintainers

Merge Checklist

  • Code review completed
  • All CI checks passing
  • No merge conflicts
  • Providers tested by reviewer

@An0n-01 An0n-01 added the enhancement New feature or request label Apr 29, 2026
Copy link
Copy Markdown
Member

@An0n-01 An0n-01 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great

* aes-gcm decryption key used by peachify for encrypted api responses.
* this is embedded in their frontend bundle.
*/
const ENCRYPTION_KEY =
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice that you could solve the encryption. For the future, please move encryption logic into decryptor.ts in the /[provider]/ folder. thanks

Oh and please store the encryption key Base64 encoded. thanks

(for now, i'll do the changes👍)

@An0n-01 An0n-01 merged commit 837da0e into cinepro-org:dev Apr 29, 2026
2 checks passed
@An0n-01 An0n-01 linked an issue Apr 29, 2026 that may be closed by this pull request
6 tasks
@An0n-01 An0n-01 mentioned this pull request Apr 29, 2026
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Provider Request: Peachify

2 participants