by NiceGroupOfPeople


Heroku Buildpack: NGINX

This is MongoDB's fork of Belly's fork of ryandotsmith/nginx-buildpack.

Changes by MongoDB Aug 2016:

Belly's readme is below, with slight edits to the rebuild process.

  • Ruby isn't needed to start the rebuilder dyno. A Procfile alone will suffice.

This is Belly's fork of ryandotsmith/nginx-buildpack. Here's what is different:

  • Moved the port variable configuration to a file that can be included in any nginx config file. This is helpful for breaking a large config file into multiple files and still being able to achieve a variable port number (necessary for Heroku). 9c1528a
  • Upgraded nginx to version 1.9.4 & added openssl support. Belly's requirements dictate that our proxy support SSL, so we added it, also upgraded to the latest nginx, since we were recompiling it anyway. 8233318, 0176e38, bfacddd
  • Added start-nginx-solo. The original buildpack expected that you were proxying a request to some app running within the same dyno. This isn't necessary for Belly's use case, so the solo option was added to remove some of the moving parts. f14698e, b19c940
  • Added a configurable domain name option b010d13, 001259a

Recompile nginx

In order to recompile nginx, you need to build it on the target system that it will be running on. In this case we want to build it for cedar-14. Here's how to do it:

  1. Make a local directory for the app that will be used to do the compiling and git init it:

    mkdir nginx-builder
    cd nginx-builder
    git init .
  2. Next, create an app on Heroku for your target stack using the multi buildpack.

    heroku create --buildpack --stack cedar-14
    Creating infinite-wave-4795... done, stack is cedar-14
    Buildpack set. Next release on infinite-wave-4795 will use |
    Git remote heroku added
  3. Add this nginx buildpack to the .buildpacks file.

    echo '' >> .buildpacks
  4. Create a Procfile in your local directory to tell the app what to do when it starts up. is the compiler script. So when the dyno boots it will just start to compile right away.

    echo 'web: scripts/' >> Procfile
  5. Commit those files locally:

    git add Procfile .buildpacks
    git commit -m "Added Procfile, Gemfile & buildpacks"
  6. Start tailing the logs in a separate terminal and deploy the app, then immediately scale to a performance L dyno:

    heroku logs --tail
    git push heroku master
    heroku ps:scale web=1:performance-l
  7. If all goes well, the compiler will kick off and you will see output in the logs. This will take some time, so go grab some coffee.

  8. Once the compiler is done the logs will just output a .. From there you can go to your browser and get the built binary.

    heroku open

    The compiled binary will be in /nginx/sbin/nginx.

  9. Once you have the file, copy it to the bin directory in the nginx-buildpack repo under the appropriate stack name nginx-cedar-14. You can delete the temporary app created on Heroku.

-- original ryandotsmith/nginx-buildpack readme below --

Heroku Buildpack: NGINX

Nginx-buildpack vendors NGINX inside a dyno and connects NGINX to an app server via UNIX domain sockets.


Some application servers (e.g. Ruby's Unicorn) halt progress when dealing with network I/O. Heroku's Cedar routing stack buffers only the headers of inbound requests. (The Cedar router will buffer the headers and body of a response up to 1MB) Thus, the Heroku router engages the dyno during the entire body transfer –from the client to dyno. For applications servers with blocking I/O, the latency per request will be degraded by the content transfer. By using NGINX in front of the application server, we can eliminate a great deal of transfer time from the application server. In addition to making request body transfers more efficient, all other I/O should be improved since the application server need only communicate with a UNIX socket on localhost. Basically, for webservers that are not designed for efficient, non-blocking I/O, we will benefit from having NGINX to handle all I/O operations.


  • Buildpack Version: 0.4
  • NGINX Version: 1.5.7


  • Your webserver listens to the socket at /tmp/nginx.socket.
  • You touch /tmp/app-initialized when you are ready for traffic.
  • You can start your web server with a shell command.


  • Unified NXNG/App Server logs.
  • L2met friendly NGINX log format.
  • Heroku request ids embedded in NGINX logs.
  • Crashes dyno if NGINX or App server crashes. Safety first.
  • Language/App Server agnostic.
  • Customizable NGINX config.
  • Application coordinated dyno starts.


NGINX will output the following style of logs:

measure.nginx.service=0.007 request_id=e2c79e86b3260b9c703756ec93f8a66d

You can correlate this id with your Heroku router logs:

at=info method=GET path=/ request_id=e2c79e86b3260b9c703756ec93f8a66d fwd="" dyno=web.1 connect=1ms service=8ms status=200 bytes=21

Language/App Server Agnostic

Nginx-buildpack provides a command named bin/start-nginx this command takes another command as an argument. You must pass your app server's startup command to start-nginx.

For example, to get NGINX and Unicorn up and running:

$ cat Procfile
web: bin/start-nginx bundle exec unicorn -c config/unicorn.rb

Setting the Worker Processes

You can configure NGINX's worker_processes directive via the NGINX_WORKERS environment variable.

For example, to set your NGINX_WORKERS to 8 on a PX dyno:

$ heroku config:set NGINX_WORKERS=8

Customizable NGINX Config

You can provide your own NGINX config by creating a file named nginx.conf.erb in the config directory of your app. Start by copying the buildpack's default config file.

Customizable NGINX Compile Options

See scripts/ for the build steps. Configuring is as easy as changing the "./configure" options.

Application/Dyno coordination

The buildpack will not start NGINX until a file has been written to /tmp/app-initialized. Since NGINX binds to the dyno's $PORT and since the $PORT determines if the app can receive traffic, you can delay NGINX accepting traffic until your application is ready to handle it. The examples below show how/when you should write the file when working with Unicorn.


Here are 2 setup examples. One example for a new app, another for an existing app. In both cases, we are working with ruby & unicorn. Keep in mind that this buildpack is not ruby specific.

Existing App

Update Buildpacks

$ heroku config:set BUILDPACK_URL=
$ echo '' >> .buildpacks
$ echo '' >> .buildpacks
$ git add .buildpacks
$ git commit -m 'Add multi-buildpack'

Update Procfile:

web: bin/start-nginx bundle exec unicorn -c config/unicorn.rb
$ git add Procfile
$ git commit -m 'Update procfile for NGINX buildpack'

Update Unicorn Config

require 'fileutils'
listen '/tmp/nginx.socket'
before_fork do |server,worker|
$ git add config/unicorn.rb
$ git commit -m 'Update unicorn config to listen on NGINX socket.'

Deploy Changes

$ git push heroku master

New App

$ mkdir myapp; cd myapp
$ git init


source ''
gem 'unicorn'

run {[200,{'Content-Type' => 'text/plain'}, ["hello world"]]}


require 'fileutils'
preload_app true
timeout 5
worker_processes 4
listen '/tmp/nginx.socket', backlog: 1024

before_fork do |server,worker|

Install Gems

$ bundle install

Create Procfile

web: bin/start-nginx bundle exec unicorn -c config/unicorn.rb

Create & Push Heroku App:

$ heroku create --buildpack
$ echo '' >> .buildpacks
$ echo '' >> .buildpacks
$ git add .
$ git commit -am "init"
$ git push heroku master
$ heroku logs -t

Visit App

$ heroku open


Copyright (c) 2013 Ryan R. Smith Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.