Added env.example File for Environment Variable Configuration #475
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of Changes:
Added a .env.example file to provide a template for environment variables used in the project.
Included placeholders for Cloudinary credentials, Google OAuth credentials, JWT secret, email settings, MongoDB connection string, React app base URL, and Unsplash API key.
Fixes #474
Type of change
Please mark with an X the type that applies:
Motivation and Context
Adding a .env.example file helps new contributors understand the required environment variables and how to configure them for local development. This improves the onboarding process and ensures consistency in environment setups.
How Has This Been Tested?
This change doesn’t require specific tests since it involves adding a sample configuration file.
Test A: Verified that the .env.example file includes all necessary environment variables and provides clear instructions.
Test B: Confirmed that the file format is correct and that placeholders are accurately described.
Screenshots and Videos
No screenshots or videos are applicable for this change.
Checklist
Please mark with an X the items that apply: