ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #nginx
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
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
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested docker: Error response from daemon: could not select device driver "" with capabilities: [[gpu]]. I am facing this error on mac while trying to run this command docker run --rm --gpus all -v static_volume:/ho
The goal is to lower request latency for short‑lived, bursty traffic in nginx without exceeding system file descriptor limits or causing excessive memory use. Increasing worker_connections lets each worker handle more simultaneous sockets, but raises memory pressure and may hit FD limits. Enabling keepalive reuses existing TCP connections, cutting handshake
The same project needs to behave consistently on developer machines, in CI and after deployment. Which versions, dependencies and configuration should be recorded?
docker
debian
django