I just wrote a page describing the directory structure of Ubooquity so that you can know what contains what:

https://vaemendis.github.io/ubooquity-doc/pages/dir-structure.html

Basically, if you want to backup your installation and restore it without having to rescan your files, you'll need:

• preferences.json (your settings)
• ubooquity-5.mv.db (the database)
• webadmin.cred (contains your admin password)
• the cache folder (the covers of your books)
• the themes folder (if you added additional themes inside)

So if you don't care about wasting a few megs, you might as well just backup and restore your whole Ubooquity directory without the "jar" file (or with, if you want to keep the same version ).

Good then !

I must admit I have sometimes a hard time remembering all I post here. :)

I don't remember it, but I guess I said no at the time ? :)

Empty folders are completely ignored starting with version 2.0.0.

The trick is that they are removed at the end of the scanning process. So, new empty directories will be shown until the scan is finished.
If you still see them afterwards, let me know and I'll investigate.

In the next vedrsion (2.0.3), you'll be able to click on the Ubooquity logo on the admin page to go to your library.

Thanks ! :)

So, this one was tricky.

Turns out Safari doesn't like images with a application/pdf MIME type.

That's understandable.

Fixed, will be part of next release (2.0.3).

Thanks for the investigation !

I'll take a look asap (got a baby last week, so I don't have much time for anything else these days :) ).

I still can't reproduce the problem on Windows (working with Ubooquity 2.0.2), so I tried on my Raspbery Pi (on Raspbian).

I followed your protocol, and the number of opened file descriptor stays quite stable, around 70, even when browsing a lot of pages with hundreds of covers.

So I don't understand why you still have the problem unfortunately.

Unfortunately I still have no idea of what could cause this.

I'm not the one who wrote the Synology instruction (I don't own a NAS), so you'll have to wait for a Synology user to update them.

I recently transfered the documentation to Github to give people an easier way to contribute.