Converting DSO to SuPHP ...

One of my most common requests is a script to handle system changes needed when converting to SuPHP and though such an automation script has been a part of our toolbox at My Server Expert for a long time, here is a variation of it for the rest of you ....

http://www.myserverexpert.com/build/dso2su.sh

Background:
-----------------------------------------------------------------------------
Though converting from DSO (Apache Module) based PHP to SuPHP is easy to do with EasyApache, this only changes the PHP platform on the system and doesn't address the possibly thousands of permissions, ownerships, and .htaccess files you have to edit to get SuPHP working with your existing accounts which may already be full of disallowed items such as scripts with the owner set to "nobody", script files or folders set to 777, or .htaccess files trying to set PHP configuration overrides. If you don't get rid of these items, scripts will fail or the sites will throw Error 500 after converting over to SuPHP as your new PHP platform. This script helps avoid that problem!

Converting to SuPHP (Basic Rundown):

1. Use EasyApache to setup SuPHP

2. Set PHP Config to PHP 5, SuPHP, SuExec

3. Run the script given above ...

Code:

# wget http://www.myserverexpert.com/build/dso2su.sh
# chmod 700 ./dso2su.sh
# ./dso2su.sh

4. Check your /var/log/messages log to see if there are any user
accounts requiring special handling or a custom PHP.INI file

That's it! You should be up and running on SuPHP!


No warranties are made or implied. Use the above script at your own risk!

 

Jim:

Actually our site was up for a long time and then about 3 weeks ago, we radically changed our entire product and service line up adding on a whole new catalog of servers and services as well as simultaneously changing both our billing and support systems and then one week later, yet another set of new services was deployed so everything is a little bit of a mess at the moment web site wise and still playing catch up getting the information added to the site and the new backend links setup which the past few weeks has been non-stop revisions but things now are finally settling down and getting back to a more normal pace and new price lists have been finalized.

Our internal development crew is already working quickly on the above; However, if you think you might be able to do something better, I'd consider letting you take a stab at it

Maybe not so much as you think! Our primary market is actually hosting providers themselves.

While we do have servers and various managed and monitoring services, our primary business
first and foremost is deep security analysis and server hardening and most of our clients are
actually web hosts that against our server offerings would be technically competition I suppose
but nobody really ever seems to really care just so long as they get me personally (biggest request)
for handling their server setups. (what can I say, I'm popular )

 

This version of the script is designed to skip unusual problem it can't recognize in this simplified form of the script. If something is "wrong" with the account requiring manual attention, it will simply leave the account in place.

Also, it doesn't target all "777" files, just those that are PHP scripts. Other files may still be set to 777.

As for "developing" the script or "adding logging", my response to those statements would be to laugh hysterically at and spit my coffee all over the monitor

(The script published on Cpanel is actually a small subset of the script I actually use which in the full verstion already has all of those things and much, much more including logging, handling unusual accounts, automatically creating custom PHP.INI configurations and adapting previous overrides, extended notifications, verifying accounts functioning, seeking out actual system errors and fixing them, etc )

 

If anyone had problems downloading "dso2su.sh" this past weekend, my apologies!


I forgot that there was links to that script here a Cpanel forums and had moved the file to another location during website updates and re-organizing this weekend. The script is now moved back to it's original web address.