riverui executables does not support sqlite

[michealroberts]

So attempting to run

riverui

with a sqlite backend seems to fail:

time=2025-10-02T15:34:02.183Z level=ERROR msg="Error initializing server" error="error parsing db config: cannot parse `sqlite://./db.sqlite3`: failed to parse as keyword/value (invalid keyword/value)"

Not quite sure what to do here ... ?

[bgentry]

Ah, we only just made riverui capable of supporting different drivers and we haven’t made any changes to executable to support multiple drivers. Could you try making a program that uses the riverui Handler type with your own SQLite driver to see if that works ok?

I’m on the road today and can’t try this out myself right now.

[michealroberts]

@bgentry Hi Blake, awesome. Yeh was wondering if that was working. I’ll have a play around and see what I find.

[michealroberts]

@bgentry Ok loads of issues with the documentation, here:

Adding the DB field here:

raises a unknown field DB in struct literal of type riverui.HandlerOpts error:

At this point, with the issues with the workers actually not running ... I am scratching my head as to what I am doing wrong. I can't follow the documentation because it seems out of date ... 🤔

I would look to go pro but ... the DX so far has been pretty bad tbh.

[michealroberts]

I'm pretty sure I am running on the right versions ...

[bgentry]

There's a bit of refactoring to do to make the executables handle sqlite out of the box. I definitely messed up the doc update when we recently overhauled riverui to be multi-driver—the DB field indeed does not exist anymore. Just pushed a doc fix for that one.

Other than that, the approach outlined for embedding River UI into an existing Go app should be right, and you can look at what riverui's own executables do here for more details: https://github.com/riverqueue/riverui/blob/ba481328d8590088655148c0abbf00a95029532c/internal/riveruicmd/riveruicmd.go

[michealroberts]

Awesome, thanks @bgentry Blake. Appreciate the updated docs, I will give this a try ASAP.