Xaque8787
commented
2 months ago Not sure I understand this part here
The idea is to create and use an file to match the groups with the category e.g movie,series
File could look like this:
movie provider 1=movies movie provider 2=movies series123 = series
As for using a file instead of env var to define terms for REPLACE TERMS, REMOVE TERMS, and or SCRUB HEADER. This is once how I was handling this, but after moving the project to a Docker image I switched to using env variables. I think there may be some commented out legacy code I could try to bring back and have this be a feature, but this would introduce needing to include the files in a mapped volume so they could be edited on the host machine, and that isn't necessarily a bad thing, however the other branches of this project use docker managed volumes rather than volume mounts, and I'd like to not introduce volume mounts into those. So if I do implement this, it may be a specific feature of the main branch "m3uparser" and not the other branches.
The idea is to create and use an file to match the groups with the category e.g movie,series
File could look like this:
movie provider 1=movies movie provider 2=movies series123 = series ...
The Replacements could also be done via a file to increase maintainability? This could be optional so the use of the parameters would still work
File would look like this:
"replace-this=with-this" "replace-that=with-that"