📘 ** Shebang ( #! )**

---

---

🎯 What You Will Learn

1. Understand what a shebang ( #! ) is and why it is required in scripts.
2. Identify the correct interpreter path for Bash, Python, PHP, and other shells.
3. Learn how the kernel uses the shebang line to execute scripts reliably.
4. Apply correct shebang usage in WordPress-related automation scripts.
5. Recognize common errors caused by missing or incorrect shebang lines.
6. Validate script portability across Linux distributions and shells.

---

1. 5W + 1H Framework

Element	Description
What	The shebang ( #! ) is the first line in a script that tells Linux which interpreter to use.
Why	Ensures consistent execution regardless of user shell or system default.
Who	Used by all shell and script developers—especially for VPS automation and WordPress maintenance.
Where	Always appears on the first line of the script file.
When	Required when running scripts directly ( ./script.sh ) rather than calling an interpreter manually.
How	Write the interpreter path after #!, for example #!/bin/bash.

---

2. Prerequisites

• Familiarity with creating and running basic Bash scripts.
• Access to a Linux terminal (Ubuntu or equivalent).
• Understanding of file permissions (chmod +x).
• Knowledge of where interpreters are installed (which bash, which python3, etc.).

---

3. Core Concept: The Shebang Mechanism

When you run a script directly:

./script.sh

the kernel reads the first line of the file. If it begins with #!, Linux uses the specified interpreter to execute the script. Example:

#!/bin/bash
echo "Hello from Bash"

Execution flow

1. Kernel detects #!
2. Loads /bin/bash
3. Passes the remaining file contents to Bash for interpretation

---

4. Common Interpreter Paths

Language / Shell	Typical Path	Example Shebang	Description
Bash	/bin/bash	#!/bin/bash	Most common on Linux; stable path.
Dash (Ubuntu /bin/sh)	/bin/sh	#!/bin/sh	Lightweight POSIX shell used for init scripts.
Python 3	/usr/bin/python3	#!/usr/bin/python3	For Python automation or webhooks.
PHP CLI	/usr/bin/php	#!/usr/bin/php	For WordPress CLI automation or maintenance tools.
Node.js	/usr/bin/node	#!/usr/bin/node	Used for JavaScript-based utilities.
Env method	/usr/bin/env bash	#!/usr/bin/env bash	Portable way to locate Bash even if not in /bin.

---

5. Verify Interpreter Path

Use which to confirm the exact path:

which bash
which python3
which php

Expected Output:

/bin/bash
/usr/bin/python3
/usr/bin/php

If your system differs, update the shebang accordingly.

6. Example Scripts and Expected Output

6.1 Bash Example

#!/bin/bash
echo "Running with Bash interpreter"

Run:

./test.sh

Expected Output:

Running with Bash interpreter

---

6.2 Python Example

#!/usr/bin/python3
print("Running with Python interpreter")

Run:

./pytest.py

Expected Output:

Running with Python interpreter

---

6.3 PHP Example

#!/usr/bin/php
<?php
echo "Running with PHP interpreter\n";
?>

Run:

./phptest.php

Expected Output:

Running with PHP interpreter

---

7. Use in WordPress Automation

When automating WordPress on a VPS, reliable interpreter definition is essential: Example – WP CLI Auto-Update Script

#!/usr/bin/env bash
set -e
wp plugin update --all --path=/var/www/html
wp theme update --all --path=/var/www/html
wp core update --path=/var/www/html

Why important:

• Cron jobs and remote automation may not know the default shell.
• Without a shebang, the script can fail silently or run in an unexpected shell (e.g., sh instead of bash).

---

8. Best Practices

Practice	Description
Always include #!/bin/bash	Prevents misinterpretation by other shells.
Use /usr/bin/env bash for portability	Works across different distributions.
Place shebang on line 1 only	Anything above will break detection.
Test before deploying	Run manually and confirm correct interpreter.
Keep scripts Unix-formatted	Avoid Windows carriage returns (\r).

---

9. Static vs Dynamic Framing

Mode	Description	Example
Static	Hard-coded interpreter path; faster but less flexible.	#!/bin/bash
Dynamic	Uses env to find interpreter dynamically; more portable.	#!/usr/bin/env bash

Use static for internal production scripts, dynamic for cross-platform or distributed systems.

10. Troubleshooting Matrix

Issue	Symptom	Root Cause	Solution
bash: ./script.sh: command not found	No output, shell prompt returns	Missing or incorrect shebang path	Verify path with which bash
Exec format error	Kernel refuses to execute	Extra spaces or Windows line endings	Remove \r with dos2unix script.sh
Wrong interpreter used	Script runs but behaves unexpectedly	Default shell ( /bin/sh ) used instead of Bash	Add explicit #!/bin/bash
Cron job fails	Works manually but not in cron	Cron uses minimal environment	Always define full interpreter path

---

11. Quick Lab – Comparing Shebangs

A. Create two scripts:

# test_sh.sh
#!/bin/sh
echo "Using sh"

# test_bash.sh
#!/bin/bash
echo "Using bash"

B. Run both:

./test_sh.sh
./test_bash.sh

Expected Output:

Using sh
Using bash

C. Test Dynamic Path

#!/usr/bin/env bash
echo "Dynamic path executed"

Expected Output:

Dynamic path executed

---

12. Cheat Sheet

Task	Command / Example
Define shebang for Bash	#!/bin/bash
Portable shebang	#!/usr/bin/env bash
Find interpreter path	which bash
Convert Windows to Unix format	dos2unix file.sh
Test interpreter	head -1 file.sh
Run script explicitly	bash file.sh
Check file encoding	file file.sh

---

13. Mini-Quiz

#	Question	Answer
1	What does the shebang line do?	It tells the system which interpreter to use.
2	Where must the shebang line be placed?	On the first line of the script.
3	Which shebang provides best portability?	#!/usr/bin/env bash
4	What happens if the shebang is missing?	Script runs in the current user’s shell (may fail).
5	How to verify the Bash path?	Run which bash.

---

---