Download Fluxheim
Pre-built Linux binaries for x86_64 and ARM64, plus macOS developer builds. Wydano 23 czerwca 2026.
Pełny production build
Wszystkie stabilne moduły production: proxy, web, cache, compression, load balancing, raw TCP stream proxying, TLS (rustls), PHP-FPM, ACME client, GeoIP/Geo-Context, security hardening, metrics i OpenTelemetry.
Load balancer edge
Skupiony HTTP/TCP load-balancer build bez cache, static web, PHP, GeoIP, stream proxying lub traffic mirroring.
PHP application build
Static web + reverse proxy + Moduł Moduł PHP-FPM FastCGI bridge. Idealny dla WordPress i aplikacji PHP front-controller. Bez skompilowanego modułu cache.
Cache edge build
Skupiony cache edge bez local static web serving. Zawiera proxy, cache, compression, TLS i ACME. Idealny dla deploymentów CDN-style.
Proxy edge build
Skupiony reverse proxy bez cache, static web lub dedykowanego modułu load-balancer. Zaprojektowany dla czystych reverse-proxy deploymentów z TLS, ACME, compression i upstream resilience.
Platform Downloads
Production Linux builds plus Level 1 macOS developer tarballs.
| Profil build | Linux x86_64 | Linux ARM64 | macOS dev build |
|---|---|---|---|
| Pełny | x86_64-linux | aarch64-linux | Apple Silicon |
| PHP | x86_64-linux | aarch64-linux | - |
| Load Balancer | x86_64-linux | aarch64-linux | - |
| Cache build | x86_64-linux | aarch64-linux | - |
| Proxy build | x86_64-linux | aarch64-linux | - |
| Config tester tool | x86_64-linux | aarch64-linux | - |
Instalacja
# 1. Pobierz pełny tarball build Linux
# Użyj aarch64-linux zamiast x86_64-linux na serwerach ARM64.
curl -L https://github.com/valkyoth/fluxheim/releases/download/v1.6.30/fluxheim-1.6.30-full-x86_64-linux.tar.gz \
-o fluxheim-1.6.30.tar.gz
# 2. Zweryfikuj i rozpakuj
tar xzf fluxheim-1.6.30.tar.gz
# 3. Przenieś binary i helper tools do system path
sudo mv fluxheim /usr/local/bin/
sudo mv fluxheim-acme /usr/local/bin/ # ACME companion tool tool
sudo mv fluxheim-config-tester /usr/local/bin/ # Config validator tool tool
# 4. Utwórz config directory i dodaj swój config
sudo mkdir -p /etc/fluxheim /srv/fluxheim
sudo cp packaging/default/fluxheim.toml /etc/fluxheim/fluxheim.toml
# 5. Zweryfikuj config
fluxheim --check-config --config /etc/fluxheim/fluxheim.toml
# 6. Uruchom bezpośrednio (albo zobacz tab Systemd dla service setup)
sudo fluxheim --config /etc/fluxheim/fluxheim.toml
# Pull GHCR images (full, load-balancer, cache, proxy i warianty PHP)
podman pull ghcr.io/valkyoth/fluxheim:v1.6.30 # pełny image
podman pull ghcr.io/valkyoth/fluxheim:v1.6.30-load-balancer # wariant load balancer
podman pull ghcr.io/valkyoth/fluxheim:v1.6.30-cache # wariant cache edge
podman pull ghcr.io/valkyoth/fluxheim:v1.6.30-proxy # wariant proxy edge
podman pull ghcr.io/valkyoth/fluxheim:v1.6.30-php # wariant managed PHP-FPM
# Ten sam build set jest dostępny na Quay
podman pull quay.io/valkyoth/fluxheim:v1.6.30
podman pull quay.io/valkyoth/fluxheim:v1.6.30-load-balancer
podman pull quay.io/valkyoth/fluxheim:v1.6.30-cache
podman pull quay.io/valkyoth/fluxheim:v1.6.30-proxy
podman pull quay.io/valkyoth/fluxheim:v1.6.30-php
# Uruchom rootless — porty wewnętrzne 8080 i 8443
podman run -d \
--name fluxheim \
--restart unless-stopped \
-p 8080:8080 \
-p 8443:8443 \
-v /srv/sites:/srv/sites:ro \
-v /srv/fluxheim/certs:/etc/fluxheim/certs:rw \
-v ./fluxheim.toml:/etc/fluxheim/fluxheim.toml:ro \
ghcr.io/valkyoth/fluxheim:v1.6.30
# Sprawdź logi
podman logs -f fluxheim
# Archiwum tarball zawiera hardened systemd unit
sudo cp packaging/systemd/fluxheim.service /etc/systemd/system/
# Utwórz system user fluxheim
sudo useradd -r -s /sbin/nologin -d /var/lib/fluxheim fluxheim
# Skonfiguruj directory
sudo mkdir -p /etc/fluxheim /srv/fluxheim /var/log/fluxheim
sudo chown fluxheim:fluxheim /srv/fluxheim /var/log/fluxheim
# Reload systemd i enable service
sudo systemctl daemon-reload
sudo systemctl enable --now fluxheim
# Sprawdź status
sudo systemctl status fluxheim
sudo journalctl -u fluxheim -f
Uwaga: Spakowany systemd unit używa CAP_NET_BIND_SERVICE aby Fluxheim mógł bind do portów 80 i 443 bez działania jako root. Unit file zawiera opcje security hardening.
# Fluxheim dostarcza acme-init dla prowadzonego setup certyfikatów
# Let's Encrypt issuer (HTTP-01)
sudo fluxheim acme-init letsencrypt
# Actalis (darmowy EAB-capable issuer)
sudo fluxheim acme-init actalis
# Companion tool fluxheim-acme obsługuje renewal dla
# deploymentów container i external service-manager
fluxheim-acme status
fluxheim-acme renew
fluxheim-acme reload
[[vhosts]]
name = "site"
hosts = ["example.com", "www.example.com"]
[vhosts.tls]
enabled = true
[vhosts.tls.acme]
enabled = true
# przykład: issuer = "letsencrypt"
Wymagania systemowe
Obsługiwane platformy
- Linux x86_64 (kernel 4.14+)
- Linux ARM64 / aarch64
- Tylko binary macOS developer
Container images
Wszystkie release image buildy są publikowane w GHCR i Quay.
- Wolfi (minimalny, hardened image)
- Profile image full, load-balancer, cache, proxy i PHP
- Alpine Linux
- SUSE Micro
- Debian
- Opublikowane w GHCR i Quay
All Releases
Zobacz wszystko na GitHub →| Wersja | Data | Najważniejsze punkty | Pobrania |
|---|---|---|---|
|
v1.6.0 – v1.6.30
Najnowsza seria
|
czerwiec 2026 | Linia native-runtime cutover: Pingora-exit foundations, Fluxheim-owned HTTP/1 i HTTP/2 paths, native TLS/listener previews, route proxy/static-web parity, compression i error pages, forwarded-header policy, auth-request, traffic mirroring, rate limits, gRPC validation, pooled upstream HTTP/2 i hardened runtime evidence. | Wszystko na GitHub |
| v1.5.0 - v1.5.23 | czerwiec 2026 | Linia enterprise load-balancer i runtime-ownership: focused load-balancer binaries/images, runtime member i weight controls, managed affinity cookies, stream i HTTP boundary work, active i protocol-aware health checks, service discovery, background task ownership, cache crate boundaries, UDP beta guardrails, origin-protection budgets, ARM/macOS assets i szeroki security hardening. | Wszystko na GitHub |
| v1.4.0 – v1.4.7 | maj 2026 | Linia proxy operations z production proxy parity, richer route policy, traffic mirroring, dynamic upstream discovery, modular runtime/config split, Apple Silicon i Linux ARM64 release assets, GeoIP/Geo-Context, config-tester archives i hardened TCP stream proxying | Wszystko na GitHub |
| v1.3.0 – v1.3.7 | maj 2026 | Linia production PHP-FPM, managed php-fpm supervision, config tester i ACME companion binaries, FIPS/ISO validation tracks, focused cache/proxy profiles i security hardening | Wszystko na GitHub |
| v1.2.0 – v1.2.6 | maj 2026 | Baseline cache i observability z route-scoped cache policy, backendami memory/disk/tiered, encrypted disk cache, peer fill, range caching, Prometheus i OpenTelemetry export | Wszystko na GitHub |
| v1.1.x | 2026 | Linia certificate operations z TLS policy profiles, multi-certificate rustls SNI, managed ACME issuance i renewal, EAB-capable issuers, file-backed TLS secrets i renewal units | Wszystko na GitHub |
| v1.0.0 | 2026 | Gateway foundation z vhost routing, route-level static/proxy/redirect actions, static file serving, reverse proxying, rustls TLS, admin control-plane, secure headers, systemd packaging i rootless containers | GitHub |
| v0.5.0 | Publiczny pre-release | Pierwszy publiczny pre-release milestone przed stabilną linią gateway 1.x | GitHub |
Zobacz Dziennik zmian dla szczegółowych release notes.