From nobody Sat Jun 12 00:56:08 2021 X-Original-To: ports-bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 40A6E7CF959 for ; Sat, 12 Jun 2021 00:56:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4G1zmS1H4Fz3Fl8 for ; Sat, 12 Jun 2021 00:56:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 114C52CBDF for ; Sat, 12 Jun 2021 00:56:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 15C0u8WP071730 for ; Sat, 12 Jun 2021 00:56:08 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 15C0u8oF071729 for ports-bugs@FreeBSD.org; Sat, 12 Jun 2021 00:56:08 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 255980] net-mgmt/netdata: Update to 1.31.0 Date: Sat, 12 Jun 2021 00:56:08 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: namkhai.n3@protonmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Ports bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-ports-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports-bugs@freebsd.org X-BeenThere: freebsd-ports-bugs@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255980 --- Comment #17 from Namkhai B. --- So, here's the process I followed to build the custom dashboard: 1. I have a fork at https://github.com/forkbomb9/dashboard, in which the br= anch `freebsd` removes the social media components. 2. I then build the dashboard (using Node LTS), and pack `build/` in `dashboard.tar.gz`. This file can be found here: https://github.com/forkbomb9/dashboard/releases/tag/v2.17.1-bsd0. I then use that as a basis to update the dashboard in netdata: 1. go to web/gui, and in bundle_dashboard.py, change URLTEMPLATE to point t= o my fork, e.g. instead of github.com/netdata/dashboard use github.com/forkbomb9/dashboard. 2. call bundle_dashboard.py with my custom release tag :./bundle_dashboard.= py v2.17.1-bsd0. This is now the customized dashboard. This procedure is only to generate the patch, it has to be done on every dashboard update (it's not that hard). Then, to generate the actual patch, I commit the changes to my `netdata` fo= rk in the `freebsd` branch. And then I use that commit as a patch in the Makef= ile (https://github.com/forkbomb9/netdata/commit/69bb76a794d8ae7fde1d9a1a8202fe= f3ec04726a) This is the most efficient way I found to update the dashboard, while follo= wing the build procedure. The only thing that I have to do is update my `netdata` branch every time there's a package update, and it isn't very hard to do. Another option would be to run bundle_dashboard.py on the build process, th= us skipping the patch download. But that would pull Python as a build dependency... I could also try to rewrite it in Lua, but that feels much hackier than the procedure I described above. And I don't have the skills in Bash/Sh to do i= t... --=20 You are receiving this mail because: You are the assignee for the bug.=