On Sat, Nov 16, 2013 at 6:03 PM, Eric Mill <[email protected]> wrote:
> I did misread the docs, and missed that Standalone mode is free. However, it
> doesn't actually feel very standalone, shipping with nginx compiled inside
> it -- it's the same clunky situation as non-Standalone mode! You've just
> made it easier to forget that the problem is there.

Hi Eric.

Actually the standalone mode *is* fully standalone. The fact that it
is powered by an Nginx core is an implementation detail. As a user,
you never have to deal with it directly. Using the standalone mode you
never have to touch the Nginx config file, or start/stop Nginx, etc.
There is only the 'passenger' command.

I understand that you might *feel* that it is not standalone because
there is an Nginx in it. But consider what the alternative would be:
to implement an HTTP server ourselves. And why would we want to do
that? Nginx is awesome, it's a wonderful HTTP server. Why reimplement
the wheel? Reusing Nginx makes a lot of sense. The result is still
small and lightweight.

It is also not "a patched Nginx". It is just Nginx, with an extra
module added to it.

Of course, if you have specific criticisms against the implementation,
I'm very open to hearing them. Passenger is under active development
and any issues can be addressed.


> Looking closer, I see Passenger continues to impose requirements on my app's
> structure (app.js, a public dir, a tmp dir). Those kinds of requirements,
> that either straitjacket you or force you to manage vestigial filesystem
> cruft, were very nice to leave behind when I moved from Passenger to Unicorn
> in my Ruby apps years ago, and in leaving Capistrano behind for Fabric.

These requirements are merely conventions. If you do not like these
requirements, they can easily be made optional in the next version (a
few weeks from now). Would you like me to go ahead and do so?

You believe that Passenger does too much and is too tightly coupled. I
am stressing the point that that is merely in appearance only. Code
speaks louder than words, so if you have any specific concerns, I'm
all ears.

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

Web: http://www.phusion.nl/
E-mail: [email protected]
Chamber of commerce no: 08173483 (The Netherlands)

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to