Developer by day, curious by night.
What I do care most are people. I started as Full Stack developer on a Ruby On Rails project.
Now focusing on bridging development with operations and security.
If you do dotenv sensibly, there should be no need to be shared in the team.
It's true that 12factor app ask you to out configuration in the environment, but this does not mean to add them in a .env file.
Put only personal configuration there, like your token for a service, and put every other configuration in committed configuration files.
If you go down this path you will find that .env are very personal and thus there should be no need to share them.
If for some special reason you need to share them, encrypt them and share any way you like. gpg or a service like onetimesecret.com/ may come handy.
The only other path, but beware that may have some unintended consequences, is to commit a .env.default sort of file that each Dev has to copy and fill appropriately.
May I ask you what configurations are in your .env file?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
If you do dotenv sensibly, there should be no need to be shared in the team.
It's true that 12factor app ask you to out configuration in the environment, but this does not mean to add them in a
.envfile.Put only personal configuration there, like your token for a service, and put every other configuration in committed configuration files.
If you go down this path you will find that
.envare very personal and thus there should be no need to share them.If for some special reason you need to share them, encrypt them and share any way you like.
gpgor a service like onetimesecret.com/ may come handy.The only other path, but beware that may have some unintended consequences, is to commit a
.env.defaultsort of file that each Dev has to copy and fill appropriately.May I ask you what configurations are in your
.envfile?