This project is an example of how to use my fork of this Heroku Common Lisp Buildpack. See the buildpack repository for more information and credits.
Example App: https://fathomless-spire-2385.herokuapp.com/
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 https://github.com/jonatack/heroku-buildpack-cl.git
# Enable config vars at build time http://devcenter.heroku.com/articles/labs-user-env-compile
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!
There are currently 2 branches. Master has Huchentoot specific code and aserve has AllegroServe specific code.
Currently, https://github.com/jonatack/heroku-buildpack-cl allows running 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.