It seems dangerous to check .env into source control. I suggest creating a sample.env file and unchecking .env. The file us usually reserved for environment specific information and my contain sensitive data. setup.sh checks for the existence of the file anyway, and it could even copy sample.env if no custom .env exists.
wileyj
commented
3 years ago
It seems dangerous to check
.envinto source control. I suggest creating asample.envfile and unchecking.env. The file us usually reserved for environment specific information and my contain sensitive data.setup.shchecks for the existence of the file anyway, and it could even copysample.envif no custom.envexists.