Just a thought here. Would it be fair to say that Nethserver is a name that no longer covers the load? No longer do we have we have a ‘old school’ server, but actually a SaaS platform providing all kinds of services and being extendible, distributed and HA?
So my thought is if we should we reach back to old school descriptions for a ‘stand alone’ server which was perfectly valid a while ago, but today maybe the naming convention and positioning should be reconsidered?
2 cents…
Impressive.
From the docs:
Is there a preference among these? Or is any of them as good as the others?
And is it, or will it be, possible to migrate from OpenLDAP to AD as an accounts provider?
Let’s call it NethService 
I personally prefer CentOS stream for development and Rocky Linux for production
No, I think it’s not possible due to different and incompatible password encryption schemes. But I might be wrong…
Any roadmap available?
Any matrix of NS7 service vs NS8 service and status of implementation?
The roadmap link is still Trello
It is frequently updated
I don’t know of such comparative document now but for the first stable release I expect the admin manual contains it.
don’t like centos stream but I could be wrong
alma linux should be fine
must admit I do not use often debian
@giacomo could you share, when easible your notes on implementing and running this particular module into NS8 and having it work with matermost. would provide a good starting point.
thanx.
oh what a wonderful thing.
its interesting that you can update individual componets on the nethserver dashboard, i hope that feature carries forward to ns8 as well.
Thank @giacomo for the NsC 27 Update.
