bgror

Launching unofficial, automatically updated Github mirror for the Nginx SVN repository »

Created at: 09.08.2011 19:34, source: Phusion Corporate Blog, tagged: nginx programming Software

I probably don’t need to tell you what a great web server Nginx is. It’s lightweight, it’s fast, it’s scalable, and many people like it for its configuration file syntax yet flexible features. It’s no surprise that Nginx is doing a great job serving as a core for Phusion Passenger Standalone (our Ruby/Rails web application server which supports Apache and Nginx).

Nginx’s development has traditionally been behind closed doors. Nginx is written for the most part by one brilliant man, Igor Sysoev, who accepts patches on the Nginx mailing list. But for a long time there was no source repository with which contributors and interested people can track the development process, and no official bug tracker. All of that have changed in 2011. Igor has established Nginx as a company. The Nginx SVN repository is now open to the public and a few days ago they even opened a Trac. In short: a lot of great news lately.

Announcing the Github Nginx mirror

These days a lot of people have switched from Subversion to Git. When you’ve worked with Git for a while, Subversion probably feels archaic and unproductive. The “killer app” for Git is Github, which provides an unbeatable collaboration experience. Indeed, many projects that have switched to Github reported a dramatic increase in contributions!

In order to stimulate Nginx development, we’ve launched a Github mirror of the Nginx SVN repository:

• Github page: https://github.com/phusion/nginx
• Git URL: git://github.com/phusion/nginx.git

A few notes about this mirror:

• It’s automatically updated twice a day.
• It’s read-only. We don’t accept pull requests. Changes should be sent to the Nginx mailing list in the form of patches.
• We intentionally don’t mirror all the branches and tags, only the most recent ones, because we don’t believe the old branches and tags are useful to anybody.
• Please feel free to contact us if you have an issue with our mirror.

Happy developing!

[Update] Nginx Update Coming Wednesday »

Created at: 14.05.2011 04:19, source: Engine Yard Blog, tagged: Product appcloud nginx passenger

MAY 15, 2011 UPDATE: We've decided to postpone this update until Wednesday, May 18, 2011 in order to give you some additional time to review the necessary information and ensure that you are prepared. We hope that you will benefit from this nginx update. On Monday, May 16, 2011 Wednesday, May 18, 2011 we will release an updated version of the ngnix web server to our AppCloud technology stack in addition to a few other minor stack updates. All customers not using Passenger 2 will be updated to 0.8.54. This change happens when the “Update” button is clicked. Highlights of this update include –

• Increased alignment with “Nginx Best Practices” by replacing If statements with try_files.
• Reduction of 502 Gateway errors on Passenger via increased standardization across stack components.

Quick TIp, solve nginx issue with Typo5 »

Created at: 25.03.2010 20:02, source: Hackido, tagged: linux nginx

Quick Tip: Compiile nginx/passenger with SSL »

Created at: 10.02.2010 22:34, source: Hackido, tagged: rails nginx ssl

Nginx Security Vulnerability: SSL Man in the Middle Attack »

Created at: 10.11.2009 19:30, source: Engine Yard Blog, tagged: News nginx security vulnerability

A security vulnerability in all versions of nginx (as well as several other web servers) has been reported. Attackers can exploit this vulnerability by intercepting SSL sessions and compromising encryption key renegotiation via a plaintext injection, allowing the attacker to read the plaintext of the SSL session. A patch has been released for this vulnerability.

Engine Yard customers have already been contacted via email about this issue. For Engine Yard Cloud customers, this patch will be automatically applied the next time you perform a deploy. All other customers should open a support ticket so that you can arrange an appropriate maintenance window with support.