Learn how to use buildpacks to automate your application builds.
Language | Directory |
---|---|
Node.js | /layers/heroku_nodejs-engine/dist/bin/node |
Ruby | /usr/bin/ruby |
Python | /usr/bin/python |
Java | /layers/heroku_jvm/openjdk/bin/java |
Scala | Scala doesn’t have a specific default binary path like some other compiled languages. When you compile a Scala program, it generates bytecode that runs on the Java Virtual Machine (JVM). The compiled Scala classes are typically stored in a directory structure that mirrors the package structure of your code. This is similar to how Java classes are organized. By default, when you compile a Scala source file, the compiled .class files will be placed in the same directory as the source code (within a subdirectory structure based on the package declarations). If needed, you can install Scala’s runtime tools using a Dockerfile instead of a buildpack. |
PHP | /workspace/.heroku/php/bin/ |
Go | Go doesn’t have a specific default binary path like some other compiled languages. When you compile a Go program, the resulting binary executable is typically placed in the same directory as your source code by default. If needed, you can install Go’s runtime tools using a Dockerfile instead of a buildpack. |
dependencies
of your package.json file:
.user.ini
file in the same directory as the .php
file. For more information about which settings you can control, refer to the PHP manual.
A small set of PHP.ini
configuration directives cannot be modified using .user.ini
; for example, always_populate_raw_post_data
and PHP_INI_SYSTEM
. In this case, you must pass additional configuration settings for PHP at startup time using a custom configuration file fpm_custom.conf
with the php_value
and php_flag
directives.
If you use a custom configuration file, you must tell your application to start with this configuration by adding -F
to the start command. You can also use this configuration file to modify the PHP-FPM behavior.