How to Use the Source Command in Bash

The source command is a Bash shell builtin that executes commands from a file in your active shell environment, rather than launching a new subshell. Unlike running a script directly, source reads and evaluates the file's contents in your active shell session. As a result, any variables, functions, or environment changes take effect immediately.

This article covers common use cases for the source command, including loading configuration files, debugging scripts with existing shell variables, importing functions, and setting environment variables. You will learn the syntax and practical applications that make source an essential tool for Bash scripting and system administration.

Common Uses for the source Command

Use the source command to execute a script in your active shell environment. This allows any environment changes or variable assignments to persist after the script runs.

The basic syntax is:

source filename [arguments]

You can also use the shorthand dot (.) notation:

. filename [arguments]

When you provide arguments, they become positional parameters ($1, $2, $3, and so on) inside the sourced script. This makes it possible to pass configuration values or options dynamically.

Loading Configuration Files

Use the source command to load configuration files that define environment variables, aliases, or other shell customizations. This approach is useful for making session-specific changes that take effect immediately.

Command Syntax

source path/to/config_file

• path/to/config_file: Path to a file containing shell-compatible commands, such as export, alias, or function definitions.

You can also use the shorthand version:

. path/to/config_file

Command Demonstration

1. Create a new configuration file named .my_config.

   CONSOLE

   Copy

   $ nano ~/.my_config

   Explain Code

   Powered by Vultr AgentBeta

2. Add the following lines to define an environment variable and an alias:

   INI

   Copy

   export MY_APP_PATH="/opt/myapp"
   alias ll='ls -la'

   Explain Code

   Powered by Vultr AgentBeta

   Save and close the file.

3. Source the configuration file to apply the changes.

   CONSOLE

   Copy

   $ source ~/.my_config

   Explain Code

   Powered by Vultr AgentBeta

4. Verify that the variable and alias are now available in the shell.

   CONSOLE

   Copy

   $ echo $MY_APP_PATH && ll

   Explain Code

   Powered by Vultr AgentBeta

   Output:

   /opt/myapp
   total 21
   drwxr-xr-x  2 user user 4096 Dec 15 10:30 .
   drwxr-xr-x 18 user user 4096 Dec 15 10:25 ..
   -rw-r--r--  1 user user  220 Dec 15 10:30 .my_config
   ...

Debugging with Existing Shell Variables

Use the source command to test scripts that rely on environment variables or need to modify the current shell state. Unlike direct execution, sourcing ensures that changes made inside the script persist in the calling shell.

Command Syntax

source script.sh

• script.sh: A script that references or modifies environment variables in the current shell session.

Command Demonstration

1. Set an environment variable in your current shell.

   CONSOLE

   Copy

   $ export MY_VAR="Original value"

   Explain Code

   Powered by Vultr AgentBeta

2. Create a script named test.sh.

   CONSOLE

   Copy

   $ nano test.sh

   Explain Code

   Powered by Vultr AgentBeta

3. Add the following content:

   BASH

   Copy

   #!/bin/bash
   
   echo "MY_VAR is: $MY_VAR"
   MY_VAR="Modified value"
   echo "MY_VAR is now: $MY_VAR"

   Explain Code

   Powered by Vultr AgentBeta

   Save and close the file.

4. Make the script executable.

   CONSOLE

   Copy

   $ chmod +x test.sh

   Explain Code

   Powered by Vultr AgentBeta

5. Run the script directly (in a subshell).

   CONSOLE

   Copy

   $ ./test.sh

   Explain Code

   Powered by Vultr AgentBeta

   Output:

   MY_VAR is: Original value
   MY_VAR is now: Modified value

6. Check the variable in your shell.

   CONSOLE

   Copy

   $ echo "MY_VAR is: $MY_VAR"

   Explain Code

   Powered by Vultr AgentBeta

   Output:

   MY_VAR is: Original value

   The variable remains unchanged because the script ran in a subshell.

7. Source the script to execute it in your shell.

   CONSOLE

   Copy

   $ source test.sh

   Explain Code

   Powered by Vultr AgentBeta

   Output:

   MY_VAR is: Original value
   MY_VAR is now: Modified value

8. Check the variable again.

   CONSOLE

   Copy

   $ echo "MY_VAR is: $MY_VAR"

   Explain Code

   Powered by Vultr AgentBeta

   Output:

   MY_VAR is: Modified value

Loading Functions in Existing Scripts

Use the source command to load functions from an external file into your current shell session. This makes custom utilities reusable without rewriting code across multiple scripts.

Command Syntax

source path/to/functions_file.sh

• functions_file.sh: A file that contains function definitions written in Bash syntax.

Command Demonstration

1. Create a function library file named functions.sh.

   CONSOLE

   Copy

   $ nano functions.sh

   Explain Code

   Powered by Vultr AgentBeta

2. Add the following function definition:

   BASH

   Copy

   #!/bin/bash
   
   system_info() {
      echo "System Information:"
      echo "==================="
      echo "Hostname: $(hostname)"
      echo "Uptime: $(uptime)"
   }

   Explain Code

   Powered by Vultr AgentBeta

   Save and close the file.

3. Source the file to load the function into your shell.

   CONSOLE

   Copy

   $ source functions.sh

   Explain Code

   Powered by Vultr AgentBeta

4. Call the function directly.

   CONSOLE

   Copy

   $ system_info

   Explain Code

   Powered by Vultr AgentBeta

   Output:

   System Information:
   ===================
   Hostname: ubuntu-server
   Uptime: up 2 hours, 34 minutes, 3 users, load averages: 4.20 4.41 3.87

Setting Environment Variables

Use the source command to apply multiple environment variables from a single file. This method is useful for application configuration and development environments where consistent variables are required across sessions.

Command Syntax

source environment_file.sh

• environment_file.sh: A shell script that defines variables using export.

Command Demonstration

1. Create an environment file named app_env.sh.

   CONSOLE

   Copy

   $ nano app_env.sh

   Explain Code

   Powered by Vultr AgentBeta

2. Add the following variable definitions:

   BASH

   Copy

   #!/bin/bash
   
   export DB_HOST="localhost"
   export DB_PORT="5432"
   export APP_ENV="development"
   export APP_PORT="8080"

   Explain Code

   Powered by Vultr AgentBeta

   Save and close the file.

3. Source the environment file to apply the variables.

   CONSOLE

   Copy

   $ source app_env.sh

   Explain Code

   Powered by Vultr AgentBeta

4. Create a script that uses the environment variables.

   CONSOLE

   Copy

   $ nano test_env.sh

   Explain Code

   Powered by Vultr AgentBeta

5. Add the following content to the file.

   BASH

   Copy

   #!/bin/bash
   
   echo "Connecting to database at $DB_HOST:$DB_PORT"
   echo "Application running on port $APP_PORT"
   echo "Environment: $APP_ENV"

   Explain Code

   Powered by Vultr AgentBeta

   Save and close the file.

6. Give the execution permission to the file.

   CONSOLE

   Copy

   $ chmod +x test_env.sh

   Explain Code

   Powered by Vultr AgentBeta

7. Run the script to verify the environment variable usage.

   CONSOLE

   Copy

   $ ./test_env.sh

   Explain Code

   Powered by Vultr AgentBeta

   Output:

   Connecting to database at localhost:5432
   Application running on port 8080
   Environment: development

Conclusion

In this article, you used the source command to load configuration files, debug scripts with environment variables, import shell functions, and apply environment variables from external files. Unlike scripts that run in subshells, source applies changes immediately to your current shell session, making it a powerful tool for managing environment state and reusable configurations.