Inspect before editing
Find the active compose file, mounted configuration, network names and service boundaries before changing a running system.
Tutorials
Commands with reasons attached.
The goal is not a magic paste box. It is a workflow you understand well enough to recover when reality differs from the example.
Back up the exact target
Create timestamped backups before whole-file replacements, then validate before recreating only the affected service.
Use bounded restarts
Restart or recreate the intended container instead of treating an entire production stack as one disposable object.
Learn what paths mean
Absolute paths, permissions, ownership, processes and logs turn Linux from a collection of spells into a coherent system.
Test each layer
DNS, TLS, reverse proxy routing, container networking and application response are separate checks with separate evidence.
Carry the decisions forward
Continuation prompts should preserve names, contracts, architecture, file paths, completed work and the exact next task.