Deploy projects without .env file.
That file should be ignored.
What I do is I have .env.staging and another file .env.production
On the remote server I will copy one of those files to .env
Alternatively, just have a single .env.example file without any sensitive information in it. On remote, you can copy that file to .env and edit the contents on the remote server.
To edit a file on your server, you may type: nano .env
or if that doesn't work, try vi .env else vim .env
PS: VI and VIM are difficult to use if you don't know how. You'll need to search for instructions on how to switch to edit mode, and back, then how to quit and save.
Nano is the easiest text editor for Linux noobs like me.