New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use Calibre Specific Environment Variables #8
Comments
I don't think it does what you think it does. It just lets you specify the config folder location while starting Calibre, as opposed to setting it in the gui after first start. |
Specifically I'm talking about:
As my library is on a network drive that doesn't play well with file locking. |
Gotcha. I'll look into it. |
Try this:
|
This seems to work if I let the docker install create a new database and then move it. If I copy my existing calibre database to the override path it reports a corrupted database (can't implement the file lock) and tries to create a new metadata.db in the networked library location. However, the previous install has carried across operating systems so this may also be interfering. I may have to recreate the database. |
I have not tested moving database across OSes |
setting calibre variables ( |
@hex2a - Hi mate, could you elaborate on this a little? I'm a bit of a noob and backing up my system tonight with a view to trying this out tomorrow. I'm currently using docker on Ubuntu and will be moving my libraries from local storage to GDrive (loads of comics). From what you're saying it's better to specify the env. override in the services file. I've been reading a bit online and it's not immediately clear. |
Passing |
It's also not working for me, does anyone have any ideas? |
Someone is going to have to do a pull request to bring in the support: |
Just asking regarding the above - would I be able to modify a local copy of the docker to support this prior to it possibly being pulled into a future master? If so, how could I do this? It's a showstopper for me right now due to mergerfs/gsuite causing Calibre to regenerate an empty metadata.db on the local filesystem after each restart of the container. Thanks! |
Sorry, I'm a little thick, and I just saw hurricane's posts. Yup, calibre is missing the |
Is it possible to use the calibre environment variables to have the calibre metadata.db in a folder separate to the book storage.
I've tried adding this as a docker environment option with no success.
The text was updated successfully, but these errors were encountered: