The uWSGI project¶
The uWSGI project aims at developing a full stack for building hosting services.
Application servers (for various programming languages and protocols), proxies, process managers and monitors are all implemented using a common api and a common configuration style.
Thanks to its pluggable architecture it can be extended to support more platforms and languages.
Currently, you can write plugins in C, C++ and Objective-C.
The “WSGI” part in the name is a tribute to the namesake Python standard, as it has been the first developed plugin for the project.
Versatility, performance, low-resource usage and reliability are the strengths of the project (and the only rules followed).
Included components (updated to latest stable release)¶
The Core (implements configuration, processes management, sockets creation, monitoring, logging, shared memory areas, ipc, cluster membership and the uWSGI Subscription Server)
Request plugins (implement application server interfaces for various languages and platforms: WSGI, PSGI, Rack, Lua WSAPI, CGI, PHP, Go …)
Gateways (implement load balancers, proxies and routers)
The Emperor (implements massive instances management and monitoring)
Loop engines (implement events and concurrency, components can be run in preforking, threaded, asynchronous/evented and green thread/coroutine modes. Various technologies are supported, including uGreen, Greenlet, Stackless, Gevent, Coro::AnyEvent, Tornado, Goroutines and Fibers)
Note
uWSGI is a very active project with a fast release cycle. For this reason the code and the documentation may not always be in sync. We try our best to have good documentation, but it is a hard work. Sorry for that. If you are in trouble, the mailing list is the best source for help regarding uWSGI. Contributors for documentation (in addition to code) are always welcome.
Quickstarts¶
Table of Contents¶
- Getting uWSGI
- Installing uWSGI
- The uWSGI build system
- Managing the uWSGI server
- Supported languages and platforms
- Supported Platforms/Systems
- Web server integration
- Frequently Asked Questions (FAQ)
- Things to know (best practices and “issues”) READ IT !!!
- Configuring uWSGI
- Fallback configuration
- Configuration logic
- uWSGI Options
- Defining new options for your instances
- How uWSGI parses config files
- uwsgi protocol magic variables
- The uwsgi Protocol
- Managing external daemons/services
- The Master FIFO
- Socket activation with inetd/xinetd
- Running uWSGI via Upstart
- Systemd
- Running uWSGI instances with Circus
- Embedding an application in uWSGI
- Logging
- Formatting uWSGI requests logs
- Log encoders
- Hooks
- Overriding Workers
- Glossary
- uWSGI third party plugins
Tutorials¶
- The uWSGI Caching Cookbook
- Setting up Django and your web server with uWSGI and nginx
- Running uWSGI on Dreamhost shared hosting
- Running python webapps on Heroku with uWSGI
- Running Ruby/Rack webapps on Heroku with uWSGI
- Reliably use FUSE filesystems for uWSGI vassals (with Linux)
- Build a dynamic proxy using RPC and internal routing
- Setting up Graphite on Ubuntu using the Metrics subsystem
Articles¶
uWSGI Subsystems¶
- The uWSGI alarm subsystem (from 1.3)
- The uWSGI caching framework
- WebCaching framework
- The uWSGI cron-like interface
- The uWSGI FastRouter
- uWSGI internal routing
- The uWSGI Legion subsystem
- Locks
- uWSGI Mules
- The uWSGI offloading subsystem
- The uWSGI queue framework
- uWSGI RPC Stack
- SharedArea – share memory pages between uWSGI components
- The uWSGI Signal Framework
- The uWSGI Spooler
- uWSGI Subscription Server
- Serving static files with uWSGI (updated to 1.9)
- SNI - Server Name Identification (virtual hosting for SSL nodes)
- The GeoIP plugin
- uWSGI Transformations
- WebSocket support
- The Metrics subsystem
- The Chunked input API
Scaling with uWSGI¶
Securing uWSGI¶
Keeping an eye on your apps¶
Async and loop engines¶
Web Server support¶
Language support¶
- Python support
- The PyPy plugin
- Running PHP scripts in uWSGI
- uWSGI Perl support (PSGI)
- Ruby support
- Using Lua/WSAPI with uWSGI
- JVM in the uWSGI server (updated to 1.9)
- The JWSGI interface
- The Clojure/Ring JVM request handler
- Introduction
- Building the JVM support
- Exposing functions via the RPC subsystem
- Registering signal handlers
- The fork() problem and multithreading
- How does it work?
- Passing options to the JVM
- Loading classes (without main method)
- Request handlers
- Notes
- The Mono ASP.NET plugin
- Running CGI scripts on uWSGI
- The GCCGO plugin
- The Symcall plugin
- The XSLT plugin
- SSI (Server Side Includes) plugin
- uWSGI V8 support
- The GridFS plugin
- The GlusterFS plugin
- The RADOS plugin
Other plugins¶
Broken/deprecated features¶
Release Notes¶
Stable releases¶
- uWSGI 2.0.18
- uWSGI 2.0.17.1
- uWSGI 2.0.17
- uWSGI 2.0.16
- uWSGI 2.0.15
- uWSGI 2.0.14
- uWSGI 2.0.13.1
- uWSGI 2.0.13
- uWSGI 2.0.12
- uWSGI 2.0.11.2
- uWSGI 2.0.11.1
- uWSGI 2.0.11
- uWSGI 2.0.10
- uWSGI 2.0.9
- uWSGI 2.0.8
- uWSGI 2.0.7
- uWSGI 2.0.6
- uWSGI 2.0.5
- uWSGI 2.0.4
- uWSGI 2.0.3
- uWSGI 2.0.2
- uWSGI 2.0.1
- uWSGI 2.0
- uWSGI 1.9.21
- uWSGI 1.9.20
- uWSGI 1.9.19
- uWSGI 1.9.18
- uWSGI 1.9.17
- uWSGI 1.9.16
- uWSGI 1.9.15
- uWSGI 1.9.14
- uWSGI 1.9.13
- uWSGI 1.9.12
- uWSGI 1.9.11
- uWSGI 1.9.10
- uWSGI 1.9.9
- uWSGI 1.9.8
- uWSGI 1.9.7
- uWSGI 1.9.6
- uWSGI 1.9.5
- uWSGI 1.9.4
- uWSGI 1.9.3
- uWSGI 1.9.2
- uWSGI 1.9.1
- uWSGI 1.9
Contact¶
Mailing list |
|
Gmane mirror |
|
IRC |
#uwsgi @ irc.freenode.org. The owner of the channel is unbit. |
Commercial support |
.
Commercial support¶
You can buy commercial support from http://unbit.com
Donate¶
uWSGI development is maintained by Unbit . You can buy commercial support and licensing. If you are not an Unbit customer, or you cannot/do not want to buy a commercial uWSGI license, consider making a donation. Obviously please feel free to ask for new features in your donation.
We will give credit to everyone who wants to sponsor new features.
Check http://unbit.it/uwsgi_donate for the donation link.