writing-shell-scripts

Robust bash scripts require using `set -Eeuo pipefail` to catch errors early, properly quoting variables to prevent word splitting, and defining functions with clear structures. Using `trap` ensures cleanup actions execute if a script fails or exits unexpectedly.

Portable shell scripts require understanding functional differences between GNU and BSD utilities. You should write cross-platform scripts by identifying command-specific flags and behaviors, avoiding GNU-only extensions, and testing execution environments to ensure compatibility across different Unix-like systems.

Validating shell scripts involves running `bash -n` to check for syntax errors without executing the code, and integrating `shellcheck` into your workflow. This automated validation identifies common scripting errors, improves maintainability, and enforces best practices.

Bash scripts fail on spaced file paths due to improper variable quoting and unsafe iteration methods. You must quote variables consistently and use safe file iteration patterns, often combined with `set -u` to catch unset variables that cause unexpected word splitting.

Yes, you can use `trap` to execute cleanup commands when your deployment script exits or receives a signal. This ensures temporary files are removed and resources are released, making the script reliable and easy to maintain even if an error occurs.