Difference between revisions of "Heroku: procfile"
Jump to navigation
Jump to search
↑ https://elements.heroku.com/buildpacks/heroku/heroku-buildpack-static
Tags: Mobile web edit, Mobile edit |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 14: | Line 14: | ||
web: [[bundle exec]] rails server -p $PORT | web: [[bundle exec]] rails server -p $PORT | ||
| − | === [[Clojure]] | + | === [[Clojure]] === |
web: [[lein]] run -m demo.web $PORT | web: [[lein]] run -m demo.web $PORT | ||
| Line 22: | Line 22: | ||
== Related == | == Related == | ||
* <code>[[app.json]]</code> | * <code>[[app.json]]</code> | ||
| + | * [[Buildpack]] | ||
== See also == | == See also == | ||
Latest revision as of 03:57, 17 March 2022
https://devcenter.heroku.com/articles/procfile Heroku apps include a Procfile that specifies the commands that are executed by the app on startup. You can use a Procfile to declare a variety of process types, including:
- Your app’s web server
- Multiple types of worker processes
- A singleton process, such as a clock
- Tasks to run before a new release is deployed
Contents
Examples[edit]
Rails[edit]
web: bundle exec rails server -p $PORT
Clojure[edit]
web: lein run -m demo.web $PORT
In case you have multiple buildpacks for the application you can ensure static rendering in procfile
web: bin/boot [1]
Related[edit]
See also[edit]
- Heroku, Heroku Review Apps,
procfile,app.json, Heroku Flow,heroku login,heroku --helpHerokudns.com, Heroku Dynos
Advertising:
