Getting the server ready to build applications from source:

Check for any RPM installations of the applications.

rpm -qa | grep -i apache
rpm -qa | grep -i httpd
rpm -qa | grep -i php
rpm -qa | grep -i mysql

Remove any RPM installations found with the “rpm -e” command:

rpm -e application_name_here

Install some base requirements to compile and install the software.

yum -y install gcc gcc-c++ ncurses-devel libxml2-devel libpng-devel

Download the appropriate sources for Apache, PHP, and MySQL and decompress it.

cd /usr/src
wget http://us3.php.net/get/php-5.2.11.tar.gz/from/us.php.net/mirror
wget http://apache.inetbridge.net/httpd/httpd-2.2.14.tar.gz
wget http://downloads.mysql.com/archives/mysql-5.0/mysql-5.0.87.tar.gz
wget ftp://ftp.ibiblio.org/pub/Linux/ALPHA/freetds/stable/freetds-stable.tgz
tar xzf php-5.2.11.tar.gz
tar xzf httpd-2.2.14.tar.gz
tar xzf mysql-5.0.87.tar.gz
tar xzf freetds-stable.tgz

Build and Install MySQL.

Add the MySQL User and Group

groupadd mysql
useradd -g mysql -c "MySQL Server" mysql

Install MySQL.

cd mysql*
chown -R root.root *
make clean
./configure \
--prefix=/usr/local/mysql \
--localstatedir=/usr/local/mysql/data \
--disable-maintainer-mode \
--with-mysqld-user=mysql \
--with-unix-socket-path=/tmp/mysql.sock \
--without-comment \
--without-debug \
--without-bench
make && make install

Configure MySQL.

/usr/local/mysql/bin/mysql_install_db
chown -R root:mysql /usr/local/mysql
chown -R mysql:mysql /usr/local/mysql/data
cp support-files/my-medium.cnf /etc/my.cnf
chown root:sys /etc/my.cnf
chmod 644 /etc/my.cnf

Set MySQL to start on boot

echo "/usr/local/mysql/lib/mysql" >> /etc/ld.so.conf
ldconfig
cp ./support-files/mysql.server /etc/rc.d/init.d/mysql
chmod +x /etc/rc.d/init.d/mysql
/sbin/chkconfig --level 3 mysql on
service mysql start

This sets up symlinks for all MySQL binaries so that they can be run from anywhere.

cd /usr/local/mysql/bin
for file in *; do ln -s /usr/local/mysql/bin/$file /usr/bin/$file; done

Set a MySQL Root Password for security (obviously use something other than “new-password-here”.

mysqladmin -u root password new-password-here

Test the Password:

mysql -u root -p

While logged into MySQL delete the test database.

drop database test;
use mysql;
delete from db;
delete from user where not (host="localhost" and user="root");
flush privileges;

Building Apache

cd /usr/src/httpd*
make clean
./configure \
--prefix=/usr/local/apache \
--enable-shared=max \
--enable-module=rewrite \
--enable-module=so
make && make install

Build and Install FreeTDS for MSSQL Extension Support.

cd /usr/src/freetds*
./configure
make && make install

Build and Install PHP

cd /usr/src/php*
./configure \
--with-apxs2=/usr/local/apache/bin/apxs \
--disable-debug \
--enable-ftp \
--enable-inline-optimization \
--enable-magic-quotes \
--enable-mbstring \
--enable-mm=shared \
--enable-safe-mode \
--enable-track-vars \
--enable-trans-sid \
--enable-wddx=shared \
--enable-xml \
--with-dom \
--with-gd \
--with-gettext \
--with-mysql=/usr/local/mysql \
--with-regex=system \
--with-xml \
--with-zlib-dir=/usr/lib \
--with-mssql=/usr/local/
make && make install
cp php.ini-dist /usr/local/lib/php.ini

I prefer to symlink configuration files to /etc so that they are easy to find and edit.

ln -s /usr/local/lib/php.ini /etc/php.ini
ln -s /usr/local/apache/conf/httpd.conf /etc/httpd.conf

Edit the Apache Configuration File – I prefer nano.

nano /etc/httpd.conf

Uncomment the following lines or add them (uncommented) if they do not exist after “AddType application/x-tar .tgz”

#AddType application/x-httpd-php .php
#AddType application/x-httpd-php-source .phps

Find the DirectoryIndex (CTRL+W in Nano) and add index.php to the beginning.

DirectoryIndex

Set Apache to start on boot and start it for the first time.

ln -s /usr/local/apache/bin/apachectl /etc/rc.d/init.d/apache
ln -s /etc/rc.d/init.d/apache /etc/rc.d/rc3.d/S90apache
/etc/rc.d/init.d/apache start

Then, you must configure FreeTDS to point to your MSSQL DB server. To do so, edit (or create) the /usr/local/etc/freetds.conf file and put in there exclusively these lines:

[global]
host = xxx.xxx.xxx.xxx (ip of the MSSQL server)
port = 1433
client charset = UTF-8
tds version = 7.0 (or 8.0 if using FreeTDS 0.82 or later)
text size = 20971520

I was doing the math on the licensing structure (we’ll go with the 1-CPU Enterprise license as this example).

I will start by saying that I realize it is in LiteSpeed Technologies’ best interests for you to lease your license from them as this gives them the most profit/income etc… where as an Owned license is generally seen as a larger up-front investment to reduce long-term costs.

I am also aware that I am comparing monthly lease to a yearly ownership as I am wanting to compare the extremes (smallest up-front investment vs the largest).

Owned licenses are an investment into LiteSpeed Web Server/Technologies and I always look at investments based upon how well they will return and how long until they return. A 39 month wait until the investment begins to return is a tad too long in my opinion and as you read on you will see the details of my analysis of their licensing program.

The primary problem that I see is that the Owned licensing doesn’t really reduce long-term costs fast enough – the argument could be seen either way that either the leasing prices need increased (sorry, have to share both view points) or that the owned licensing needs to be reduced either the initial purchase or the support renewal costs.

The price of a 1-CPU Enterprise Leased license is $32/month or $384 paid monthly for a year.

The price of a 1-CPU Enterprise Owned license is $41.58/month or $499 paid yearly.

At these prices you could have a Leased license for 15.6 Months for the price of an Owned license for one year – which makes sense if you think about it.  At the end of the first year if you want to continue support and upgrades for your owned license you then have to pay $99 for a support renewal.  You do not have to pay any such renewal fee for Leased license.

The price of a 1-CPU Enterprise Owned license for two years is $598 which would get you 18.69 months of Leased licensing – so after you have your owned license for over 18 and a half months you’ve broken even on your investment of an owned license.  While a year and a half is not a tremendous amount of time – it is asking for a huge investment of your money up front.  To make the Owned license an option you have to be willing to invest over a year and a half into LiteSpeed before you even break even.

After 18.69 months of being on an Owned license and having paid the $99 support fee after a year you will be at approximately $8.25/month for each owned license which isn’t terribly bad (a savings over leased of $23.75/month), but keep in mind it took over a year and a half to get to this point which leads me to my next concern.

The next major concern in my eyes with the current structure is that for the Owned license to “pay for itself” (to return on my original investment) which is one of the primary reasons I look at owned licenses over leased – it will take an additional  21 months for a total of 39 months before going Owned has “paid for itself” and returns on your initial owned licensing investment will be realized if you don’t include the support Renewals. The first and second renewal for a total addition of $198 because by this point you’re already at 39 months before going Owned has paid for itself.

Is it really intentional on the part of LiteSpeedTech to make an Owned license holder have to wait 39 months before they can start to see a return on their investment of going Owned?

What are your thoughts? Post comments!

I have in the past fought tooth-and-nail for Apache’s ability to match LiteSpeed Web Server’s speed when serving web sites.  Apache can be configured to be nearly as fast if not just as fast as LiteSpeed but the problem is that Apache requires in my own personal testing nearly two times as much memory and FastCGI to come close to LiteSpeed comes out of the box.  LiteSpeed claims to serve static content up to 9 times faster than Apache and PHP up to 50% faster.  While I won’t go into depth as to which one can do what faster, I will go into why I chose to move my company from Apache to LiteSpeed and what benefits we have seen.  If you want to see benchmarks that compare LiteSpeed and Apache I recommend you search Google.

My company has relied upon Apache for years however I recently began testing the latest version of LiteSpeed which has come a long way.  LiteSpeed out of the box offers the performance of an extremely-optimized Apache installation with half or less memory consumption in my testing which is a major benefit.  Apache is very weak against certain DoS attacks such as a HTTP Request DoS which doesn’t require a large amount of outgoing bandwidth but can be devastating to an Apache web server where as LightSpeed takes such attacks in stride in my testing.

I found personally that the overall “feel” of browsing various test sites, both dynamic and static, felt snappier or zippier which is an additional benefit to running LiteSpeed.  In the end if you know what you are doing and you have the RAM in your server to accomplish it you can match LightSpeed Web Server’s speed at the cost of efficiency.

LiteSpeed’s Web Server is a direct replacement for Apache and installation was a breeze.  LiteSpeed supports all of the popular control panels and all of the features of Apache except for your old Server Side Includes but who uses those any more?  In my experience on a cPanel based web server you can log into WHM and switch between LiteSpeed and Apache at any time and you can run LiteSpeed on an alternate port for testing any sites that you wish to make sure will function correctly before “making the switch.”  I have yet to run into any issues that are caused by LiteSpeed however I will post an update if I do run into any.

At the end of the day my advice is to spend the extra money you would be paying to add additional RAM into your server on a LiteSpeed Web Server license.

Edit: LiteSpeed 4.0 *does* support Server Side Includes even though the current FAQ on LiteSpeedTech.com says that it does not.