Calibre Server - read only?

[john_es]

I am setting up the headless calibre server on my machine. Is there a way to make that readonly? I just don't want people to be able to add/dlete books or metadata.

[kovidgoyal]

The calibre server does not allow adding/deleting/editing operations.

[john_es]

Awesome - that was the answer I was hoping to see

[aarcane]

Can the calibre server be configured to detect changes to the metadata and reload itself when they occur, since it can't make changes itself?

[kovidgoyal]

The server does detect changes to metadata.db and reload itself.

[timofonic]

Originally Posted by kovidgoyal

The calibre server does not allow adding/deleting/editing operations.

Why not? It can be quite convenient for uses that move quite often of location and want to upgrade their libraries.

[theducks]

Originally Posted by timofonic

Why not? It can be quite convenient for uses that move quite often of location and want to upgrade their libraries.

1) Big (write) Security issues would need to be solved.
2) This is not as simple a task as you make it. any change a is a 'Transaction' a) DB Metadata change. b)1 or more Book format files written/changed. 3)Backup metadata written. (there might be more, I am not a Calibre developer)

To steal Kovid's line 'Patches are welcome'

[timofonic]

Originally Posted by theducks

1) Big (write) Security issues would need to be solved.
2) This is not as simple a task as you make it. any change a is a 'Transaction' a) DB Metadata change. b)1 or more Book format files written/changed. 3)Backup metadata written. (there might be more, I am not a Calibre developer)

To steal Kovid's line 'Patches are welcome'

What about using a subset of CMIS?

Seriously, it's pure madness when you go to multiple computers and need to read a book or modify one, calibre-server doesn't support writing so the process is messy if you are remote (right?). What about an interoperatibility standard for ebook libraries?

A multi-user library server for Calibre could be useful, if it's strong enough and adopted as standard, ebook readers and other ebook managers could implement it.

You are right about patches, but I'm not so used to Python. I think Calibre must be improved in resource efficiency first, currently it's damn slow.

[DoctorOhh]

I don't expect a content server to have adding, deleting, or editing features any time soon. I don't believe the demand for this is high enough at present and there are multiple solutions that work around this issue.

Originally Posted by timofonic

A multi-user library server for Calibre could be useful, if it's strong enough and adopted as standard, ebook readers and other ebook managers could implement it.

A multi-user server is on Kovid's todo list but currently there is no ETA on when it will be available. I don't know if or when the content server might reflect anything of the sort.

Originally Posted by timofonic

I think Calibre must be improved in resource efficiency first, currently it's damn slow.

If you find calibre slow, you may want to open a new thread detailing where you run into slowness. For some areas it is easy to point out why and speed can be dramatically increased. I have a library with about 13000 entries and it did a cold open in 20 seconds.

[Adoby]

Originally Posted by timofonic

You are right about patches, but I'm not so used to Python. I think Calibre must be improved in resource efficiency first, currently it's damn slow.

Compared to what other ebook managers?

Some hints for speedup here:

https://www.mobileread.com/forums/sho....php?p=2244745