Project dying?

[jimmyd-be]

This is a great project and I'm using it already for a long time on my home server.
But it looks like just one person (jc21) is fully responsible for maintaining and releasing. This is not a healthy situation for this great project.
If jc21 stops because of a reason we need to fork it and this project will be dead (multiple forks will be made and not one fork).
The speed of development/release is also dependent on jc21 free time.

Is it not better to find a couple core maintainers that can help jc21 with his great work on this project. PRs should be checked and merged quicker and the project can go forward even if one of the maintainers are on holliday.

[3rdStng]

My concerns exactly. There have been a couple of known exploits in nginx recently and those fixes have not made their way into this project yet.

[jimmyd-be]

I just moved over to Traefik because of this. Now my config is living inside git.

I loved using proxy manager for his simplicity.

[MikaelKW]

I migrated to NPMplus (fork of Nginx Proxy Manager) some time ago mainly because i see loads of vulnerabilities not being handled or at least it takes way too long. NPMplus has a very active maintainer and has some nice additional features that are not present in NPM. Highly recommend!
https://github.com/ZoeyVid/NPMPlus

[3rdStng]

Thank you! This is the replacement I have settled on. Just need time for the maintenance

[unsortedcode]

Ah, well, now I see this. I just went through a bunch of work forking and adding full support for compose stacks and cloudflare DNS. NPMPlus looks promising. I might pull some of the security fixes and patches into CompHost.