Cache/Index retention

[Darkassassin07]

I have noticed that when my filebrowser container is restarted, after updates or after manually stopping and starting, the entire index has to be rebuilt from scratch. (all the folders contain '0 bytes' until they're re-scanned)

Is the index stored within the container, in a location I can map to the host and retain? Or is it only stored in memory?

[Kurami32]

What I know is that the index is currently memory-based.

In the future, there will be a SQLite database, so I guess that's where it'll be stored on disk.

[gtsteffaniak]

I have created a release that utilizes sqlite to improve memory performance, would love to get feedback

https://github.com/gtsteffaniak/filebrowser/releases/tag/v1.1.2-experimental-sqlite

[Darkassassin07]

I'm not seeing it on docker; am I just too early?

/edit, I was too early. Tag: '1.1.2-experimental-sqlite'

Gonna let it run for a day or so, and I'll be back.