> nfsen is *very* old code, and actually I wanted to rewrite a new version,
> which got delayed and finally aborted for a number of reasons.
> I could consider to give it a go again, but I am still uncertain if it would
> still be used these days. Feedback would be appreciated.
I use nfsen, and install it on new deployments. I even have a simple
Ansible cookbook to automate installations.
I think it does what it does pretty well and is very light. Of course
heavier solutions based on Elasticsearch are very powerful and extensible. But
for small ASen with not a lot of technical people, it is still the best fit.
> If there would be a new NfSen incarnation, I would write it in Golang as it
> provides far more flexibility and speed. I am not a exceptionally gifted
> GUI/Web developer - maybe someone would be willing to support. However, also
> for a new NfSen, I could prefer KISS
Perhaps this chap has a fair idea of what the GUI could look like,
although the backend (at least the last time I checked it out) is hacky:
https://github.com/mbolli/nfsen-ng
I would certainly be very happy to see nfsen rewritten and packaged. I
would be willing to test and maybe help with Debian packaging (my experience
with the latter is limited, but am willing to give it a go).
—
Alfredo Sola
_______________________________________________
Nfsen-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
