On May 27, 4:54 pm, Ben Welsh wrote:
> The nabble link I provided has a lot of that stuff. The answers are prefork,
> mod_python and the following. If you would recommend a switch to mod_wsgi,
> could you please recommend the best guides for how and why? I'm always
>
Also, sorry to have missed the Q, I'm serving media from a separate machine.
On Tue, May 26, 2009 at 11:54 PM, Ben Welsh wrote:
> The nabble link I provided has a lot of that stuff. The answers are
> prefork, mod_python and the following. If you would recommend a switch to
The nabble link I provided has a lot of that stuff. The answers are prefork,
mod_python and the following. If you would recommend a switch to mod_wsgi,
could you please recommend the best guides for how and why? I'm always
interested in reading more on this topic that I can educate myself on the
On May 27, 4:17 pm, Ben Welsh wrote:
> Thanks for your advice. It's much appreciated.
>
> I've been encountering "too many file open" errors through Apache. I have a
> thread open on httpd-users discussing the topic.
>
>
Thanks for your advice. It's much appreciated.
I've been encountering "too many file open" errors through Apache. I have a
thread open on httpd-users discussing the topic.
http://www.nabble.com/-users%40httpd--What-is-the-best-way-to-handle-%22too-many-open-files%22-errors--td23629492.html
To
On May 27, 2:33 pm, Ben Welsh wrote:
> Thanks, Graham. So the conclusion is that zero Apache modules should be
> necessary.
>
> I suspect that after reading the docs before posting, but mainly I wanted to
> confirm that here. And I suppose I should have just been more
Thanks, Graham. So the conclusion is that zero Apache modules should be
necessary.
I suspect that after reading the docs before posting, but mainly I wanted to
confirm that here. And I suppose I should have just been more clear about
that from the start.
So, my working conclusion from reading
On May 26, 5:20 am, Ben Welsh wrote:
> Sorry to have been too brief.
>
> My objective is to rely as completely as possible on the Django
> authentication methods. The only auth I need is
>
> 1) admin login for CMS managment
> 2) staff_member_required protections for
Sorry to have been too brief.
My objective is to rely as completely as possible on the Django
authentication methods. The only auth I need is
1) admin login for CMS managment
2) staff_member_required protections for certain pages (for example content
preview pages that link out of the admin)
AFAIK there are thousands of ways to combine Apache+Django for
authentication.
Just to name a few:
* no apache, just django: you can define custom authentication methods
(or even Basic Auth) with django. See the docs [1]
* apache handles authentication using django as the backend. See the
docs
On 23 May 2009, at 11:57 , Graham Dumpleton wrote:
> On May 23, 5:59 am, palewire wrote:
>> The default httpd.conf loaded on my CentOS server contains the
>> following authentication modules.
>>
>> LoadModule auth_basic_module modules/mod_auth_basic.so
>> LoadModule
On May 23, 5:59 am, palewire wrote:
> The default httpd.conf loaded on my CentOS server contains the
> following authentication modules.
>
> LoadModule auth_basic_module modules/mod_auth_basic.so
> LoadModule auth_digest_module modules/mod_auth_digest.so
> LoadModule
The default httpd.conf loaded on my CentOS server contains the
following authentication modules.
LoadModule auth_basic_module modules/mod_auth_basic.so
LoadModule auth_digest_module modules/mod_auth_digest.so
LoadModule authn_file_module modules/mod_authn_file.so
LoadModule authn_alias_module
13 matches
Mail list logo