Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ENH] read .env file for environment variables #347

Open
AlbertDeFusco opened this issue Dec 2, 2021 · 1 comment
Open

[ENH] read .env file for environment variables #347

AlbertDeFusco opened this issue Dec 2, 2021 · 1 comment
Labels
TRIAGE Uncategorized issue

Comments

@AlbertDeFusco
Copy link
Collaborator

Currently a user can define local values of variables defined the anaconda-project.yml file in a file called anaconda-project-local.yml. It seems reasonable to also support a more standard approach with a .env file in the project directory.

Does anyone reading this have a strong opinion about which one would take precedence if both a .env and anaconda-project-local.yml file are present?

@AlbertDeFusco AlbertDeFusco added the TRIAGE Uncategorized issue label Dec 2, 2021
@jbednar
Copy link
Collaborator

jbednar commented Dec 3, 2021

I would think anaconda-project-local.yml would take precedence, as it's the one more specific to a-p, and the most specific should normally be the final word (and the least used).

Should the title be read .env file for environment variables?

@AlbertDeFusco AlbertDeFusco changed the title [ENH] read .env file for commands [ENH] read .env file for environment variables Dec 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TRIAGE Uncategorized issue
Projects
None yet
Development

No branches or pull requests

2 participants