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.
It seems dangerous to check
.env
into source control. I suggest creating asample.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 copysample.env
if no custom.env
exists.