Django - Foreman cannot find installed models

Question

I am trying to use Foreman / Honcho to control my Procfile based Django application. When I run the application in normal python manage.py runserver , everything works fine. However, when I launch the application through honcho start or foreman start web , I get this error:

 11:59:31 system | web.1 started (pid=27959) 11:59:31 web.1 | [2016-04-26 11:59:31 -0700] [27959] [INFO] Starting gunicorn 19.4.5 11:59:31 web.1 | [2016-04-26 11:59:31 -0700] [27959] [INFO] Listening at: http://0.0.0.0:5000 (27959) 11:59:31 web.1 | [2016-04-26 11:59:31 -0700] [27959] [INFO] Using worker: sync 11:59:31 web.1 | [2016-04-26 11:59:31 -0700] [27962] [INFO] Booting worker with pid: 27962 11:59:31 web.1 | [2016-04-26 18:59:31 +0000] [27962] [ERROR] Exception in worker process: 11:59:31 web.1 | Traceback (most recent call last): 11:59:31 web.1 | File "/Library/Python/2.7/site-packages/gunicorn/arbiter.py", line 515, in spawn_worker 11:59:31 web.1 | worker.init_process() 11:59:31 web.1 | File "/Library/Python/2.7/site-packages/gunicorn/workers/base.py", line 122, in init_process 11:59:31 web.1 | self.load_wsgi() 11:59:31 web.1 | File "/Library/Python/2.7/site-packages/gunicorn/workers/base.py", line 130, in load_wsgi 11:59:31 web.1 | self.wsgi = self.app.wsgi() 11:59:31 web.1 | File "/Library/Python/2.7/site-packages/gunicorn/app/base.py", line 67, in wsgi 11:59:31 web.1 | self.callable = self.load() 11:59:31 web.1 | File "/Library/Python/2.7/site-packages/gunicorn/app/wsgiapp.py", line 65, in load 11:59:31 web.1 | return self.load_wsgiapp() 11:59:31 web.1 | File "/Library/Python/2.7/site-packages/gunicorn/app/wsgiapp.py", line 52, in load_wsgiapp 11:59:31 web.1 | return util.import_app(self.app_uri) 11:59:31 web.1 | File "/Library/Python/2.7/site-packages/gunicorn/util.py", line 357, in import_app 11:59:31 web.1 | __import__(module) 11:59:31 web.1 | File "../wsgi.py", line 17, in <module> 11:59:31 web.1 | application = get_wsgi_application() 11:59:31 web.1 | File "/Library/Python/2.7/site-packages/django/core/wsgi.py", line 13, in get_wsgi_application 11:59:31 web.1 | django.setup() 11:59:31 web.1 | File "/Library/Python/2.7/site-packages/django/__init__.py", line 18, in setup 11:59:31 web.1 | apps.populate(settings.INSTALLED_APPS) 11:59:31 web.1 | File "/Library/Python/2.7/site-packages/django/apps/registry.py", line 85, in populate 11:59:31 web.1 | app_config = AppConfig.create(entry) 11:59:31 web.1 | File "/Library/Python/2.7/site-packages/django/apps/config.py", line 90, in create 11:59:31 web.1 | module = import_module(entry) 11:59:31 web.1 | File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/importlib/__init__.py", line 37, in import_module 11:59:31 web.1 | __import__(name) 11:59:31 web.1 | ImportError: No module named django_messages 11:59:31 web.1 | [2016-04-26 18:59:31 +0000] [27962] [INFO] Worker exiting (pid: 27962) 11:59:31 web.1 | [2016-04-26 11:59:31 -0700] [27959] [INFO] Shutting down: Master 11:59:31 web.1 | [2016-04-26 11:59:31 -0700] [27959] [INFO] Reason: Worker failed to boot. 11:59:31 system | web.1 stopped (rc=3) 

This is done with an attempt to install the django-message module. I have the same problems with other modules. I also come across the same issue with django-webpack-loader . I should also mention that I get an error both in virtualenv and when it is deactivated.

Here is the command to install django messages:

 $> pip install django-messages Requirement already satisfied (use --upgrade to upgrade): django-messages in ./lib/python2.7/site-packages 

Installed applications

 INSTALLED_APPS = ( 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.messages', 'django.contrib.staticfiles', 'my_app', 'django_messages', ) 

I'm not sure what other information I can provide to help troubleshoot, but the main question is, how can I install installed applications to work with the / honcho wizard?

Answer 1

Honcho and Foreman do not use the Python executable and libs from your virtualenv, and until you enable your Honcho Procfile, just calling python will use the entire system executable and libs.

Unfortunately, you cannot just call /path/to/virtualenv/bin/activate as part of the Procfile file because Honcho exits when one of the subprocesses exits, as discussed in this Github topic release . However, you can execute this script and your python script in one subshell using the && operator to combine them:

 web: source venv/bin/activate && python manage.py 

Alternatively, you might be lucky to modify your wsgi.py shell to explicitly embed your virtualenv libraries before importing a Django application:

 # Activate your virtual env activate_env=os.path.expanduser("/path/to/virtualenv/bin/activate_this.py") execfile(activate_env, dict(__file__=activate_env)) 

They must be completed before importing any modules (except os ) to ensure that your application reads the correct site libraries.

Finally, Honcho itself supports the use of .env files along with Procfile, which sets up the environment in which processes are running. The format of this file is the same as the bash script format. You can use the .env file to set PYTHONPATH and PYTHONHOME to point to the libraries in your Virtualenv, and then specify the explicit Python interpreter inside Virtualenv from the Procfile file.

.env file

 PYTHONHOME=/path/to/virtualenv/lib/python2.7 PYTHONHOME=