brew

lighttpd mit Homebrew, apk, apt, dnf, MacPorts, Nix, pacman, zypper, scoop installieren

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

Installationsbefehl Sicherheitshinweise

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%

brew install lighttpd

local Homebrew formula metadata

MacPortsverifiziert · 94%

sudo port install lighttpd

MacPorts ports tree · www/lighttpd/Portfile · Quelle: api.github.com

Linux

Alpine Linux apkverifiziert · 92%

sudo apk add lighttpd

Alpine Linux edge package indexes · lighttpd · Quelle: dl-cdn.alpinelinux.org

Debian aptverifiziert · 92%

sudo apt install lighttpd

Debian stable package indexes · lighttpd · Quelle: deb.debian.org

Fedora dnfverifiziert · 92%

sudo dnf install lighttpd

Fedora Rawhide package metadata · lighttpd · Quelle: dl.fedoraproject.org

Nixverifiziert · 92%

nix profile install nixpkgs#lighttpd

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

Arch Linux pacmanverifiziert · 92%

sudo pacman -S lighttpd

Arch Linux sync databases · lighttpd · Quelle: geo.mirror.pkgbuild.com

openSUSE zypperverifiziert · 92%

sudo zypper install lighttpd

openSUSE Tumbleweed package metadata · lighttpd · Quelle: download.opensuse.org

Windows

Scoopverifiziert · 92%

scoop install extras/lighttpd

Scoop official bucket manifest trees · bucket/lighttpd.json · Quelle: api.github.com

Überblick

Paketzusammenfassung

Small memory footprint, flexible web-server

Projektlinks

Befehle und Aliase

lighttpd
lighttpd-angel

Verlauf

Projektgeschichte und Nutzung

lighttpd, pronounced "lighty", is a lightweight open-source HTTP server designed for high-performance environments with low memory and CPU use. It became part of the early-2000s wave of event-driven web servers that challenged process-heavy Apache deployments for static content, FastCGI, and constrained systems.

Projektgeschichte

Jan Kneschke's own project story traces lighttpd to February 2003, when he used Dan Kegel's c10k problem as a distraction while finishing a thesis. The prototype was explicitly about handling 10,000 parallel connections on one server after seeing Apache-style deployments exhaust memory with much smaller concurrency.

The project evolved into the 1.4 series with modules for FastCGI, CGI, authentication, compression, URL rewriting, proxying, TLS, and other common web-server jobs. Its official site continued to emphasize secure, fast, compliant, flexible service and lower resource use than other popular web servers.

Adoptionsgeschichte

lighttpd spread through Unix package managers because it was small, permissively licensed, and useful wherever Apache was too heavy or a reverse proxy/static-file server was enough. Its FastCGI support made it a practical companion for PHP, Ruby, Python, Perl, and other application stacks before nginx became the default lightweight-web-server answer for many administrators.

Wie es verwendet wird

Administrators generally run lighttpd as a daemon with a central lighttpd.conf file and optional included configuration fragments. It is used for static sites, embedded-device admin interfaces, FastCGI applications, reverse proxying, and small services where predictable resource usage matters.

Warum Paket-Nerds sich dafür interessieren

lighttpd is package-nerd significant because it preserves a distinct branch of web-server history: event-driven C infrastructure from the c10k era, a compact module system, and long-lived distro packaging across Linux, BSD, macOS, and Windows-adjacent ecosystems. It is also a reminder that "small web server" was a competitive category before nginx and Caddy dominated newer conversations.

Zeitleiste

2003-02: Jan Kneschke began the proof-of-concept that became lighttpd while thinking about the c10k problem.
2004: lighttpd licensing and copyright notices identify Jan Kneschke and incremental as early rightsholders.
2000s: lighttpd became a common package-manager web server for FastCGI and low-resource deployments.
2026: The official site still described active 1.4.x releases and a focus on secure, fast, compliant, flexible service.

Related projects

lighttpd is historically compared with Apache httpd, nginx, thttpd, and other event-driven or lightweight HTTP daemons. Its FastCGI usage ties it to PHP-FPM-style application serving, and its module set overlaps with reverse proxies used in modern web stacks.

Quellen

Sicherheitslage

Risikostufe: orange

broad file, network, media, or database tool signal. formula declares a Homebrew service.

Risikoklassifikator

orange Risiko · mittel Konfidenz · infrastructure

Warum

broad file, network, media, or database tool signal
formula declares a Homebrew service

Signale

metadata:service
text:http,server

Installationsverhalten

In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
Formelmetadaten deklarieren einen Service- oder Daemon-Block.
Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
Installiert mit 3 Laufzeitabhängigkeiten.
Build-Metadaten listen 4 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.

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: /etc/lighttpd/lighttpd.conf/etc/lighttpd/conf.d/*.conf

Executables

Installierte Executables

Befehl	Art	Sichtbarkeit	Hinweis
`lighttpd`	cli	globales Executable
`lighttpd-angel`	cli	globales 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-Version1.4.85

Manager aktualisiert2026-07-09

lokale DatenOK

Upstreamnot checked

neueste erkannte Versionnicht erkannt

Paketschlüssel	brew:lighttpd
Version	1.4.85
Paketmanager	Homebrew
Paketmanager-Seite	https://formulae.brew.sh/formula/lighttpd
Homepage	https://www.lighttpd.net/
Repository	https://git.lighttpd.net/lighttpd/lighttpd1.4.git
Upstream-Dokumentation	https://redmine.lighttpd.net/projects/lighttpd/wiki/Docs
Lizenz	BSD-3-Clause
Quellarchiv	https://download.lighttpd.net/lighttpd/releases-1.4.x/lighttpd-1.4.85.tar.xz
Zuletzt aktualisiert	2026-07-09T06:51:40Z
Pulse	updated
Abhängigkeiten	openldap, openssl@3, pcre2
Build-Abhängigkeiten	autoconf, automake, libtool, pkgconf
Von macOS bereitgestellte Bibliotheken	bzip2, libxcrypt
Bottle	verfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install	nicht definiert
Dienst	declared
Einschränkungen	Docroot is: $HOMEBREW_PREFIX/var/www The default port has been set in $HOMEBREW_PREFIX/etc/lighttpd/lighttpd.conf to 8080 so that lighttpd can run without sudo.

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	lighttpd
Version Scheme	0
Revision	0
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	stable