Databases
StackOverflow2013
Postsdbo
POProcfile declares types -> (none) in Heroku
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POProcfile declares types -> (none) in Heroku
    primarykey
    data
    text
    <p>I'm stuck in running a Django 1.4 app on Heroku via Procfile. I've read all the related posts and I'm sure this is not a case sensitive related issue as I named correctly to Procfile. This is my project structure. Notice Procfile is at the same level that manage.py</p> <pre><code>. ├── README.md ├── docs ├── project │   ├── Procfile │   ├── client │   │   ├── __init__.py │   │   ├── __init__.pyc │   │   ├── models.py │   │   ├── templates │   │   │   └── welcome.html │   │   ├── tests.py │   │   ├── views.py │   │   └── views.pyc │   ├── manage.py │   └── wings │   ├── __init__.py │   ├── __init__.pyc │   ├── settings.py │   ├── settings.pyc │   ├── urls.py │   ├── urls.pyc │   ├── wsgi.py │   └── wsgi.pyc ├── requirements.txt ├── static │   ├── css │   ├── images │   └── js ├── tests └── uploads </code></pre> <p>Here is the Procfile:</p> <pre><code>web:python manage.py runserver </code></pre> <p>Here the output of foreman running it locally (works fine)</p> <pre><code>10:29:28 web.1 | started with pid 595 </code></pre> <p>I'm getting this on the push to heroku:</p> <pre><code>Procfile declares types -&gt; (none) </code></pre> <p>Trying to scale it via heroku toolbelt:</p> <pre><code>$ heroku ps:scale web=1 --app myapp Scaling web processes... failed ! Record not found. </code></pre> <p>I always create my apps via web, so I need always to put the --app argument. Might be any issue related to how I create my apps?</p> <p>I also tried the following:</p> <pre><code>MacBook-Pro-de-Sergio:myapp sergio$ heroku run python project/manage.py runserver Running `python project/manage.py runserver` attached to terminal... up, run.1 Validating models... 0 errors found Django version 1.4, using settings 'wings.settings' Development server is running at http://127.0.0.1:8000/ Quit the server with CONTROL-C. </code></pre> <p>This are the logs of my app:</p> <pre><code>2012-07-18T09:18:51+00:00 heroku[run.1]: Starting process with command `python project/manage.py runserver` 2012-07-18T09:18:51+00:00 heroku[run.1]: State changed from starting to up 2012-07-18T09:19:16+00:00 heroku[router]: Error H14 (No web processes running) -&gt; GET peoplewings.herokuapp.com/ dyno= queue= wait= service= status=503 bytes= 2012-07-18T09:19:16+00:00 heroku[router]: Error H14 (No web processes running) -&gt; GET peoplewings.herokuapp.com/favicon.ico dyno= queue= wait= service= status=503 bytes= </code></pre> <p><strong>Answer</strong></p> <p>As Neil pointed out Procfile should be in the root of git repo. I also had to set the host and port on Procfile as default web server points to 127.0.0.1:8000 which will not work on heroku</p> <pre><code>web: python project/manage.py runserver 0.0.0.0:$PORT </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USsgimeno
    1. USsgimeno
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload