Actually if AMPPS was just a WAMP/MAMP Stack it would be easy for us. But here we have Softaculous auto installer too which provides many scripts. So to keep them all compatible with the stack (with different php versions) is little tedious. We are still trying. We don't have any ETA as of now.

If AMPPS could provide a Apache/NGINX selector for the http server, that would be very nice. Think "NAMPPS".

To the extent that Softaculous scripts are more particular about the PHP & database configuration(s) and less sensitive the http server, one would hope that a Apache/NGINX selector might be feasible.

If a "NGINX+MPPS" stack were to appear separate from AMPPS, this might also be OK. However, one would need compare & choose between the both stacks as a whole (instead of just choosing between which http server).

So, any "NMPPS" would need to be on par with "AMPPS".

Either an inclusive "NAMPPS" or fully capable "NMPPS" could work for me. I'm ready to switch from Apache httpd to NGINX.

I fully understand the need for integration with the Scripts, but I don't use any of them. Neither does anybody else on my team. We use AMPPS for Development, but we recently switched our production servers to Nginx. So we need to do a lot of conversion when going to Production (ie Redirects, Caching)

It would be nice if there was an option now, but it stated that it may not work with all the scripts and should be used only for testing/development, etc.
Maybe even a checkbox so the user has to acknowledges the issue.

This would be great if it was an option when creating the site so each site could be set to either Nginx or Apache, but I understand there would be issues with ports. I would be fine with only having one server running at a time.

It has been a while now since the first request was made to include NGINX in this stack.

Has anything happened?

I find out that more and more companies are now requesting fast and lightweight system using NGINX/PHP5-FPM along with any other caching systems.

It seems that Apache becomes a dinosaur and it might now be the good time to offer this for developpers.

Don't forget that as a developer and main contact for customers, we are in good position to promote Softaculous applications to their existing systems, providing Softaculous with more revenues. I think it would be fair that in exchange the Softaculous development team moves into higher gears and work on this.

However, I feel that you might be jumping in too soon without all the details.
I feel that you should provide a suggested process and let the developers help with some of the decisions.

You don't want to end up with something that is not useful to most of the developers because you didn't understand all the ways that they need it.

I would suggest a page somewhere that outlines how you plan on building it and how it will work. Then list somewhere where developers can post suggestions or concerns.

Some example questions to be considering:
1. How will I be switching between the two? Different ports can be useful to most, but I don't like using other ports besides 80 so can I switch Apache and Nginx on port 80.
2. Will there be templates for nginx site configuration files. I really need the ability to alter the site configuration. I would prefer a Template file that I can modify that has variables in it that I can use like {{documentroot}} and {{domains}} etc.
3. Will PHP-FPM be part if this and will I be able to configure a template for the PHP-FPM files.