GitHub user Ma77Ball edited a discussion: Proposal: a desktop app to set up, 
run, and monitor Texera

Running Texera today means installing Docker, running the right 
`bin/single-node` compose 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-node` 
deployment: it runs `docker compose up` / `down`, reads health from `ps`, 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.

<img width="1144" height="954" alt="desktop-home" 
src="https://github.com/user-attachments/assets/71f1075f-981a-4348-934d-528fcc3d3a6c";
 />

## 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.

<img width="1144" height="954" alt="desktop-explore" 
src="https://github.com/user-attachments/assets/91bd870d-47eb-4243-bf66-3834417b181d";
 />

## 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`).

<img width="1144" height="954" alt="desktop-developer" 
src="https://github.com/user-attachments/assets/fbdf8b6f-d299-4d77-9c91-e6079940ae53";
 />

It only ever shells out to the same compose files:

```mermaid
flowchart LR
  App[Desktop app] -->|compose up/down/ps, exec, logs| Docker[Docker]
  Docker --> Stack[single-node stack + optional observability]
  App -.embeds.-> Dash[Grafana, Jaeger, Parca, VictoriaMetrics]
```

## Open questions

1. Worth a second toolchain and a three-OS installer matrix, or keep end-user 
setup a documented script in the spirit of `bin/local-dev`?
2. Is a full in-app terminal (it pulls in the node-pty native module) wanted, 
or should the developer tools stay read-only?
3. Single-node local only, or should it also connect to a remote deployment?
4. Who owns signing and notarization, and where do the binaries live (GitHub 
Releases, the Apache incubating dist area per version)?

If there is interest I will open a tracking issue and a draft PR.

GitHub link: https://github.com/apache/texera/discussions/9567

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to