Private
Public Access
ksmithandClaude Sonnet 5
c79e96dd48
Adds room_invites table + migration, owner/admin/member role enforcement (require_room_role), and endpoints for private room creation, room management (update/delete/leave/transfer-ownership/change-role/remove-member), and the invite lifecycle (create/list/accept/decline/revoke). Registration stays invite-only via the CLI from Phase 1 — this is a separate, room-level invite system for adding existing users to private rooms. Frontend is untouched: the UI redesign is happening separately, so this phase is backend + tests only (35 passing). Verified no regressions in the Phase 1 open-room/WebSocket flow via manual smoke test. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
56 lines
2.1 KiB
Markdown
56 lines
2.1 KiB
Markdown
# KeepItTalking
|
|
|
|
A web-based team chat service (Mattermost-style, no threaded conversations),
|
|
invite-only. See [ARCHITECTURE.md](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/`](backend/) — FastAPI + SQLAlchemy 2.0 (async) + PostgreSQL. See
|
|
[`backend/README.md`](backend/README.md) for 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/`](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
|
|
|
|
```bash
|
|
# 1. Postgres (see backend/README.md for details)
|
|
docker run -d --name chatapp-postgres \
|
|
-e POSTGRES_USER=chatapp -e POSTGRES_PASSWORD=chatapp -e POSTGRES_DB=chatapp \
|
|
-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
|
|
|
|
Not part of Phase 1. The target is two plain Linux servers with no
|
|
containers — see [ARCHITECTURE.md §9](ARCHITECTURE.md#9-deployment-architecture--two-linux-servers-no-docker)
|
|
and the corresponding "Production deployment" issue in the tracker.
|