pkg.soopen package index

brew / Rang 2277

foreman mit Homebrew, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install foreman

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#foreman

nixpkgs package indexes · pkgs/by-name/fo/foreman/package.nix · Quelle: api.github.com

Überblick

Paketzusammenfassung

Manage Procfile-based applications

Befehle und Aliase

  • foreman

Verlauf

Projektgeschichte und Nutzung

Foreman is a Ruby command-line process manager for Procfile-based applications. It is best known for making the Heroku-style Procfile a local-development and deployment artifact outside Heroku itself.

Projektgeschichte

David Dollar introduced Foreman in May 2011 as a way to start multi-process web applications from a Procfile, covering web, worker, and clock processes with shared environment handling and automatic port assignment.

The project grew beyond local development by adding export targets for process supervisors. Its manual documents running an app directly, running one-off commands, and exporting process definitions to formats such as init, upstart, systemd, runit, and supervisord.

Adoptionsgeschichte

Foreman's README points users to installation as a Ruby gem and warns Ruby users not to bundle Foreman inside an application's Gemfile, reflecting its role as a developer tool around an application rather than a library dependency.

The README's ports list shows the Procfile-runner idea spreading into other languages and ecosystems, including forego, node-foreman, goreman, honcho, shoreman, and other reimplementations.

Wie es verwendet wird

Foreman reads a Procfile, loads environment from .env by default or from files passed with --env, starts each declared process, prefixes output, and can scale process counts with formation options.

Package users typically install the foreman executable and keep Procfile and .env files in the application root, making it a bridge between twelve-factor app conventions, local shells, and service managers.

Warum Paket-Nerds sich dafür interessieren

Foreman is historically important because it helped normalize Procfile as a portable, package-manager-distributed convention rather than only a Heroku deployment file.

It is also a small example of a package whose interface became a pattern: many later packages are not forks of Foreman, but compatibility ports of the same Procfile workflow.

Zeitleiste

  • 2011: David Dollar publishes the Introducing Foreman post and documents Procfile-based local process startup.
  • 2011: The changelog records 0.26.x and 0.27.0 releases with .env loading and Travis CI configuration.
  • 2012: Early releases add and refine concurrency, root directory handling, and one-off command execution.
  • 2016: The changelog records systemd exporter work and related service-management fixes.
  • 2024: Foreman 0.88.0 refreshes CI and updates documentation for systemd export.
  • 2025: Foreman 0.90.0 is released with Ruby dependency updates.

Related projects

  • Forego, goreman, node-foreman, honcho, shoreman, proclet, and other ports listed by the upstream README reuse Foreman's Procfile-runner model in other languages or shell environments.
  • Foreman is related to platform Procfile conventions used by Heroku-style applications and to Unix service managers such as systemd, upstart, runit, and supervisord through its export functionality.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • Es wurden keine Homebrew-Bottle-Metadaten erfasst.

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.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
./Procfile./.env

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
foremanExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.

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-08-03
Manager-Version0.90.0
Manager aktualisiert2026-06-06
lokale Datenunbekannt
Upstreamnicht verfügbar
neueste erkannte Versionnicht erkannt
  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:foreman
Version0.90.0
PaketmanagerHomebrew
Homepagehttps://ddollar.github.io/foreman/
Repositoryhttps://github.com/ddollar/foreman
Zuletzt aktualisiert2026-06-06T20:56:44-04:00
Pulseupdated
Bottlenicht erfasst
Dienstkeiner deklariert

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

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

Nix95%

foreman

nix profile install nixpkgs#foreman
  • normalized package name match
  • Abgeglichen nach: Foreman
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/fo/foreman/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

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
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • pkg.so package database
  • pkgdb category and tag curation