Ubooquity uses H2 in embedded in-memory mode.

As far as I know, this mode does not allow multiple connections.

In any case, I think an API would be more adapted to your use case.

This is indeed more a problem of compression level than compression format.

Oh, you mean you want to display several nesting levels on the same screen ? (like in your first screenshot)

If this is the case, Ubooquity is indeed not capable of that.

Ubooquity displays root folders (the one you explicitely share in the admin screen) as text (the black text on grey background, your second screenshot), then all subfolders are displayed using the cover of the first found book/comic in the subfolder (and using the name of the subfolder).

What I meant is that there is no limit on the number of nesting levels you can have in your collection. But you'll have to click 4 times (for instance) to navigate to the 4th level, and have 4 different pages.

Why would you prefer it ?

Same answer: probably not too hard to do, but remind me once I've managed to do the first part of the job. :)

There is no such option, the online ebook reader is indeed made to read epubs that consists mostly in text.

The behaviour you describe (navigating using edges) is the one of the online comics reader (used for cbr/cbz/pdf files).

You can have as many levels of nesting as you want.

Just make sure the grouping option (accessed via the gear at the top left of the page when browsing books or comics) is set to "folders" and not "flat".

Hi Scott,

I'm in the process of merging books and comics in Ubooquity. This has of course a lot of impacts on the database and the way the metadata is stored.

This merge will make it easier to provide full theming (HTML templates in addition to CSS) for Ubooquity.

The interesting point is that, under the hood, the themes will use maps of metadata.

So exposing them through an API should not be too complex.

 BUT I want to finish books/comics merge, theming and read/unread status (and release a version) before anything else.

So an metadata API will not be part of the next version, but feel free to remind me of your idea once the version is released (I might have forgotten it by then), as I find it quite interesting.

Yes, will do.

For my own instance, I allow Ubooquity to use up to 1GB of memory ( -Xmx1024m).

Not because of the size of the database (about 10k books), but because of some big/complex PDF files that required a lot of memory to be rendered.

I'm not sure your database file issue was linked to the mount of allocated memory though...