We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As you shouldn't check in .env, is there a practical way to commit non-secret stuff, like AWS_FUNCTION_NAME, AWS_RUNTIME etc?
The text was updated successfully, but these errors were encountered:
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.
"scripts": { "lambda-deploy": "node-lambda deploy --functionName=piyo --runtime=nodejs6.10" }
% npm run lambda-deploy
Sorry, something went wrong.
No branches or pull requests
As you shouldn't check in .env, is there a practical way to commit non-secret stuff, like AWS_FUNCTION_NAME, AWS_RUNTIME etc?
The text was updated successfully, but these errors were encountered: