Search
5 results for “nodejs”
Search results
Why Every Container in Your Rolling Deploy Takes an Extra 10 Seconds to Stop
Why npm as PID 1 can prevent Node.js from receiving SIGTERM, trigger Docker's ten-second timeout, and end container shutdown with SIGKILL.
Your GitHub Actions Cache Hit Rate Is Worse Than You Think, and the Key Isn't the Problem
Why identical GitHub Actions cache keys still miss across pull requests, how branch scope and restore keys work, and the correct npm cache YAML.
Why is publishing a port with `-p 8080:80` different from the container just "having" port 80?
A container's ports exist only on its own private network namespace by default; nothing on the host or outside can reach them until Docker explicitly forwards a host port to it. `-p 8080:80` tells Docker's network layer to forward the host's port 8080 to port 80 inside the container's namespace, host port first, container port second. Leaving a port `EXPOSE`d in a Dockerfile only records metadata/documentation, it has no effect on connectivity at all: another container on the same Docker network can already reach any port the first container is listening on, EXPOSE or not. Publishing to the host is the one thing that always requires an explicit `-p`.
Linux Beginner Labs: Foundations (Understand Linux, Not Just Commands)
Hands-on Linux labs for beginners that build a mental model of how Linux actually works, runnable on any VM, cloud instance, or WSL.
Linux Foundations: How Linux Really Works, Not Just Commands
Learn how Linux actually works (the shell, processes, users, permissions) so commands make sense instead of being memorized one at a time.