After plinking around with php for a while, I finally think of myself as minimaly competent. One thing I have noticed is that most of the time my "apps" end up having one config.php include-type file per deployment on a virtual host and the rest of the code is static no matter how many clients I setup with the same app.
It occurs to me that it would be more efficient to maintain versions of my deployed apps if I could share the "static" code among all my deployments and let each virtual host have it's own unique config.php file (and mysql db).
Has anyone attempted to maintain one copy of php code files in a central location and shared this among different virtual hosts each with its own config.php?
For example, in a virtual apache environment for foo.com:
/home/foo/subdomain1/config.php
/home/foo/subdomain2/config.php
with both subdomain1.foo.com and subdomain2.foo.com both using php scripts stored in say:
/home/phpappbase/
Each subdomain's config.php file would have unique dbuser, dbname, prefs, etc ... ????
This is a bit off topic as it is more of a deployment architecture/code maintenance question but it involves knowledge of apache AND php environments so I thought I'd give phpbuilders a try. Thank you all in advance for what I hope is a very interesting thread for us all!
