Friday, October 21, 2016

Re: Deploy on Heroku Error

Hi Aline,

I have encountered the problem described by you as well. I am using heroku for about 5 django projects.

For some reason this problem does not exist when you run django server with manage.py command.

Try to read that heroku article. Using `heroku local` command helps fix/run/check locally and after all ok you safely commit and push to heroku.

Hope that helps

Regards,
Constantine C.

On Fri, Oct 21, 2016 at 8:39 AM, Antonis Christofides <antonis@djangodeployment.com> wrote:

Hello,


that repo only contains the blog app. Could you show us the polls app?

Regards,

Antonis Christofides  http://djangodeployment.com    
On 2016-10-20 22:49, Aline C. R. Souza wrote:
Hello everybody,

I am catching an error on trying to deploy my app on heroku. This is the traceback:

  File "/app/.heroku/python/lib/python3.5/site-packages/polls/admin.py", line 3, in <module>
2016-10-20T18:42:46.734824+00:00 app[web.1]:   File "/app/.heroku/python/lib/python3.5/importlib/__init__.py", line 126, in import_module
2016-10-20T18:42:46.734830+00:00 app[web.1]: ImportError: No module named 'models'
2016-10-20T18:42:46.735201+00:00 app[web.1]: [2016-10-20 18:42:46 +0000] [7] [INFO] Worker exiting (pid: 7)
2016-10-20T18:42:46.734826+00:00 app[web.1]:     from models import Poll, Choice, Vote
2016-10-20T18:42:46.736625+00:00 app[web.1]: [2016-10-20 18:42:46 +0000] [8] [ERROR] Exception in worker process

The app runs normally on localhost.

That is what I tried to do: I went to my virtualenv directory at site-packages/polls/ and changed all the imports to polls.models instead of .models. Then, I cleaned the cache of the polls app and the cache of the blog app (blog app uses polls app). Built my app again and ran it locally. The app looks fine. So, I tried to push to heroku and run the app, but the same error occurs.

Any thoughts?

--
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-users@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/8704854e-48ab-460e-8ff1-cedc427cb037%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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-users@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/cdd71b29-ab8f-3736-71b3-ded998a6b82c%40djangodeployment.com.

For more options, visit https://groups.google.com/d/optout.

--
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-users@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/CAK52boVpRZ2o_7b9mLcsA31aMSJmRySN6%3D0FM8uDSsjd3eHw8g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment