On Sat, Apr 16, 2011 at 7:02 PM, Yuka Poppe <[email protected]> wrote: > The location of document root (app/webroot/ in CakePHP land) is > variable. One can put the entire app in a directory accessible by each > vhost/webserver/what-have-you, and also make sure its somewhere that > can be seen by php. > > Have the webserver serve up any request that isnt a static file by the > 'shared' app, using url rewriting (mod_rewrite in case of apache) and > everything else is served up as usual like you'd expect from the > domains document root (assuming thats what you want for css/images > etc). > > The only thing you'd have to modify, is the index.php or bootstrap.php > where the core paths are defined, and have the webroot path adjusted > based on the current hostname, also you want a customer specific > databases, so you'd need to modify the config/database.php file to > include its settings from the relevant customer path.
What you and Krissy said makes sense, and is what I had in mind. But it seems to me that there would be issues surrounding AppController ad sessions. Maybe not. I haven't put too much thought into it. > Thats pretty much it, probably no need to mess around with symlinks, > allthough thats also a possible solution, but that would just add to > extra administration and setup when you need to prepare a new hosting > account. Yes, setting the classpath makes more sense, as Vitor pointed out. As for hassles with setting up a new account, though, I'd think something like this would be done through a shell script, ant, or similar, regardless of whether one was using symlinks or a prearranged config. Doing it by hand each time would be too tedious and error-prone. -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
