A little tiny bug in Phusion Passenger 2.0.5

If you are using Phusion Passenger like me, I believe you would love it very much. It is such an effort saver. So I've put it on all my machines, even on my dev. , testing and staging machines. But some times I want my Rack apps started in a development mode, so I went through Passenger's document, and added RackEnv environtment variable.

	<VirtualHost *:80>
	ServerName app.myapp.com
	DocumentRoot /Users/zhonghai/apps/ruby/current/public
	# setting the env to development
	RackEnv development
	</VirtualHost>

view raw httpd.conf.xml hosted with ❤ by GitHub

After a restart, I've found that the app was still in production mode. Just played with it for a while and added some debug info, finally I found a workaround, that is, put the RackEnv outside the VirtualHost block.

	# setting the env to development
	RackEnv development
	<VirtualHost *:80>
	ServerName app.myapp.com
	DocumentRoot /Users/zhonghai/apps/ruby/current/public
	</VirtualHost>

view raw httpd.conf.xml hosted with ❤ by GitHub

I am hoping this will save you some time.

P.S. I've submitted a bug report on the issue tracker