2009/10/27 prodigitalson <[email protected]> > > Im in the process of porting an existing application. Currently there are a > number of shell scripts written in a number of scripting languages. > Typically these can be considered "owned" by particular ZF modules within > the web application in that they supply supportive functionality (like > daily > downloads and parsing of data from other servers on the network amongst > other things). > > I was wondering in general terms how others may have impelmented this in > their applications... Did you use a CLI environment var and go through the > normal bootstrapping? Did you just do it as a conventional php shell script > manually including the needed framework files? Or did you use the > Zend_Tool_Framework? Did you nest these script within your module dirs or > at > the library or application level? etc..
I've been struggling with this as well. I've been trying to go down the Zend_Tool route, which I have managed to get working, but my solution is far from ideal: * I've had to add my application's model/library directories to my local PHP CLI php.ini include_path, so that ZF can find my provider classes. This is not very portable. * To give my provider classes access to my application's classes, resources etc. I've had to add a base provider class which does some bootstrapping in its constructor. My application provider classes then require this class in and extend it. I'd be interested to know how others have approached this. -- Tim Fountain http://tfountain.co.uk/
