Hi Markus, I'm in a similar situation inasmuch as I'm running many sites off the same codebase. Have you not thought of having all your clients connect into the same library directory? Then you don't need to upload massive amounts of data lots of times, just once. I also upload the tarball to the server and untar it on there instead of uploading the untarred directory as this saves an amazing amount of time
Jude A. On Monday 16 July 2007 23:28, Markus Wolff wrote: > Hi all, > > I'm currently assembling a stripped-down version of the Zend Framework, > including only the few components that our application needs, with the > purpose of bundling these components with our application. > > This is a slow and tedious process, as I really don't want to include > any files that are not needed - all files are FTP'd over to the > customer's webspace whenever an update has been made to the system, > which happens quite frequently... and we got *lots* of customer sites, > so each file saved equals lots of bandwith saved :-D. > > I have been searching for any information on the website regarding each > component's dependencies on other components, but I didn't find any. So > what I'm doing now is taking only the files that I include directly, try > to reload, watch out for the error messages, and copy over more files to > complete the bundle. Not fun. > > It would be really great if each component could have a list of > dependencies in the manual. Even better if each component would be > installable individually using the PEAR installer, which auto-resolves > dependencies - but I guess this is reaching for the stars :-D > > CU > Markus
