Automic VaultAutomic Vault

brew

ecflow-ui mit Homebrew, apt installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für ecflow-ui in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install ecflow-ui

local Homebrew formula metadata

Linux

Debian aptverifiziert · 92%
sudo apt install ecflow-client

Debian stable package indexes · ecflow-client · Quelle: deb.debian.org

Überblick

Paketzusammenfassung

User interface for client/server workflow package

Befehle und Aliase

  • ecflow_client
  • ecflow_ui
  • ecflow_ui.x

Verlauf

Projektgeschichte und Nutzung

ecFlowUI is the graphical client shipped with ECMWF's ecFlow workflow manager. As a Homebrew package, ecflow-ui exposes the UI and client pieces of an operational workflow system used to define, submit, monitor, and restart large dependency-driven job suites.

Projektgeschichte

ECMWF's ecFlow documentation says ecFlow is a client/server workflow package for running many programs with dependencies on each other and on time, in a controlled environment with failure tolerance and restart capabilities. It is used at ECMWF to run all operational suites across a range of platforms.

The history documented by ECMWF starts with SMS, the Supervisor Monitoring Scheduler, which ECMWF used for almost three decades. SMS let scientists, analysts, and operators design, submit, and monitor jobs in Research and Operations, and was also used by many organizations outside ECMWF member states.

ecFlow 4 superseded SMS as a complete object-oriented rewrite using modern standardized components. The proprietary CDP scripting language used by SMS was replaced by Python. Development of ecFlow 4 later stopped, support continued, and ecFlow 5 replaced it.

The ecFlow repository was created on GitHub in August 2020, but the documentation and copyright history show an older ECMWF project line. The current documentation is for ecFlow 5.16.0 and lists ecflow_client, ecflow_ui, ecflow_server, and the Python API as the main components.

Adoptionsgeschichte

ecFlow's adoption is strongest in operational forecasting and scientific production environments where workflows are long-running, dependency-heavy, and monitored by teams. ECMWF's own documentation frames it as production infrastructure rather than a general-purpose desktop scheduler.

The package split is important: Homebrew's ecflow-ui package includes ecflow_client and ecflow_ui executables, giving workstation users a way to inspect and control ecFlow suites without necessarily packaging the full server deployment in the same way.

Wie es verwendet wird

ecFlow runs a server that receives requests from clients over TCP/IP. Clients include ecflow_client, ecflow_ui, scripts, and the Python API; suite jobs communicate status and events back through child commands embedded in scripts.

ecFlowUI is the Qt-based graphical client used to monitor and visualize the node-tree hierarchy. The CLI and Python API are used for suite definition, automation, and communication with the server.

Warum Paket-Nerds sich dafür interessieren

ecflow-ui matters to package nerds because it is a UI/client package carved out of a larger scheduler ecosystem. That is a classic operational packaging problem: users may need local client tools and a GUI even when servers live elsewhere.

It also represents a lineage change in scientific operations tooling: SMS to ecFlow 4 to ecFlow 5, CDP to Python, and a move toward open GitHub-hosted ECMWF software with documented maturity status.

Zeitleiste

  • 2009: ecFlow documentation copyright range begins.
  • 2011: ECMWF newsletter article introduces ecFlow.
  • 2020: ECMWF ecFlow GitHub repository created.
  • 2024: ecFlow 5.12 and 5.13 release series visible in GitHub releases.
  • 2026: ecFlow 5.16.0 released and documented on Read the Docs.

Related projects

  • SMS, the Supervisor Monitoring Scheduler, is ecFlow's direct predecessor.
  • ecflow_client, ecflow_server, ecflow_ui, and the Python ecflow module are the main components of the same system.
  • The documentation explicitly notes that ecFlow is a scheduler and not a queueing system such as NQS, SGE, LoadLeveler, or PBS, though it can submit jobs to queueing systems.

Sicherheitslage

Risikostufe: blue

broad file, network, media, or database tool signal.

Risikoklassifikator

blue Risiko · mittel Konfidenz · tool

Warum

  • broad file, network, media, or database tool signal

Signale

  • text:client,server

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Installiert mit 5 Laufzeitabhängigkeiten.
  • Build-Metadaten listen 2 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
ecflow_clientcliglobales Executable
ecflow_uicliglobales Executable
ecflow_ui.xcliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25
Manager-Version5.18.0
Manager aktualisiert2026-07-07
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://ecflow.readthedocs.io

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:ecflow-ui
Version5.18.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/ecflow-ui
Homepagehttps://ecflow.readthedocs.io
Repositoryhttps://github.com/ecmwf/ecflow
Upstream-Dokumentationhttps://confluence.ecmwf.int/display/ECFLOW/ecFlowUI+Documentation
LizenzApache-2.0
Quellarchivhttps://confluence.ecmwf.int/download/attachments/8650755/ecFlow-5.18.0-Source.tar.gz
Zuletzt aktualisiert2026-07-07T09:59:02Z
Pulseupdated
Abhängigkeitenopenssl@3, qt5compat, qtbase, qtcharts, qtsvg
Build-Abhängigkeitenboost, cmake
Von macOS bereitgestellte Bibliothekenlibxcrypt
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameecflow-ui
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Debian apt92%

ecflow-client 5.13.8-1

Client tools for Meteorological workflow

https://software.ecmwf.int/wiki/display/ECFLOW/The+ECFLOW+Pre-processor

sudo apt install ecflow-client
  • Section: science
  • Architecture: amd64
  • Source Package: ecflow
  • 16 Abhängigkeiten
  • installed executable or alias match
  • Abgeglichen nach: Ecflow Client
Debian stable package indexes · deb.debian.org · Debian stable package indexes: ecflow-client from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz
Ubuntu apt92%

ecflow-client 5.12.0-1build3

Client tools for Meteorological workflow

https://software.ecmwf.int/wiki/display/ECFLOW/The+ECFLOW+Pre-processor

sudo apt install ecflow-client
  • Section: universe/science
  • Architecture: amd64
  • Source Package: ecflow
  • 16 Abhängigkeiten
  • installed executable or alias match
  • Abgeglichen nach: Ecflow Client
Ubuntu 24.04 LTS package indexes · archive.ubuntu.com · Ubuntu 24.04 LTS package indexes: ecflow-client from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment