We could leverage the interface code to also build a standalone executable.
We would have to distinguish how the binaries are executed (docker and gefyra-json).
Furthermore we'd have to replace the calls through the docker client with some own.
A custom theme would be also pretty nice - this should be achievable through ThemeProvider from MUI framework.
Also - we link back to the docker native container views when a container is run. We also need to distinguish here.
To wrap the code into a standalone executable we already played around with Tauri - it seems like a neat solution to tackle this.
Would probably make sense to rename this repo to gefyra-desktop then.
We could leverage the interface code to also build a standalone executable. We would have to distinguish how the binaries are executed (docker and gefyra-json). Furthermore we'd have to replace the calls through the docker client with some own. A custom theme would be also pretty nice - this should be achievable through ThemeProvider from MUI framework.
Also - we link back to the docker native container views when a container is run. We also need to distinguish here.
To wrap the code into a standalone executable we already played around with Tauri - it seems like a neat solution to tackle this.
Would probably make sense to rename this repo to gefyra-desktop then.