Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Example use of Heroku Common Lisp Buildpack
Common Lisp
Pull request Compare This branch is 36 commits ahead, 20 commits behind mtravers:master.
Latest commit a67a3eb @jsmpereira Add license. Closes #4

Common Lisp on Heroku -- Example Project

This project is an example of how to use my fork of the Heroku Common Lisp Buildpack. See the buildpack repository for more information and credits.

This is the Hunchentoot branch.

Example App:


First, get yourself set up with a Heroku account and tools.

Then fork this project (and optionally modify it with your own content).

Change directory into the heroku-cl-example.

Next, create your own Heroku application using CL Buildpack:

heroku create -s cedar --buildpack
# Enable config vars at build time 
heroku labs:enable user-env-compile -a myapp

# Choose implementation:
heroku config:add CL_IMPL=sbcl
# or
heroku config:add CL_IMPL=ccl

# Choose Web Server:
heroku config:add CL_WEBSERVER=hunchentoot
# or 
heroku config:add CL_WEBSERVER=aserve

# Avoid trouble with SBCL source encoding
heroku config:add LANG=en_US.UTF-8

# deploy 
git push heroku master

That's it! Use heroku open to view your app in your browser!

More details:

There are currently 2 branches. Master has Huchentoot specific code and aserve has AllegroServe specific code.

Currently let's you run Hunchentoot with SBCL and CCL and AllegroServe(portableaserve) with CCL.

There is a pending issue with acl-compat bundled with portableaserve preventing use with SBCL. Look here for more information.

The file heroku-setup.lisp gets loaded at compile time, and needs to load any Lisp files or packages required.

Thanks to Mike Travers for getting Common Lisp on Heroku.

Something went wrong with that request. Please try again.