Allow loading environment variables from given path

[altugbakan]

Component

Forge, Cast, Chisel

Describe the feature you would like

Now, the .env file is only loaded from the project root. A CLI flag can be added to load the .env file from another directory. This will be helpful if Foundry is used within a monorepo that uses a single .env file.

The lines that load the .env file can be seen here:

foundry/crates/cli/src/utils/mod.rs

Lines 181 to 203 in 8dd7ad2

	/// Loads a dotenv file, from the cwd and the project root, ignoring potential failure.
	///
	/// We could use `warn!` here, but that would imply that the dotenv file can't configure
	/// the logging behavior of Foundry.
	///
	/// Similarly, we could just use `eprintln!`, but colors are off limits otherwise dotenv is implied
	/// to not be able to configure the colors. It would also mess up the JSON output.
	pub fn load_dotenv() {
	let load = |p: &Path| {
	dotenvy::from_path(p.join(".env")).ok();
	};
	// we only want the .env file of the cwd and project root
	// `find_project_root_path` calls `current_dir` internally so both paths are either both `Ok` or
	// both `Err`
	if let (Ok(cwd), Ok(prj_root)) = (std::env::current_dir(), find_project_root_path(None)) {
	load(&prj_root);
	if cwd != prj_root {
	// prj root and cwd can be identical
	load(&cwd);
	}
	};
	}

I would also like to work on this.

Additional context

The code can be seen below:

pub fn load_dotenv() {
    let load = |p: &Path| {
        dotenvy::from_path(p.join(".env")).ok();
    };

    // we only want the .env file of the cwd and project root
    // `find_project_root_path` calls `current_dir` internally so both paths are either both `Ok` or
    // both `Err`
    if let (Ok(cwd), Ok(prj_root)) = (std::env::current_dir(), find_project_root_path(None)) {
        load(&prj_root);
        if cwd != prj_root {
            // prj root and cwd can be identical
            load(&cwd);
        }
    };
}

[pikonha]

I'm interested in this solution because I have a monorepo structure with the .env file placed in the root folder. Is there any workaround until this is released?

[zerosnacks]

Hi @altugbakan thanks for your suggestion! Would you still be willing to work on this?

[altugbakan]

Hey, I would like to!

[zerosnacks]

Awesome! Assigning to you

[altugbakan]

Opened #8346 for this

[altugbakan]

Hey, I tried my hand, but don’t currently have the capacity to work on this. Anyone who wants to solve this can check this out.

[zerosnacks]

No problem @altugbakan, thanks for your time and effort