soroush.asadi 60e2ac1355
CI/CD / CI · API (dotnet build + test) (push) Successful in 1m53s
CI/CD / CI · Admin API (dotnet build) (push) Successful in 1m37s
CI/CD / CI · Dashboard (tsc) (push) Successful in 1m5s
CI/CD / CI · Admin Web (tsc) (push) Successful in 35s
CI/CD / CI · Website (tsc) (push) Successful in 44s
CI/CD / CI · Koja (tsc) (push) Successful in 1m8s
CI/CD / Deploy · all services (push) Successful in 1m40s
fix(auth): non-rotating, sliding refresh tokens to stop the OTP storm
Login already issues a 7-day access token + 30-day refresh token, and the
dashboard persists the session and silently refreshes on 401 — so a session
should last well over a week. The real cause of "re-login every time / massive
OTP" was single-use refresh-token rotation: RefreshAsync revoked the presented
token and minted a new one, so when a café runs POS + KDS + queue display at
once (or two tabs), the first refresh won the race and every other concurrent
refresh hit the now-revoked token -> INVALID_TOKEN -> forced logout -> OTP.

Make refresh idempotent and race-safe:
- IssueTokensAsync takes an optional existingRefreshToken; on refresh we reuse
  the presented token and re-store it (sliding the 30-day TTL) instead of
  minting a new one. Login still mints a fresh token.
- RefreshAsync no longer revokes the presented token.

Net effect: concurrent refreshes all succeed; an active session slides forward
and effectively never forces re-auth. Access stays 7 days, refresh 30 days.
All 81 API tests pass.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-02 15:09:25 +03:30
2026-05-31 13:01:38 +03:30
2026-05-31 11:06:24 +03:30
2026-05-31 11:31:05 +03:30
2026-05-31 11:06:24 +03:30
2026-05-31 11:06:24 +03:30
2026-05-31 11:06:24 +03:30
2026-05-31 11:06:24 +03:30
2026-05-28 20:43:35 +03:30

Meezi — Day 1 Quick Start

Step 1 — Copy these 4 files to your project root

.cursorrules ← AI rules for Cursor MEEZI_CURSOR_GUIDE.md ← Full development guide docker-compose.yml ← Local DB + Redis README.md ← This file

Step 2 — Start local services

docker-compose up -d

Step 3 — Create project structure

mkdir meezi && cd meezi git init

mkdir src web mobile cd src dotnet new sln -n Meezi dotnet new webapi -n Meezi.API --use-controllers dotnet new classlib -n Meezi.Core dotnet new classlib -n Meezi.Infrastructure dotnet new classlib -n Meezi.Shared dotnet sln add Meezi.API Meezi.Core Meezi.Infrastructure Meezi.Shared

cd ../web npx create-next-app@latest dashboard --typescript --tailwind --app

cd ../mobile flutter create meezi_app --org ir.meezi

Step 4 — Open in Cursor

cursor . (from the meezi/ root folder)

Step 5 — Paste this FIRST prompt in Cursor chat (Cmd+L)

Read .cursorrules and MEEZI_CURSOR_GUIDE.md completely. Then do Sprint 1 Week 1:

  1. Set up the .NET solution with proper references between projects
  2. Add all NuGet packages listed in the guide to each project
  3. Create the complete EF Core entity schema from the guide
  4. Set up AppDbContext with all DbSets
  5. Create TenantMiddleware and ITenantContext
  6. Set up Program.cs with full middleware pipeline

Cursor Chat Tips

Ask one sprint at a time

"Do Sprint 2: build the POS order APIs (menu, tables, orders)"

Reference specific sections

"Build the CRM endpoint from Step 10 of MEEZI_CURSOR_GUIDE.md"

Debug with context

"The order API returns 403. Check if TenantMiddleware is injecting CafeId correctly"

Generate Flutter screens

"Build the Flutter POS screen from Sprint 2 in the guide. RTL, Farsi, Riverpod state"


Useful Cursor Keyboard Shortcuts

Cmd+L → Open AI chat Cmd+K → Inline AI edit (select code first) Cmd+I → Composer (multi-file edits) Cmd+. → Quick fix / suggestion Tab → Accept autocomplete


Local URLs when running

Backend API: https://localhost:7001 API Swagger: https://localhost:7001/swagger Dashboard: http://localhost:3000 Hangfire UI: https://localhost:7001/hangfire Flutter web: http://localhost:8080

S
Description
No description provided
Readme 8.4 MiB
Languages
C# 47.1%
TypeScript 46.1%
Dart 3.7%
MDX 1.8%
Shell 0.5%
Other 0.6%