shell-scripting

To write a robust shell script, employ `set -euo pipefail` for error handling and variable safety. This approach prevents scripts from continuing on errors and ensures safe file management during system administration automation.

Making bash scripts portable involves differentiating between Bash-specific and POSIX-compliant features. By prioritizing POSIX compliance and proper variable quoting, you ensure your shell scripts run consistently across diverse system environments.

Add error handling to a deployment script by using functions, local variables, and `set -e`. This allows you to check prerequisites, configure services, and safely trigger a rollback upon failure, ensuring deployment consistency.

Your shell script fails because of improper variable quoting. By consistently quoting variables and using safe file management practices, you prevent word splitting and globbing issues when handling spaces in file paths.

You cannot use Bash-specific features if the script must run on POSIX-compliant systems. You must differentiate between Bash and POSIX features, substituting Bash arrays or specific syntax with POSIX-compliant alternatives for portability.

Improve shell script maintainability by using functions, local variables, and clear argument parsing. This modular approach separates logic into manageable blocks, making complex automation scripts easier to read, debug, and update.