Restart policies need a rate limit
Use an explicit service type, bounded restart behavior, and start-rate limits that leave evidence in the journal.
Operations
SSH host keys are part of the deployment record
Record the expected fingerprint, use a deliberate StrictHostKeyChecking policy, and treat changes as an incident until explained.
The advantage of small systems
Small does not mean unfinished; it means each boundary has a clear job and a visible owner.
robots.txt and sitemaps answer different questions
robots.txt is a crawler-facing preference; a sitemap is a URL inventory; neither is an authorization layer.
Reliable defaults beat clever recovery
Keep the common path explicit, observable, and safe to repeat before adding recovery branches.
Redirects and error codes should preserve the story
Check the method, Location header, and cache behavior before choosing a redirect or an error status.
Read the public edge in two commands
Two small read-only helpers turn the public endpoint into evidence you can inspect before and after a release.
Log rotation needs writer handoff and a retention budget
Log rotation divides a continuing stream into files that can be retained, searched, compressed, and eventually removed. A useful policy defines both when to rotate and which history to keep. It must also account for how the application holds its output file open. Renaming a pathname and successfully redirecting future log records are separate steps in that operational contract. ...