サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
Pixel 9
uwsgi-docs.readthedocs.io
After having forked itself a bunch of times, each process will generally start blocking on accept() The funny problem is that on older/classic UNIX, accept() is woken up in each process blocked on it whenever a connection is attempted on the socket. Only one of those processes will be able to truly accept the connection, the others will get a boring EAGAIN. This results in a vast number of wasted
The Art of Graceful Reloading¶ Author: Roberto De Ioris The following article is language-agnostic, and albeit uWSGI-specific, some of its initial considerations apply to other application servers and platforms too. All of the described techniques assume a modern (>= 1.4) uWSGI release with the master process enabled. What is a “graceful reload”?¶ During the life-cycle of your webapp you will relo
Setting up Django and your web server with uWSGI and nginx¶ This tutorial is aimed at the Django user who wants to set up a production web server. It takes you through the steps required to set up Django so that it works nicely with uWSGI and nginx. It covers all three components, providing a complete stack of web application and server software. Django is a high-level Python Web framework that en
Things to know (best practices and “issues”) READ IT !!!¶ Obviously, never expose a socket speaking the uwsgi protocol to the public network unless you know what you are doing. That channel allows for dynamic loading of applications (read: arbitrary execution of code). The protocol is meant to be sanitized/validated by a proxy like nginx, apache, the uWSGI routers, etc. For example, if uwsgi uses
Quickstart for Python/WSGI applications¶ This quickstart will show you how to deploy simple WSGI applications and common web frameworks. Python here is meant as CPython, for PyPy you need to use the specific plugin: The PyPy plugin, Jython support is under construction. Note You need at least uWSGI 1.4 to follow the quickstart. Anything older is no longer maintained and is highly buggy! Tip When y
The PyPy plugin¶ Requires uWSGI >= 2.0.9 Introduction¶ Idea/Design: Maciej Fijalkowski Contributors: Alex Gaynor, Armin Rigo A new PyPy plugin based on cffi is available since uWSGI 1.9.11. The old slow cpyext-based one has been removed from the tree. The plugin is currently supported only on Linux systems. Following releases will support other platforms as well. The plugin loads libpypy-c.so on s
Note The project is in maintenance mode (only bugfixes and updates for new languages apis). Do not expect quick answers on github issues and/or pull requests (sorry for that) A big thanks to all of the users and contributors since 2009. The uWSGI project¶ The uWSGI project aims at developing a full stack for building hosting services. Application servers (for various programming languages and prot
Nginx support¶ Nginx natively includes support for upstream servers speaking the uwsgi protocol since version 0.8.40. Configuring Nginx¶ Generally you only need to include the uwsgi_params file (included in nginx distribution), and set the address of the uWSGI socket with uwsgi_pass directive
The uWSGI Emperor – multi-app deployment¶ If you need to deploy a big number of apps on a single server, or a group of servers, the Emperor mode is just the ticket. It is a special uWSGI instance that will monitor specific events and will spawn/stop/reload instances (known as vassals, when managed by an Emperor) on demand. By default the Emperor will scan specific directories for supported (.ini,
このページを最初にブックマークしてみませんか?
『uwsgi-docs.readthedocs.io』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く