Instruct users to create their own .env.sample file with their specific details.

Author: AtulRajput01

README.md

@@ -33,6 +33,26 @@ services:
       POSTGRES_USER: warpSQLUser
       POSTGRES_PASSWORD: warpSQLPass
 ```
+# Environment Variables
+
+This project requires certain environment variables to be set for proper configuration. These variables include sensitive information such as database credentials. To securely manage these variables, we follow a specific approach.
+Ensure that you have a `.env.sample` file same directory as the `docker-compose.yml` file.
+Open the `.env.sample` file in a text editor.
+Provide placeholders for the required environment variables in the `.env.sample` file. Do not include any actual sensitive information in this file. Here's an example of how the `.env.sample` file should look:
+
+```
+POSTGRES_USER=
+POSTGRES_PASSWORD=
+```
+Replace `POSTGRES_USER` and `POSTGRES_PASSWORD` with the appropriate variable names specific to your project.
+Save the `.env.sample` file.
+Before running the project, create a new file named `.env` in the same directory as the `docker-compose.yml` file.
+Open the `.env` file and provide the actual values for the environment variables, specific to your setup. For example:
+`POSTGRES_USER=myuser`
+`POSTGRES_PASSWORD=mypassword`
+
+Replace myuser and mypassword with the actual values you want to use.
+Save the `.env` file. Ensure that this file is not committed to version control to protect your sensitive information.
 
 WarpSQL is a powerful solution that provides opinionated extensions to Postgres, conveniently packaged as a single Docker deployment. It eliminates the need to install multiple separate databases by offering a comprehensive set of features in one place (although not everything, as some features might not be included).