All .strm files are going to /torbox/movies folder

[ianweatherburn]

.strm files are all placed in the /torbox/movies folder despite using SCAN_METADATA option. (my mistake...see response below)
movies and series folders are created but series folder remains empty

image

anonymoussystems/torbox-media-center:latest

.env values

MOUNT_METHOD=strm
MOUNT_PATH=/torbox
SCAN_METADATA=true

docker log

root INFO Mount method: strm
root INFO Mount path: /torbox
root INFO TorBox API Key: <redacted>
root INFO Mount refresh time: 3 hours
root INFO Fetching all user downloads...
root INFO Processing files with 15 parallel threads
root INFO No webdl downloads found.
apscheduler.scheduler INFO Adding job tentatively -- it will be properly scheduled when the scheduler starts
root INFO Starting scheduler and mounting...
apscheduler.scheduler INFO Adding job tentatively -- it will be properly scheduled when the scheduler starts
apscheduler.scheduler INFO Added job "getAllUserDownloadsFresh" to job store "default"
apscheduler.scheduler INFO Added job "runStrm" to job store "default"

[ianweatherburn]

Apologies, I see the .env is not SCAN_METADATA but ENABLE_METADATA instead.

The separation of movies and series however is still not correct with many series appearing in the movies folder. I don't appear to have movies ending up in the series folder though?
In addition on container startup, many rate limit logs appear.

2025-10-30 09:05:26,176 root ERROR Error searching metadata: 429. rate limit exceeded
2025-10-30 09:05:26,268 root ERROR Error searching metadata: 429. rate limit exceeded
2025-10-30 09:05:26,355 root ERROR Error searching metadata: 429. rate limit exceeded

[AktasC]

Hello there 👋

Apologies, I see the .env is not SCAN_METADATA but ENABLE_METADATA instead.

Indeed, if you do not enable the environment variable everyting will end up in the /movie folder as stated in the README:

This isn't perfect, so use with caution. If this option is false it skips scanning and places all of your video files in the movies folder

---

The separation of movies and series however is still not correct with many series appearing in the movies folder. I don't appear to have movies ending up in the series folder though? In addition on container startup, many rate limit logs appear.

There's also a warning about this in the README:

Please also keep in mind that you will be subject to rate limiting of our search endpoint when using the metadata option. Seeing 429 errors will be common.

---

This is why I proposed manual classification in #37.
Let's wait for a response from @Wamy-Dev, hopefully they can find a suitable solution.

[ianweatherburn]

Yes, definitely using ENABLE_METADATA is there, and some shows are going to "Series". I have similar utilities working elsewhere and identifying shows with a regex of "(?i)S0?\d{1,2}E0?\d{1,2}" is simple enough, but doesn't seem to be applied here as many series episodes end up in movies incorrectly.
But let's see...

[Wamy-Dev]

Manual classification is planned, but it is quite a complicated system in this case. I will figure out what to do for this.