Saturday 24 April 2010 2:24:05 pm
I've been working/thinking about this a bit now, and I think I've come up with a solution that'll enable you to have all your extensions and sites/siteaccesses structured outside of ez publish, and have a build script that'll do all the "hard work" setting up the installation for you, based on the extensions and siteaccesses you choose to include at that time. Which basically means that you can easily split them up into separate installations, or have them all in the same, whatever suits you (the site) best. Here's the structure of the code outside of ez publish: root
extension
custom_extension1
custom_extension2
sites
sitename
extension
site_extension1
site_extension2
siteaccess
sitename_eng
sitename_admin
build.xml
build.properties
When you build this, it'll checkout / copy the core of eZ Publish and place it in a folder you choose and put all the extensions and siteaccess you wish to include (all, or a specified list), into the installation. root / sites / sitename / extension goes into ez-installation / extension root / sites / sitename / siteaccess goes into ez-installation / settings / siteacess root / extension goes into ez-installation / extension When you build this for development, the extensions and siteaccess will be symlinks inside the installation, but if you build if for production / distribution, it will copy each extension / siteaccess into the installation instead, so you're able to have each installation standalone, and isolated from each other. You can take this even further, splitting settings into environment-specific folders (development, integration, preprod, production), and have the build-script copy/link the correct settings based on what you're building for. The only downside I can see to this right now is that you have to be careful with the settings / override folder. You really shouldn't use it all, since it can potentially ruin every single installation you have. But you kind of should be careful with that folder anyway... Any thoughts on this?
|