sqlitefs VS libsqlfs

> but also presents as a true filesystem.

As does:

https://github.com/guardianproject/libsqlfs

https://github.com/narumatt/sqlitefs

(I know nothing about these, just got them from a quick search)

- Use clone file to duplicate the cached data directory to give to individual tests.

One thing I'd like to pursue is to store the Postgres data dir in SQLite [1]. Then, I can reset the "file system" using SQL after each test instead of copying the entire datadir.

[1]: https://github.com/guardianproject/libsqlfs

Not sure about compression but somebody could probably hack it in an afternoon using this:

https://github.com/guardianproject/libsqlfs

or something similar to check the potential for speed up.

Maybe there isn't a database engine that explicitly supports file system daya structures, but you could implement a filesystem in the application layer using SQLite as a storage mechanism.

Here's an example of someone doing that very thing.

https://github.com/guardianproject/libsqlfs

now let's see what it takes to make absurd-fs, where we use https://github.com/guardianproject/libsqlfs to make a filesystem on top of sqlite on top of the File System Access API.

gotta keep ourselves fully looped. ⥀