Note that though MySQL is usually chosen for speed, it lacks some functions and is in some cases very "unstandard". PostgreSQL might be worth looking at. Tim Purdue of SourceForge has written an interesting article about the new version 7 of PostgreSQL compared to MySQL:
http://www.phpbuilder.com/columns/tim20000705.php3
and there is also something about optimizing it here:
http://www.phpbuilder.com/columns/smith20010821.php3
Discussion on:
View:
Show:
I've tried installing and configuring PHP on a Windows machine "manually" and found it a big headache. Then I found out about this product from www.nusphere.com that bundles APACHE, PERL, PHP, MySQL and WebAdmin, and I was up and running in a few minutes. I've never "looked back" ever since.
Serge (serge525@hotmail.com)
Serge (serge525@hotmail.com)
Unfortunately that was a typo in the article. The instructions are correct (they reference the right version), but when I typed that line, I must have hit 3 instead of 4 and din't catch it during proofing. Thanks!!
The README sent with PHP says the same, but in flat text.
No real 'new' news or insights here.
No real 'new' news or insights here.
everytime I do the (make, then I get blowen out of the build..
src/modules/php4
make[4] ***No rules to make target "all" . stop
make[3] ***[all] Error 1
make[2] ***[subdirs] Error1
make[2] ***Leaving directory '/usr/local/apache_1.3.22/src'
make[1] ***[build-std]Error 1
make[1] ***Leaving '/usr/local/apache_1.3.22'
make: ***[build] Error2
up to this point all seemed to be working.
any help would appreciated.
src/modules/php4
make[4] ***No rules to make target "all" . stop
make[3] ***[all] Error 1
make[2] ***[subdirs] Error1
make[2] ***Leaving directory '/usr/local/apache_1.3.22/src'
make[1] ***[build-std]Error 1
make[1] ***Leaving '/usr/local/apache_1.3.22'
make: ***[build] Error2
up to this point all seemed to be working.
any help would appreciated.
the world has changed since this article was written. I would like to see something on a modern apache version and what distros actually have RPMS that work. There is a lot of blood under the bridge where I set up mysql with php on Red Hat 7.1...
We recently setup a web site with the latest Apache and PHP rpms on RH 7.2 with absolutely no grief.
First of all, to all those mentioning rpms:
I like and perefer RPMs when possible, but in the case of php and apache I compile from source.
There is so many choices and options compiling those two that no RPM could fit them all. I've seen somewere on the net a how-to for making your own rpm... That would be a good option (pretty complex and not worth unless you plan on doing this a lot).
This article is barely touching the subject, it will work, but it is a little superficial. Php itselfcan (and in most cases should) be compiled with many more options and libraries. As an example --with-GD for image manipulation (wich requires GD library and depending on what you're going to do other libraries (--enable-gd-native-ttf for true type fonts --with-jpeg --with-png).
On the apache side, php is compiled in this example as a static apache module. (--with-apache) wich means that the day you want to add something to your php configuration (for example the GD library just mentioned) you'll need to recompile apache as well. Personally I prefer to load php as a dynamic module (--with-apxs). That will only require you to restart apache after recompiling php. I still need to understand the drawback of this approach (other than a slower apache startup).
All is valid for both, read the documentation (not just the quick start) and you'll realize how many ways and options those two have to be compiled. RPM would mean someone else is making decisions for you. (More often than not keeping it too simple in order to lower the dependancy requirements).
In most cases for a production server installing the above means getting paper and pen and making a list of other stuff you'll want to install before you even start (eg GD, PGP-GPG, JPEG, SSL) the list goes on.
If you're overwelmed by what I'm mentioning and none of the "extra stuff" is needed, than keep it simple and RPM will do!
I like and perefer RPMs when possible, but in the case of php and apache I compile from source.
There is so many choices and options compiling those two that no RPM could fit them all. I've seen somewere on the net a how-to for making your own rpm... That would be a good option (pretty complex and not worth unless you plan on doing this a lot).
This article is barely touching the subject, it will work, but it is a little superficial. Php itselfcan (and in most cases should) be compiled with many more options and libraries. As an example --with-GD for image manipulation (wich requires GD library and depending on what you're going to do other libraries (--enable-gd-native-ttf for true type fonts --with-jpeg --with-png).
On the apache side, php is compiled in this example as a static apache module. (--with-apache) wich means that the day you want to add something to your php configuration (for example the GD library just mentioned) you'll need to recompile apache as well. Personally I prefer to load php as a dynamic module (--with-apxs). That will only require you to restart apache after recompiling php. I still need to understand the drawback of this approach (other than a slower apache startup).
All is valid for both, read the documentation (not just the quick start) and you'll realize how many ways and options those two have to be compiled. RPM would mean someone else is making decisions for you. (More often than not keeping it too simple in order to lower the dependancy requirements).
In most cases for a production server installing the above means getting paper and pen and making a list of other stuff you'll want to install before you even start (eg GD, PGP-GPG, JPEG, SSL) the list goes on.
If you're overwelmed by what I'm mentioning and none of the "extra stuff" is needed, than keep it simple and RPM will do!
It's not tough to make your own customized version of an existing RPM. Download the matching source RPM (.src.rpm), "install" it (which unpacks it into /usr/src/redhat/{SOURCES,SPECS} on Red Hat), and build it with "rpm -bb /usr/src/redhat/SPECS/packagename.spec". To customize it, edit the build instructions in the spec file (eg. the configure options) and add your intials to the release number (to distinguish it from the distribution's RPM). Then issue the above rpm command to build your custom package.
I have had no problems getting any version of php/apache to run on any version of RH - all you need to do is use the MySQL-provided RPMS (not the redhat ones), and compile apache and PHP yourself from source. Voila. (Shall I write an article lol?)
I installed PHP, Apache and mySQL in rpm format. What should I do to configure PHP to be running with MySQL? I do know that in my machine PHP can run Apache Web Server. Thank you so much for your help.
my linux system has PHP,Apache and postgres installed.When i access webapplication via browser typing http://localhost/app the PHP is running from a different working directory,and all reference of directories starting with ./directoryname/ fails to find actual path.But when php cammand is issued from Applications directory PHP pages are correctly parsed...why is so happening?
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
