Support team says Nginx + Passenger harder to support than Apache

[Scott Larson]

     Frankly it sounds more like laziness or being averse to change. All I
can relay is experience with our setup here which is purely FreeBSD with an
internal Poudriere based package build server, and system/config management
with Salt. Taken as a whole it's a painless and relatively trivial process
to keep nginx+modules fully up to date and pushed to all the servers. In
your case the key part is the management layer. Salt, Ansible, Chef,
Puppet, whatever, those things do the true heavy lifting once your server
count rises to greater than two and completely levels the field for ease of
updates between nginx and Apache.
     I will say the Passenger module seems to be one of those which goes
through fits of updates which if I had to use it would be mildly irksome
for non-technical reasons. But with a proper method of package deployment
it remains an easy job. Even if nginx were slightly harder to keep updated,
which again it's not, I'd still go through the trouble simply for the
performance circles it runs around Apache.



*__________________Scott LarsonSystems AdministratorWiredrive/LA310 823
8238 ext. 1106310 943 2078 faxwww.wiredrive.com
<http://www.wiredrive.com/>www.twitter.com/wiredrive
<http://www.twitter.com/wiredrive>www.facebook.com/wiredrive
<http://www.wiredrive.com/facebook>*

On Tue, Sep 30, 2014 at 9:50 AM, Dewangga <dewanggaba at xtremenitro.org>
wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Are you using system and/or config management to manage your third
> party software? IMHO, nginx and apache is same, the different is only
> on configuration and performance.
>
> Pkgs, pacthes, updates, etc depend on each linux distribution. IMHO.
>
> On 9/30/2014 23:41, drfence wrote:
> > I work for a big news organization in the South East..  The support
> > team is arguing that it's more difficult to support Nginx +
> > Passenger because any patches, etc are made by updating source (
> > compiling modules statically ) and re-installing.  This is as
> > opposed to Apache that can be updated using yum with pre-built
> > binaries.
> >
> > Curious what people on this mailing list say about the support
> > team argument.
> >
> > Posted at Nginx Forum:
> > http://forum.nginx.org/read.php?2,253635,253635#msg-253635
> >
> > _______________________________________________ nginx mailing list
> > nginx at nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
> >
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.17 (MingW32)
>
> iQEcBAEBAgAGBQJUKt9tAAoJEF1+odKB6YIxXmcH/R2XEajEDZ/ugiVEt0r56d44
> EoGN+xtno1a1M3/5VuhpFBdK2D/MXxus7RxuS9HhNAovNMTWgjmee5pulhyeYyOW
> uX9B5zdXtXRl9eTaGU+646d1lAEYv1HXpHuRxX8rUVFXF2ZFj4rLqEttk8+zj/5s
> 0vsT/p9CCQDgpugyUdWClkXsadMGUVOat6huVg5Wbo06dGuqu7IxbZpSGMA/7HG1
> IGLLFbgH4+botm7knQCr1UwooQC6OI7N8vF8aV0f7LYwmZ/ZBkAOLwW0TQbFPld9
> ap993bpRJ6EAlVZqTgwSzxRjzxPZKYB/6JtDXM2hO1SNGMvOe8N3MyKmqr/pK4E=
> =Piv4
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140930/d7d029bf/attachment.html>