Hi, the (tiny) attached patch enable support for new websockets handling when the uwsgi protocol is used instead of HTTP. I have tested it with various websocket libraries and with the api available in uWSGI 1.9. From 1.9 sources (with nginx pointing to uwsgi port 3031): ../uwsgi -s :3031 -w tests.websockets_echo --gevent 10 no additional configuration is needed for nginx -- Roberto De Ioriby roberto - Nginx Mailing List - English
> FastCGI is language-independent and like cgi can serve all languages, but > setting up nginx with fcgiwrap and spawn-fcgi is only used for serving > Perl. > Almost all tutorials and instructions use this method for Perl-FasctCGI. > For > serving Pythong scripts, the dominant method is uWSGI. > > Is there any limitation for using FastCGI for Python that it is not usual? &gby roberto - Nginx Mailing List - English
Il giorno 30/ago/2012, alle ore 19:12, David | StyleFlare <david@styleflare.com> ha scritto: > I am trying to figure out what I dont see request headers added to the request. > > I am trying to add 'X-Server-ID: $id' > > Here is a snippet form my config. > > location /{ > more_set_input_headers 'X-Server-ID: $id'; > more_set_headers 'X-Server-ID: $id'; &gby roberto - Nginx Mailing List - English
> Hi Roberto, > > Thanks for the prompt response. That really helps. > > Our major consideration for going with Nginx is performance. > If we have another process running (a wsgi server with python application) > and nginx working as a proxy translating HTTP requests to another protocol > (uwsgi, http or fastcgi), won't that be an overhead? Yes, there is an overhead, butby roberto - Nginx Mailing List - English
> Hi, > > > > We are building a Media Content Management and Delivery Platform based on > Python (and python based web framework like Pylons/Pyramid). We are > planning > to use nginx as the web server. > > > > We are new to nginx (have prior experience with Apache) and have > downloaded > 1.2.1. The OS is CentOS. > > > > We are not sure how uwby roberto - Nginx Mailing List - English
Il giorno 20/mar/2012, alle ore 12:10, Delai S. ha scritto: > My be the question is: HOW CAN I TELL UWSGI to run index.php defaultly? --php-app <path_to_php_file> > -- Roberto De Ioris http://unbit.it JID: roberto@jabber.unbit.it _______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginxby roberto - Nginx Mailing List - English
> Roberto De Ioris wrote in post #1052159: >>>>> How would I then proceed to build the uWSGI php plugin? >>>> if all goes well you will end with a binary named 'uwsgi' >>>> >>> >>> server { >>> listen 8080; >>> server_name www.myphp.com myphp.com; >>> location ~ .php { >>>by roberto - Nginx Mailing List - English
> > > > There should be not much difference in both (or php-fastcgi), the only > thing that came to my mind is in different configuration. > > Best way to test is in using both with a single process, or with the same > number of processes (adaptive process spawning is completely different > from the php-fpm one so i would not expect a fair comparison). But again, > doby roberto - Nginx Mailing List - English
> > Hello Roberto, > > > Thank you for so cute plugin. > > > > I'd tested the PHP-FPM and uWSGI-PHP at the same box. They can be > configued to run at the same time to the same scripts. > > > I found from the scripts's spend time that PHP-FPM is a little faster than > uWSGI-PHP, about 0.010ms ~0.030ms faster than uWSGI-PHP. > > > I wonder if is tby roberto - Nginx Mailing List - English
> Roberto De Ioris wrote in post #1048644: >>> --with-mysqli=mysqlnd --with-pdo-mysql=mysqlnd --with-openssl >>> --with-xmlrpc --with-xsl --with-bz2 --with-gettext >>> --with-fpm-user=www-data --with-fpm-group=www-data --disable-debug >>> --enable-fpm --enable-exif --enable-wddx --enable-zip --enable-bcmath >>> --enable-calendar --enable-ftp --enableby roberto - Nginx Mailing List - English
I am pleased to announce the 1.1 release of the uWSGI project. This release focuses on a new option parser subsystem, improved perl/psgi and ruby/rack support and a new (stable) php plugin. A lot of optimizations have been introduced for the fastrouter and the various threading modes. This is the first release officially deprecating some old-style configuration (see notes). Changelog [20120317]by roberto - Nginx Mailing List - English
> > Thanks for the heads up on uWSGI. But my sysadmin skills are basic (I'm > a developer really) and it looks a bit scary. There's not much info out > there, while fastcgi is supported in the php core. For someone who is > not a proper sysadmin, is uWSGI, in its present state of development, > really a sensible way to go? > php-fpm (far better that the fastcgi embedded serveby roberto - Nginx Mailing List - English
> Roberto > >> I am not a big fan of opcode caching > > I'm interested in your reasons for this. My experience with mod_php is > that I get huge performance improvements with opcode caching (my app > loads a lot of code and libraries). If you don't use opcode caching, is > there a better way to get the same benefits? > Your answer, is my reason :) It is app-dependenby roberto - Nginx Mailing List - English
> Hi folks > > Thinking of abandoning mod_php for the wonderful world of nginx, but > googling the issue of opcode caching with fastcgi is proving > surprisingly confusing: there's a lot of conflicting information out > there. > > My basic question is this: what is the most performant, > memory-efficient, Slashdot resistant way to set up nginx for running a > complexby roberto - Nginx Mailing List - English
> I've tried that, but same result: > > LDFLAGS="-Lpath" LD_RUN_PATH="/opt/php5/lib/libphp5.so" python > uwsgiconfig.py --plugin plugins/php it must be LDFLAGS="-L/opt/php5/lib/" LD_RUN_PATH="/opt/php5/lib/" > using profile: buildconf/default.ini > detected include path: ['/usr/lib/gcc/x86_64-linux-gnu/4.6.1/include', > '/usr/local/by roberto - Nginx Mailing List - English
> Thanks for all the help so far Roberto. > > When I run > > python uwsgiconfig.py --plugin plugins/php > using profile: buildconf/default.ini > detected include path: ['/usr/lib/gcc/x86_64-linux-gnu/4.6.1/include', > '/usr/local/include', > '/usr/lib/gcc/x86_64-linux-gnu/4.6.1/include-fixed', > '/usr/include/x86_64-linux-gnu', '/usr/include'] > *** uWSGI buildingby roberto - Nginx Mailing List - English
> I'm a bit stuck with 'running the php script in the uWSGI server' > > My PHP is built from source, as far as I understand I need to build it > with --enable-embed > > ./configure --prefix=/opt/php5 --with-config-file-path=/opt/php5/etc > --with-config-file-scan-dir=/opt/php5/etc/conf.d --with-curl > --with-mhash --enable-cgi --with-pear --with-gd --with-jpeg-dir > --wiby roberto - Nginx Mailing List - English
> I tried building this on my Ubuntu 11.10 server with nginx-1.0.12 > > ./configure \ > --prefix=/opt/nginx \ > --conf-path=/etc/nginx/nginx.conf \ > --pid-path=/var/run/nginx.pid \ > --lock-path=/var/lock/nginx.lock \ > --http-log-path=/var/log/nginx/access.log \ > --error-log-path=/var/log/nginx/error.log \ > --http-client-body-temp-path=/var/lib/nginx/body \ > -by roberto - Nginx Mailing List - English
> On 2012-02-24 17:46, Roberto De Ioris wrote: >> Be sure to fully rebuild (do a make clean) uWSGI if you have added >> devel packages during php_plugin compilation as they can modify CFLAGS >> setup > > Thank you, it's working fine now. The DOCUMENT_ROOT (or something else) > doesn't seem to be passed properly though? I get "Not Found" (uwsgi's?) > unlesby roberto - Nginx Mailing List - English
> On 2012-02-24 16:23, Roberto De Ioris wrote: >> In my company, we are using this plugin proxied behind nginx from about >> 2 >> weeks without problems. Every report will be wellcomed. >> > > Segfaulted on my server. > > !!! uWSGI process 31078 got Segmentation Fault !!! > *** backtrace of 31078 *** > ./uwsgi(uwsgi_backtrace+0x2a) [0x80779ea] > ./uwby roberto - Nginx Mailing List - English
Hi everyone, uWSGI has got a new php plugin, allowing you to run php apps at full speed (read: not in CGI mode) and getting all of the uWSGI features (like adaptive process spawning and jailing technics). In addition to this a bunch of uwsgi api functions has been added, allowing your php apps to interact with other apps hosted in uWSGI. http://projects.unbit.it/uwsgi/wiki/PHP The build systemby roberto - Nginx Mailing List - English
After 2 years of development, the uWSGI project is at 1.0 This major release focuses on adaptive process spawning (--cheaper mode), the new stats framework, Mules and an incredible amount of bug fixes and code refactoring. Changelog: - adaptive process spawning (--cheaper option) - new control options --stop, --reload, --suspend, --resume, --pause - stats framework http://projects.unbit.it/by roberto - Nginx Mailing List - English
Hi everyone, i have just released a cgi_plugin for the uWSGI server. This allows nginx to easily run cgi scripts passing requests to the uWSGI server (very similar to the current fcgiwrap solution, but with all of the features of uWSGI and with an implementation fully compatible with apache) Here is a preliminary doc: http://projects.unbit.it/uwsgi/wiki/CGI The plugin should be versatile enougby roberto - Nginx Mailing List - English
> On Saturday 03 December 2011 16:44:56 etrader wrote: >> Thanks James! >> The idea of building a mini-webserver for C programming is brilliant. I >> searched a lot to find a guidance for building very basic web server in >> C (obviously I prefer to write the web server in C with native API for C >> files); but I was unable to find. All web servers in C are advanceby roberto - Nginx Mailing List - English
> I am running Trac inside uWSGI, with nginx as front-end server. I have > also set up basic http authentication in nginx. Now, theoretically, > when authenticated in nginx, Trac should recognize the user and > display its name, identify the new tickets, etc. But that is not > happening. > > How can make sure the authentication information is being sent to > uWSGI and receiby roberto - Nginx Mailing List - English
> > On Oct 12, 2011, at 5:09 AM, Igor Sysoev wrote: >> >> BTW, I know that some people prefer to use uWSGI server for python. >> > > I prefer frameworks like gunicorn that use plain HTTP. uWSGI suggests using the uwsgi protocol to improve performance and to add some specific feature, but you can run it in http, fastcgi and zeromq mode. > -- Roberto De Ioris htby roberto - Nginx Mailing List - English
Hi everyone, i am pleased to announce a new major release of the uWSGI project. The 0.9.9 version focuses on optimizations in various area, an improved spooler and native gevent support. A new python-specific feature is the 'pyshell': adding --pyshell to your options will run a python shell in the uwsgi environment (useful for testing the uwsgi api). The rack plugin has been improved and the olby roberto - Nginx Mailing List - English
Il giorno 17/ago/2011, alle ore 06:58, yejun ha scritto: > I have tried this. The uwsgi server gives an error > > > INVALID PROTOCOL: > () {22 vars in 803 bytes} => generated 45 bytes in 0 msecs ( 500) 2 headers in 63 > bytes (0 switches on core 0) > > > My uwsgi is a django app, the command line looks like this > > > uwsgi --uid 1000 -H /mnt/pytby roberto - Nginx Mailing List - English
Il giorno 17/ago/2011, alle ore 05:10, yejun ha scritto: > I tried use uwsgi_params, but the uwsgi server will fail to pass it. The directive is uwsgi_param KEY VALUE; You have to put them under a location stanza: location / { include uwsgi_params; uwsgi_param FOO bar; uwsgi_param fookey fooval; uwsgi_pass 127.0.0.1:3031; } They will be blindly put in your app request dby roberto - Nginx Mailing List - English
Hi everyone, i am pleased to announce the second maintenance release for uWSGI 0.9.8 This release focuses on a better Spooler, binary file embedding in server core and support for plugins/apps written in C++ * 0.9.8.2 [20110719] - fixed an ini and yaml parsing bug spotted by Raffaele Colace - spooler has been extremely improved the 'at' and 'body' options have been added to allows executing tby roberto - Nginx Mailing List - English