…4.0.24-4.0.26 should upgrade immediately. Users of Phusion Passenger for Nginx or do not need to upgrade.
This version also introduces friendly process titles forapplication processes.
Phusion Passenger's core is open source. Please fork or watch us on Github.
If you would …
nginx logs : Your nginx logs are located at /var/log/ nginx.org . Also Martin Fjordvald has a nice post on tuning nginx for high loads , albeit in a context. However he covers both the access and error log and makes some …/. Nginx log events are stored in the yourapp.access.log and yourapp.error.log. The access log contains records of requests made to the web server, with any related errors being sent to the error.log. Further info on nginx logs can be found at
Yes, it should. I have personally tried, , , Unicorn, Thin, and . They all understood PATCH requests out of the box.
Also,should be in general able to issue PATCH requests. For example in curl(1) you'd execute: curl -d'user[name]=wadus' -X PATCH http://localhost:3000/users/1
We would like to thank David Lee for this contribution and endless patience to keep interested in this even after months of …
[ Nginx] The ` issue #401 .` variable is now set correctly for HTTPS connections, even without setting `ssl on`. Fixes
 It is now possible to listen on both a normal and an HTTPS port.
 The `passenger-status` tool now displays rolling restart status.
's core is open source. …
This morning we released Enterprise Chef Server 11.0.2 and Chef Server 11.0.10. We recommend all users upgrade to these new versions to pick up the following security fixes:
Nginx [ CVE-2013-4547] - security restriction bypass flaw due to whitespace parsing
Rails [ CVE-2013-4389] - Possible DoS Vulnerability in Action Mailer
Our currently include things like installing and recipes (from source and through a launchpad repository), , , , haproxy and many other things. The list was literally growing every day for the first few weeks.
Continue reading "Getting the most out of Chef with and vagrant"
InDan Kegel issued a big hairy audacious challenge to web servers:
It's time for web servers to handle ten thousand clients simultaneously, don't you think? After all, the web is a big place now.
This became known as the C10K problem . Engineers solved the C10K scalability problems by fixing OS kernels and moving away from threaded servers like to event-driven servers like Nginx and Node.
Today we are considering an even bigger goal, how to support …
…header on POST and PUT requests, which was causing issues when running a chef server cluster behind nginx. Akzhan also made the webui sort nodes by name, so they'll be easier to find, and patched ohai to support network devices with underscores in the name.
Joshua Sierles, in addition to being one of the earliest adopters of this release and providing invaluable testing for the attribute precedence updates, fixed the ability to access automatic attributes in attribute files.
[Excellent write-up that covers protected downloads using, , the local filsystem, and/or . Awesome.]
A pretty good idea would be to contribute heavily to open source, and then look for work at companies that look at open source work as equivalent to a resume. If you build up enough really good open source work, you'll soon find people clamoring to hire you. [Even with my limited experience, I've found this to be true. Working …
Nginx hardcodes 16KB size in ngx_event_openssl , which you can change and recompile from source.
For other servers, check the documentation!
is latency bound and eliminating extra roundtrips is critical for delivering better performance. All servers are configured to begin new connections with TLS records that fit into a single network segment - it is critical to get useful data to the client as quickly as possible. Your server should do so as well!