-
-
Notifications
You must be signed in to change notification settings - Fork 180
Running Boot on Heroku
Juho Teperi edited this page Mar 8, 2016
·
2 revisions
Boot buildpack: https://github.com/upworthy/heroku-buildpack-boot.git
If you have existing Heroku project, you can change the buildpack with following command:
heroku buildpacks:set https://github.com/upworthy/heroku-buildpack-boot.git
Your Boot project should define build
task which makes the project ready to run, e.g. creates uberjar.
Procfile
web: java $JAVA_OPTS -jar target/app.jar
Instead of creating uberjar, you could also call boot
in your Procfile. This will result in smaller slug at cost of startup time.
- All files from both the repository and from build will be included in Heroku slug
- Maximum size is 300MB
- When using uberjar clear target directory of any unnecessary files to reduce slug size
(comp ... (jar :file "app.jar") (sift :include #{#"app.jar"}) (target :dir #{"target"}))
You can find other developers and users in the #hoplon
channel on freenode IRC or the boot slack channel.
If you have questions or need help, please visit the Discourse site.
- Environments
- Boot environment
- Java environment
- Tasks
- Built-ins
- Third-party
- Tasks Options
- Filesets
- Target Directory
- Pods
- Boot Exceptions
- Configuring Boot
- Updating Boot
- Setting Clojure version
- JVM Options
- S3 Repositories
- Scripts
- Task Writer's Guide
- Require inside Tasks
- Boot for Leiningen Users
- Boot in Leiningen Projects
- Repl reloading
- Repository Credentials and Deploying
- Snippets
- Troubleshooting
- FAQ
- API docs
- Core
- Pod
- Util