How to distinguish between .env in Laravel for Live and Dev systems?

Question

git

Good afternoon.
There is a project, for devs own settings, for live others .env. How to manage .env files so that during deployment the dev file does not go live and vice versa?
Same question for docker-compose.yml
Thanks

Answer 1

https://laravel.com/docs/5.4/configuration#environ...
Configs for different environments should be different in principle, different files.
Yes, and in general, you have to try to screw up like that.
dev and prod cannot intersect at all, especially since the configs get mixed up.
They only have a common repository in the git, everything else is different. And it's also necessary to be able to store configs in the git.

Answer 2

What about .gitignore?