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 Triton Grafana service uses Joyent's fork of Grafana. The sole difference between the fork and the upstream repo is that the fork removes phantomjs from the build, since phantomjs won't build on illumos.
With the release of Grafana 7.0, phantomjs has been removed from the upstream Grafana repo entirely and replaced with a new image rendering plugin using headless chromium.
Thus, if this repo is upgraded to use a version of Grafana >= 7.0, we will probably have to update the content and build process of the Grafana fork. It would be nice if we no longer need a fork at all, but I have a hunch that chromium on illumos will prove problematic as well.
The text was updated successfully, but these errors were encountered:
The Triton Grafana service uses Joyent's fork of Grafana. The sole difference between the fork and the upstream repo is that the fork removes phantomjs from the build, since phantomjs won't build on illumos.
With the release of Grafana 7.0, phantomjs has been removed from the upstream Grafana repo entirely and replaced with a new image rendering plugin using headless chromium.
Thus, if this repo is upgraded to use a version of Grafana >= 7.0, we will probably have to update the content and build process of the Grafana fork. It would be nice if we no longer need a fork at all, but I have a hunch that chromium on illumos will prove problematic as well.
The text was updated successfully, but these errors were encountered: