Skip to content

Commit c57846d

Browse files
committed
modified readme
1 parent 063c643 commit c57846d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -162,9 +162,9 @@ Powered by **AWS Lambda**, **Redis**, and **DynamoDB**.
162162
---
163163

164164
## 🚀 Running the Project Locally
165-
Due to our automated CI/CD pipeline, the environment variables currently point to the deployed instances of the various endpoints. If you wish to test the project locally, comment out the environment variables under `# Endpoints` in `frontend/.env.local`. Then, perform the local setups shown below.
165+
The `.env.local` file at `frontend/.env.local` is already configured to use the local endpoints. Simply perform the local setups shown below.
166166

167-
Note that for ease of use, there is a deployed cloud instance of the graph database hosted on Neo4j. The provided .env file at `graphdb/.env` already points to the cloud database, hence no action is needed. However, it is on a free trial, and will expire on 28th November 2025. Past this date, the deployed frontend will no longer display the various trade routes, though other features will work as intended. To see the trade route visualisation once it expires, you must run all endpoints locally.
167+
Note that for ease of use, there is a deployed cloud instance of the graph database hosted on Neo4j, which local endpoints reference. The provided .env file at `graphdb/.env` already points to the cloud database, hence no action is needed. However, it is on a free trial, and will expire on 28th November 2025. Past this date, the deployed frontend will no longer display the various trade routes, though other features will work as intended. To see the trade route visualisation after the trial expires, you must run all endpoints locally.
168168

169169
### Backend Setup
170170
```bash

0 commit comments

Comments
 (0)