# foreman mit Homebrew, Nix installieren

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

## Installation

```sh
sudo av install brew:foreman
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install foreman
```

  Evidenz: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#foreman
```

  Evidenz: nixpkgs package indexes: pkgs/by-name/fo/foreman/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Paketfakten

- **Paketschlüssel:** brew:foreman
- **Paketmanager:** Homebrew
- **Version:** 0.90.0
- **Quellzusammenfassung:** Manage Procfile-based applications
- **Homepage:** <https://ddollar.github.io/foreman/>
- **Repository:** <https://github.com/ddollar/foreman>
- **Zuletzt aktualisiert:** 2026-06-06T20:56:44-04:00
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- foreman (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 0.90.0
## 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.

### Quellen

- <https://blog.daviddollar.org/2011/05/06/introducing-foreman.html>
- <https://ddollar.github.io/foreman/>
- <https://github.com/ddollar/foreman>
- <https://raw.githubusercontent.com/ddollar/foreman/main/Changelog.md>
- <https://raw.githubusercontent.com/ddollar/foreman/master/README.md>


## Sicherheitshinweise

narrow executable package without higher-risk signals.

- **Geiger-Risiko:** grün / niedrig
- narrow executable package without higher-risk signals


## 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

- Unix: ./Procfile, ./.env
## Andere Paketmanager-Einträge

- Nix - foreman: normalized package name match | nixpkgs package indexes: pkgs/by-name/fo/foreman/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Verwandte Links

- [foreman](https://pkg.so/de/pkg/npm/foreman/) - Same normalized package name exists in another local package ecosystem.

## Combined YAML source

View the package source record on GitHub. [combined/foreman.yml](https://github.com/mxcl/pkgdb/blob/main/combined/foreman.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph