Hey guys, i see that Nethserve rhas reached Public Beta, NS8 project | Trello
anyone tested it out. @giacomo how has the prodcution run with the Nethserver in your offices been so far.
I am curious, will the Enteprise Telephony service available with Nethserver be available in NS8 soon, and if Yes, will it support multiple PBX instances on the same server, with some form of routing with same, or even multiple IP address for SIP trunks the related polcies.
In the mornign Ejabberd was in progress, now i see its been completed, cool.
Wait! The beta is still not out, in the board you see all tasks that should be implemented to reach the beta
Of course we are going to announce it when it’s done.
Yes, the PBX will be available on NS8. For the first release probable we are going to support only one PBX per node, but we have plans to add the support of multiple instances on the same node.
It’s going very well, even the migration worked without pain.
For now, we faced a bug only during Nextcloud latest upgrade but we are working on it.
It could be done (I’ve tested it) but it’s hard to maintain in the core since is not officially supported by Mattermost and could break anytime.
Still, if someone want to contribute as a module, I have no problem to help the integration
Maybe we could start with a complete NOOB tutorial for building a NS8 module.
would help grow the commuity.
you could also build is as a community module, just leave it outside of the core functions, for whoever needs to make use of it,
Am also curious, there was talk of creating a module migration tool, that would convert all community modules from NS7 to NS8, is this really feasible to be done, woulc it be done, or all modules have to be re-done one by one from scratch.
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?
