1021471 - switch Procfile to gunicorn for collector, middleware and django

Status: RESOLVED FIXED

(Socorro :: General, task)

Description

[Robert Helmer [:rhelmer]]

Switching to uwsgi will allow our Procfile to work in Heroku and foreman, as well as with honcho (which is the Python clone of foreman that our install docs recommend for dev installs)

This means the default web server in the config should be WSGI not CherryPy, and we'll need to change our .wsgi files to be .py files instead and we'll need __init__.py in our wsgi/ dirs, because uwsgi wants to import them with Python not as files.

I think this will simplify the lives of people going from dev to production Apache/Nginx/etc. installs, as well as anyone who wants to run on Heroku or similar.

One downside is that "honcho start" won't be running the Django dev server, so it won't automatically restart when files change etc. You can still run "./manage.py runserver" though so in practice I don't think it'll hurt much.

Comment 1

[Robert Helmer [:rhelmer]]

Oops I meant to say "gunicorn" not "wsgi"... this is what Heroku recommends and what  I use for testing.

Comment 2

[[github robot]]

Commits pushed to master at https://github.com/mozilla/socorro

https://github.com/mozilla/socorro/commit/bdc402ca6269358e96fd681b154ca74dcf54aa83
fix bug 1021471 - switch Procfile to gunicorn

https://github.com/mozilla/socorro/commit/4fbfb98f02214fedb9ba3f199db1e7f0d0e85caf
Merge pull request #2126 from rhelmer/bug1021471-switch-procfile-to-gunicorn

fix bug 1021471 - switch Procfile to gunicorn