HTTPD Buildpack Reference

This reference documentation offers an in-depth description of the behavior and configuration options of the Paketo HTTPD Buildpack. For explanations of how to use the buildpack for several common use-cases, see the Paketo HTTPD Buildpack How To documentation.

The HTTPD Paketo Buildpack supports the installation of the Apache HTTP Server binary distribution onto the $PATH inside a container. This makes it available to subsequent buildpacks.

Supported Dependencies

The HTTPD Paketo Buildpack supports several versions of Apache HTTP Server. For more details on the specific versions supported in a given buildpack version, see the release notes.

Supported Environment Variable Configuration

BP_LIVE_RELOAD_ENABLED

Enables reloadable processes.

BP_HTTPD_VERSION

Allows you to specify the version of Apache HTTP Server that is installed.

BP_WEB_SERVER

When the value is set to httpd the buildpack will generate a default httpd.conf.

BP_WEB_SERVER_ROOT

Defaults to public, setting this allows you to modify the location of the static files served by the web server with either an absolute file path or a file path relative to /workspace.

BP_WEB_SERVER_ENABLE_PUSH_STATE

Enables push state routing functionality.

BP_WEB_SERVER_FORCE_HTTPS

Allows you to enforce HTTPS for server connections by redirecting all requests to use the HTTPS protocol.

Supported Service Bindings

The HTTPD buildpack can be configured using service bindings.

Behavior

When the HTTPD Buildpack participates in a build, it will contribute in one of three ways:

1. When an httpd.conf file is present in your app’s source code, the buildpack will set up an Apache HTTP server with that config.

2. When the httpd.conf is not present in the app’s source code, the buildpack simply provides the Apache HTTP Server dependency to subsequent buildpacks without actually setting up a server.

3. When the BP_WEB_SERVER is set to httpd, the buildpack will set up an Apache HTTP server with a default configuration.