Repository navigation
Replies: 2 comments 3 replies
|
I had the local-dev CLI I think it is for similar idea. a few benefit of cli is
Of course those are the assessment months ago. Now you could argue that agent compute use is more mature but still cli would be its most efficient way to interact with, and UI/desktop app is for human users. I like the idea of evolving it to a desktop app! I just wonder if it can reuse or extend the local-dev so we don't keep two copies of the code? to me the desktop app can underneath calling cli, right? |
2 replies
|
On a side note, I would like to encourage more desktop app solutions. Now react + Electron can easily reuse the same code we have in browser and local desktop app. It will be great if we can even have a Texera desktop app. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Running Texera today means installing Docker, running the right
bin/single-nodecompose commands, and then remembering which port each service and dashboard lives on. The closest tool we have,bin/local-dev, is a terminal dashboard for contributors (macOS and Linux). There is no packaged app for an end user who just wants to click "start".I am prototyping a small cross-platform desktop app (Windows, macOS, Linux from one Electron codebase) that is a thin layer over the existing
bin/single-nodedeployment: it runsdocker compose up/down, reads health fromps, and opens the dashboards. It does not replace the engine or own any config. A Linux build runs today.Simple by default
The home screen is the logo and one status light that is the on/off switch: click it to start or stop the stack (red stopped, green running). When it is green, Open Texera and Explore Monitoring appear.
Monitoring, embedded
Explore Monitoring is a tabbed web view of Grafana, Jaeger, Parca, and VictoriaMetrics, inside the app, so a user sees charts instead of hunting for ports.
Developer view when you want it
One click away: Texera's own services, grouped, with ports and Shell / Logs / Restart, plus a real interactive terminal (shell into a container, follow logs, live
docker stats).It only ever shells out to the same compose files:
Open questions
bin/local-dev?If there is interest I will open a tracking issue and a draft PR.
All reactions