Skip to content

Set up development environment + AGENTS.md cloud instructions#4

Draft
HornLakeFire wants to merge 1 commit into
mainfrom
cursor/setup-dev-environment-b4b8
Draft

Set up development environment + AGENTS.md cloud instructions#4
HornLakeFire wants to merge 1 commit into
mainfrom
cursor/setup-dev-environment-b4b8

Conversation

@HornLakeFire

Copy link
Copy Markdown
Collaborator

Summary

Sets up the local development environment for the Horn Lake Fire Department dashboards app and documents how to run it for future Cursor Cloud agents.

  • Adds AGENTS.md with a ## Cursor Cloud specific instructions section covering how to run the standalone Express dev server, expected no-secret behavior (Firestore/Active911 logs are non-fatal), good endpoints to verify, and the available npm run check syntax check.
  • Update script configured as npm install (no build/test framework exists in this repo).

Environment verification

  • npm install — dependencies installed (290 packages).
  • npm run checknode --check server.js passes.
  • node server.js — server boots on port 10000; Firestore/Active911 warnings are expected without secrets and handled gracefully.
  • GET /api/health, GET /api/analytics-dashboard, and the /analytics UI all return/render real data from bundled CSVs.

Hello-world demonstration

Loaded the /analytics dashboard in Chrome — it renders real incident analytics (1,286 total calls; 160 Fire / 932 EMS / 194 Other), monthly call-volume chart, incident-type breakdown, recent incidents, and busiest addresses.

analytics_dashboard_demo.mp4
Analytics dashboard rendered with real data

To show artifacts inline, enable in settings.

Open in Web Open in Cursor 

Co-authored-by: jeremy <jeremyepowell@hotmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants