-
Notifications
You must be signed in to change notification settings - Fork 467
tutor status support from MFEs #1204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I think if I understand your problem correctly, you need some of way knowing the status of your MFE mounted containers that are not running. Right? You can run |
Making the behavior that I desire optional makes sense. Could you include a sample of the output you expect to produce? I find the output on first start after running
You can clearly see the running MFEs. |
The output you get by using the
Or if it is stopped:
This is for mounted MFEs, there would be no difference for the ones that are part of the Regarding the output you shared for |
@mlabeeb03 this is not the output that I'm seeing. Here's what I have, on a stopped platform:
But @e0d, it seems you instead be satisfied if you had instead a separate command that would print the list of available hosts, right? Something like:
Note that this list does include hosts from stopped containers. |
The list of hosts with their current status, think |
Is your feature request related to a problem? Please describe.
A useful approach for MFE development with Tutor is to
tutor dev stop learner-dashboard
npm run dev
It would be useful for tutor status to provide some better visibility here.
Currently if you run
tutor dev status
you get output like the followingWhile you can determine from that with inside knowledge that port 1996 isn't being proxied and thus the learner-dashboard isn't running, it would be nicer to get a status for MFEs that is similar to what you get for backend services.
The text was updated successfully, but these errors were encountered: