在Heroku的

我試圖部署我在Heroku上的應用程序，運行Django的無網工藝，但是當我終於嘗試在Heroku上運行我的應用我惱火的瀏覽器這樣的：在Heroku的

Application Error 
An error occurred in the application and your page could not be served. Please try again in a few moments. 

If you are the application owner, check your logs for details.

當我看到我的日誌我得到下一個：

2013-08-31T19:53:30.672416+00:00 heroku[api]: Enable Logplex by [email protected] 
2013-08-31T19:53:30.700218+00:00 heroku[api]: Release v2 created by [email protected] 
2013-08-31T19:58:41+00:00 heroku[slug-compiler]: Slug compilation started 
2013-08-31T20:04:12.967456+00:00 heroku[router]: at=info code= desc="Blank app" method=GET path=/ host=cristowip.herokuapp.com fwd="189.137.81.39" dyno= connect= service= status=502 bytes= 
2013-08-31T20:04:13.161016+00:00 heroku[router]: at=info code= desc="Blank app" method=GET path=/favicon.ico host=cristowip.herokuapp.com fwd="189.137.81.39" dyno= connect= service= status=502 bytes= 
2013-08-31T20:13:46+00:00 heroku[slug-compiler]: Slug compilation timed out: 904.285527871 seconds. 
2013-08-31T20:22:52.646361+00:00 heroku[router]: at=info code= desc="Blank app" method=GET path=/ host=cristowip.herokuapp.com fwd="189.137.81.39" dyno= connect= service= status=502 bytes= 
2013-08-31T20:22:55.043424+00:00 heroku[router]: at=info code= desc="Blank app" method=GET path=/favicon.ico host=cristowip.herokuapp.com fwd="189.137.81.39" dyno= connect= service= status=502 bytes= 
2013-08-31T20:26:14+00:00 heroku[slug-compiler]: Slug compilation started 
2013-08-31T20:38:41+00:00 heroku[slug-compiler]: Slug compilation started 
2013-08-31T20:41:22+00:00 heroku[slug-compiler]: Slug compilation timed out: 908.241350492 seconds. 
2013-08-31T20:49:24.238496+00:00 heroku[router]: at=info code= desc="Blank app" method=GET path=/ host=cristowip.herokuapp.com fwd="189.137.81.39" dyno= connect= service= status=502 bytes= 
2013-08-31T20:49:24.644910+00:00 heroku[router]: at=info code= desc="Blank app" method=GET path=/favicon.ico host=cristowip.herokuapp.com fwd="189.137.81.39" dyno= connect= service= status=502 bytes= 
2013-08-31T20:53:47+00:00 heroku[slug-compiler]: Slug compilation timed out: 907.148099965 seconds. 
2013-08-31T20:56:59+00:00 heroku[slug-compiler]: Slug compilation started 
2013-08-31T20:58:50.641624+00:00 heroku[api]: Attach HEROKU_POSTGRESQL_AQUA resource by [email protected] 
2013-08-31T20:58:50.658435+00:00 heroku[api]: Release v3 created by [email protected] 
2013-08-31T20:58:50.742803+00:00 heroku[api]: Add DATABASE_URL config by [email protected] 
2013-08-31T20:58:50.782484+00:00 heroku[api]: Release v4 created by [email protected] 
2013-08-31T20:58:50.840509+00:00 heroku[api]: Deploy 78dba6c by [email protected] 
2013-08-31T20:58:50.852187+00:00 heroku[api]: Release v5 created by [email protected] 
2013-08-31T20:58:54+00:00 heroku[slug-compiler]: Slug compilation finished 
2013-08-31T21:00:25.085053+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path=/favicon.ico host=cristowip.herokuapp.com fwd="189.137.81.39" dyno= connect= service= status=503 bytes= 
2013-08-31T21:00:24.751074+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path=/ host=cristowip.herokuapp.com fwd="189.137.81.39" dyno= connect= service= status=503 bytes= 
2013-08-31T21:01:03.272614+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path=/ host=cristowip.herokuapp.com fwd="189.137.81.39" dyno= connect= service= status=503 bytes= 
2013-08-31T21:01:03.815558+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path=/favicon.ico host=cristowip.herokuapp.com fwd="189.137.81.39" dyno= connect= service= status=503 bytes= 
2013-08-31T21:02:10.279054+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path=/ host=cristowip.herokuapp.com fwd="189.137.81.39" dyno= connect= service= status=503 bytes= 
2013-08-31T21:03:25.381362+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path=/ host=cristowip.herokuapp.com fwd="189.137.81.39" dyno= connect= service= status=503 bytes= 
2013-08-31T21:03:25.709121+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path=/favicon.ico host=cristowip.herokuapp.com fwd="189.137.81.39" dyno= connect= service= status=503 bytes= 
2013-08-31T21:03:45.285962+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path=/favicon.ico host=cristowip.herokuapp.com fwd="189.137.81.39" dyno= connect= service= status=503 bytes= 
[email protected]:~/Documentos/heroku/portafolio/venv$

來源

2013-08-31 Cris Towi

在Heroku上部署[錯誤H14（沒有web進程運行）]的可能重複（http://stackoverflow.com/questions/11405826/error-h14-no-web-processes-running-deploy-on-heroku ） –

你有沒有通過Heroku guide for setting up a Django application？你的Procfile是什麼樣的？

您的項目應該有一個名爲Procfile文件應該有類似的內容

web: gunicorn hellodjango.wsgi

來源

2013-08-31 21:27:23

本傑明·曼斯解決方案爲我，但我需要一個額外的步驟，以及。

據this，該Procfile解決方案已被推後，運行以下命令：

heroku ps:scale web=1

網站現在應該正確加載。

更多的幫助推到Heroku的git倉庫，看到this

來源

2014-03-30 17:04:49 ecoe

當說明要運行的文件時，確保它相對於Procfile。例如：如果你想在根目錄下運行「manage.py」，procfile條目應該是web：python manage.py runserver 0.0.0.0:$PORT – astroanu

如果你錯誤地推送了一個沒有Procfile的分支，它會關閉所有的dynos。一旦使用Procfile推送分支，運行上面的命令重新啓動。 – hgolov

你是我的英雄。 – wogsland

添加proc文件並運行以下命令

$ heroku ps:scale web=1

來源

2014-12-01 05:58:25

同時訪問[link]（https://devcenter.heroku.com/articles/getting-started-with-django）獲取完整教程 –

你Procfile必須看起來像這樣（爲Python）：

web：python myApp.py runserver 0.0.0.0:$PORT

來源

2017-10-10 18:42:43

回答

相關問題