Quote:
Originally Posted by kovidgoyal
No, you need to either run the server from within the GUI (there is an option to autostart the server when the GUI is started) or stop the standalone server when you are launching the GUI.
|
Kovid, what do you think of simulating read-only content server access by using CALIBRE_OVERRIDE_DATABASE_PATH? The content server startup script would copy the metadata.db somewhere, set the env var, then start the content server.
I see two failure modes:
1) The user makes changes using the content server. These changes could modify the library folder structure but would not get written to the correct db. Result: library and db out of sync.
2) The user makes changes using the GUI. In this case the library that the content server sees could be out of sync with its db.
The first one is a "you got what you deserve" sort of error. The "promise" has to be that the content server never makes changes to the library, even if it can.
The second one can be worked around with a script that checks the timestamp on metadata.db, stops the content server(s), copies the metadata.db file, then restarts the content server. This is more-or-less what I do with my library in dropbox being served by my VPS. I don't want the content server to have the "real" db open so I avoid dropbox sync problems.
Yes, this is a hack, but is it an egregious one?