include additional nginx configuration for Passenger Standalone

[Yar Dmitriev]

Hi

3.0 seems amazing in its usefulness and quality of code!

It would be a substantial improvement, though, if Passenger Standalone
also automatically included fragments of nginx configuration files
from the project directory.

For example:

conf/nginx_http.conf
conf/nginx_server.conf

into the respective parts of the nginx.conf.erb that Passenger is
using internally.

Or, alternatively, would provide a command line option to override the
nginx config file altogether.

Many of our projects depend heavily on custom nginx configuration.
These configurations, for example, are mapping some too-bulky file
assets from outside of the Rails project tree and supporting
redirections from numerous legacy URLs. Also the module
nginx_upload_module that we use to report upload progress back to the
Rails app requires configuration too.

Yet it would be very attractive to use Passenger Standalone for its
portability and ease of moving between developer/designer machines.

Best regards
--
Yaroslav Dmitriev

[DrMark]

Yar,

I recently asked about using Passenger stand-alone in development with
the proxy module to reverse proxy calls to a web service. Basically, I
was told to not touch the configuration files for Passenger stand-
alone. If I needed anything more than they offered, I should install
my own version of Passenger. I have done this and things are working
fine.

I do like your idea of automatically including configuration files in
your application, but I am not sure how widely this feature would be
used. It may not be used widely enough for the effort of making it
happen.

Best regards,

Mark

[Robert Rouse]

Passenger Standalone doesn't mean it's "Standalone"

You stick a webserver in front of it. Your webserver can handle the stuff you want to do.

--
You received this message because you are subscribed to the Google Groups "Phusion Passenger Discussions" group.
To post to this group, send email to phusion-...@googlegroups.com.
To unsubscribe from this group, send email to phusion-passen...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/phusion-passenger?hl=en.

[Hongli Lai]

We do not plan on supporting this. Phusion Passenger Standalone is
meant to be its own web server, designed to handle the most basic use
cases very very well at the expense of customizability. That it
happens to be using Nginx under the hood today is an implementation
detail that the user should not bother with; it may very well happen
that we one day swap Nginx with something else. If you want any kind
of complex customization you should use Phusion Passenger for Nginx
instead.

--
Phusion | The Computer Science Company

Web: http://www.phusion.nl/
E-mail: in...@phusion.nl
Chamber of commerce no: 08173483 (The Netherlands)

[Hongli Lai]

On Mon, Nov 12, 2012 at 2:27 PM, beez <mshu...@gmail.com> wrote:
> Hello,
>
> If we are not to alter the Passenger Standalone configuration, I am unclear
> about the default behavior with regards to the reverse proxy.
>
> 1) When I launch Standalone using 'passenger start', is it by default in
> reverse-proxy mode?
>
> 2) If not, as I understand from this thread, it is not possible to set it
> up as a proxy and thus I would have to install the Nginx version of
> Passenger and configure that for reverse proxy. Is this correct?

The answer for (1) is "not applicable", and the answer for (2) is "not correct".

When you start Standalone, it will listen on a specific port using the
regular HTTP protocol. You can set this up in a reverse proxy
configuration, exactly like how you would setup Thin, Unicorn,
Mongrel, or whatever in a reverse proxy configuration. There is no
special "reverse proxy mode", it was and is already reverse proxyable
because it's HTTP.


--
Phusion | Ruby & Rails deployment, scaling and tuning solutions