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

Non-secret stuff and .env #375

Open
azatoth opened this issue Sep 21, 2017 · 1 comment
Open

Non-secret stuff and .env #375

azatoth opened this issue Sep 21, 2017 · 1 comment
Labels

Comments

@azatoth
Copy link

azatoth commented Sep 21, 2017

As you shouldn't check in .env, is there a practical way to commit non-secret stuff, like AWS_FUNCTION_NAME, AWS_RUNTIME etc?

@abetomo
Copy link
Contributor

abetomo commented Sep 21, 2017

The .env setting can be specified as an option.

ex)

% node-lambda deploy --functionName=piyo --runtime=nodejs6.10

So, there is a way to set it to the script of package.json.

ex)

"scripts": {
  "lambda-deploy": "node-lambda deploy --functionName=piyo --runtime=nodejs6.10"
}
% npm run lambda-deploy

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

No branches or pull requests

3 participants