Difference between revisions of "Heroku: procfile"
Jump to navigation
Jump to search
↑ https://elements.heroku.com/buildpacks/heroku/heroku-buildpack-static
| Line 10: | Line 10: | ||
== Examples == | == Examples == | ||
| − | [[Rails]] | + | |
| + | === [[Rails]] === | ||
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 | ||
In case you have multiple [[buildpacks]] for the application you can ensure static rendering in <code>procfile</code> | In case you have multiple [[buildpacks]] for the application you can ensure static rendering in <code>procfile</code> | ||
web: bin/boot <ref>https://elements.heroku.com/buildpacks/heroku/heroku-buildpack-static</ref> | web: bin/boot <ref>https://elements.heroku.com/buildpacks/heroku/heroku-buildpack-static</ref> | ||
| − | |||
== Related == | == Related == | ||
Revision as of 06:59, 1 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
Rails
web: bundle exec rails server -p $PORT
=== Clojure
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
See also
- Heroku, Heroku Review Apps,
procfile,app.json, Heroku Flow,heroku login,heroku --helpHerokudns.com, Heroku Dynos
Advertising:
