I have just started working with Easyapache 3. I have to say my first thoughts, I'm not that impressed. Maybe its because I am not going to Apache 2 yet. I know this is one of the main reasons for Easyapache 3. I know Apache 2 and 2.2 is going to have to happen sooner or later, but we have a lot of servers. When I do the upgrade to Apache 2, I want to upgrade them all. I don't want to have some servers with Apache 2 and some with Apache 1.
Anyway, so I am still using Apache 1.3.39 with Easyapache 3. I am a little confused by all of the included configuration files. I know cPanel wanted to get away from direct Apache configuration file editing, but I used that a lot.
For example, I run a customized suPHP set up and a customized mod_security set up. When I install mod_security, the module gets loaded directly into the httpd.conf file. When I rebuild Apache (new server, so I'm just playing around) the mod_security module is gone.
If you install your own Apache module, what file is the LoadModule and AddModule lines suppose to go in?
I also noticed that there doesn't appear to be an option to just not compile PHP with Easyapache3. The custom suPHP set up I use, uses my own PHP compile as well. In the old Easyapache, if a new version of Apache came out, you could just run easyapache and not select PHP. This would just compile Apache, and would not compile PHP. It would not remove PHP, it just wouldn't compile it.
Now with Easyapache 3 it seems that if you select the No PHP option, it actually removes PHP entirely. Is it not possible to just compile Apache and leave whatever PHP version that is installed, active?
It seems that the new Easyapache 3 took away a lot of hand-made customizing. Now everything has to be done through the Easyapache 3 interface or through the series of include files, which I haven't figured out yet.
I suppose I am in the minority in regards to this and if that is the case, I'll just have to make adjustments.
Anyway, so I am still using Apache 1.3.39 with Easyapache 3. I am a little confused by all of the included configuration files. I know cPanel wanted to get away from direct Apache configuration file editing, but I used that a lot.
For example, I run a customized suPHP set up and a customized mod_security set up. When I install mod_security, the module gets loaded directly into the httpd.conf file. When I rebuild Apache (new server, so I'm just playing around) the mod_security module is gone.
If you install your own Apache module, what file is the LoadModule and AddModule lines suppose to go in?
I also noticed that there doesn't appear to be an option to just not compile PHP with Easyapache3. The custom suPHP set up I use, uses my own PHP compile as well. In the old Easyapache, if a new version of Apache came out, you could just run easyapache and not select PHP. This would just compile Apache, and would not compile PHP. It would not remove PHP, it just wouldn't compile it.
Now with Easyapache 3 it seems that if you select the No PHP option, it actually removes PHP entirely. Is it not possible to just compile Apache and leave whatever PHP version that is installed, active?
It seems that the new Easyapache 3 took away a lot of hand-made customizing. Now everything has to be done through the Easyapache 3 interface or through the series of include files, which I haven't figured out yet.
I suppose I am in the minority in regards to this and if that is the case, I'll just have to make adjustments.