wsgi error

30 views
Skip to first unread message

tango ward

unread,
Jan 26, 2018, 10:06:36 PM1/26/18
to django...@googlegroups.com
Hi Team,

Not sure if this issue covered here but I am getting an error uploading my pet project in Heroku.

ModuleNotFoundError: No module named 'animals.wsgi'
2018-01-27T02:59:26.637953+00:00 app[web.1]: [2018-01-27 02:59:26 +0000] [8] [INFO] Worker exiting (pid: 8)
2018-01-27T02:59:26.669632+00:00 app[web.1]: [2018-01-27 02:59:26 +0000] [4] [INFO] Shutting down: Master
2018-01-27T02:59:26.669770+00:00 app[web.1]: [2018-01-27 02:59:26 +0000] [4] [INFO] Reason: Worker failed to boot.


my Procfile in my root folder contains this:

web: gunicorn animals.wsgi:application --log-file - --log-level debug

where animals is the name of my project, where my wsgi.py file is residing.

I tried searching this in StackOverflow but most of the answers are saying that it must be "web: gunicorn PROJECT_NAME.wsgi:application --log-file - --log-level debug" which I already did in my Procfile.


Any suggestions?



Regards,
Jarvis

Matemática A3K

unread,
Jan 30, 2018, 1:02:18 AM1/30/18
to django...@googlegroups.com
This is more a Heroku question, you should seek help in their docs, forums / communication channels.

AFAIK, a Procfile with "web: gunicorn animals.wsgi" should be enough and work.

HTH!
 


Regards,
Jarvis

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAA6wQLKi4vjKpVByRykvkXoPkpPUBprVq2pvmn-OabzSkAFoyQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

tango ward

unread,
Jan 31, 2018, 10:44:49 AM1/31/18
to django...@googlegroups.com
Hi, thanks for the response. I was able to solved it. Turns out that my should be in the same directory with manage.py.

Reply all
Reply to author
Forward
0 new messages