-
Notifications
You must be signed in to change notification settings - Fork 521
add daemon or watch mode equivalent of tye run
#13
Comments
Just a thought, but could the dashboard be in a container that is automatically added to a tye.yaml? It'd be useful to have a preexisting and non-trivial working component in a new tye project by default. Especially one that uses some of the newer goodies like Blazor, and potentially uses the very features that tye offers for microservices... |
What does the dashboard being in a container gain you? |
No must-haves, but aside from the built-in sample I mentioned above, I think it'd also be useful to a user of tye for a few other reasons:
Cool thing is tye already knows how to create containers and helm charts, could be like an embedded resource thing that turns into a container...but, just thinking out loud on that 🤔. |
Yes I think that's one of the reasons for making that kind of experience in the first place. We'll have to do something like this anyways to make it run in the cluster. I'm hesitant to rely on docker for core functionality but it might be fine as a mode. |
Presume this would watch |
Yes, we super want this 👍 The work that I did this milestone with diagnostics integration makes it even more important because those things are slow to start. |
The idea is that we can leave the host and dashboard running, and services can drop in and out.
The text was updated successfully, but these errors were encountered: