[Zope-Coders] ZEO install/runtime issues

Richard Jones richard@commonground.com.au
Fri, 4 Apr 2003 11:20:40 +1000


On Friday, April 4, 2003, at 01:13 AM, Chris McDonough wrote:
> One strategy would be to sed out a small shell script like the 
> "zopectl"
> shell script (which is written to an instance_home's "bin" during
> install") which itself sets the PYTHONPATH and calls zdctl.

OK, ro recap the various mkfoo and make install things, there'd be:

. "make install" installs "bin" scripts for mkzeo[server|client], 
mkzopeinstance
   and zconfig but _not_ runzope.py or zopectl.py - they're useless in 
their
   current form.
. mkzopeinstance would install zopectl and runzope as it currently does
. mkzeoserver would install zeoctl and runzeo which would look a lot 
like
   the zope instance scripts
. mkzeoclient would do what mkzopeinstance does, but also install the
   custom_zodb.py

I'll try to get zconfig, runzeo and mkzeoclient going today.

On the runzope.py or zopectl.py note, perhaps INSTANCE_HOME-agnostic 
versions of zopectl and runzope currently installed by mkzopeinstance 
could be installed. Not sure how that'd work - some prompt or 
command-line handling to determine the INSTANCE_HOME? I don't 
particularly care about getting this going for 2.7


     Richard