Skip to content

Latest commit

 

History

History
83 lines (56 loc) · 3.12 KB

README.md

File metadata and controls

83 lines (56 loc) · 3.12 KB
Raw

Heroku buildpack: Grails

This is a Heroku buildpack for building and deploying Grails apps on Heroku.

Usage

Create a Git repository for a Grails 1.3.7 or 2.0 app:

$ cd mygrailsapp
$ ls
application.properties    lib        src               target    web-app
grails-app                scripts    stacktrace.log    test
$ grails integrate-with --git
| Created Git project files..
$ git init
Initialized empty Git repository in /Users/jjoergensen/mygrailsapp/.git/
$ git commit -m init
[master (root-commit) 7febdd9] init
 58 files changed, 2788 insertions(+), 0 deletions(-)
 create mode 100644 .classpath
 create mode 100644 .gitignore
 create mode 100644 .project
 create mode 100644 application.properties
...

Create a Heroku app on the Cedar stack specifying my custom buildpack.

$ heroku create --stack cedar --buildpack https://github.com/csherstan/heroku-buildpack-grails.git
Creating vivid-mist-9984... done, stack is cedar
http://vivid-mist-9984.herokuapp.com/ | git@heroku.com:vivid-mist-9984.git
Git remote heroku added

If you already have an existing app on Heroku then specify the custom buildpack like so:

$ heroku config:add BUILDPACK_URL=https://github.com/csherstan/heroku-buildpack-grails.git

Specifying a specific build environment

By default the build pack runs grails war, which assumes the production environment. To specify a different environment to use do the following:

  1. Make the Heroku environment variables available during build time (replace "myapp" with the Heroku name of your app)

     $ heroku labs:enable user-env-compile -a myapp

  2. Specify your desired environment (replace "myenvironment" with the desired environment)

     $ heroku config:add GRAILS_ENV=myenvironment

If you have already pushed your app this will not automatically rebuild it, you will need to do a git push on your app in order for the changes to take affect.

Push the app to Heroku

$ git push heroku master
Counting objects: 73, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (69/69), done.
Writing objects: 100% (73/73), 97.82 KiB, done.
Total 73 (delta 2), reused 0 (delta 0)

-----> Heroku receiving push
-----> Grails app detected
-----> Grails 2.0.0 app detected
-----> Installing Grails 2.0.0..... done
-----> executing grails -plain-output -Divy.default.ivy.user.dir=/app/tmp/repo.git/.cache war

       |Loading Grails 2.0.0
       |Configuring classpath
...

Auto-detection

Heroku auto-detects Grails apps by the existence of the grails-app directory in the project root and the application.properties file is also expected to exist in the root directory.

Using a Customized (Forked) Build Pack

This is the default buildpack repository for Grails. You can fork this repo and tell Heroku to use the forked version by passing the --buildpack option to heroku create:

$ heroku create --stack cedar --buildpack http://github.com/jesperfj/heroku-buildpack-grails.git

License

Licensed under the MIT License. See LICENSE file.