Skip to content

container-ratpack.md

Latest commit

 

History

History
42 lines (31 loc) · 2.1 KB

container-ratpack.md

File metadata and controls

42 lines (31 loc) · 2.1 KB

Ratpack Container

Implementation Note

Ratpack applications are handled by the Dist ZIP Container in the Go-based Java Buildpack. There is no separate Ratpack-specific container implementation because Ratpack applications use the standard Gradle distZip packaging format.

The Ratpack Container allows Ratpack applications, packaged distZip-style to be run.

Detection Criteria The lib/ratpack-core-.*.jar file exists in either the top-level directory or an immediate subdirectory of the application, AND the application has the standard bin/ and lib/ directory structure from Gradle's distZip task.
Tags Dist ZIP (Ratpack is detected as a distZip application)
Container Used Dist ZIP Container
Tags are printed to standard output by the buildpack detect script

The container expects to run the application created by running gradle distZip in an application built with the Ratpack Gradle plugin. The Gradle distZip task creates a standard bin/ and lib/ directory structure, which the Dist ZIP container handles automatically.

How Ratpack Applications Are Deployed

  1. Build: Run gradle distZip in your Ratpack project
  2. Extract: Extract the generated ZIP file to get the bin/ and lib/ directories
  3. Deploy: Push the extracted contents to Cloud Foundry
  4. Detection: The buildpack detects the distZip structure and uses the Dist ZIP container
  5. Execution: The startup script in bin/ is executed automatically

Configuration

Ratpack applications use the same configuration as any distZip application. See the Dist ZIP Container documentation for details.

No Ratpack-specific configuration is needed - the framework is detected automatically when ratpack-core-*.jar is found in the lib/ directory.