i got grafana running on openbsd before, and took the same approach to getting the web assets. getting the node dependencies into ports seemed like a rabbit hole i'd never climb out of.
i will likely be using this port in the future if it is comitted - thank you for your work. On Mon, Dec 25, 2017 at 11:38 PM, Landry Breuil <[email protected]> wrote: > Hi, > > turns out it wasnt so hard to port, given that the grafana folks vendor > their go dependencies in the source tarball, it wasnt the same mess as > influxdb. I took inspiration from the FreeBSD port where they fetch the > linux binary tarball to extract the web assets instead of going through > the whole nodejs/yarn hell to build them again. Life is too short for > this. > > One thing i dont really like so far, the defaults for homepath/config > arent set anywhere in the code itself, so i have to set them via > daemon_flags in the rc script, but without -homepath grafana-server will > loudly complain at startup (and wont find web assets), so im pondering > if it should be patched in the code itself. Thoughts ? > > Been able to add my influxdb datasource, and create a network bandwidth > graph using derivative() function (booo @facette which doesnt allow this > :) > > Feedback & testing welcome. Remember, this is a quick hackish wip. > > Landry
