Apache Hop Server: deployment options¶
The Apache Hop Server template (category Processing) deploys an Apache Hop execution server: it runs the pipelines and workflows of the Git project synchronised on the instance, on demand or on a schedule — see Jobs and scheduling.
General¶
| Field | Role |
|---|---|
| Hop version | Tag of the ds/hop-server image. |
| Memory limit, CPU limit | Container resources (Capacity category): 4Gi and 2000m by default. |
| File Browser | Accessory file manager (upload/download), enabled by default. |
| Hop environment name | HOP_ENVIRONMENT_NAME: the project environment activated at startup. |
Git source¶
The project source is required here, and is filled in as for Apache Hop GUI: managed Forgejo instance (instance, repository, branch) or manual entry (URL, branch, user and token for a private repository).
| Field | Role |
|---|---|
| Synchronisation interval | How often the git-sync sidecar polls the repository (30s, 1m, 5m…), 60s by default. |
Unlike Hop GUI, the project is synchronised continuously: a commit pushed to the tracked branch is picked up at the next synchronisation, without restarting the application.
See also¶
- Jobs and scheduling — queue, launching a job, periodic scheduling.
- API compatibility test, a card action: checks that the server's API answers, check by check.