Private
Public Access
ksmithandClaude Sonnet 5
1c2d2e91c1
The service worker cached /api/rooms/mine, /api/rooms, .../messages, .../members, and /api/invites/mine with StaleWhileRevalidate: serve the previous cached response immediately, refresh the cache in the background for next time. That means every repeat visit showed content one visit behind -- reopening a room after someone messaged it, or checking a second device, both showed stale data until a manual reload (which finally picked up the now-revalidated cache). Only registers in a production build (vite dev never activates it), which is why this didn't surface during in-browser testing this session for #26/#27/#34. Switched all five routes to NetworkFirst: always prefer a live response, fall back to cache only when the network request itself fails or times out (genuinely offline), keeping the "readable while offline" behavior without the staleness. Verified against a real production build (`vite preview`, the only way the SW actually registers): sent a message from a second session against an already-cached room, and the very next fetch showed it immediately with no staleness. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
DS Chat
A web-based team chat service (Mattermost-style, no threaded conversations), invite-only. See ARCHITECTURE.md for the full system design and phased build plan.
Phase 1: auth, open-room CRUD, and single-instance WebSocket chat, backend
- a minimal frontend. Phase 2: private rooms, room roles (owner/admin/ member), and room invites — backend only, see below. Later phases (push notifications, Redis fan-out, the admin portal, the bot/extension system, and production deployment) are tracked as issues in the repo's issue tracker, prioritized.
Structure
backend/— FastAPI + SQLAlchemy 2.0 (async) + PostgreSQL. Seebackend/README.mdfor local setup, migrations, how to create a user (site registration is invite-only — no public sign-up endpoint), and the Phase 2 room-roles/invites API.frontend/— React + Vite PWA (login, room list, chat view). Still Phase-1-only: it doesn't yet call any of the Phase 2 endpoints. A UI redesign is happening separately; frontend work resumes once that lands.
Quickstart
# 1. Postgres (see backend/README.md for details)
docker run -d --name ds-chat-postgres \
-e POSTGRES_USER=ds_chat -e POSTGRES_PASSWORD=ds_chat -e POSTGRES_DB=ds_chat \
-p 5432:5432 postgres:16-alpine
# 2. Backend
cd backend
python3 -m venv .venv
.venv/bin/pip install -e ".[dev]"
cp .env.example .env # then set SESSION_SECRET
.venv/bin/alembic upgrade head
.venv/bin/python -m app.cli create-user alice alice@example.com "some-password"
.venv/bin/uvicorn app.main:app --reload &
# 3. Frontend (in another shell)
cd frontend
npm install
npm run dev
Then open http://localhost:5173 and log in with the account created above.
The Vite dev server proxies /api and /ws to the backend on :8000, so no
CORS configuration is needed in development.
Deployment
See DEPLOYMENT.md for the full production runbook — two Debian 13 servers, no containers, matching ARCHITECTURE.md §9.