Select from available Build Packs to build up your own kit.
You can use Anvil to test buildpacks without publishing them:
$ heroku plugins:install https://github.com/ddollar/heroku-anvil $ cd myproject $ heroku build -b /path/to/local/buildpack Generating app manifest... done Uploading new files... done, 0 files needed Generating buildpack manifest... done Uploading new files... done, 0 files needed Launching build process... done Recreating app from manifest... done Fetching buildpack... done Detecting buildpack... done, Clojure Fetching cache... empty Compiling app... Installing Leiningen Downloading: leiningen-1.7.1-standalone.jar Writing: lein script Running: LEIN_NO_DEV=y lein deps [...] Creating slug... done Uploading slug... done Success, slug is https://anvil.herokuapp.com/slugs/bbbde9d0-b650-11e1-9829-659a6807d866.img
Once you're happy with your buildpack, you can publish it for others to use with the heroku buildpacks plugin:
$ heroku plugins:install https://github.com/heroku/heroku-buildpacks $ cd heroku-buildpack-clojure $ heroku buildpacks:publish clojure Publishing clojure buildpack... done
# Database first: $ initdb pg && postgres -D pg $ createdb buildkits $ lein run -m buildkits.db/migrate
You may need to add
/usr/lib/postgresql/$PG_VERSION/bin to your
$PATH first on Debian-based systems. You'll also need a new enough
version of PostgreSQL to have HStore support.
$ lein run -m buildkits.web
For developing against a local app:
$ export BUILDPACK_SERVER_URL=http://localhost:5000
Start with a production repl using
$ heroku run lein repl
If you configure a new bucket, you'll want to populate it from the DB:
user> (doto 'buildkits.buildpacks require in-ns) buildkits.buildpack> (update-s3-tarballs)
Transferring buildpacks to a different org is currently only exposed via the repl:
user> (doto 'buildkits.buildpacks require in-ns) buildkits.buildpack> (transfer "heroku/emacs" "technomancy")
Copyright © 2012 Heroku, Inc.
Distributed under the Eclipse Public License, the same as Clojure.