A self-hosted Real-Debrid webdav server you can use with Infuse. Together with rclone it can mount your Real-Debrid torrent library into your filesystem and load it to Plex or Jellyfin.
This RFC outlines procedures for handling repair issues with the Real-Debrid API during file processing in the zurg project.
Context
Two scenarios require repair actions:
Link Discrepancy: Fewer links returned by the Real-Debrid API than selected files in a torrent.
Unusable Links: Links that cannot be downloaded or streamed.
Scenarios Requiring Repair
Case 1: Link Discrepancy
When the API returns fewer links than selected files:
Unrestrict each returned link to determine its corresponding file.
Match links with files.
Result: Files with corresponding links are functional; those without are "broken."
Case 2: Unusable Links
When a link cannot be used:
Verify if data can be received from Real-Debrid.
Discard the unusable link.
Result: File is marked as "broken."
Definition of Broken Files
Files without a functional link are classified as "broken files" and require repair.
Repair Process
Repair Method 1: Redownload Entire Torrent
Description: Redownload all video files in the torrent.
Steps:
Initiate download for the entire torrent.
Check link completeness and assign files their respective links.
End repair process if no broken files remain.
Repair Method 2: Redownload Cached Variations
Description: Redownload all cached variations of the torrent with broken file IDs.
Steps:
Use Real-Debrid's unrestrict check endpoint to find cached variations.
Redownload cached variations and verify broken files.
End repair process if no broken files remain.
Repair Method 3: Selective Redownload of Broken Files
Description: Redownload broken files in batches of 100 items.
Steps:
Create batches of broken files.
Sequentially download each batch.
Verify the integrity of downloaded files.
Diagram
graph TD
A[Identify Broken Files] --> B{Case 1: Link Discrepancy?}
B -->|Yes| C[Unrestrict Links]
C --> D[Match Links to Files]
D --> E[500 Files Linked, 500 Broken]
B -->|No| F{Case 2: Unusable Link?}
F -->|Yes| G[Discard Unusable Link]
G --> H[1 File Marked Broken]
E --> I[Initiate Repair Process]
H --> I[Initiate Repair Process]
I --> J{Repair Method}
J -->|Method 1| K[Redownload Entire Torrent]
J -->|Method 2| L[Redownload Cached Variations]
J -->|Method 3| M[Selective Redownload in Batches]
Conclusion
I will only implement methods 1 and 3 on the next version. Method 2 will come on the version after that. Feedback is welcome to improve the repair process.
Introduction
This RFC outlines procedures for handling repair issues with the Real-Debrid API during file processing in the
zurgproject.Context
Two scenarios require repair actions:
Scenarios Requiring Repair
Case 1: Link Discrepancy
When the API returns fewer links than selected files:
Case 2: Unusable Links
When a link cannot be used:
Definition of Broken Files
Files without a functional link are classified as "broken files" and require repair.
Repair Process
Repair Method 1: Redownload Entire Torrent
Repair Method 2: Redownload Cached Variations
Repair Method 3: Selective Redownload of Broken Files
Diagram
Conclusion
I will only implement methods 1 and 3 on the next version. Method 2 will come on the version after that. Feedback is welcome to improve the repair process.