Skip to content

Apache Hop GUI: deployment options

The Apache Hop (GUI) template (category Processing) deploys Hop Web, the design interface for Apache Hop pipelines and workflows. The Hop project comes from a Git repository, cloned on first start then updated with git pull --ff-only on later starts. Each user's work, file-picker bookmarks and history are kept on the application's data volume.

General

Field Role
Hop version Tag of the ds/hop-web image.
Memory limit, CPU limit Container resources (Capacity category).
File Browser Accessory file manager (upload/download), can be disabled if unused.
Hop project name The project's displayed name in Hop Web. Empty: the name of the Git repository chosen at creation. The project folder on disk does not change.

Git source

The project opened in Hop Web comes from a Git repository, chosen in the Git source category:

Field Role
Git project source None (empty project), Managed Forgejo instance or Manual entry.
Forgejo instance, Repository, Branch Forgejo mode: a platform instance, a repository visible to its admin account, then the branch (empty = the repository's default branch) — see Git.
Repository URL, Branch, Git user, Git token / password Manual entry: external repository. User and token only for a private repository; they are kept in a namespace Secret and never shown again.

Access

Apache Hop GUI is the only template with direct granting: from Access, a user is either allowed or not, with no profiles — see Access and permissions.

Project connections

The platform writes the namespace's connection metadata into the Hop project: PostgreSQL databases, Hop servers and S3 buckets. They are regenerated periodically, and immediately with the card's Resynchronise Hop connections action. Passwords there are encrypted with an AES key shared across the platform, so Apache Hop Server instances can decrypt them too.

See also