Different site-access directories?

Next topic

Author	Message
William Steenbergh	Monday 02 January 2006 7:18:28 am Hi I was wondering if it would be possible to install eZ Publish some place, and have the actual site-sensitive content somewhere else? Something like: /var/www/sites/ezpublish <= kernel, libraries, extensions etc /var/www/sites/site1 <= Design, cache, storage, template overrides etc /var/www/sites/site2 <= Design, cache, storage, template overrides etc I don't need optical tricks to accomplish this in Apache, or symbolic links in Linux, I really need this to be a physical reality on my hard drive. Thanks William
Thomas Nunninger	Monday 02 January 2006 7:32:36 am A short grep shows: settings/ and design/ are hardcoded all over the code. I think it's no fun to fix this :-) Can you explain the reasons, why you need it this way and why symlinks are not usable? I have a similar setting with links in design/, settings/, extension/ and var/ folders. I can't imagine any situation where it should not be possible to write a small shell script which creates symlinks in the original folders to site1/ design/ setings/ ... If you describe your reasons and targets it's perhaps possible to find a solution. Have a nice day Thomas
William Steenbergh	Monday 02 January 2006 8:31:37 am Hey Thomas Thanks for the swift reply! I wish not to use links, because I'm afraid of the tangled mess this might become... If this thimg could be settled phisically, then that would have been ideal. Since it can't, I can either go hack the EP core (and hope I don't miss a thing...) or accept it as is...
Xavier Dutoit	Tuesday 03 January 2006 3:50:00 am Hi, On one config, I have installed ez with symlinks for kernel, share (this one is taught as a shared folder on svn, that's an external for instance), lib and a few others. It works and that's not too messy. X+ http://www.sydesy.com
William Steenbergh	Tuesday 10 January 2006 5:18:39 am Hey I have now used sym-links all over the system, with the actual files in the customer's directory. Mysql doesn't seem to mind working with a link instead of the actual database directory, apache keeps a VHost-specific logfile in the right directory, and all of ez publish's variable parts are accessible. I had some trouble however starting ez publish. I had set the apache's DirectoryIndex to /home/customer/index.php. Index.php was a symlink to /var/www/ezpub/index.php. I got the most exotic php-errors i ever saw! One nasty, low, dirty trick: Make an actual /home/customer/index.php, but instead of linking to ez publish, include it in a frameset: <!-- /home/customer/index.php --> <html> <head> <title> Foo </title> </head> <frameset> <frame src="http://[host]/index.php/[siteaccess]"> </frameset> </html>