QMediaSync addresses the challenge of managing media metadata for files stored in cloud drives by automating the synchronization of STRM files, metadata downloads, and uploads. It targets users of media servers like Emby, providing a direct link parsing and 302 redirect service to streamline access to cloud-stored content. The project aims to simplify media library organization and access for users leveraging cloud storage solutions.

How It Works

The project utilizes cloud drive open platform APIs to interact with stored files. It generates STRM files, which are essential for media server integration, and handles the downloading and uploading of associated metadata. A key feature is its ability to provide direct link parsing and external 302 redirects, simplifying how users access their media remotely or through compatible applications. It also includes specific proxy ports for Emby integration.

Quick Start & Requirements

• Primary install/run command: Debugging: go run .. Release build: cd build_scripts && sudo ./build_and_release.sh -v vx.xx.xx. Docker image publishing requires prior Docker Hub login.
• Non-default prerequisites: PostgreSQL (version 15.x recommended, requires separate installation and configuration), 115 Open Platform AppID, TMDB API KEY, OpenAI compatible API KEY, Fanart.tv API KEY (optional, requires code modification). GitHub CLI (gh) is needed for building releases.
• Companion frontend: QMediaSync-Frontend is required.
• Links: Telegram group: http://t.me/q115_strm, QQ group: 1057459156. Detailed setup instructions are available via an implied Wiki.

Highlighted Details

• Automated synchronization of STRM files and media metadata from cloud drives.
• Direct link parsing and 302 redirect service for media access.
• Emby proxy support with dedicated ports.
• Cross-platform binary compilation (Linux, Windows) and Docker image publishing capabilities.

Maintenance & Community

The project maintains active community channels via a Telegram group (http://t.me/q115_strm) and a QQ group (1057459156). Contributions via Pull Requests are accepted for most functionalities, excluding resource searching, subscription, downloading, and reverse engineering interfaces. Users can contact the author via email, Telegram, or QQ if PRs require attention.

Licensing & Compatibility

The license type is not specified in the provided README content. Compatibility for commercial use or linking with closed-source projects cannot be determined without a stated license.

Limitations & Caveats

The open-source version requires users to self-provision a 115 Open Platform account and install PostgreSQL separately. Certain core functionalities, such as resource searching and downloading, are explicitly excluded from contribution acceptance. The project relies heavily on multiple external API keys, which must be obtained and configured by the user.