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
Create an application that runs the MATS "home" app. (E.g. - https://esrl.noaa.gov/gsd/mats/). This is currently a couple of static HTML files for MATS & METexpress. At the moment they're served up with a Go file server. (https://github.com/halverneus/static-file-server) It'd be nice to template the HTML so it's easier to maintain.
The home app currently pulls in some JSON config information about which apps to show and where they're deployed.
Ideally, this would be containerized and deployed to the Kubernetes cluster.
The text was updated successfully, but these errors were encountered:
I currently have the app up and running at https://apps-dev2.gsd.esrl.noaa.gov/mats-dev/ (the MET-* and ensemble links are known to not be working as the apps don't exist in the cluster) and have been working through some small bugs with Molly.
The last nit is that it would be nice to also collapse the group names if they don't have any related apps under them when switching between the various "Verification Methodology" sources.
Randy also noted that it would be nice to add additional functionality to the app to detect when downstream apps aren't online as well as to monitor the downstream app versions and reveal those through a tooltip. However, I'll create new issues for those since that will be adding new functionality and I wonder if there may be some other ways to achieve the same goals.
Create an application that runs the MATS "home" app. (E.g. - https://esrl.noaa.gov/gsd/mats/). This is currently a couple of static HTML files for MATS & METexpress. At the moment they're served up with a Go file server. (https://github.com/halverneus/static-file-server) It'd be nice to template the HTML so it's easier to maintain.
The home app currently pulls in some JSON config information about which apps to show and where they're deployed.
Ideally, this would be containerized and deployed to the Kubernetes cluster.
The text was updated successfully, but these errors were encountered: