Re: Using the pear installer (or pyrus) as an application deployment tool

On Mon, Oct 26, 2009 at 11:54 PM, Stephan Wentz <stephan@wentz.it> wrote: > (...) > 1. Since every deployment would need it's own pear-config-file / base > directory - is the base directory relocatable yet? I know that I fought with > this issue some time ago (several years, I guess). It was hard to relocate > the pear base-dir, since several of the directories were written > "hard-coded" (I know, wrong term) inside the base dir. How does pyrus handle > this? I think you can do a .pearrc file per "module". And adjust settings as you wish. For a shared hosting environment and a lot of local pear installs, I scripted that (kinda like that): #!/bin/bash -ex MODULE=$1 if [ -z $MODULE ]; then echo "Must call with $0 modulename" exit 1; fi # delete $1 shift $* COMMANDS=$@ /usr/bin/pear -c $MODULE/.pearrc $COMMANDS Usage: ./wentz.sh module1 install foo runs: pear -c module1/.pearrc install foo > 2. Our components are all completely capsuled, every component has a base > dir where everything resides, PHP-files, stylesheets, javascript-files, and > what's left. This encapsulating would have to be left intact, but how can I > achieve this inside the package.xml-file? Can i specify the PHP-role for > each file, even if it isn't a PHP-file? Or is there another mechanism/role > for this, that I missed? If they are all supposed to be a in a document-root like directory, I'd use www (and see pear config-get www-dir). It just sounds semanticly correct(er). :-) Till