If you were wondering whether you can use  apache licensed code in your commercial applications and what do you need to do in order to comply with the license here’s the unofficial simple ans short answer.

You can use Apache 2.0 licensed source code in your project as long as you include the copy of the license in your distribution and provide attribution in an applicable way in your distribution.

The slightly lengthier and detailed (but still very simple explanation) is below, taken from Apache license FAQ

Describing legal documents in non-legalese is fraught with potential for misinterpretation. Notwithstanding the text that follows, the actual text of the license itself is legally binding and authoritative.

That said, here’s what the Apache license says in layman’s terms:

It allows you to:

• freely download and use Apache software, in whole or in part, for personal, company internal, or commercial purposes;
• use Apache software in packages or distributions that you create.

It forbids you to:

• redistribute any piece of Apache-originated software without proper attribution;
• use any marks owned by The Apache Software Foundation in any way that might state or imply that the Foundation endorses your distribution;
• use any marks owned by The Apache Software Foundation in any way that might state or imply that you created the Apache software in question.

It requires you to:

• include a copy of the license in any redistribution you may make that includes Apache software;
• provide clear attribution to The Apache Software Foundation for any distributions that include Apache software.

It does not require you to:

• include the source of the Apache software itself, or of any modifications you may have made to it, in any redistribution you may assemble that includes it;
• submit changes that you make to the software back to the Apache Software Foundation (though such feedback is encouraged).

Related posts:

1. Some web server administration tips on CentOS and cPanel (but not only)

This is more of a personal notes for myself but I am sure others will find it useful.

Apache:

/usr/local/apache/logs/error_log

All exceptions caught by httpd, along with standard error output form CGI applications are logged here.  The first place you should look when httpd crashes, or you incur errors when accessing a website.

/usr/local/apache/logs/suexec_log

Contains auditing information reported by suexec each time a CGI applicaiton is executed.  If you receive an internal server error, with no relevant information being reported to the Apache error_log, check here for potential suexec policy violations.

Domain specific access logs are located here:

/usr/local/apache/domlogs/

PHP

To find out which php.ini is used for PHP configuration (to save you frustration of editing a non active php.ini) find it with the following simple command:
php -i | grep php.ini

where -i switch is used to give you PHP information (obviously). To see other useful switches run

php -h

to locate where php is use:

which php

(but you already knew this – right ?   )

*** Some of these tips are applicable not only to CentOS and cPanel configuration.

Related posts:

1. How to use Apache 2.0 license in commercial products, explained in simple terms