Install uwsgi with Homebrew, apk, apt, dnf, Nix, pacman, zypper

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• uwsgi

Project history

The uWSGI documentation says the project has had users and contributors since 2009 and that the WSGI part of the name is a tribute to Python's Web Server Gateway Interface because WSGI was the first developed plugin. The docs also note that, despite the name, the project grew into a pluggable multi-language hosting system rather than only a Python WSGI server.

uWSGI's architecture evolved around a shared core and plugins. The official index lists request plugins for WSGI, PSGI, Rack, Lua WSAPI, CGI, PHP, Go, gateways for load balancers and routers, loop engines for preforking, threaded, async/evented, and green-thread modes, and the Emperor for managing many instances.

The official project page currently marks uWSGI as being in maintenance mode, with bug fixes and updates for new language APIs rather than rapid feature development. Recent changelog files in the official documentation repository label modern releases as maintenance releases.

Adoption history

uWSGI became a staple of classic Python web deployment because it connected Python WSGI applications to production web servers and process-management patterns. Official quickstarts and tutorials document Django/nginx setups, Heroku usage, systemd, Upstart, Circus, socket activation, logging, graceful reloads, and many operational modes.

Its adoption also spread beyond Python through plugins and protocol support. The Rack quickstart, for example, explains Ruby/Rack operation, modular distribution packages, nginx integration through the uwsgi protocol, process/thread concurrency, and config-file usage.

How it is used

The package-nerd usage is usually a system or Homebrew package providing the `uwsgi` executable, with deployments configured through command-line flags or config files in INI, XML, JSON, YAML, and other supported formats. Operators often place uWSGI behind nginx or another front server, run multiple workers, enable the master process, and manage reload behavior.

uWSGI is also a source-build and distro-packaging story. The official build-system docs explain that its build approach dates to 2009 project guidelines and intentionally depends mainly on a C compiler and a Python interpreter, a choice made for sysadmin-oriented source builds and fast project evolution.

Why package nerds care

uWSGI is significant because it represents the older, operations-heavy side of Python packaging: C extensions, plugin builds, distro-specific modular packages, protocol integration, service managers, config formats, and long-running daemon behavior. It is less fashionable than newer ASGI servers, but it remains a key package in the history of Python deployment tooling.

For maintainers, uWSGI is a reminder that packaging an application server is not just placing a binary on PATH. The package has to account for plugins, language headers, compiler behavior, web-server integration, security fixes, service managers, and maintenance releases across operating systems.

Timeline

• 2009: Official docs describe the first public release era and thank users and contributors since 2009.
• 2010s: uWSGI expanded around plugins, gateways, loop engines, the Emperor, and multi-language hosting modes.
• 2022-2026: Official project materials describe maintenance mode, and changelogs list maintenance releases for the 2.0 series.

Related projects

• WSGI is the Python interface that gave uWSGI its name and its first plugin.
• nginx, Apache/mod_proxy_uwsgi, Gunicorn, PSGI, Rack, PHP, Go, Gevent, Greenlet, Tornado, systemd, Upstart, and Circus are related integration or deployment surfaces documented by uWSGI.

Sources

• https://github.com/unbit/uwsgi - Official repository describes uWSGI as an application server container and repeats the maintenance-mode note.
• https://uwsgi-docs.readthedocs.io/en/latest/ - Official docs describe the project scope, plugin architecture, maintenance mode, and since-2009 note.
• https://uwsgi-docs.readthedocs.io/en/latest/BuildSystem.html - Official build-system docs describe 2009 project guidelines and the C-compiler/Python-interpreter build approach.
• https://uwsgi-docs.readthedocs.io/en/latest/RackQuickstart.html - Official Rack quickstart documents plugins, nginx integration, workers, master process, and config-file usage.
• https://uwsgi-docs.readthedocs.io/en/latest/articles/SerializingAccept.html - Official article describes early project concerns, hosting-company origins, and first public release-era locking work.