fixed the path for the environment variables - #118
Open
alisha-sapkal wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The main change was not to the file itself, but in how the application uses it. Your project was trying to manage two separate environment files for the backend, which led to the errors.
Original Problem: Your application (server.js and app.js) was configured to load its settings from backend/config/config.env. However, your actual, up-to-date credentials were in a different file, backend/.env. This meant the application was ignoring your correct settings and using old or empty values from config.env, causing it to fail.
The Solution: We modified server.js and app.js to load their configuration from backend/.env, which is a more standard and centralized location.
Current Status of config.env: As a result of this change, the file backend/config/config.env is now obsolete and no longer used by your application. It contains outdated information (like the local MongoDB connection string) and can be safely removed to avoid future confusion.
The modifications:
