zope.conf extensibility
This might be the third time I hit this issue, and I've always given up before. I hope this is the last time. I have some product that would greatly benefit from being able to be configured from within zope.conf. I don't want a separate configuration file. Period. Why? Apache doesn't have separate configuration files for mod_cache or mod_anything. Chris McDonough has used the %import feature on ClockServer product, but that just works because zopeschema.xml has a <multisection> definition for ZServer.server type. I think it would be very useful for zopeschema.xml to have a <multisection> for some abstract type to allow third-party product to define their own section type extending this abstract type and thus have their configuration kept inside zope.conf Consider this a proposal *wink*. -- Sidnei da Silva Enfold Systems, LLC. http://enfoldsystems.com
On 11/30/05, Sidnei da Silva <sidnei@enfoldsystems.com> wrote:
I have some product that would greatly benefit from being able to be configured from within zope.conf. I don't want a separate configuration file. Period.
Tres Seaver and I implemented this during the Goldegg sprint in Fredericksburg, which we provided a location for. This should be in Zope 2.9. I don't know that there's any real documentation for this. Feel free to add some. -Fred -- Fred L. Drake, Jr. <fdrake at gmail.com> "There is no wealth but life." --John Ruskin
On Wed, Nov 30, 2005 at 03:55:22PM -0500, Fred Drake wrote: | On 11/30/05, Sidnei da Silva <sidnei@enfoldsystems.com> wrote: | > I have some product that would greatly benefit from being able to be | > configured from within zope.conf. I don't want a separate | > configuration file. Period. | | Tres Seaver and I implemented this during the Goldegg sprint in | Fredericksburg, which we provided a location for. This should be in | Zope 2.9. | | I don't know that there's any real documentation for this. Feel free | to add some. I haven't seen this being checked in at all, maybe it's in Tres laptop? -- Sidnei da Silva Enfold Systems, LLC. http://enfoldsystems.com
On 11/30/05, Sidnei da Silva <sidnei@enfoldsystems.com> wrote:
I haven't seen this being checked in at all, maybe it's in Tres laptop?
These were committed to the trunk before the 2.9 branch was created: ------------------------------------------------------------------------ r39652 | tseaver | 2005-10-26 15:10:40 -0400 (Wed, 26 Oct 2005) | 1 line Allow custom section types to play in <product-config>. ------------------------------------------------------------------------ r39635 | tseaver | 2005-10-26 12:09:59 -0400 (Wed, 26 Oct 2005) | 7 lines Added a 'product-config' section type to zope.conf, allowing arbitrary key-value mappings. Products can look for such confgiurations to set product-specific options (see the example '<product-config>' section in skel/etc/zope.conf.in for sample usage). -Fred -- Fred L. Drake, Jr. <fdrake at gmail.com> "There is no wealth but life." --John Ruskin
On Wed, Nov 30, 2005 at 04:27:11PM -0500, Fred Drake wrote: | On 11/30/05, Sidnei da Silva <sidnei@enfoldsystems.com> wrote: | > I haven't seen this being checked in at all, maybe it's in Tres | > laptop? | | These were committed to the trunk before the 2.9 branch was created: | | ------------------------------------------------------------------------ | r39652 | tseaver | 2005-10-26 15:10:40 -0400 (Wed, 26 Oct 2005) | 1 line | | Allow custom section types to play in <product-config>. | ------------------------------------------------------------------------ | r39635 | tseaver | 2005-10-26 12:09:59 -0400 (Wed, 26 Oct 2005) | 7 lines | | Added a 'product-config' section type to zope.conf, allowing arbitrary | key-value mappings. | | Products can look for such confgiurations to set product-specific options | (see the example '<product-config>' section in skel/etc/zope.conf.in | for sample usage). Oh, thanks! Missed that one. -- Sidnei da Silva Enfold Systems, LLC. http://enfoldsystems.com
Fred Drake wrote:
I don't know that there's any real documentation for this. Feel free to add some.
In this case, I think zopeschema.xml should be documentation enough, especially as any product author wanting to use this feature is going to have to write a component.xml at least ;-) cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On 12/1/05, Chris Withers <chris@simplistix.co.uk> wrote:
In this case, I think zopeschema.xml should be documentation enough, especially as any product author wanting to use this feature is going to have to write a component.xml at least ;-)
Actually, a product author isn't required to write a component.xml, though they probably should for anything interesting. -Fred -- Fred L. Drake, Jr. <fdrake at gmail.com> "There is no wealth but life." --John Ruskin
participants (3)
-
Chris Withers -
Fred Drake -
Sidnei da Silva