title: Procfile gunicorn custom module name
body: <p><strong>Context:</strong>
  I am writing a medium sized flask application (10-15 views), and in the process, I am hoping to organize the code in a manner that will make it easily maintainable and extensible (not a monolithic file as most Flask applications are).</p>
  
  <p>The structure of the application mimics the <a href="http://flask.pocoo.org/docs/patterns/packages/" rel="nofollow">documentation</a> as follows:</p>
  
  <pre><code>/AwesomeHackings
      /ENV
      /AwesomeHackings
          /models
          /static
          /templates
          /__init__.py
          /awesome.py
          /awesome.cfg
      /Procfile
      /README.MD
      /requirements.txt
      /run.py
  </code></pre>
  
  <p><strong>Problem:</strong>
  I am unable to get foreman to work with a flask application which is not named 'app'. I would love to have run.py be the entry point to my application.</p>
  
  <p>I am using gunicorn + gevent, and my current Procfile contains:</p>
  
  <pre><code>web: gunicorn -w 2 -b 0.0.0.0:$PORT -k gevent app:run
  </code></pre>
  
  <p>I have been using <code>run.py</code> to test the application:</p>
  
  <pre><code>from AwesomeHackings import awesome
  awesome.app.run(debug=True)
  </code></pre>
  
  <p>Thus I assumed I could simply substitute <code>run</code> for <code>app</code> in the Procfile, but when executing <code>foreman start</code> , gunicorn fails with  meaningless verbiage about modules.</p>