Libraries handling multiple directories

[kactaplb]

Issues managing multiple directories in a single komga library.

Running docker on a windows machine with smb shared pools. My library is spread out amongst these pools eg. pool1/ebooks, pool2/ebooks, etc. A komga library seems to only allow 1 root directory, and I am having issues trying to mount docker cif volumes accordingly.

 # invalid named volume paths
- namedvol1/ebooks:/data/ebooks/pool1
- namedvol2/ebooks:/data/ebooks/pool2
# valid but last mount overwrites the previous
- namedvol1:/data/ebooks/
- namedvol2:/data/ebooks/

# technically valid bind mounts however since host machine is windows, there are issues with the docker seeing the mapped network drives and paths properly.
# Workarounds like manual drive mounting using wsl command has drawbacks such as a machine restart clearing it.
- /mnt_path/ebooks:/data/ebooks/pool1

Best workaround I could come up with is this but not ideal. Komga library root folder: /data/ebooks

  komga:
    volumes:
      - namedvol1_ebooks:/data/ebooks/pool1
      - namedvol1_comics:/data/comics/pool1
      - namedvol2_ebooks:/data/ebooks/pool2
...
volumes:
  namedvol1_ebooks:
...
      type: cifs
      device: "//ip/pool_1/media/ebooks"
  namedvol1_comics:
...
      type: cifs
      device: "//ip/pool_1/media/comics" # multiple connections same pool perf issues?
  namedvol2_ebooks:
...
      type: cifs
      device: "//ip/pool_2/media/ebooks"
...

Please let me know if I am missing something specific to my server or docker setup. Despite my niche case, I think having komga handle multiple directories is not far fetched request. A lot of other self hosted media software lets libraries define multiple directories at the app level like plex.

[gotson]

raised before in #1524

with Docker there shouldn't be any need, Docker should be able to handle mounting whatever you want in the container

[kactaplb]

Thanks for the link, but subdirectories isn't quite so simple on a non linux machine as I outlined above. Much like the last reply in #1524, the problem comes from a library that is spread out across multiple drives. The workarounds all have problems, like with bind mounted smb share drives not bring visible to docker after a restart.

I'd also like to +1 for a feature request for the app to handle this.