Your server log said this (loading my.wsgi)
Exception occurred processing WSGI script
'/code/projects/my_web/wsgi/my.wsgi'.
But your structure said that wsgi file is called different (idrac.wsgi).
Other thing, call core your app is not a good idea, do it if you understand
well how python import
On Tue, Apr 28, 2015 at 9:40 PM, dk wrote:
> I check the apache httpd log and do get this
>
> [Tue Apr 28 10:33:49.982311 2015] [:error] [pid 18060] [client
> 10.35.0.91:61408] from django.apps import apps
> [Tue Apr 28 10:33:49.982336 2015] [:error] [pid 18060] [client
> 10.35.0.91:61408] I
I check the apache httpd log and do get this
[Tue Apr 28 10:33:49.982311 2015] [:error] [pid 18060] [client
10.35.0.91:61408] from django.apps import apps
[Tue Apr 28 10:33:49.982336 2015] [:error] [pid 18060] [client
10.35.0.91:61408] ImportError: No module named apps
[Tue Apr 28 10:33:5
my folder structure is like this
├── my_web
│ ├── core (i rename this so i know where all the original django files
are)
│ │ ├── __init__.py
│ │ ├── settings.py
│ │ ├── urls.py
│ │ ├── urls.pyc
│ │ ├── wsgi.py
│ ├── db.sqlite3
│ ├── __init__.py
│ ├── manage.py
│ ├──
I check the apache httpd log and do get this
[Tue Apr 28 10:33:49.982311 2015] [:error] [pid 18060] [client
10.35.0.91:61408] from django.apps import apps
[Tue Apr 28 10:33:49.982336 2015] [:error] [pid 18060] [client
10.35.0.91:61408] ImportError: No module named apps
[Tue Apr 28 10:33:5
This looks fine. Are there any errors in the web server logs?
Regards,
Abhaya
On Mon, Apr 27, 2015 at 10:23 PM, dk wrote:
> we decided to test django 1.8, using python manage.py runserver works
> great. but now the production wsgi stop working,
> I remember there was a change between version
we decided to test django 1.8, using python manage.py runserver works
great. but now the production wsgi stop working,
I remember there was a change between version 1.6 and 1.7.
this is my code. Did it something change?
import os
import sys
sys.path.append("/code/projects/my_web")
sys.path
7 matches
Mail list logo