smacke / smacke/ffsubsync

[Feature Request] Docker image + batch processing

Open
#214 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
7.9k
Forks
323
PR merge metrics
No merged PRs in 30d

Description

Hi and thanks for this amazing project.

I'm hosting (like many) an instance of Plex/Emby/Jellyfin in a containerised environment and I think this project would be a godsend for such scenarios.

What I'm suggesting with this Issue is the possibility of making ffusbsync available as a container image, able to run as a deamon and operate continuously on a pre-defined media library (path passed as an ENV variable when container is started maybe?).

Structure of these media library (regardless of the media service used) looks like this:

  • LIbrary
    • Film_A
      • Film_A.mkv
      • Film_A.srt
    • Film_B
      • Film_B.mkv
      • Film_B.srt

What do you think about it? Thanks!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points; begin by clarifying the Docker image, daemon behavior, media-library path configuration, and batch-processing expectations. Done would require an agreed scope and a working container that continuously processes the described library structure.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, python
Domain
audio-video-rtc, devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.