ozan
a81a450e7e
Merged into tinqs/studio: - cmd/tinqs-cli/ — tinqs-cli (Go binary, from bot/cli) - cmd/tea/ — Gitea CLI tool (from tinqs/cli-tea) - services/bot/ — Bot service (from tinqs-ltd/bot on git.arikigame.com) - services/admin/ — Admin panel (from tinqs/admin) - services/team-tool/ — Team Tool (from tinqs/team-tool) - services/proxy/ — tinqs-proxy (from bot/proxy) - web/landing/ — tinqs.com website (from tinqs/website) - web/docs/ — Platform docs (from tinqs/docs) - web/blog/ — Blog (placeholder) - runner/ — Ephemeral CI runner (from tinqs/runner) All source repos will be deleted after verification.
1.3 KiB
1.3 KiB
API architecture (classical Next)
This app exposes one HTTP server: Next.js (standalone output in Docker).
Data layer (no ORM)
- PostgreSQL via
pgonly —src/lib/db.ts(query,queryOne). - Migrations — raw SQL in
db/migrations/anddb/schema.sql. - Do not add Prisma, Drizzle ORM, TypeORM, or similar as the primary data access layer.
Hosting & network (yes)
- AWS — e.g. Lightsail; Docker on the host is the expected shape unless we document otherwise.
- Tailscale — primary access path for the team; see
docs/TAILSCALE-PRODUCTION.md(identity headers, optional whois proxy,tailscale serve).
Where handlers live
| Area | Path |
|---|---|
| Route handlers | src/app/api/**/route.ts |
| Infra REST (v1) | src/app/api/v1/** |
| Gateway merge (MCP, chat, votes, …) | src/app/api/mcp, chat, votes, … |
| Shared logic | src/lib/ |
| Edge / global | src/middleware.ts |
What we avoid
- A second Node HTTP server in-process for the same routes.
- Splitting “API” into another deployable without a strong reason.
Monorepo (future)
If the repo grows, introduce workspaces (packages/*) for shared types and clients; keep all user-facing HTTP in this Next app’s app/api tree.