Update: INSTALLATION.md

[kb-0311]

Describe the bug

talawa-api/INSTALLATION.md

Lines 18 to 20 in 01b2c8e

	3. Talawa-API uses a configuration file named `.env` in the root directory. It is not a part of the repo and you will need to create it. There is a sample configuration file named `.env.sample` in the root diretory. Create a new `.env` file by copying the contents of the `.env.sample` file.
	cp .env .env.sample

This is a wrong method of copying the contents of .env.sample to env and instead, the command should be cp .env.sample .env as rectified below in the same installation guide.

To Reproduce
Steps to reproduce the behavior:

1. Running cp .env .env.sample makes the .env.sample file empty
2. Sample env contents are flushed

Expected behavior
Content of .env.sample compiled to newliy created .env file .

Actual behavior
Contents of empty .env file copied on .env.sample (clearing out the file).

Possible Fix
change the command in that line to cp .env.sample .env

[github-actions]

Congratulations on making your first Issue! 🎊 If you haven't already, check out our Contributing Guidelines and Issue Reporting Guidelines to ensure that you are following our guidelines for contributing and making issues.

[palisadoes]

@kb-0311 Please follow the procedure of creating the issue, and waiting for it to be approved. We do it this way to prevent a chaotic process. We had that situation in the past and we really don't want to repeat it. Thanks for your contribution, but please follow the guidelines in our CONTRIBUTING.md file

[kb-0311]

Thanks for the merge @palisadoes . Yes, Sorry, I will first discuss the issue on the slack channel before opening an issue. Thanks for the CONTRIBUTING guide.