Is it necessary to give 'worker' information in Procfile? If yes then what it is actually - couldn't find nice article regarding this. I hope you guys might have idea. I have already added web: node server/server.js detail in the Procfile. Any help would be appreciated!
相关问题
- MongoDB can not create unique sparse index (duplic
- npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fs
- Spring Data MongoDB - lazy access to some fields
- google-drive can't get push notifications
- Golang mongodb aggregation
相关文章
- node连接远程oracle报错
- mongodb有没有什么办法禁止读取数据的时候进行缓存
- mongodb-aggregate聚合查询分组后如何获得多字段
- mongodb error: how do I make sure that your journa
- How can make folder with Firebase Cloud Functions
- How to track MongoDB requests from a console appli
- Django/Heroku: FATAL: too many connections for rol
- @angular-cli install fails with deprecated request
You would only need a 'worker' entry in your
Procfile
if you plan on using some sort of background job system (i.e. queuing long running tasks for later). Heroku has more information here:https://devcenter.heroku.com/articles/procfile
From Process Types and the Procfile, which is a good introduction, but basically you use the Procfile to tell Heroku how to run various pieces of your app. The part to the left of the colon on each line is the process type; the part on the right is the command to run to start that process.
Process types can be anything, although
web
is special, as Heroku will route HTTP requests to processes started with theweb
name. Other processes, such as background workers, can be named anything, and you can use the Heroku toolbelt to start or stop those processes by referring to its name.So, in short,
worker
is not necessary, unless you want to run some other process in the background by controlling process with theheroku ps
command.