![]() Calibre provides some control through its calibredb command (and others), but plugins do not necessarily provide CLI control and in anycase the presentation of the data in the GUI can be really useful when cleaning and maintaining your library. Having played with the calibre GUI on a separate machine and an isolated copy of my library, I now realise the power of tools provided by calibre and third-party plugins to clean and maintain my library. With the setup described above, my ability to manage the library is very limited. * Optional: Use Nginix to provide an easy url (without port numbers) for my users to access calibre-web. * Install calibre-web on the same headless server to provide the users with a great front-end via a browser. This will provide calibre-web with the tools and APIs it needs to serve the library to the users. * Install calibre on a headless server at home, which is in any case always on (so won't represent additional material energy consumption) and is not in danger of being turned off by a user (so calibre is more likely to be always available). * I want a single admin user (me) to be able to manage the library to keep metadata clean, remove duplicates, etc. * I want my users to be able to access the library from any device and retain any of their personal settings. * I want a number of different users to be able to be able to access the calibre library using an interface designed for calibre, but without them having to install any specific software. * I want my Calibre library to be always available and not at risk of being turned off by a user. ![]() Here's an update on my experience so far, perhaps it will be useful for people who have similar plans. Do you tend to convert everything to a single format when you intially import, or do you just leave each file in its original format and convert each time a user sends it to a reader (if necessary)?Īnswers to these questions and any other headless tips are welcome ![]() Those of you with a headless setup - do you use a separate isolated instance of calibre on a desktop to prepare the ebooks to your satisfaction and then 'calibredb add' the modified ebooks into the headless calibre database?Ģ) Our collection has a mix of formats mostly AZW3 and MOBI but also AZW, EPUB, and PRC. ![]() Two questions have already arisen:ġ) When populating the library by importing books from an ereader, I often want to take advantage of plugins that would be available within the calibre GUI, but that don't necessarily support a headless setup. However, there are some things in my workflow (as the general family librarian) that I still need to optimise and would love some tips. Everything's central and each user can log on from any terminal or mobile device without installing or configuring anything - so far so good. I've got calibre-server running on a linux server and calibre-web on the same box providing a friendly, well-featured interface for each of the users to browse books and send them to their devices. I'm getting to grips with my family's ebooks - previously stuck on our individual readers.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |