automated terminal push
All checks were successful
code.softwareshinobi.com-learn/docker.softwareshinobi.com/pipeline/head This commit looks good
All checks were successful
code.softwareshinobi.com-learn/docker.softwareshinobi.com/pipeline/head This commit looks good
This commit is contained in:
32
docs/.Bash-Scripting/002-bash-structure.md
Executable file
32
docs/.Bash-Scripting/002-bash-structure.md
Executable file
@@ -0,0 +1,32 @@
|
||||
# Bash Structure
|
||||
|
||||
Let's start by creating a new file with a `.sh` extension. As an example, we could create a file called `devdojo.sh`.
|
||||
|
||||
To create that file, you can use the `touch` command:
|
||||
|
||||
```bash
|
||||
touch devdojo.sh
|
||||
```
|
||||
|
||||
Or you can use your text editor instead:
|
||||
|
||||
```bash
|
||||
nano devdojo.sh
|
||||
```
|
||||
|
||||
In order to execute/run a bash script file with the bash shell interpreter, the first line of a script file must indicate the absolute path to the bash executable:
|
||||
|
||||
```bash
|
||||
#!/bin/bash
|
||||
```
|
||||
|
||||
This is also called a [Shebang](https://en.wikipedia.org/wiki/Shebang_(Unix)).
|
||||
|
||||
All that the shebang does is to instruct the operating system to run the script with the `/bin/bash` executable.
|
||||
|
||||
However, bash is not always in `/bin/bash` directory, particularly on non-Linux systems or due to installation as an optional package. Thus, you may want to use:
|
||||
|
||||
```bash
|
||||
#!/usr/bin/env bash
|
||||
```
|
||||
It searches for bash executable in directories, listed in PATH environmental variable.
|
||||
Reference in New Issue
Block a user