You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The kubetail-ui project has a nice docker-compose based dev environment that makes it easy to handle dev dependencies (https://github.com/kubetail-org/kubetail-ui) and it would be nice to have something similar for the main kubetail repo.
From a user perspective, running docker compose up should run these commands inside a docker container:
# run the Dashboard servercd modules/dashboardgo run cmd/main.go -c hack/config.yaml
# run the Dashboard UIcd dashboard-uipnpm installpnpm dev
The tricky thing in this setup is that the docker dashboard needs access to the host's kube config file and must also be able to make network calls to the kubernetes dev cluster running on the host. In addition, for a nice developer experience the backend/frontend should also restart in response to code changes. The frontend does this automatically for source code changes but doesn't handle new dependencies. The backend doesn't have support for automatic restarts at all.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
The
kubetail-uiproject has a nice docker-compose based dev environment that makes it easy to handle dev dependencies (https://github.com/kubetail-org/kubetail-ui) and it would be nice to have something similar for the main kubetail repo.From a user perspective, running
docker compose upshould run these commands inside a docker container:The tricky thing in this setup is that the docker dashboard needs access to the host's kube config file and must also be able to make network calls to the kubernetes dev cluster running on the host. In addition, for a nice developer experience the backend/frontend should also restart in response to code changes. The frontend does this automatically for source code changes but doesn't handle new dependencies. The backend doesn't have support for automatic restarts at all.
Beta Was this translation helpful? Give feedback.
All reactions