We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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 a developer, it is easier to develop if we have a .env file where all the secrets are stored.
During local development, the .env file is loaded into the Makefile and the envs are used in the commands.
In CI/CD pipelines, the envs are directly added as secrets in the CI/CD tool used.
The text was updated successfully, but these errors were encountered:
Lucifergene
Successfully merging a pull request may close this issue.
As a developer, it is easier to develop if we have a .env file where all the secrets are stored.
During local development, the .env file is loaded into the Makefile and the envs are used in the commands.
In CI/CD pipelines, the envs are directly added as secrets in the CI/CD tool used.
The text was updated successfully, but these errors were encountered: