Local filesystem path feeds do not work — likely unimplemented

[MrNeptune44]

Hey, I was trying to use opds-proxy to serve a local directory of .epub files and noticed that the path: field appears supported in the config (based on feed/file.go and the LocalFeed struct), but using it results in a 404 when accessing the expected URL.

Example config I used:

port: 9090

feeds:
  - name: "Library"
    url: "lib"
    path: /home/user/media/books

Running the server shows no errors, but the /lib route returns a 404, and no feed is registered. Even with valid book files present in the path, the route never appears on the homepage.

It seems like path: support for local filesystem feeds exists in the source, but the feed loader logic doesn’t register FileFeed types properly.

Would love to see this officially implemented (or documented if I’m missing something)! Happy to PR if needed.

[evan-buss]

You are correct, the path object field is not recognized on the struct and is just ignored. Currently, opds-proxy only works with an existing OPDS feed and doesn't generate the feed itself.

There are other lightweight OPDS servers that I've seen to generate an OPDS feed from a directory of files/folders such as https://github.com/dubyte/dir2opds, but I've not used them.

At this time I don't have any plans add OPDS feed generation to this project. I try to adhere to the unix philosophy of doing one thing and allowing other software to compose/integrate. In this case that's separating the OPDS feed generation from the rendering of the web interface.