Thank you all for your responses!
- Gustavo.
On 15/03/10 17:02, Nathan Yergler wrote:
> We've migrated a couple applications from mod_wsgi to mod_fcgid
> (http://httpd.apache.org/mod_fcgid/) without any problems, and it's
> now our default deployment strategy.
>
> Regards,
>
> Nathan
>
>
> On Mo
Le 15/03/2010 16:02, Benoit Chesneau a écrit :
> On Mon, Mar 15, 2010 at 3:12 PM, Gustavo Narea wrote:
> why not just use a gateway behind a proxy ?
That could be what i would have done too.
> - benoit
--
Cordialement,
KiOrKY
GPG Key FingerPrint: 0x1A1194B7681112AF
signature.asc
Descripti
We've migrated a couple applications from mod_wsgi to mod_fcgid
(http://httpd.apache.org/mod_fcgid/) without any problems, and it's
now our default deployment strategy.
Regards,
Nathan
On Mon, Mar 15, 2010 at 9:54 AM, Gustavo Narea wrote:
> On Mon, Mar 15, 2010 at 2:47 PM, Manlio Perillo
> wr
On Mon, Mar 15, 2010 at 2:47 PM, Manlio Perillo wrote:
> Note that you can simply recompile mod_wsgi to use your custom Python.
>
We may need to use different versions of Python. :/
___
Web-SIG mailing list
Web-SIG@python.org
Web SIG: http://www.python.
On Mon, Mar 15, 2010 at 3:12 PM, Gustavo Narea wrote:
> Hello,
>
> We're considering migrating from mod_wsgi to FastCGI (Apache) because we'll
> need to use versions of Python compiled by ourselves.
>
> In addition to the research I've done and the pre-deployment tests we'll
> carry out, I'd love
Gustavo Narea ha scritto:
> Hello,
>
> We're considering migrating from mod_wsgi to FastCGI (Apache) because
> we'll need to use versions of Python compiled by ourselves.
>
Note that you can simply recompile mod_wsgi to use your custom Python.
> [...]
Manlio
__
