Re: [PyWrapper-devel] Running PyWrapper on Windows with Apache

[Gideon G. <gg...@et...>]

Hi Ricardo,

I would like to test it when you get there.
It would be good to include this in the maual then. It was very =20
dissatisfying that I could not get it to work.
Contact me if you need more detailed information.

Gideon


On Nov 14, 2007, at 2:54 PM, Ricardo Scachetti Pereira wrote:

>    Thanks Gideon and Markus for your input.
>
>    I think that to make PyWrapper more robust and easier to install =20=

> on Windows (part of my goals for 2008) I'll definitely have to work =20=

> on this specific task. I'll keep all that you said in mind when I =20
> start working on PyWrapper early next year.
>
>    Cheers,
>
> Ricardo
>
>
> D=F6ring, Markus wrote:
>> Ricardo,
>> It might be best to evaluate if we cant move to mod_python/apache =20
>> as the
>> recommended installation (apart from standalone which is really =20
>> useful for
>> testing and quick setups). I havent followed the CherryPy =20
>> developments, but
>> there must have been some changes happening there. As PyWrapper is =20=

>> based on
>> CherryPy thats the first source we should investigate:
>>
>> http://www.cherrypy.org/
>>
>> I agree it's the most disturbing part in setting up pywrapper, =20
>> especially on
>> windows. Now that fastcgi doesnt seem to be supported anymore, I'd =20=

>> prefer to
>> ignore IIS and require apache on windows. If that works painlessly =20=

>> I think
>> we are fine.
>>
>> Markus
>>
>>
>>
>> "Gideon Gijswijt" wrote on 13.11.2007 12:26 Uhr:
>>
>>
>>> Hi Ricardo,
>>>
>>> According to Markus, the fastGCI option is the only option with
>>> sufficient performance, so we went on with this option.
>>>
>>> I tried to get it working under Apache 1.3, 2.0 and 2.2 on =20
>>> Windows XP
>>> and on Server 2003.
>>> I also tried FastCGI but also FCGI, since FastCGI does not work with
>>> Apache 2.2 anymore.
>>> After trying for 5 days, I had to give up because of the deadline.
>>>
>>> It may be possible that with some rewriting of the wrapper =20
>>> itself, it
>>> is possible to use the FCGI, but we lacked the time to work this =20
>>> out.
>>> This is why we could only suggest the stand-alone option for =20
>>> Windows.
>>>
>>> Cheers,
>>>
>>> Gideon
>>>
>>> On Nov 12, 2007, at 12:09 PM, Ricardo Scachetti Pereira wrote:
>>>
>>>
>>>>    Hi guys,
>>>>
>>>>    I've been running PyWrapper on Windows for sometime now using
>>>> standalone CherryPy web app server.
>>>>
>>>>    Now I tried to run PyWrapper using Apache 2.0 on Windows without
>>>> success and I was wondering whether you could help me with that.
>>>>
>>>>    First, I tried to run PyWrapper with mod_python and
>>>> modpython_gateway without success. I realized that there was a
>>>> script modpython_gateway.py on the webapp directory (that is needed
>>>> to run PyWrapper with mod_python) but that file was later deleted.
>>>> My reading is that you guys gave up on that combination of
>>>> mod_python and modpython_gateway. Is that right?
>>>>
>>>>    Then I tried FastCGI, without success either. I've used the
>>>> sample Apache configuration for FastCGI but couldn't get PyWrapper
>>>> to work.
>>>>
>>>>    I've noticed that the documentation on PyWrapper 3.1 from ETI
>>>> says PyWrapper doesn't run on Windows/Apache nor explains how to
>>>> set it up. If that's the case, is there any specific reasons why
>>>> you give up on it?
>>>>
>>>>    In any case, do you guys have any hints for me on how to run
>>>> PyWrapper on Windows with Apache, or hints on how to make PyWrapper
>>>> run on that platform again?
>>>>
>>>>    Cheers,
>>>>
>>>> Ricardo
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>
>>
>>
>
>