Guest_imported
New member
- Jan 1, 1970
- 0
How would i go about installing apache with php, mysql, perl and ssl? Please point me to right direction 
thanks!
thanks!
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Help apache/php/mysql/perl
- Thread starter Guest_imported
- Start date
- Status
Hi,
That all depends on what version of linux you have. Most distros will have pre-packaged rpms (or debs) for all of the above. Essentially, you'd install all the packages in their own right (Apache / perl / php / mysql / openssl) and then configure apache to 'talk' to the others. This is done via apache modules - e.g. mod_php, mod_ssl, etc. These may be available as separate rpms or could be provided by some distros in their main 'apache' rpm.
For perl you'd need to enable cgi ( and, possibly, install mod_perl if you wanted high performance --> .
Enabling cgi and modules are done via the apache httpd.conf file. There are commented-out examples for most things. In general, activating a module requires you do add lines like this (or uncomment) :
LoadModule php4_module libexec/libphp4.so
AddModule mod_php4.c
AddType application/x-httpd-php .php .php4
(The first line points at the location of the actual module (libphp4.so) relative to the ServerRoot directory.)
Of course, if you want you can install everything from source tarballs. I personally tend to recommend using rpms for most things if you are on such as system because eventually you will end up with dependency issues - for example if you later want to install a rpm for something that requires perl >= 5.6 and you didn't use a rpm for perl in the first place then you'll start to have problems.
Hope this helps to start with...
Regards
That all depends on what version of linux you have. Most distros will have pre-packaged rpms (or debs) for all of the above. Essentially, you'd install all the packages in their own right (Apache / perl / php / mysql / openssl) and then configure apache to 'talk' to the others. This is done via apache modules - e.g. mod_php, mod_ssl, etc. These may be available as separate rpms or could be provided by some distros in their main 'apache' rpm.
For perl you'd need to enable cgi ( and, possibly, install mod_perl if you wanted high performance --> .
Enabling cgi and modules are done via the apache httpd.conf file. There are commented-out examples for most things. In general, activating a module requires you do add lines like this (or uncomment) :
LoadModule php4_module libexec/libphp4.so
AddModule mod_php4.c
AddType application/x-httpd-php .php .php4
(The first line points at the location of the actual module (libphp4.so) relative to the ServerRoot directory.)
Of course, if you want you can install everything from source tarballs. I personally tend to recommend using rpms for most things if you are on such as system because eventually you will end up with dependency issues - for example if you later want to install a rpm for something that requires perl >= 5.6 and you didn't use a rpm for perl in the first place then you'll start to have problems.
Hope this helps to start with...
Regards
- Status