Hi Andre,
thanks for the report.
On Thu, Oct 13, 2022 at 09:03:21PM -0400, Andre Pedro wrote:
> Hello folks,
>
> I am trying to get the below load balancer config to work in our
> environment. Basically, this server should receive v6 udp packets sflow
> sample packets on port 6343 and forward ou
Hello folks,
I am trying to get the below load balancer config to work in our
environment. Basically, this server should receive v6 udp packets sflow
sample packets on port 6343 and forward out to these 3 servers part of
stream_backend. However, it doesn't seem to work. If I switch to v4, it
does
Thank you for all of your input!
Ed
On Thu, Oct 13, 2022 at 5:54 PM PGNet Dev wrote:
> > My primary driving reason for considering the deployment of Nginx from
> source is to use ModSecurity WAF with Nginx. I'm under the impression that
> it's much easier to use ModSecurity with Nginx when comp
My primary driving reason for considering the deployment of Nginx from source
is to use ModSecurity WAF with Nginx. I'm under the impression that it's much
easier to use ModSecurity with Nginx when compiled from source.
If ModSecurity is the issue ...
There are old instructions easily found O
My primary driving reason for considering the deployment of Nginx from
source is to use ModSecurity WAF with Nginx. I'm under the impression that
it's much easier to use ModSecurity with Nginx when compiled from source.
My only goal of installing patches would simply be to keep the install up
to d
I don't know the process to install patches.
That's a big ol' red flag. Personally, I'd strongly recommend against
building/installing into a *production* env, until you're up to snuff with
managing the sources, including patches.
That said, are you solving for a real/existing production pro
Hi,
hope you're doing well.
On Thu, Oct 13, 2022 at 03:40:35PM +, edflecko wrote:
> I'm curious how many people run Nginx in a production environment that was
> installed from source and not a package.
>
> For those people who are running Nginx in this manner, how do you keep
> Nginx patched
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 w
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 m
If you're on Ubuntu you have some tradeoffs by doing this yourself.
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 ex
Thank you for your reply!
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 environmen
Nginx is an easy build from source, thankfully.
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.
But, it's a bit of a slog to deploy into usual distro env, avoid collisi
I'm curious how many people run Nginx in a production environment that was
installed from source and not a package.
For those people who are running Nginx in this manner, how do you keep
Nginx patched when patches are released?
How do you upgrade your existing Nginx in your production environment
13 matches
Mail list logo
