4 releases

0.16.2 Nov 16, 2023
0.16.1 Nov 16, 2023
0.16.0 Nov 11, 2023
0.15.0 May 1, 2023

#892 in Configuration

Download history 7950/week @ 2025-03-11 7787/week @ 2025-03-18 5540/week @ 2025-03-25 6704/week @ 2025-04-01 5379/week @ 2025-04-08 6126/week @ 2025-04-15 6868/week @ 2025-04-22 5764/week @ 2025-04-29 7484/week @ 2025-05-06 5597/week @ 2025-05-13 7470/week @ 2025-05-20 4859/week @ 2025-05-27 6950/week @ 2025-06-03 7069/week @ 2025-06-10 6952/week @ 2025-06-17 7476/week @ 2025-06-24

29,635 downloads per month
Used in razel

MIT license

37KB
919 lines

Crates.io

dotenv-flow.rs

A fork of dotenv-rs that adds support for the popular dotenv-flow loading strategy.

The dotenv-flow strategy works as follows:

  • if a DOTENV_ENV environment variable is set, load .env.{DOTENV_ENV}.local (e.g. .env.staging.local)
  • load .env.local
  • if a DOTENV_ENV environment variable is set, load .env.{DOTENV_ENV} (e.g. .env.staging)
  • load .env

Each step will only load variables that are not already present in the environment, so for example variables in the .env.{DOTENV_ENV}.local file will have the highest priority, followed .env.local and so on.

Breaking in 0.16.0

  • env.{DOTENV_ENV}.local is now loaded before .env.local

HowTo

Installation

cargo add dotenv-flow

Usage

To use this package, add the following line to your main function to load the environment variables from available .env.* files:

fn main() {
  dotenv_flow::dotenv_flow().ok();
}

Tests

To test this project, make sure you pass --test-threads=1 to cargo test, e.g.

cargo test -- --test-threads=1

This is necessary because cargo test runs tests in multiple threads by default, but environment variables are process-globals, therefore we need to limit concurrency to avoid race conditions.

Dependencies

~0–285KB