Ticket #12224 (closed PLIP: fixed)
Create a filesystem resource directory by default
Reported by: | optilude | Owned by: | smcmahon |
---|---|---|---|
Priority: | major | Milestone: | 4.2 |
Component: | Installers | Version: | |
Keywords: | Cc: |
Description (last modified by optilude) (diff)
Proposer: Martin Aspeli
Seconder: David Glick
Motivation
With plone.app.theming and other uses of plone.resource, it is possible to create things like themes on the filesystem by placing them in a top-level directory. That needs to be configured at startup in Zope. plone.recipe.zope2instance supports this:
resources = ${buildout:directory}/resources
However, people have to know about this, do it manually in a buildout, and we may end up with inconsistent names for the top level directory, which makes documentation harder to write.
Assumptions
N/A
Proposal & Implementation
Change the default p.r.zope2instance option from 'off' to creating a top level 'resources' directory in the buildout.
Ensure this works with standard Plone 4.3 builds and in the installers.
Deliverables
- Change to p.r.zope2instance.
- Testing of installers
Risks
This may make all sites created by p.r.zope2instance depend on plone.resource, which may be undesirable. We can work around that by using a zcml:condition="installed plone.resource" if there isn't such a check already.
Participants
- Martin Aspeli
- Laurence Rowe
- David Glick
Progress
The option is already in the released p.r.zope2instance, it's just about default policy.