ad60247f33
- Web: Setup Storybook, added addons, configured Tailwind, added stories for UI components. - Backend: Updated API router, database, workers, and auth in common. - Stream Server: Removed SQLx queries and updated auth. - Docs & Scripts: Updated documentation and recovery scripts.
42 lines
1.4 KiB
Markdown
42 lines
1.4 KiB
Markdown
# Veza Minimal Web Stack
|
|
|
|
> **Goal**: Run a functional end-to-end version of Veza with the absolute minimum resources.
|
|
|
|
## 🚀 How to Run
|
|
|
|
```bash
|
|
# 1. Start everything (DB, Redis, Backend, Frontend)
|
|
make web-minimal
|
|
|
|
# 2. View in Browser
|
|
# http://localhost:5173
|
|
```
|
|
|
|
## 🛠️ Components
|
|
- **Frontend**: Vite Dev Server (Port 5173). Bundled minimal.
|
|
- **Backend**: Go API (Port 8080).
|
|
- **Database**: Postgres + Redis (Docker).
|
|
- **Ignored**: Chat Server, Stream Server, Workers, S3, MinIO.
|
|
|
|
## ✅ Verified User Journey
|
|
We have verified that the following core loop works:
|
|
1. **Registration** (New User)
|
|
2. **Login** (JWT Token access)
|
|
3. **Create Playlist** (Write to DB)
|
|
4. **List Playlists** (Read from DB)
|
|
|
|
You can verify this yourself by running:
|
|
```bash
|
|
./scripts/verify_minimal_journey.sh
|
|
```
|
|
|
|
## ⚠️ Known Limitations
|
|
- **Profile Endpoint**: The `/api/v1/profile` or `/auth/me` endpoint returns 404 in some contexts. The frontend likely relies on the User object returned during Login.
|
|
- **Chat**: Disabled. Chat page will likely fail or show loading.
|
|
- **Uploads**: Disabled/Mocked. S3 is not running.
|
|
- **Critical JS**: We are still missing `<noscript>` tags (as reported by TMT).
|
|
|
|
## 🔧 Technical Fixes Applied
|
|
- **JWT_SECRET**: Increased length to meet 32-char security requirement.
|
|
- **Backend Router**: Fixed a panic caused by duplicate `/health` route registration.
|
|
- **Env**: Auto-generated minimal `.env` if missing.
|