On Tue, Dec 26, 2017 at 08:38:34AM +0100, Landry Breuil 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 ?
Would like feedback on the latter, ie is it fine as is with
daemon_flags="-homepath ${TRUEPREFIX}/share/grafana -config
${SYSCONFDIR}/grafana/config.ini"
in the rc script or should i patch the code so that it defaults to those
'hardcoded' values ?
> 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.
Actually works fine on -current and on my 6.2 gateway at home, been able
to work it with influxdb and collectd without a single issues; and then
building dashboards.
Besides whitespaces i don't see much to change in the port itself so..
oks & testing welcome.
Landry
