I Pulled /etc/passwd Off My Own Server
An nginx 400 felt like a fix. send_from_directory felt like a fix. Then a different endpoint handed me /etc/passwd, and the real question was how bad that actually is.
An nginx 400 felt like a fix. send_from_directory felt like a fix. Then a different endpoint handed me /etc/passwd, and the real question was how bad that actually is.
cert.crt, chain_cert.crt, root_cert.crt and a .key. I’d installed them a dozen times without knowing why there were four, so I finally sat down and worked it out on my own server.
Running dev and prod side by side on one AWS box. Compose project names fixed the collisions, and made it really easy to forget everything Docker doesn’t own.
Splitting an all-in-one Docker image into separate services broke a bunch of assumptions I didn’t know existed. Every “how did this work before?” had the same answer.
Answering a marketing question with grep and awk on nginx access logs: requests vs. visitors, bots, timezones, and why the log can’t tell you what the browser never sent.