Thank you! I appreciate it. On the note of the GitHub search results, I was really disturbed by how many commits are being made with a similar title. I just felt the need to write about it as a PSA and a friendly reminder to all that they shouldn't commit the .env file unless it's there for a justifiable reason, such as the case with @buphmin
.
That said I have a repo on github right now, symfony4-impressions, that I explicitly intended to commit the .env and give to people. In this case I wanted people to have the foobar password for the docker mysql container so they can easily run the performance benchmarks to see for themselves if they wanted.
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.
Thank you! I appreciate it. On the note of the GitHub search results, I was really disturbed by how many commits are being made with a similar title. I just felt the need to write about it as a PSA and a friendly reminder to all that they shouldn't commit the
.env
file unless it's there for a justifiable reason, such as the case with @buphmin .I agree 100% in any real project.
That said I have a repo on github right now, symfony4-impressions, that I explicitly intended to commit the .env and give to people. In this case I wanted people to have the foobar password for the docker mysql container so they can easily run the performance benchmarks to see for themselves if they wanted.