Original, source-backed articles about running small systems, static sites, HTTP, DNS, TLS, and operations.
Posts are original articles written for this site. Each one is script-free, source-backed, and tied to the same operational reality the rest of the site records: how a small, static, publicly served system is built, secured, and kept honest.
Ansible tasks can declare repeatable target states
An Ansible playbook is an ordered orchestration of tasks. State-aware modules can record what a machine should have and repair missing pieces after a partial deploy. Convergence comes from the selected modules and arguments, not an engine-wide guarantee that every task safely repeats. A playbook is an executable contract between the inventory, the modules, and the operator who reviews the change.
...
gRPC multiplexes many streams over one HTTP/2 connection
gRPC’s HTTP/2 transport lets multiple RPC attempts share a connection while keeping each stream’s messages ordered. That is useful for both short calls and long-lived exchanges. It does not make the connection an unlimited independent transport for every call: bandwidth, TCP delivery, connection flow control, and implementation resources remain shared.
...
HTTP/2 multiplexing fixes a queue
HTTP/2 removes HTTP response-order constraints by multiplexing streams, but those streams still share a TCP connection and its failure modes. One useful boundary is cancellation: terminating a request need not destroy its sibling requests or the reusable connection. That is a scoped capability, not a guarantee that streams never affect each other.
...
GROUPING SETS build several aggregate views
GROUPING SETS asks one SQL statement to produce several aggregation levels. A sales report can return totals by region and product, region subtotals, and a grand total together. The result contains different kinds of rows, so identifying each row’s level is as important as calculating its amount correctly.
...
Readiness changes routing eligibility; liveness restarts a container
Readiness and liveness answer different operational questions. Readiness asks whether this container should contribute to a Pod that accepts ordinary Service traffic now. Liveness asks whether restarting this container is the configured recovery action. Both can use HTTP, but sharing a protocol does not make their meanings interchangeable. Define the action you want before choosing the condition that triggers it.
...
Cookies and sessions hold boundaries
A cookie is a browser storage and transport mechanism. A server-side session is one application design that uses a cookie value to locate stored state. Keeping those responsibilities separate makes login, expiry, and logout testable. This article follows an opaque session identifier, rather than repeating the host, path, or SameSite matching rules.
...
Shell traps turn a signal into a cleanup step
A trap lets a shell arrange an action for a signal or a shell event. It is useful for removing temporary files and coordinating shutdown, but it does not make interruption atomic or guarantee cleanup under every termination. In Bash, trap is a builtin, and EXIT is a shell event rather than an operating system signal. A reliable design names the exits it handles and preserves evidence of why execution stopped.
...
Redis Sentinel coordinates primary failover
Redis Sentinel supervises a non-Cluster primary/replica deployment and publishes the current primary’s address. It does not store the application’s dataset or proxy its commands. Automatic promotion can restore write availability after a primary fails, but discovery, replica freshness, client reconnection, and protection from stale writers remain separate parts of the system.
...
