The Scriptage field guide

Run a Bash recipe

Understand the shell, tools, input paths, and report files.

Check the environment

Bash examples target the Linux environment stated on each page. macOS may ship older Bash and different versions of command-line tools. On Windows, use an appropriate Linux environment such as WSL when the prerequisites call for Linux.

Check bash --version and verify required programs with command -v followed by the tool name.

Inspect before running

Read the .sh file and its guide. Commands in a shell script operate with your user permissions. These recipes focus on reports and controlled local tasks; inspect paths and outputs before adapting them.

Run with Bash explicitly

Open a terminal inside the extracted folder and use the recipe’s command, usually bash script-name.sh followed by arguments. Running through Bash does not require making the file executable.

Use the expected path style

Quote filenames containing spaces. Linux paths are case-sensitive. In WSL, Windows drives are commonly mounted under /mnt; choose input paths that exist in the shell where you run the recipe.

Keep reports separate

Use a new output path for a new run. Some operating-system reports vary by distribution or require utilities that are not installed by default. Check the recipe’s listed tools and the tool’s own help output.

Put it into practice

Choose one small task from the library, run its example, and change one thing you understand.

Find a beginner script ↗