klesh commented on PR #130: URL: https://github.com/apache/incubator-devlake-helm-chart/pull/130#issuecomment-1552380363
To clarify, `devlake` supports both `.env` and `ENV` vars already, in fact, `ENV` vars are overriding the settings from the `.env` file. The only reason `.env` is needed is to allow `devlake` to generate a random `ENCODE_KEY` on the first boot for sensitive information encryption such as `github token` in case the database is compromised. Theoretically, the `ENCODE_KEY` can be generated by the user when deploying devlake, then we don't need the `.env` file at all. However, there are some concerns: 1. Is it acceptable for our users to set up such an Encryption Key manually, I feel like it is hard for most of them to understand the concept. 2. Can we semi-automate this process? maybe we could accept an manual input or generate one for them, and even prompt them to store the Key somewhere safe in case they want to redeploy it in the future. We have to support `helm` and `docker-compose` at the same time in a similar manner. @hezyin @Startrekzky -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
