Roger Ineichen wrote:
We also have to define how Zope3 get installed on a windows
machine. I don't like the normal installation where is
located in the
python installation root right now.
Is that where it ends up on Linux? If so, then we should
respect that...
That's not a normal patte
Hi Chris
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Chris Withers
> Sent: Monday, October 17, 2005 10:09 AM
> To: [EMAIL PROTECTED]
> Cc: zope3-dev@zope.org; 'Tim Peters'
> Subject: Re: [Zope3-dev]
Hi Roger,
Roger Ineichen wrote:
The main question is, what's the base "source" for build the Zope3
application server. I guess this will be generated by zpkgtools
in some way.
If I understand zpkgtools correct, we can use it for checkout the
source.
Right.
The step after the checkout isn't
Hi Chris
> -Original Message-
> From: Chris Withers [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 14, 2005 11:46 AM
> To: [EMAIL PROTECTED]
> Cc: 'Mats Nordgren'; zope3-dev@zope.org
> Subject: Re: [Zope3-dev] Zope 3.1
>
> Roger Ineichen wrote:
&g
Roger Ineichen wrote:
The Zope 3 application server is stable and ready for procuction.
But the Zope3 windows installer isn't.
We really have to improve the installation process and offer
also a built in service manager where you can start and stop
the server in the future. Also the missing pro
Hi
[...]
> Bolotov,
>
> Zope 3.1 is definitely ready for production use.
> Zope-3.1.0-win32-py2.4.exe
> is a Windows executable. Just double click and install.
>
> When you have installed the Zope you need to go to
> c:\Python24\Scripts and
> run the mkzopeinstance.bat. Specify an install
Bolotov,
Zope 3.1 is definitely ready for production use. Zope-3.1.0-win32-py2.4.exe
is a Windows executable. Just double click and install.
When you have installed the Zope you need to go to c:\Python24\Scripts and
run the mkzopeinstance.bat. Specify an install path to your zope instance,
use