No offense taken, I was simply showing what I was seeing when checking a default install which was an rpm install not a true build from scratch. I’ll have to do a kickstart install on an Ipfire vm to see what perms it lays out on there also before changing the install script.
1 Like
I can have a look at that. However remember that just building the addon package as per the wiki info will not get it into pakfire.
To get an addon package into pakfire you have to submit a patch via email to the IPFire dev mailing list. There it will be reviewed and if accepted as is or after modifications, then it will bec\ome available in pakfire.
You can’t install a package directly into pakfire yourself without changing the code. Pakfire expects all addons to be available from the mirrors list that it gets from the IPFire Server. All packages are stored on the mirrors in encrypted form and pakfire checks that the encryption signature is correct and only then will it decrypt the packages and install them.
@siosios has already done the addon build work, except that the build is installed in /opt/ which would have to be changed for submitting to IPFire as it expects things to be installed in /usr as a prefix.
These are the wiki sections related to patch format and email submission.
https://wiki.ipfire.org/devel/submit-patches
https://wiki.ipfire.org/devel/send-tb-patches
https://wiki.ipfire.org/devel/git/commit-messages
EDIT:
One thing I have noticed is that the lfs file is running netdata-installer.sh from the source tarball rather than the expected autotools commands of ./configure, make, make install
Looking through the netdata-installer.sh script it is basically doing the autotools commands but with a huge amount of additional sections that make it very difficult to figure out what is being installed. It is also following its own installation approach for the startup sym links rather than using the IPFire symlink approach. There is also no IPFire backup definition defined as it doesn’t know anything about it.
I suspect that the use of the netdata-installer.sh script will need to be changed to the standard autotools commands to be acceptable as a patch submission and with the addition of the IPFire startup symlink and backup file installation approaches. These can be found from looking through some other example addon lfs files.
4 Likes
I have made a link to the Building Addon section at the end of the pakfire page.
5 Likes
i can change it back to the original install locations fairly easily. i have more work to do on it to make it a solid package for it to be considered to be put on pakfire as a approved package.
3 Likes
updated to 1.39.0 to github
4 Likes
Here is a default (not /opt) netdata 1.39.0 install package built on 174 that needs tested by more than just me. this one is just netdata with no frills.
2 Likes
Updated the NetData packages to 1.4.0, I have also changed up the structure of the repository somewhat.
you now have the below to choose from:
netdata-1.40.0-1.proxy.menu.ipfire ← package is installed in /opt, has proxy using nginx
netdata-1.40.0-1.ipfire <–plain jane /opt netdata install
netdata-1.40.0-1.normal.ipfire ← regular netdata install
the two opt packages use part of @jiab77 's perms propasition (if there are problems let me know please).
3 Likes
That’s awesome! Perfect time for updating and testing the new version 
PS: Nice work on the menu! I was going on the wrong direction then looked back at your work and seen my error. Btw, I think I can implement what you did along the install script so I’ll remove what I wrote on that, add the right logic and push a test version soon.
Updated the NetData packages to 1.4.2 on core 178
you now have the below to choose from:
netdata-1.42.0-1.proxy.menu.ipfire ← package is installed in /opt, has proxy using nginx
netdata-1.42.0-1.ipfire <–plain jane /opt netdata install
netdata-1.42.0-1.normal.ipfire ← regular netdata install
the two opt packages use part of @jiab77 's perms propasition (if there are problems let me know please).
2 Likes
Updated the NetData packages to 1.4.2.4 on core 180
you now have the below to choose from:
netdata-1.42.4-1.proxy.menu.ipfire ← package is installed in /opt, has proxy using nginx
netdata-1.42.4-1.ipfire <–plain jane /opt netdata install
netdata-1.42.4-1.normal.ipfire ← regular netdata install
the two opt packages use part of @jiab77 's perms propasition (if there are problems let me know please).
3 Likes
Updated the NetData packages to 1.44.1 on core 182
you now have the below to choose from:
netdata-1.44.1-1.proxy.menu.ipfire ← package is installed in /opt, has proxy using nginx
netdata-1.44.1-1.ipfire <–plain jane /opt netdata install
netdata-1.44.1-1.normal.ipfire ← regular netdata install
2 Likes
Updated the NetData packages to 1.47.0 on core 189
you now have the below to choose from:
netdata-1.47.0-1.proxy.menu.ipfire ← package is installed in /opt, has proxy using nginx
netdata-1.47.0-1.ipfire <–plain jane /opt netdata install
netdata-1.47.0-1.normal.ipfire ← regular netdata install
2 Likes
Hello, I’d like to help test this out - can you elaborate on the version using nginx? I already use nginx, installed via Pakfire, as a reverse proxy for my services in my network; will this conflict with that?
It will conflict with your current setup, i recommend using one of the other packages and manually setting up the proxy for it.
to setup the menu would also be manual which you can get the menu files from the proxy package and upload them ← check the install.sh file for locations
netdata-2.1.1-1.proxy.menu.ipfire ← package is installed in /opt, has proxy using nginx
netdata-2.1.1-1.ipfire <–plain jane /opt netdata install
netdata-2.1.1-1.normal.ipfire ← regular netdata install