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

set environment variable to the shell (not just in node process) #22

Open
FabienDehopre opened this issue Jul 4, 2014 · 11 comments
Open

Comments

@FabienDehopre
Copy link

It would be nice if the environment variables are also exported to the shell.
This is useful when using grunt-bower-task when being behind a proxy. Since bower uses git to download the packages.

@stephanebachelier
Copy link
Collaborator

@LordDawnhunter still interested in this ?

@dayjobtitus
Copy link

I am.

@pcolazurdo
Copy link

Me too

@ArmorDarks
Copy link

+1

@xcambar
Copy link

xcambar commented Feb 13, 2015

Same here

@stephanebachelier
Copy link
Collaborator

@xcambar @pcolazurdo @iamchrismiller @FabienDehopre @ArmorDarks do you have any use case to share ?

The task is already exporting to node process.env variable the content of any .env file.

For example runnning grunt writeDotEnv env:testDotEnv testDotEnv is working because this will be the same process.

But running the following command on a *nix os won't work:
grunt writeDotEnv env:testDotEnv testDotEnv; env

@xcambar
Copy link

xcambar commented Feb 23, 2015

It would be useful with grunt-concurrent, grunt-contrib-watch or grunt-shell, the 3 of which spawn processes.

My specific use case involves grunt-shell, which created processes must have some environment variables.

@stephanebachelier
Copy link
Collaborator

@xcambar thanks for you explanations

@bradoyler
Copy link

👍

1 similar comment
@constantx
Copy link

👍

@namlet
Copy link

namlet commented Aug 3, 2015

Agree with @xcambar - have the same need.

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

9 participants