Disable or Compile without suPHP

I am trying to find a way to either disable or compile apache without suPHP, but after 2 days of trying I am still not one step further and would like your help.

Reason for not wanting suPHP is because I want to use ZendOpcache, see http://pecl.php.net/package/ZendOpcache and http://php.net/manual/en/book.opcache.php, which unfortunately doesn't work with suPHP.

I understand that suPHP is better for security reasons, but all-in-all I still prefer to use mod_php/DSO as PHP handler, not only because of the ability to use an opcache solution but also because I only have my own websites on my dedicated server and many websites use scripts located at other websites. This setup has worked for many, many years and I prefer it this way.

I have tried many things, but none have worked so far and I would be grateful if somebody has a solution to not use suPHP.

Thanks.

you can install Varnish as a cache server in front of the apache, it should increase performances.
Varnish can be installed from CWP.admin

Thanks for the reply, that I have implemented already.

Will you consider adding an option to build without suPHP so that the normal functionality of all config files remains editable trough CWP admin?

this would we possible with some future versions.

tfbpa, what did you end up doing?

Nothing, so far I am still using suPHP and am waiting for the day it is possible to compile without it, as disabling it just messes everything up.

I'm vote to mod_php or other php hendler because compatibility all cache software.

I'm unlike suphp because consum high ram. suPHP best for site only use .html

My vps 1GB ram on vps.net, traffick 900/1300 per day, cwp very slow and every down, vestacp good ram good performance but cwp best features. 

Please develop this options.

varnish not support ssl. 

What about PHP-FPM / FCGI (FastCGI), as I understand a form of implementation is already being used for CWP; although not for user/customer operations. 

My reasoning for wanting an alternative handler is that of caching; additionally I require SSL and based on my limited knowledge of utilizing an NGIX/Apache/Varnish configuration, a multi-product integration seems far more complex and resource intensive than that of utilizing an alternative PHP handler?

Thoughts?

Thanks!

PS - My apologies for resurrecting an old thread, although the question appears to have relevancy.