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

Global configuration #64

Closed
asmeurer opened this issue Apr 14, 2014 · 3 comments
Closed

Global configuration #64

asmeurer opened this issue Apr 14, 2014 · 3 comments

Comments

@asmeurer
Copy link

Is there a way to use a global env configuration with this? I don't want to pollute various directories with .env, and having a global ~/.autoenv.yaml or whatever would be much easier for me to track in my dotfiles repo and sync across computers.

@sirajulm
Copy link

This one works by overriding cd. A simple hack for your issue is to make a base directory that contain all your projects, or at least symlinks, place .env file inside that base directory, and while working cd through that base directory.

@dasJ
Copy link
Contributor

dasJ commented Aug 1, 2016

Yes, I agree with @sirajulm, this is the best approach. Putting yaml logic (or anything like this) into autoenv would make the project too complex.

@dasJ dasJ closed this as completed Aug 1, 2016
@asmeurer
Copy link
Author

asmeurer commented Aug 1, 2016

I was actually (somewhat lazily) waiting for this issue to be fixed to use autoenv (lazy in the sense that for now I just do things the old fashioned way). This way seems about as hacky as just forking autoenv and doing it the right way (again, though, I'm lazy, so I doubt it will happen).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants