bin\mkzeoinstance.py creates unix instance on windows

[ChrisW]

Not a batch file in sight, just a coupla of shell scripts :-(

[Rodrigo Senra (rsenra)]

Since mkzopeinstance.py generates a nice runzope.bat,
 but mkzeoinstance.py lacks a runzeo.bat,
 I made a little runzeo.bat.in:

<runzeo.bat.in>

@set PYTHON=<<PYTHON>>
@set ZOPE_HOME=<<ZOPE_HOME>>
@set INSTANCE_HOME=<<INSTANCE_HOME>>
@set SOFTWARE_HOME=<<SOFTWARE_HOME>>
@set CONFIG_FILE=<<INSTANCE_HOME>>\etc\zeo.conf
@set PYTHONPATH=%SOFTWARE_HOME%
@set ZEO_RUN=%SOFTWARE_HOME%\ZEO\runzeo.py
"%PYTHON%" "%ZOPE_RUN%" -C "%CONFIG_FILE%" %1 %2 %3 %4 %5 %6 %7

</runzeo.bat.in>

Just dropping that at <<ZOPE_HOME>>\skel\bin
should do the trick, but it seems that mkzeoinstance.py does not use skeletons!
I guess it would be a bit awkward to have runzeo.bat
created by mkzopeinstance.py instead of mkzeoinstance.

I don't know if is there any interest in converting mkzeoinstance.py to use skeletons
(instead of code embeeded templates) ?

Nevertheless, I believe runzeo.bat would be a plus.

regards,
Senra <rsenra at acm.org>

[Colin Watson (cjwatson)]

The zope.mkzeoinstance project on Launchpad has been archived at the request of the Zope developers (see https://answers.launchpad.net/launchpad/+question/683589 and https://answers.launchpad.net/launchpad/+question/685285). If this bug is still relevant, please refile it at https://github.com/zopefoundation/zope.mkzeoinstance.