From 9420c89f524c585eb15b083c33fa69d97558f031 Mon Sep 17 00:00:00 2001
From: u1 <u1@rv32i.pl>
Date: Thu, 8 Jan 2026 06:00:23 +0000
Subject: [PATCH] docs: update Vite staging proxy instructions

---
 README.md | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index e59377c..d5250dc 100644
--- a/README.md
+++ b/README.md
@@ -18,13 +18,14 @@ Najprościej: trzymaj `VITE_API_URL=/api` i podepnij Vite proxy do VPS (żeby ni
 
 ```bash
 cd apps/visualizer
-API_PROXY_TARGET=https://trade.rv32i.pl/api \
-API_PROXY_BASIC_AUTH='USER:PASS' \
+API_PROXY_TARGET=https://trade.mpabi.pl \
 npm run dev
 ```
 
-Zamiast `API_PROXY_BASIC_AUTH` możesz użyć pliku JSON z polami `username`/`password`:
-`API_PROXY_BASIC_AUTH_FILE=tokens/frontend.json`.
+Vite proxy’uje wtedy: `/api/*`, `/whoami`, `/auth/*`, `/logout` do VPS. Dodatkowo w dev usuwa `Secure` z `Set-Cookie`, żeby sesja działała na `http://localhost:5173`.
+
+Jeśli staging jest dodatkowo chroniony basic auth (np. Traefik `basicAuth`), ustaw:
+`API_PROXY_BASIC_AUTH='USER:PASS'` albo `API_PROXY_BASIC_AUTH_FILE=tokens/frontend.json` (pola `username`/`password`).
 
 ## Docker