crocodilestick / Calibre-Web-Automated

Calibre-Web but automated and with Calibre features! Fully automate and simplify your eBook set up!
https://github.com/crocodilestick/Calibre-Web-Automated
GNU General Public License v3.0
758 stars 16 forks source link

[Feature Request] Separate Book Files from Library / Split Libraries #92

Open tucker87 opened 1 month ago

tucker87 commented 1 month ago

Description Split metadata/books options is not being respected

To Reproduce

Expected behavior Books should be in /books but are ending up in the /calibre-library

Unexpected behavior Setting the database config as above breaks the cover images Downloads 404

Configuration(please complete the following information):

Additional context No original database/config. I've removed the config dir and started over with each test

CONFIG_ROOT is local Other *_ROOTS are on NAS

tucker87 commented 1 month ago

https://github.com/janeczku/calibre-web/blob/1eb9cd44dcbdd873df00de3fa42b02e0b3ddfa2f/cps/config_sql.py#L404

Found where the path is used in calibre-web. Too late for me to dig further.

jmarmstrong1207 commented 4 weeks ago

This issue should be higher priority than others as it's a breaking change of stock calibre-web feature.

Ingest script will need to respect this setting.

tucker87 commented 3 weeks ago

Closing as fixed. See conversation in PR #93

MrLemur commented 3 weeks ago

@tucker87 Please keep this issue open, the split library issue still remains.

luukrijnbende commented 1 week ago

I'm experiencing the same issue, please re-open. I have my books on an SMB share and I don't want to put the metadata.db file there as well, it should be separated.

tucker87 commented 1 week ago

Sorry! My mistake. I don't use this project anymore and thought the recent PRs were correcting the issue,

crocodilestick commented 1 week ago

Hi all, I wasn't aware of this CW feature and so CWAs features have never been written to support it. As of V2.1.0, the option to enable Split Libraries has been temporarily removed to prevent confusion but enabling of the feature is currently being worked on for V2.2.0