procfile | 易学教程

Local or Private NPM module when deploying to Heroku

阅读更多关于 Local or Private NPM module when deploying to Heroku

问题 I have a node app that has a local npm module npm link ./local and I'm trying to deploy the app to heroku. Heroku runs npm install when I deploy, but npm link 's aren't saved in package.json so my local module is missing. I'm new to heroku and Procfiles , I'd like to run a script or just run npm link ./local before on the heroku box. Alternatively I could put the module on github as a private repository and link it from there. But as far as I know Heroku isn't able to download private repo.

Heroku No such process type web defined in procfile

阅读更多关于 Heroku No such process type web defined in procfile

问题 When i'm runing heroku ps:scale web=1 , I'm getting below error. Scaling dynos... failed No such process type web defined in Procfile. My Procfile contains below code. worker: python vot.py I also did heroku run bash and the Procfile is there and file name is also correct. How could i solve this ? 回答1: Your heroku command has "web=1" but your Procfile has "worker". Try: heroku ps:scale worker=1 回答2: I dont see you define single process type "web" in your procfile. Follow on this heroku

Getting error while running command heroku ps:scale worker=1 error

阅读更多关于 Getting error while running command heroku ps:scale worker=1 error

问题 I tried a lot but not able to find the reason for this. Need help. Following is what I am writing after deploying my first node app in Heroku and my DB is at MongoLab heroku ps:scale worker=1 It is giving me following error. ! No such type as worker. My Procfile look like this, web: node server/server.js Here is my log file look like 2013-04-20T21:12:31.474207+00:00 app[worker.1]: at startup (node.js:119:16) 2013-04-20T21:12:31.474207+00:00 app[worker.1]: at node.js:901:3 2013-04-20T21:12:32

Symfony deployment on heroku points to app folder

阅读更多关于 Symfony deployment on heroku points to app folder

问题 I am trying to deploy the symfony app on heroku and I am able to update the schema and all perfectly fine however when i try to access the site I get Forbidden You don't have permission to access / on this server. So using the command heroku logs --num 10 i can see the error Cannot serve directory /app/web/: No matching DirectoryIndex (index.php,index.html,index.htm) found, and server-generated directory index forbidden by Options directive As you can see heroku is trying to access /app/web/

Error: Cannot find module 'webpack' when deploying to heroku

阅读更多关于 Error: Cannot find module 'webpack' when deploying to heroku

问题 Judging from other topics (none which helped me), this seems to be a reoccurring issue, I am trying to deploy my app to heroku. It works fine with heroku local web , I have deployed the app and git heroku push to the master but as soon as I run heroku open , nothing loads and I get the following error: Application error An error occurred in the application and your page could not be served. If you are the application owner, check your logs for details. I checked my logs and it says: Error:

gunicorn on heroku: binding to localhost

阅读更多关于 gunicorn on heroku: binding to localhost

问题 I've been following the tutorial on https://devcenter.heroku.com/articles/django#declare-process-types-with-procfile. It went smoothly except for one thing that bothers me. After starting foreman I should see the following: $ foreman start 2013-04-03 16:11:22 [8469] [INFO] Starting gunicorn 0.17.2 2013-04-03 16:11:22 [8469] [INFO] Listening at: http://127.0.0.1:8000 (8469) However, I get: Starting gunicorn 17.5 Listening at: http://0.0.0.0:5000 How can I change it so that it listens only to

Environment variables not available in Elastic Beanstalk Procfile

阅读更多关于 Environment variables not available in Elastic Beanstalk Procfile

I'm attempting to configure my elastic beanstalk java application using environment variables via the Procfile like so: web: ./bin/myservice -Dhttp.port=$PORT The PORT environment variable is set via the AWS ui in the "Software Configuration" screen of my beanstalk environment. However, the logs are indicating that $PORT is not being interpolated: Exception in thread "main" java.lang.ExceptionInInitializerError at com.whatever.services.myservice.Main.main(Main.scala) Caused by: java.lang.NumberFormatException: For input string: "$PORT" at java.lang.NumberFormatException.forInputString

gunicorn on heroku: binding to localhost

阅读更多关于 gunicorn on heroku: binding to localhost

I've been following the tutorial on https://devcenter.heroku.com/articles/django#declare-process-types-with-procfile . It went smoothly except for one thing that bothers me. After starting foreman I should see the following: $ foreman start 2013-04-03 16:11:22 [8469] [INFO] Starting gunicorn 0.17.2 2013-04-03 16:11:22 [8469] [INFO] Listening at: http://127.0.0.1:8000 (8469) However, I get: Starting gunicorn 17.5 Listening at: http://0.0.0.0:5000 How can I change it so that it listens only to my local machine (ie. 127.0.0.1)? My Procfile contains only web: gunicorn hellodjango.wsgi thanks! This

How to get Heroku to recognize a yarn.lock or package.json within a subdirectory (not root)

阅读更多关于 How to get Heroku to recognize a yarn.lock or package.json within a subdirectory (not root)

问题 I have a Rails application using React, Webpack, and Yarn for the client side. I have everything relating to the client side within the /client directory. This includes my yarn.lock and package.json files. I have a Procfile that cds into /client and properly runs yarn run build . This works locally with no errors. However, when I deploy/push to Heroku, my push is rejected and I get the following error: remote: cd client && yarn run build:production remote: sh: 1: yarn: not found remote: rake

How to get Heroku to recognize a yarn.lock or package.json within a subdirectory (not root)

阅读更多关于 How to get Heroku to recognize a yarn.lock or package.json within a subdirectory (not root)

I have a Rails application using React, Webpack, and Yarn for the client side. I have everything relating to the client side within the /client directory. This includes my yarn.lock and package.json files. I have a Procfile that cds into /client and properly runs yarn run build . This works locally with no errors. However, when I deploy/push to Heroku, my push is rejected and I get the following error: remote: cd client && yarn run build:production remote: sh: 1: yarn: not found remote: rake aborted! remote: Command failed with status (127): [cd client && yarn run build:production...] What