Packaging & Deployment

Packing

Apps are packed using the Hantera CLI. Packing bundles all declared resources into a single distributable artifact.

This includes:

• Components (reactor, rule, discount)
• Ingresses
• Registry entries
• Job definitions
• Portal extension files (static UI assets)

To create a package, run:

h_ app pack <app_path> -v <version>

This command generates a .hapk file. The .hapk artifact contains the app manifest and all referenced resources, ready for installation.

Installation

The .hapk file can be installed through the Hantera portal UI.

After installation, the portal displays metadata from the manifest, including:

• App ID
• Name
• Authors
• Version
• Declared settings

Once installed, the app’s resources (components, ingresses, registry entries, job definitions, and portal extension) are applied to the system.

Updating an App

To update an app:

1. Modify the app source (components, registry entries, settings, etc.).
2. Repackage the app with a new version number:

h_ app pack <app_path> -v <new_version>

3. Install the new .hapk file.

The App ID is used to identify the application. When a new version with the same App ID is installed, it replaces the currently active version.

After installation, the latest version becomes the active one.

For full CLI usage and command reference, see the Hantera CLI documentation