Portfolio API

Read in Spanish

Minimal public backend for the portfolio ecosystem.

This repository owns the server-side dynamic contract consumed by the frontend and stays intentionally narrow: contact, chat, and subscription facade endpoints.

---

Role In The Ecosystem

• portfolio: public frontend, static editorial content, and Firebase deployment.
• portfolio-api: public dynamic API for contact, chat, and subscriptions.
• portfolio-cloud: cloud automation, subscriber persistence, notifications, and canonical chat knowledge publication.

---

Public Contract

Current public endpoints:

• GET /api/health
• POST /api/contact
• GET /api/chat/starters
• POST /api/chat
• POST /api/subscriptions
• DELETE /api/subscriptions

---

Main Features

• Contact form endpoint with validation and anti-spam controls
• Hybrid chat runtime for starters and portfolio assistant responses
• Minimal subscription facade delegated to portfolio-cloud
• Remote chat knowledge loading from R2 with local fallback for development or contingency
• DTO validation, throttling, and automated tests

---

Stack

• NestJS
• TypeScript
• AWS SDK for R2 access
• Resend
• Jest

---

Runtime Notes

• The API must not serve static editorial content.
• Blog posts and projects remain owned by portfolio.
• Subscription persistence and post-publication automation remain owned by portfolio-cloud.
• The chat runtime resolves the canonical editorial knowledge published from the cloud layer.

---

Local Development

npm install
npm run start:dev

Useful commands:

• npm run build
• npm run lint
• npm test
• npm run test:e2e

Environment setup is documented in .env.example.

---

Version

Current application version: 1.1.0