Blog Posts
Shipping Hilla apps to production. Part 1: Production Build
Hilla apps can be built for delivery in production using the Production Build. They can be packaged as a Fat JAR, WAR file or as a Native Image.
Hilla: What's next?
There are some exciting new functions in the pipeline for the Hilla framework. Three of these improvements are presented in this blog post.
n:m relationships in Hilla with AutoGrid and AutoForm
n:m relationships between entities can be implemented productively and flexibly in business web apps made with Hilla and the AutoGrid and AutoForm components.
Deploying Hilla apps as native image
Hilla apps can be built as a native image with an integrated server using GraalVM. They can be deployed this way. In conjunction with a Dockerfile, an individual Docker image can be created, and the application can be deployed as a Docker container, e.g. at fly.io.
Deploying Hilla apps as JAR file
Hilla apps can be built as a JAR file with an integrated server. They can be deployed with a suitable Java runtime environment. In conjunction with a Dockerfile, an individual Docker image can be created, and the application can be deployed as a Docker container, e.g. at fly.io.
Fine-tuning of Tekton event listeners with (CEL) interceptors
The integration between a source code management system (SCM), such as Bitbucket or GitHub, and Tekton can be customized with the help of interceptors. Individual filter conditions can also be applied using the Common Expression Language (CEL).