kui VS electron-vite

Links: - https://github.com/kubernetes-sigs/kind - https://github.com/kubernetes-sigs/kui - https://github.com/k3s-io/k3s - https://docs.gitlab.com/charts/installation/deployment.html - https://github.com/bitnami/charts/tree/main/bitnami/argo-cd - https://github.com/bitnami/charts/tree/main/bitnami/argo-workflows - https://github.com/fluxcd/flux2

GitHub - kubernetes-sigs/kui: A hybrid command-line/UI development experience for cloud-native development

+1 on Lens its definitely a nice way to visualise. I find https://github.com/kubernetes-sigs/kui an nice alternative too, which does a great job of visualisation without obscuring the actual underlying kubectl knowledge you'll probably want to have!

Our mission is to improve the developer experience in the terminal.

We think that layer on new interfaces can help make the commandline even more powerful... as well as making it more accessible. Check out kui[0] to get an idea of what we're imagining.

[0] https://github.com/kubernetes-sigs/kui

currently this is the best k8s tool for me - https://github.com/IBM/kui

Hi all, setting up an Electron-Vite project with Svelte as the framework (https://electron-vite.org/).

I have a electron app using electron-vite (https://electron-vite.org/). My electron app contains my nestjs backend code also. by default electron-vite build contains main,preload and renderer folder, Now I want to integrate my backend here also when I build my electron app. Can anyone help me to achieve this?

electron-vite brings Vite capabilities to Electron app development. It uses Vite at its core to build and serve web applications running in the Electron-embedded Chromium browser (renderer process).

My suggestion is to start with the Electron Vite template, and understand how they set up IPC stuff, and just use that as the template for when you have to move data between the main and renderer processes.

I'm using this one instead of forge: https://evite.netlify.app/

GitHub：https://github.com/alex8088/electron-vite/