PEAR on shared hosting environments
| From: | Eric Stewart | Date: | Mon, 06 Oct 2003 15:17:14 +0000 |
| Subject: | PEAR on shared hosting environments | ||
| Groups: | php.pear.general | ||
| Request: | Send a blank email to pear-general+get-8302@lists.php.net to get a copy of this message | ||
I am a PHP programmer for an advertising agency. I've been writing PHP applications from scratch for over 3 years now. I've recently be toying with the idea of merging my code repository with PEAR.
The biggest problem I have is more than likely my inexperience with PEAR and how it operates. I write applications for web sites that are on shared hosting servers. Because they are shared, I don't have permission to do a full PEAR install on the servers.
To try and get around this, I decided to install PEAR on my workstation, MAC OS 10.2.8 running PHP 4.3.0. The idea was to get PEAR installed on my workstation and then copy the entire PEAR folder to each server that I'm working on. I would do all new and upgrade package install to my workstation and then send the files to up to the PEAR folders on each web site.
So I used the http://pear.php.net/go-pear install script to install PEAR on my workstation. According to the installer, all went well. Then I tried to install the PHPDocumentor package, since I've been commenting all my applications to PHPDoc standards for over a year now. Every time I try to install the PHPDocumentor Package with the PEAR Web interface package manager, the installation never completes. The package manager throws no errors, it just doesn't install the files at all.
I was pointed to a patch on the sourceforge site for PHPDocumentor, but the only instructions are for using the pear command line installer, not the web interface, for installing the patch. This would be great except it seems the pear command was not installed properly because I can't get it to work. I have tried installing PHPDocumentor at least a dozen times, and tired reinstalling PEAR at least half a dozen times.
Here is my current configuration according to the PEAR web interface:
PEAR executables directory: /Library/WebServer/Documents/PearInstalled/bin
PEAR documentation directory: /usr/local/lib/php/docs
PHP extension directory: /usr/local/lib/php/extensions/no-debug-non-zts-20020429
PEAR directory: /Library/WebServer/Documents/PearInstalled/PEAR
PEAR Installer cache directory: /tmp/pear/cache
PEAR data directory: /usr/local/lib/php/data
PHP CLI/CGI binary:/Library/WebServer/Documents/PearInstalled/PEAR/cli
PEAR test directory: /usr/local/lib/php/tests
Cache TimeToLive: 3600
Preferred Package State:stable
Unix file mask:22
Debug Log Level: 1
I don't think you need the rest of the configuration information.
So, is what I'm thinking about doing possible? Or is pear setting things in the php.ini file that is going to give me problems with I upload the PEAR files to the different web folders. I realize I will need to make directory changes for each server to address PEAR file locations, I think I can handle this.
Second, does anyone know why I'm having problems installing packages, especially since PEAR isn't throwing errors of any kind.
Thanks for the help,
Eric Stewart