I think I'll add a new directive to register my application specific
plugins. That way, I can rely on my own entry points and whatnot.
That gives me a nice way to not have to rerun buildout (rather, not
have to rely on the operations department to rerun buildout).
I'm planning on running through and setting up an HA installation
using zc.zodbrecipe as long as that's a "standard" way of doing it.
I'll throw it up on my blog; if I get it wrong, someone can correct
Thanks for all of the help. It would be nice to have standard and
somewhat generic installation guides. Nothing too in-depth, just
something to get us Zope newbies pointed in the right direction.
On Sun, Jul 13, 2008 at 1:47 PM, Philipp von Weitershausen
<[EMAIL PROTECTED]> wrote:
> Paul Winkler wrote:
>> On Sun, Jul 13, 2008 at 01:20:53PM -0400, Philipp von Weitershausen wrote:
>>> Jeff McNeil wrote:
>>>> I'd love to be able to just drop an egg on the file system and tell
>>>> Zope "Here, go load that one now" via configuration alone.
>>> You could also write your own ZCML directive (+ a handler) that does
>>> that. Then you'd only ever have to change your application's site.zcml to
>>> load a new plugin.
>> There's also this:
> Yep, that only saves you the
> <include package="..." />
> directive, though.
> Zope maillist - Zope@zope.org
> ** No cross posts or HTML encoding! **
> (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce
> http://mail.zope.org/mailman/listinfo/zope-dev )
Zope maillist - Zope@zope.org
** No cross posts or HTML encoding! **
(Related lists -