> You don't need to make any symlinks - just make sure the > library directory is on your php include paths by modifying php.ini or > just > manually in your index.php for example.
I see, since I don't have access to php.ini on my shared host env, I can do an include on index.php that stays on my public folder, for example. > > You may need to change paths when deploying to different environments, > but > you can organize your application in such a way that all those settings > will > go in one file like index.php or a config. > > Dmitry. > -- Let me go in more detail. At this moment, each project on my shared host as its own subdomain configured so that, when I need to deploy things to the final host, I just grab all subdomain info and put it on the "costumer shared host", and I change the URL on my config_root file. Simple. In order to have the library folder shared for several projects, I will probably need to create a subdomain just to old my zend library files. (so that the library folder could stay on the same level as the other project folders). Once this is done, and assuming (I have no clue) that we can easily access files from a subdomain into another, I will need to replicate this same structure on the "costumer shared host", and change the config_root file. If the "costumer shared host" don't have the possibility to have subdomains, I will not be able to deploy it without some more changes. The main reason I wanted to have the library outside, was to update the library for all the zendframework sites at once but, if something goes wrong, all goes wrong at once as well. :s I do believe that, if we deploy the library for each project, and we relate each library connected to a repository where we can make synchronize, we can have more control about what project needs to use the last resources and the others that don't need for a long time. If, for some reason, one project needs to have a updated library folder later on, I can just download from the repository the info back to the development environment. I know that each case is a case, and we should organize the way it best fit us, I just want to know if, regarding this scenario, there are any better ways for doing it. Thanks again, Márcio
