Re: Re: moving forward: thanks for feedback

Greg I still think that instead of writing instructions within the mailist like this, that placing such gems in a wiki would then facilitate an easy storage and retrieval method and also allow others to add edit and add, simply then update mailist with a link saying modified PEARweb setup instructions. i.e. http://wiki.triangle-solutions.com/index.php/PEAR - great for my benefit anyway as i forget things very easily. Now I suppose it would be nice to name an OFFICIAL wiki to document the gems that happen on the mailist in a more formal manner. I know Justin is active with his Text_wiki (http://pear.reversefold.com/dokuwiki/doku.php - seems to be run by Docuwiki now maybe I am looking in wrong place ?), and you may want to select an install of this. I currently use MediaWiki as you can see above. LOL i have bought pear.nu :) thought it was an apt name.. anyway if you want to chat more about an official Wiki then I can do some work on that, its dead easy anyway. I would use MediaWiki and put a more apt design in, and place on that URL Regards Ian Warner Director Triangle Solutions Ltd Greg Beaver wrote:

David Coallier wrote:

Well just being able to install it will be a step forward for sure. Greg, you seem to know alot about the server, would you mind stating us the apache version, php version, mods we need to enable, all the specs related to the server in order to be able to have a close-to-same server.

Hi David, First of all, every needed extension and PEAR package is listed in pearweb/package.xml. As for Apache version, I have found that it works in both 1.3.x and 2.0.x, but not in 2.2.x. I currently run it at home using Apache 2.0.something with PHP 5.1.6, but it is running with PHP 4.4 on the live server. I run MySQL 4.1, the live server is running MySQL 4.0.26. When you get these things set up, you'll need mod_rewrite and will need to run PHP as an apache module rather than as fastcgi. In addition, check in docs/ and you will see apache-setup.txt, which contains extensive setup instructions. This should make it relatively easy to set up. I would allow 1-2 hours for the inevitable apache problems. I set up pearweb running as an alias to localhost, and NameVirtualHost * so that I can run it as "http://pear" This also allows me to run peclweb on my machine, but that does not interest us at the moment. Greg