New Topic

cPanel & WHM Feature Requests Topic Uncategorized

This object is in archive!

Category Uncategorized

Tags 55649, cherokee, nginx, litespeed

Support for more http daemons

Feature Importer shared this idea ago

Completed

As a Hosting Provider, I want support for more http daemons, so that I can choose the httpd that best works with my configuration.

Offer a choice between Apache and the better performing HTTPDs such as lighttpd or ngnix. I know that this would be difficult to implement and also difficult from a strategic point of view

This is a feature that has been migrated over from the cPanel Forums. All previous comments and discussions concerning this feature can be located at:

nginx for accelerating Apache: http://forums.cpanel.net/f145/nginx-accelerating-apache-case-41719-a-134209.html

Cherokee: http://forums.cpanel.net/f145/cherokee-web-server-apache-alternative-98945.html

Lighttpd: http://forums.cpanel.net/f145/lighttpd-cpanel-135229.html

I like this idea 0

Best Answer

cPanelJacob ●

The EasyApache team has been working diligently on the EasyApache 4 system. The changes we've made to Config::apache will allow it to be easier to drop variant in web servers. This code will be included in 11.50.

If/When we provide another web daemon, it will most likely start with Nginx. We look forward to your feedback and how we can continue to improve cPanel & WHM's WebStack.

Replies (7)

skinnyt ●

We can choose which mail server want to use, so why not allow us the same choice for http server? I know its hardly comparable as http will be more complex, but it's not impossible!

URL

maever ●

Though having the choice is nice, a lot comes to mind.

I can imagine compatibility issues with modules come in to play.

each server would requiring their own set of modules.

not to mention compatibility with things such as cloudlinux.

Though I support the idea, I'd like some insight to how much work this be to determine if it is feasible to even suggest it. At the very least i'd like to see support official support for a reverse-proxy setup.

URL

gnusys ●

cpXstack ( cpxstack.sysally.net) implements the full nginX + PHP-FPM stack on cpanel

URL

Marcelo Pedra ●

I'm particularly interested in implementing nginx. I second this feature!

URL

cPanelJacob ● ●

If/When we provide another web daemon, it will most likely start with Nginx. We look forward to your feedback and how we can continue to improve cPanel & WHM's WebStack.

URL

cPanelJacob ●

The methods and packages that allows us the ability to easily drop in replacement web servers is in 11.50.

Please note: This feature request is about support for more HTTP daemons. This is a giant wish for a single feature request. We'll be providing support for more daemons at a later date, however at this time, the requirement system is now in place.

URL

Marcelo Pedra ●

And... there is something we can try/test now on 11.52?

URL

cPanelJacob ●

The system we implemented in 11.50 allows a system administrator to tell cPanel where the webserver and attached locations are located on the file system. This can allow 3rd party integrators to place their webserver files into their own locations and point cPanel to use those directories in it's normal operations. As long as cPanel has appropriate methods and functions to call associated with that integrators systems, it should work properly.

URL

GNUSYS ●

@cPanelJacob - Can you give me URL's to the documentation to the system implemented in 11.50 ?

Also in my point of view ;cPanel has to provide hooks for the following operations to make way for another webstack

1. When an SSL cert is added/removed for a domain in WHM or cPanel

2.When the IP address ( ipv4/ipv6) for a domain is changed via WHM

Without the above it is very difficult to integrate another webserver that would need to use the IP address and SSL certs

URL

cPanelJacob ●

Hi,

Here's a link to the documentation regarding this system:

https://documentation.cpanel.net/display/EA4/Advanced+Apache+configuration+--+paths.conf

I think 'hooks' is the wrong word in this situation, but we're thinking of the same thing. New web servers will need to come with Perl packages and methods / functions to make sure this functionality continues. This is the main bulk of adding new web servers. This is something we're also continually making easier and better so we can keep expanding this platform.

I hope this helps!

URL

GNUSYS ●

I see that this will help transitioning from the custom compiled apache in /usr/local/apache to the rpm apache .But not sure how the above change will aid in using a different webserver (something like nginx or haiwatha) as a drop in replacement .

As I mentioned ; the first thing to do for allowing a different web server is providing necessary hook for all things that can change in a webstack..like IP address,SSL cert locations(file names) ,ssl activation , php version (once you transition to a multi version PHP ) etc .

This would allow 3rd party dev's also in adding many more drop in http daemons

URL

cPanelJacob ●

Yep, you're right, helping us transition away from Apache was the first step in this direction. For example, if you wanted to use a custom Apache binary, you could easily do this without having to touch the Apache provided by cPanel.

As we continue to expand the system, we'll be addressing those issues with the different cPanel operations. Again, I don't think we'll be using hooks, but more of an abstraction layer that allows cPanel / WHM to not care what type of web server they are running, and it will run operations in a more generic way.

URL