This repository has been archived on 2026-08-10. You can view files and clone it. You cannot open issues or pull requests or push a commit.
Files
admin e1e1b7ab21 Fundament: Zentrale Auth-Leitlinie & RequestUser vereinheitlicht (#241)
- Guard-first Auth-Architektur dokumentiert
- RequestUser als einzige User-Wahrheit etabliert
- Keine Auth-Logik in Services
- Public-Routen explizit via @Public()
- Vorbereitung für JWT ohne Service-Änderungen
2026-01-01 14:12:49 +01:00

59 lines
1.9 KiB
Markdown

This is a [Next.js](https://nextjs.org) project bootstrapped with [`create-next-app`](https://nextjs.org/docs/app/api-reference/cli/create-next-app).
## Getting Started
First, run the development server:
```bash
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
```
Open [http://localhost:3000](http://localhost:3000) with your browser to see the result.
You can start editing the page by modifying `app/page.tsx`. The page auto-updates as you edit the file.
This project uses [`next/font`](https://nextjs.org/docs/app/building-your-application/optimizing/fonts) to automatically optimize and load [Geist](https://vercel.com/font), a new font family for Vercel.
## Learn More
To learn more about Next.js, take a look at the following resources:
- [Next.js Documentation](https://nextjs.org/docs) - learn about Next.js features and API.
- [Learn Next.js](https://nextjs.org/learn) - an interactive Next.js tutorial.
You can check out [the Next.js GitHub repository](https://github.com/vercel/next.js) - your feedback and contributions are welcome!
## Deploy on Vercel
The easiest way to deploy your Next.js app is to use the [Vercel Platform](https://vercel.com/new?utm_medium=default-template&filter=next.js&utm_source=create-next-app&utm_campaign=create-next-app-readme) from the creators of Next.js.
Check out our [Next.js deployment documentation](https://nextjs.org/docs/app/building-your-application/deploying) for more details.
## Auth-Architektur (Grundlagen)
### Prinzipien
- Guard-first Architektur
- Keine Auth-Logik in Services
- Controller bleiben dünn
- Zentrale User-Wahrheit über Request-Kontext
### RequestUser
- `req.user` ist der einzige User-Kontext im Request
- Typ: `RequestUser`
- ID ist **number** (DB-kompatibel)
- Kann `null` sein (Public Routes)
```ts
export type UserRole = 'USER' | 'ADMIN' | 'MOD';
export type RequestUser = {
id: number;
role: UserRole;
isFake?: boolean;
} | null;