# Install static-web-server with Homebrew, Nix, scoop High-performance and asynchronous web server for static files-serving. Version 2.44.0 via Homebrew; verified 2026-08-01. Also installable with nix: nix profile install nixpkgs#static-web-server. ## Install ```sh sudo av install brew:static-web-server ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install static-web-server ``` Evidence: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#static-web-server ``` Evidence: nixpkgs package indexes: pkgs/by-name/st/static-web-server/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ### Windows - Scoop (92%): ```sh scoop install main/static-web-server ``` Evidence: Scoop official bucket manifest trees: bucket/static-web-server.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 ## Package facts - **Package key:** brew:static-web-server - **Package manager:** Homebrew - **Version:** 2.44.0 - **Source summary:** High-performance and asynchronous web server for static files-serving - **Homepage:** - **Repository:** - **Last updated:** 2026-08-01T02:50:39Z - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - static-web-server (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 2.44.0 ## Project history and usage Static Web Server is a Rust command-line HTTP server for serving static files and assets. In package-manager culture it belongs to the small, single-purpose server family: a binary that can be installed quickly, pointed at a directory, and used for local previews, containers, CI jobs, or simple production static hosting. ### Project history The upstream repository was created in September 2019 and the project describes itself as a cross-platform, high-performance asynchronous static-file server. Its README emphasizes a tiny production-ready server built on Rust, Hyper, and Tokio, with HTTP/1, HTTP/2, TLS, compression, directory listings, cache headers, CORS, and other deployment-oriented features. The project moved beyond a local preview utility by publishing release binaries, Docker images, a crates.io package, and official documentation. The v2 series is documented as the stable line while the main branch README identifies an upcoming v3 as still in development. ### Adoption history The input package metadata lists Static Web Server in Homebrew, Nix, and Scoop, which places it in the cross-platform CLI packaging set used by developers on macOS, Linux, and Windows. The official README also highlights prebuilt binaries, Docker images, crates.io, docs.rs, and support for Linux, macOS, Windows, FreeBSD, NetBSD, Android, Docker, and WebAssembly. Its adoption pattern is typical for Rust infrastructure CLIs: package managers provide the executable for day-to-day use, while Docker and static release binaries cover container and server deployments. ### How it is used Common usage is to install the `static-web-server` executable and serve a directory of static content. Configuration can be supplied through command-line flags, environment variables, or a TOML file, making the tool convenient both for one-off local serving and repeatable deployment. ### Why package nerds care Package maintainers care about Static Web Server because it is a modern replacement for ad hoc `python -m http.server` style workflows when users need compression, TLS, headers, logging, Docker images, and static binaries without bringing in a full application server. Its value in package indexes comes from being a small executable with a large practical surface: easy to bottle or cache, useful in CI, and relevant to web projects that only need to ship files. ### Timeline - 2019: Upstream GitHub repository created. - 2019: Early v1 release series published on GitHub. - 2026: Official downloads page listed v2.43.0 with release binaries for multiple platforms. ### Related projects - Related tools include other static-file servers and development preview servers, while the implementation is tied to the Rust Hyper and Tokio ecosystem. ### Sources - - - - input.source_facts.package-manager - input.source_facts.repo ## Security Notes broad file, network, media, or database tool signal. - **Geiger risk:** blue / medium - broad file, network, media, or database tool signal ## 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: ./sws.toml - Windows: .\sws.toml ## Other Package-Manager Records - Nix - static-web-server: normalized package name match | nixpkgs package indexes: pkgs/by-name/st/static-web-server/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - Scoop - main/static-web-server: normalized package name match | Scoop official bucket manifest trees: bucket/static-web-server.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/static-web-server.yml](https://github.com/mxcl/pkgdb/blob/main/combined/static-web-server.yml) ## Sources - 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