A way to add credentials into the .env file?
We've already talked about it in the Mattermost chat, but also we've talked internally multiple times, and it would be nice if there was a solution for it sometime, so we're creating a ticket here.
So it would be nice if credentials (ie SMTP passwords, API tokens, etc.) could be added to .env files (perhaps using Gitlab CI/CD variables).
There is usually a need for different passwords/tokens/etc. according to the project environment (ie different API tokens for production and staging).
With legacy project/deployment systems, we usually ssh into the server and manually edit the .env file. But with lakedrops this is not possible because the .env file is regenerated on every deployment.
I was wondering if we could make it so that we add Gitlab CI/CD variables in this format:
{branch_name}_{VARIABLE_NAME}=value
. E.g:
develop_SMTP_PASSWORD=some-password
or main_SMTP_PASSWORD=some-password
but the problem with this approach would be that the .env file (and passwords) will be available in the GitLab ci/cd artifacts of the job, so it's not ideal.
I see that the .env is important to the lakedrops system because it contains some variables that are widely used by the system, so probably this file cannot be easily excluded from the build process.
Maybe someone will have an idea...