On 20-Sep-07, at 9:01 AM, Graham Dumpleton wrote:
>> one caveat here - if you are running a site on shared hosting with
>> soft RAM limit - like the 40 MB webfaction account, then it is wise
>> to bypass mod_python for media to avoid those nasty monday morning
>> mails about exceeding your
On Sep 20, 12:52 pm, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
> On 20-Sep-07, at 8:09 AM, Graham Dumpleton wrote:
>
> > All those warnings about using the same Apache to serve static
> > documents as Django are generally totally meaningless to the average
> > user. This is because the load on
On 20-Sep-07, at 8:09 AM, Graham Dumpleton wrote:
> All those warnings about using the same Apache to serve static
> documents as Django are generally totally meaningless to the average
> user. This is because the load on an average Apache site is no where
> near enough for it to be of concern.
On Sep 20, 10:28 am, Steve Potter <[EMAIL PROTECTED]> wrote:
> > Django can be run fine under Apache 1.3 using mod_wsgi.
>
> > The only issue is whether they do really allow you to add additional
> > Apache modules to the installation.
>
> > Graham
>
> This is interesting... It is possible to
On Sep 20, 12:16 pm, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
> On 20-Sep-07, at 12:23 AM, Steve Potter wrote:
>
> > I'm already quite sure I don't want to install mod_python on the
> > existing Apache after reading all of the warnings about using the same
> > Apache to serve static documents
On 20-Sep-07, at 12:23 AM, Steve Potter wrote:
> I'm already quite sure I don't want to install mod_python on the
> existing Apache after reading all of the warnings about using the same
> Apache to serve static documents and Django.
I am not sure exactly what you mean by this. mod_python is
>
> Django can be run fine under Apache 1.3 using mod_wsgi.
>
> The only issue is whether they do really allow you to add additional
> Apache modules to the installation.
>
> Graham
This is interesting... It is possible to install additional modules
with cpanel, it just makes updating for new
>
> 5. Use a different server.
>
> Unless you are on what cPanel calls the bleeding edge, you're running
> Apache 1.3 which is useless for serving Django. That leaves you with
> either #3 or #4. #3 has issues because cPanel wants to bind Apache to
> all IP addresses. I had issues (though I
On Sep 20, 8:03 am, "Peter Baumgartner" <[EMAIL PROTECTED]> wrote:
> On 9/19/07, Steve Potter <[EMAIL PROTECTED]> wrote:
>
> > I currently have a dedicated server running a Cpanel installation with
> > several virtual hosts. I would like to install Django on this server
> > and as far as I can
On 9/19/07, Steve Potter <[EMAIL PROTECTED]> wrote:
>
> I currently have a dedicated server running a Cpanel installation with
> several virtual hosts. I would like to install Django on this server
> and as far as I can tell, I have several options.
>
> 1. Add mod_python to existing Apache
I currently have a dedicated server running a Cpanel installation with
several virtual hosts. I would like to install Django on this server
and as far as I can tell, I have several options.
1. Add mod_python to existing Apache installation
2. Add FastCGI to existing Apache installation
3.
11 matches
Mail list logo
