[Zope] Deployment Best Practices?

[Jeff McNeil]

That's not all that obvious to someone new to the Zope system.  Most
of the documentation I've found is geared towards the 2.x branch.  As
Zope 3 and Zope 2 are different animals, I wouldn't think that the
deployment steps and recommendations would be all that similar.

I really like what I've seen thus far, it's just been difficult at
times as it feels like I'm fighting with documentation.

So I'm assuming I'll just need to build up a Zeo server instance with
zc.zodbrecipes and update my corresponding buildout.cfg for the Zope
instances? If Buildout is the preferred deployment tool, then my
redistributable is a sandbox tarball or an RPM containing the skeleton
files needed to bootstrap a buildout run on the target hosts? Maybe
I'll dump the whole process on a blog somewhere as I step through it.

I do have another question. The project we're working on is plug-in
based. Within the old system, eggs are loaded dynamically using
setuptools pkg_resources and we define certain entry points for
capability registration.  Eggs are added to a directory and a config
entry is made such that we can load the proper version of each
plug-in.  Is there an upfront way to reproduce that functionality
without needing to update setup.py and rerun buildout every time we
want to push a new plug-in or update an existing?  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.

My apologies if some of this is obvious. As I said, I'm really just
tackling Zope for the first time.

Jeff


On Fri, Jul 11, 2008 at 11:01 AM, Andreas Jung <lists at zopyx.com> wrote:
>
>
> --On 11. Juli 2008 10:57:17 -0400 Jeff McNeil <jeff at jmcneil.net> wrote:
>
>> I'm in the process of attempting to migrate a fairly large scale
>> internal XMLRPC system over to Zope. The current system is all custom.
>> That provides for a lot of internal code that we really don't need to
>> be managing.
>>
>> I'm looking for best practices and approaches to deploying Zope 3
>> instances and a backend ZEO server to share the data.  I don't think
>> I've seen it covered anywhere. I've seen it documented from the Zope 2
>> perspective (both old school and via buildout recipes). It seems this
>> would be a fairly common configuration.
>
> I don't see how this would be different in the Zope 3 world.
> Buildout is the way to go. Depart from that your question is pretty
> generic.
>
> -aj