ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #nginx
The goal is to determine when nginx replaces a stale cache entry after a background refresh initiated by proxy_cache_background_update . Documentation specifies that stale content can be served while a background subrequest updates the cache, but it does not clarify whether the updated object overwrites the stale entry immediately upon completion of the back
Goal: verify that nginx ≥ 1.19.8 resolves the upstream keepalive memory leak that manifested as SIGSEGV in worker processes under prolonged HTTP/1.1 keepalive traffic, and determine whether the worker_processes auto setting still produces uneven load distribution on heterogeneous CPU architectures when worker_process_auto_affinity is enabled. Constraints: wh
Configuration must be available to the application without exposing credentials in source control, logs or browser code. What belongs in the runtime and which access controls matter?
I am running a local web app on my dev machine. And I want to reach my local web app from a test machine (a phone). I set up Nginx to listen on port 8888. My test machine can reach my dev machine at this port. Requests that should go the local web application are reverse-proxied from port 8888 to the local web app port 3000. These requests work fine. Request
Goal To enable automatic upstream failover for TCP backends using the NGINX Stream module without a commercial license. Constraints The open‑source edition lacks a built‑in health_check directive; upstream blocks rely on manual failover via max_fails and fail_timeout . Using Plus‑only syntax causes configuration errors. External scripts can be employed but r
In an Nginx HTTP proxy configuration, the proxy_read_timeout directive is used to manage the duration the proxy waits for a response from the proxied server. This is critical for applications utilizing long-polling or streaming data where the upstream server may maintain an open connection without sending data for extended periods. The current behavior reset
Recovery needs to recreate the working service and its required data after a machine or process is lost. Which artifacts and state need protection, and how should the restore be checked?
An upgrade needs a compatibility check, a tested release and a recovery path. Which changes deserve particular attention before the new version reaches production?
I have a Rails application that I want to deploy using Docker on an Ubuntu server. I have the Dockerfile for the application already set up, right now I want to view the nginx conf in its container. I ran the command below to start an nginx container in an interactive mode: docker run -i -t nginx:latest /bin/bash Right now I am trying to install nano editor
docker
debian