Thank you both for your replies.

While my server would be a production environment, it would only consist of
the single Ubuntu server and the single instance of Nginx that would be
running no more than 10-12 websites. The server is virtual, so any needed
changes would be scheduled and the server would be "snapshotted" so if any
changes break Nginx, the server would be easily rolled back.

The primary concern would be patching the running version of Nginx. I
subscribe to Nginx announcements, but I don't know the process to install
patches. Can anyone tell me the process and/or point me toward any
tutorials?

Ed

On Thu, Oct 13, 2022 at 4:18 PM PGNet Dev <pgnet.dev@gmail.com> wrote:

> > I should have mentioned that I'm running in an Ubuntu environment so I'm
> not sure if that makes much difference?
>
> Ubuntu/Debian have all the tools for source builds.
> They also have the apt packaging solution.
> I assume there are available build services.
>
> I'm not an Ubuntu/Debian user. Simply a matter of preference.
>
> Beyond that, no opinion worth its salt :-/
>
> > worth
>
> Per whose definition?
>
> Stuff breaks. You either live with it, patch it yourself, or ask someone
> else to patch it for you.
>
> What's the 'worth' to you of not having any particular breakage unsolved?
>
> i.e., it depends.
>
> > Thoughts? Opinions?
>
> Only, don't blindly do what others suggest. Do what works best for you.
>
> For me, 'my' distro chooses not to build/package nginx mainline. Or,
> build/config the way I want. So I do it myself, using the distro's build
> service & tools.
> Is it a PITA? sure. just less than not having what I need.
>
_______________________________________________
nginx mailing list -- nginx@nginx.org
To unsubscribe send an email to nginx-leave@nginx.org