Skip to content

Add Cursor Cloud dev environment setup instructions - #9

Draft
mnjit20 wants to merge 1 commit into
mainfrom
cursor/setup-dev-environment-e9f8
Draft

Add Cursor Cloud dev environment setup instructions#9
mnjit20 wants to merge 1 commit into
mainfrom
cursor/setup-dev-environment-e9f8

Conversation

@mnjit20

@mnjit20 mnjit20 commented Jul 6, 2026

Copy link
Copy Markdown
Owner

Summary

Sets up the development environment for this multi-project repo and documents durable, non-obvious setup guidance for future Cloud Agents in a new AGENTS.md.

This repo is a collection of independent Node.js/TypeScript sub-projects (no root workspace). The two real products are teaching-material-search (Express) and db-search (Fastify), both backed by PostgreSQL 16.

What was set up in the environment

  • PostgreSQL 16 installed natively (Docker is unavailable in this env), started, and databases teaching_materials + db-search created.
  • npm install run for all sub-projects (also captured as the startup update script).
  • .env files created for both products (gitignored, documented in AGENTS.md for recreation).

Verification

Both products were built, tested, and run end-to-end:

Product build test run + search
teaching-material-search npm run build vitest run (5/5) ✅ npm run dev/api/search returns ranked results ✅
db-search npm run build / typecheck tsx --test (9/9) ✅ npm run dev/api/search + POST /api/documents ingest ✅

Browser demo of the teaching-material-search search UI:

teaching_material_search_demo.mp4

Search results for

Changes

  • Added AGENTS.md with ## Cursor Cloud specific instructions (native Postgres startup, DB creation, gitignored .env contents, port 3000 conflict, per-product migrate/seed vs auto-seed notes).

To show artifacts inline, enable in settings.

Open in Web Open in Cursor 

Co-authored-by: Manjeet Verma  <mnjit.vrma@gmail.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