<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p>If you're on Ubuntu you have some tradeoffs by doing this
yourself.</p>
<p>You can surely uninstall the packages of nginx from Ubuntu and
then compile and install it yourself on each system. However, you
will then need to redo this compiling and patch software
yourself. This is why the packaging exists in Ubuntu - to allow
easy installation and patching of security vulns from the Security
team (yes, Ubuntu Security Team and Ubuntu Server Team both work
to patch nginx in the various releases of Ubuntu!).</p>
<p>You will lose that automated security patching, etc. and will
have to recompile your software on every machine every time
there's a security update if you do this yourself.</p>
<p>You can do the packaging yourself in a private repository (which
will be basically a 'from source' compile with the configure
options, etc. YOU want there to be), and then that package
installs the compiled binaries, etc. to whatever system you
install that package on, but again you then have to patch it
yourself.</p>
<p><br>
</p>
<p>There's pros and cons to every approach, especially security
related concerns for software patching. The question is, how big
is this 'production environment' and do you want to have to
recompile and reinstall every time there's a patch for a security
problem.</p>
<p><br>
</p>
<p><br>
</p>
<p>Thomas</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 10/13/22 12:02, edflecko wrote:<br>
</div>
<blockquote type="cite" cite="mid:CAFS4T6b3sgU_vutzEh_2k0OZuj1iGZ0kAo0Y1iTERskfnn75dA@mail.gmail.com">
<div dir="ltr">
<div>Thank you for your reply!</div>
<div><br>
</div>
<div>I should have mentioned that I'm running in an Ubuntu
environment so I'm not sure if that makes much difference? I
like the idea of installing from source because I can control
all of the options, but I'm wondering if it's worth going that
route in a production environment?</div>
<div><br>
</div>
<div>Thoughts? Opinions?<br>
</div>
<div><br>
</div>
<div>Ed<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Oct 13, 2022 at 3:49
PM PGNet Dev <<a href="mailto:pgnet.dev@gmail.com" moz-do-not-send="true" class="moz-txt-link-freetext">pgnet.dev@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Nginx
is an easy build from source, thankfully.<br>
<br>
Deploying tarbal'd local source-builds to other machines is
not terrible at all if you isolate your install DIR (e.g,
'everything' under /opt/nginx); ansible is your friend.<br>
<br>
But, it's a bit of a slog to deploy into usual distro env,
avoid collisions, and if needed, cleanly uninstall. Certainly
doable, but can be messy.<br>
<br>
To solve for that inconvenience, build your own packages from
own sources on an open build system (e.g., SUSE's OBS,
Fedora's COPR, etc), and install those packages via rpms.<br>
Or for that matter, even local rpmbuilds should be portable,
as long as you correctly account for differences in target
deployment ENVs.<br>
<br>
yes, rpm .spec files can be annoying. it's a trade-off.<br>
<br>
<br>
> I'm curious how many people run Nginx in a production
environment that was installed from source and not a package.<br>
> <br>
> For those people who are running Nginx in this manner,
how do you keep Nginx patched when patches are released?<br>
> <br>
> How do you upgrade your existing Nginx in your production
environment while minimizing downtime?<br>
> <br>
> Thank you,<br>
> Ed<br>
> <br>
> _______________________________________________<br>
> nginx mailing list -- <a href="mailto:nginx@nginx.org" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">nginx@nginx.org</a><br>
> To unsubscribe send an email to <a href="mailto:nginx-leave@nginx.org" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">nginx-leave@nginx.org</a><br>
<br>
</blockquote>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
nginx mailing list -- <a class="moz-txt-link-abbreviated" href="mailto:nginx@nginx.org">nginx@nginx.org</a>
To unsubscribe send an email to <a class="moz-txt-link-abbreviated" href="mailto:nginx-leave@nginx.org">nginx-leave@nginx.org</a>
</pre>
</blockquote>
</body>
</html>