TIPS Incredible PBX Code Collaboration

[chris_c_]

Why not make an IncrediblePBX repo under the existing user https://github.com/wardmundy or better, make a new organization called either the same name IncrediblePBX or NerdVittles and put the IncrediblePBX repo under that?

 

[Samot]

3. Incredible PBX 2026 shows node -v 20.20.2 and npm -v 10.8.2 and works. repo listing is also fine. see below...

For Node.js
Running node -v should return a version matching the NodeSource 20.x distribution branch. Depending on how recently your NodeSource repository cache was pulled, the exact output will be: [1]

• v20.20.0 (or higher, e.g., v20.x.x) [1]

For npm
Because NodeSource embeds the official bundled version of npm directly inside the runtime installer, running npm -v will automatically align with Node 20's default package manager: [1, 2, 3]

• 10.x.x (typically 10.8.2 up to 10.9.x depending on the minor Node point release)

Why this is a success
You will know the issue is entirely resolved because npm -v will execute instantly without throwing MODULE_NOT_FOUND errors.

I wasn't talking about the application versions. I was talking about the package versions. I also have 20.20.2 and 10.8.2 Cloud systems come with NodeResource based nodejs already installed. By installing npm after the fact, it overwrites NodeResource's npm and expects to work with Debian package version of nodejs.

root@noreply:/opt/ipbx# dpkg -l | grep nodejs
ii nodejs 20.20.2-1nodesource1 amd64 Node.js event-based server-side javascript engine
root@noreply:/opt/ipbx# dpkg -l | grep npm
rc npm 9.2.0~ds1-3 all package manager for Node.js

NodeJS from NodeResource and npm from Debian conflict.

Unsatisfied dependencies:
nodejs : Conflicts: npm

8. Yes. Originally installed sendmail until it started causing problems. Now we use Postfix so SendMail is removed.

Why even install sendmail to only remove it? Why is sendmail enabled and started but postfix isn't? Sendmail is only getting removed because of Debian 13....it's happenstance not intentional.

15. harmless

It is not. There's an actual thread in this forum about it causing problems and the fact conflicting PHP processors were causing race conditions. In that thread you declared php-fpm is the solo PHP processor. So no, it's not harmless and can cause issues like when trying to use Certman to generate self signed certs.

16. we handle faxing a different way now (as you know) so this is harmless

You literally updated the installer script with this not two weeks ago when you "brought back faxing" so how is it not part of how you currently do faxing...the "different way" you use now.

 

[Samot]

Why not make an IncrediblePBX repo under the existing user https://github.com/wardmundy or better, make a new organization called either the same name IncrediblePBX or NerdVittles and put the IncrediblePBX repo under that?

The reasons were given. Repo = bad.

 

[kenn10]

Does fax,2 line look like it's correct?

As I posted above, it is correct in the IncrdiblePBX-2026 install script. I could care less about 2027 or 2025 and it is a waste of time to be combing through them at this point.

 

[wardmundy]

I wasn't talking about the application versions. I was talking about the package versions. I also have 20.20.2 and 10.8.2 Cloud systems come with NodeResource based nodejs already installed. By installing npm after the fact, it overwrites NodeResource's npm and expects to work with Debian package version of nodejs.

NodeJS from NodeResource and npm from Debian conflict.


Why even install sendmail to only remove it? Why is sendmail enabled and started but postfix isn't? Sendmail is only getting removed because of Debian 13....it's happenstance not intentional.

It is not. There's an actual thread in this forum about it causing problems and the fact conflicting PHP processors were causing race conditions. In that thread you declared php-fpm is the solo PHP processor. So no, it's not harmless and can cause issues like when trying to use Certman to generate self signed certs.

You literally updated the installer script with this not two weeks ago when you "brought back faxing" so how is it not part of how you currently do faxing...the "different way" you use now.

3. We are using applications and will clean up packages as time permits. As I said, for those using Incredible PBX 2026 as delivered, this package conflict is harmless.

8. SendMail is a relic of history that has not yet been removed. The error is harmless. We don't activate Postfix until after the administrator runs enable-gmail-smarthost-with-postfix because downstream mail servers aren't supported by most ISPs.

15. Only one version of PHP is currently installed on Incredible PBX 2026 servers: dpkg -l | grep php

16. Faxing isn't a high priority for most folks. As soon as there was an actual request for faxing with Incredible PBX 2026, we addressed it in less than a day. Sorry for the delay.

 

[wardmundy]

The reasons were given. Repo = bad.

No. A repo isn't bad. It's A LOT of work for somebody at our end. I'd rather exchange sweet nothings with you here on the forum rather than wade through your code on a proprietary repo.

 

[wardmundy]

For the slow learners, let me repeat the offer: Everyone is more than welcome to start things off by telling us what's not currently working.

Finding broken components that no longer matter or are no longer used and code cleanup that doesn't affect actual operation are NOT high priority items on our end given the limited resources of the development team.

The other option is you can stick with Sangoma with NO Debian 13 support meaning NO Asterisk 22 support with FreePBX and NO Asterisk 23 support with FreePBX except with LTS-only Debian 12. It's a free country. Happy Fourth!

 

[Samot]

Finding broken components that no longer matter or are no longer used is NOT a high priority given the limited resources of the development team.

It's OK, I've done that already. Spent the last 4 or so weeks doing it. I haven't just been working on the installer I've been working on management items as well. There's some serious work that's been done and it wasn't my intention to dump and run with it. My intention is to help the project and fill in gaps that are needed....for example I already maintain repos so it's not "extra work" for me...