Question about some of the stuff you're
# generalc
creamy-ghost-62907
06/03/2025, 4:38 PMQuestion about some of the stuff you're exploring for Avo 4:
1. Is the DB-backed config stuff going to be optional?
2. What does the workflow look like for taking DB-backed configuration and move it between environments / reconcile differences?
3. For all the in-UI development features, are those built on the DB-backed config, or is it creating/modifying Ruby code?
l
lemon-wall-20836
06/03/2025, 6:53 PMGreat questions!
1. yes. completely optional. the code that back them up and migrations are opt-in
2. we asked ourselves that too. There are a few things we can do. One is to offer a system (through avohq.io or not) where you register your production and development (and other) evnironments and you can import/export them from one place to another
3. it depends which ones. if you're talking about the index view editing, those could be applied to any type of resource (db or file backed)
c
creamy-ghost-62907
06/03/2025, 7:09 PMTY!
l
lemon-wall-20836
06/03/2025, 7:09 PMwhat were your first thoughts when you watched the video?
c
creamy-ghost-62907
06/03/2025, 9:11 PMHaven't had a chance to watch it just yet. Been hip-deep in a project that boils down to "incrementally migrate a full-page-app from AngularJS 1.6 to React 18 while adding new functionality as we go", and so today has been... involved.
creamy-ghost-62907
06/04/2025, 12:51 AMChapter stops on release videos would be helpful...
creamy-ghost-62907
06/04/2025, 1:11 AMInline action definitions look very handy and ergonomic.
The let-power-users-do-light-dev-things is not a capability I'll be making use of (should I wind up in a position to use Avo again), though. Maybe saving particular filter configurations as a scope, but beyond that... not so much. Too much opportunity for an ill-performing query to hork system equilibrium.
I worry that you're headed down the path of recreating a crude MS Access-esque system. A product like that might be a perfectly reasonable thing to build, but it seems to me to be a different product than what Avo has been attempting to be thus far.
You might consider making it a separate product and just sharing code between the projects to get leverage... I'd imagine that orgs that want that functionality might be willing to pay more for it -- and that could help ensure you have the resources necessary to keep it from becoming a drag on development of the core system.
l
lemon-wall-20836
06/04/2025, 3:58 PM> but it seems to me to be a different product than what Avo has been attempting to be thus far
I get that, but we did get some requests for those capabilities
lemon-wall-20836
06/04/2025, 3:58 PMand that's also being created for some specific use-cases. I don't expect everyone to build Avo apps like that from now on