To use this custom buildpack, use the Heroku toolbelt's
$ heroku buildpacks:set https://github.com/lexi-lambda/heroku-buildpack-racket
When the application is next deployed, the new buildpack will be used.
The Racket buildpack requires that the
RACKET_VERSION environment variable be set in order to decide what version of Racket to use. It may either be set to a specific version (such as
6.2) or to either
HEAD, which will use nightly, bleeding-edge snapshots.
By default, the buildpack will use the full Racket distribution. If you want to only install a minimal Racket distribution, append
-minimal to the end of the version string (e.g.
To configure environment variables for your Heroku application, either use the web interface, or use the
heroku config:set command.
The Racket buildpack will install your repository as a package, so it must include an
info.rkt file in the root. Once installed, it will be moved to the
app/ directory. It is recommended that you specify your application entry point via the
-l flag so you can pass a module path instead of a file path, which will work no matter what the filesystem layout.
For example, if your package contained a file called
server.rkt in a collection called
my-app, the Procfile entry to start your application might look like this:
web: racket -l my-app/server
Copy the snippet above into CLI.