@chpietsch @liaizon @dev oh no, I'm sorry it was a frustrating experience but I can totally understand. It could have been different problems depending on when you tried it.
The most likely problem is that we (as in multiple people in the development chat, this was a large decision and it was best to consult multiple people before going through with this) decided to forego SQLite Support in the newest release.
The reasons were the growing complexity of keeping it in the codebase. When we introduced better full text search, we basically had to split the migrations into two with different constraints, different table layouts, etc.
Basically a lot of maintenance work.

Around that time we were also looking into different ORMs around that time since the old one was on one hand quite dynamic, but on the other hand didn't really aid us via compile-time checks.
The new one we settled on didn't have support for SQLite though.

So those two reasons combined meant that we did forego the support for it.

A classic failure to update documentation by me, my mistake and I apologise for that. I will update them ASAP.
If you wanna give it a try with a PostgreSQL database though but it still has issues, feel free to either ask Mr here or over in one of the chat rooms (linked in the project README)