Yes. I have only done small tests with it prior to the official release, but it feels solid just like SQLite itself.
This tool didn’t exist when LiteStream and LiteFS were created (I hugely admire Ben Johnson for those projects and more). And it drove changes to SQLite itself, like being able to query and modify DB page information using SQL: The SQLITE_DBPAGE Virtual Table
If those features existed earlier, they would have certainly influenced the designs and implementations of LiteStream, LiteFS and other tools in this space.
In summary, you duplicate config and your App.Repo module, and update application.ex to start both repositories on startup.
I recall some threads here in the forum about e.g. using a database per tenant on SQLite.
The introductory guides probably cover what needs to be done - the difference is you end up with 2 (or more) repositories in your app, and parts of your app explicitly reference one or the other.
Both are possible. I have practical experience with one Repo per DB. Have seen put_dynamic_repo/1 discussed here in the forum for some setups.
I particularly like having separate repositories, as code is explicit and straightforward.
