How eugustavokeller/clone-tabnews works
Project type and purpose
• It provides both a frontend (React pages under /pages) and a backend API (serverless routes under /pages/api/v1).
• It persists data via a relational database (migrations under infra/migrations and /pages/api/v1/migrations).
File structure
• Top-level directories:
• pages/ – Next.js pages and API routes
• infra/ – infrastructure artifacts (Docker Compose, database configuration, migrations)
• tests/ – integration tests for the API
• Config files like .env.development, compose.yaml, and database.js indicate a Dockerized local environment and DB connection logic.
• The presence of migrations in two places suggests a clear data schema management layer.
README for additional insights
• The README only contains the project title, so we rely on structure to infer architecture.
Detail and essential elements
• Do not omit the migrations component—capture both the infra/migrations folder and the in-API migrations routes.
• Clearly separate the Next.js runtime (renders UI) from its API runtime (handles data).
• How environment variables (.env.development) plug into the database connection.
• Test suite’s role in validating the API behavior against a running instance.