How to set dotenv variables in bash shell when changing directory?

 To set environment variables from a `.env` file when changing directories in a Bash shell, you can use the `dotenv` tool or manually source the `.env` file. Here's how you can do it:


1. **Using dotenv Command** (Recommended):


   The `dotenv` command is a tool designed for loading environment variables from a `.env` file. You can install it using Node.js and `npm`:


   ```bash

   npm install -g dotenv-cli

   ```


   Then, create a `.env` file in the directory where you want to load environment variables. The `.env` file should contain your environment variables in the format `VAR_NAME=VAR_VALUE`.


   Now, you can use the `dotenv` command in your Bash script to load the variables:


   ```bash

   cd /path/to/your/directory

   dotenv

   ```


   This will load the variables from the `.env` file in the current directory.


2. **Manually Sourcing the .env File**:


   If you don't want to use `dotenv` and prefer a manual approach, you can source the `.env` file using the `source` or `.` command in Bash:


   ```bash

   cd /path/to/your/directory

   source .env

   ```


   or


   ```bash

   cd /path/to/your/directory

   . .env

   ```


   Make sure the `.env` file is in the specified directory and contains the environment variables you want to load.


Using the `dotenv` command is a cleaner and more standardized way to load environment variables from a `.env` file, and it's especially useful if you work with Node.js projects. However, manually sourcing the file with `source` or `.` also works if you prefer to use standard Bash commands.

Comments

Post a Comment

Popular posts from this blog

bad character U+002D '-' in my helm template

 In Helm templates, the hyphen character (`-`) can sometimes be treated as a reserved character, particularly when defining values or labels. To include a hyphen character in a Helm template without issues, you can use one of the following approaches: 1. **Quoting the Hyphen:**    You can enclose the hyphen in double quotes, like this:    ```yaml    key: "-"    ```    This way, Helm will interpret the hyphen as a string rather than an operator. 2. **Using Backticks:**    If you need to use the hyphen within a Go template function or inside backticks, you can escape it with a backslash (`\`), like this:    ```yaml    value: `{{ .Values.someField | printf "%s \\-" }}`    ```    The backslash prevents Helm from interpreting the hyphen as a special character. 3. **Variable Assignment:**    Assign the value to a variable and use it. For example:    ```yaml    {{- $hyphen := "-" }}    key: {{ $hyphen }}    ```    This way, you can use the variable `$hyphen` wher
Read more

GitLab pipeline stopped working with invalid yaml error

 When your GitLab pipeline has stopped working with an "invalid YAML" error, it means there's a problem with your `.gitlab-ci.yml` file. This could be due to syntax errors, incorrect indentation, or other issues in your pipeline configuration. Here's how to troubleshoot and resolve this issue: 1. **Check for Syntax Errors**:    Carefully review your `.gitlab-ci.yml` file for any syntax errors. Common issues include missing colons, indentation problems, or mismatched quotation marks. Use a YAML linter or an online YAML validator to identify and correct syntax errors. 2. **Indentation**:    YAML relies heavily on proper indentation. Make sure that all lines within the same block have consistent indentation (typically using spaces, not tabs). Incorrect indentation can cause YAML parsing errors. 3. **Dashes and Lists**:    Ensure that you use the correct syntax for lists (arrays) in YAML by starting each item with a dash (`-`). Be consistent with your use of dashes throug
Read more

How do I add a printer in OpenSUSE which is being shared by a CUPS print server?

 To add a printer in openSUSE that is being shared by a CUPS print server, you can use the following steps: 1. **Ensure CUPS Client is Installed:**    Make sure your openSUSE system has the CUPS client tools installed. You can install them using the following command:    ```bash    sudo zypper install cups-client    ``` 2. **Discover Available Printers:**    Use the `lpinfo` command to discover available printers on your CUPS print server. Replace `cups-server-hostname` with the hostname or IP address of your CUPS server:    ```bash    lpinfo -v -h cups-server-hostname:631    ```    This command should list the printers shared by the CUPS server. 3. **Add a Printer:**    Use the `lpadmin` command to add a printer. Replace `printer-name` with the name of the printer you want to add and `printer-uri` with the URI obtained from the `lpinfo` command:    ```bash    sudo lpadmin -p printer-name -E -v printer-uri    ```    For example:    ```bash    sudo lpadmin -p MyPrinter -E -v socket://cu
Read more