4 ms·
One of the things about nginx is the lack of an organised community - for e.g. there is not even an official repository for nginx (http://marc.info/?l=nginx&m=1
by sandGorgon 18y ago
One of the things about nginx is the lack of an organised community - for e.g. there is not even an official repository for nginx (http://marc.info/?l=nginx&m=122153991029203&w=2 http://marc.info/?l=nginx&m=122153991029203&w=2). there are simply some mirrors of people who maintain a patch-based tree (http://mdounin.ru/hg/nginx-vendor-current http://mdounin.ru/hg/nginx-vendor-current).
There is no bug-tracker (!!), just a wiki page (http://wiki.nginx.org//NginxBugs http://wiki.nginx.org//NginxBugs) and as someone mentioned (http://www.wikivs.com/wiki/Lighttpd_vs_nginx http://www.wikivs.com/wiki/Lighttpd_vs_nginx), very less activity on IRC.
It comes down to the original issue of Linus Torvalds, Ingo Molnar and Con Kolivar: do you have a clear roadmap of where the architecture is going, vs a very cool technology that had a lot of support and was no doubt popular.
I am in no way commenting on the technology behind nginx, but as an architect, making a deployment decision that is going to take hell to change later, I would be very concerned.
- grandalf 18y agoi think much of this is due to the language barrier, and also due to the ease of use (and ease of writing nginx modules)...
- sandGorgon 18y agothe lack of a bug tracker and a SCM should'nt be limited by language barrier.
- TFrancis 18y agoIf your architecture is designed such that changing the web layer is hell, you probably should reconsider the architecture. Your other points stand. The channels of communication around nginx are not as clear and robust as Apache.