[Zope-Checkins] Re: CVS: Zope/skel/bin - runzope.in:1.1.2.1 zopectl.in:1.1.2.1

[R. David Murray]

On Thu, 6 Feb 2003, Fred L. Drake, Jr. wrote:
> The per-instance zopectl is just a wrapper around a shared script that
> will live in the software installation (ZOPE_HOME/bin/), and makes
> sure that the right paths are set up.  It does not preclude using the
> general (not instance-specific) zopectl.py script directly, and
> passing the right args along to specify the instance.

I guess I'm wondering why there would be any more args than just
the path to the instance home or instance config file.  In
other words, why isn't that zopectl.in a one-liner?

(apropos zopectl start all)
> Interesting idea; we'll have to think about that.  How do you handle
> the mapping?

Via a config file, of course <grin>.  The master config has a line
that defines 'all' to be a list of instance homes. It also provides
default settings that individual instance home configs can override.
Most of my instance home configs are thus two or three lines at
most.  The name all is actually arbitrary, so you could just as
well define 'production' to be the list of production sites.  In my
script there is one and only one directory that contains instance
home directories, which is something I'd change if I rewrote it.
But it does allow me to just list the instances by name instead of path.

> All the information needed to describe an instance will be in the
> config file, INSTANCE_HOME/etc/zope.conf.  The
> INSTANCE_HOME/bin/zopectl script is simply a convenience to let an SA
> avoid a bit of typing in the simple case.

For me, having the master script in my PATH and telling it the name
or path of the instace is (slightly) less typing than calling the
instance's bin script.  If that works, and if instance zope.conf
files hold overrides of a higher level config, then I'll be happy.

--RDM