Persisting Application State?

[pietz]

I like the idea of Marvin Applications and I want to explore it a bit further. What's the recommended way to persist the state of an application say in a SQLite database? Can somebody provide me with a snippet?

This might be something worse adding to the docs as well.

[zzstoatzz]

hi @pietz - I think the best way to think of Application state is as a BaseModel subclass.

so I'd simplify the question

What's the recommended way to persist a BaseModel instance in say in a SQLite database?

and there's a couple ways you could answer that, but generally I'd say its SQLModel or SQLAlchemy that already plays pretty nice with these things. So maybe a client side schema you pass as state for your Application and a SQLModel / ORM copy for your server

[pietz]

@zzstoatzz I think my problem comes from a different perspective. When I run the application on my computer and interact with it through the terminal, the entire event loop happens in the chat() function. I guess I'm still a bit puzzled on how I can build features around that like persisting the state after each call in a DB of my choice or even integrating an application/assistant in a web server application.

If you have any resources for this, I'd appreciate it. All examples are basically toy examples for the command line. How would I integrate assistants into actual applications?