Re: How to handle apps independently in a Wsgi/Apache deployment

Assuming I understood your question, here's a wild guess.

Use different settings files and set the DJANGO_SETTINGS_MODULE on the
fly on your .wsgi script

Cheers,
AT

On 10/25/11, vpetkov <petkov.venelin@gmail.com> wrote:
> Hi,
>
> I have the standard Wsgi/Apache deployment with several apps in a
> single project, admin enabled. I would like to keep the apps
> independent in production, so that a possible error in one does not
> bring down the whole wsgi daemon process and leave the other apps
> inaccessible.
>
> What I found is that after a fresh wsgi start, Django tries to
> import models.py from all registered apps in settings.INSTALLED_APPS,
> which breaks their independence. Moreover the autodiscover function of
> admin in the main urls.py also tries to import admin.py of all
> installed apps.
>
> Is there any possible way to configure Django to import all relevant
> files to an app on demand, so that a possible error in models.py or
> admin.py does not influence the others?
>
>
> Thanks,
> Venelin
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>

--
Sent from my mobile device

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.