Add services monitoring section to admin panel. #26
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Oh boy, I spent way too long on this 😕... My initial approach was to create separate components for each service and use mount / unmount events to control service startup and shutdown. This would have the nice effect of easily creating a dependency hierarchy between services, allowing, for example, automatic shutdown of Metabase when PostgreSQL crashes.
I got something mostly working, but it seemed a bit too complicated and kind of weird to allow the presentation layer to control application logic. I also realized that, most likely, we don't need these complex behaviors.
In the end, I opted to simplify things significantly by making main control each service lifetime and having the Services component only reflect the current status of managed services.
This PR includes some temporary code for testing, which I'll remove when merging it with your previous changes.