Qlockify Deployment

This repository is the deployment layer only.

It does not contain application source copies. Docker builds read directly from the sibling repositories:

Local structure

The expected directory layout is:

Qlockify/
  qlockify-backend/
  qlockify-frontend/
  qlockify-deployment/

Configure deployment env files:
- ./.env
- ./backend/.env
- ./frontend/.env
From qlockify-deployment, build and start the stack:

docker compose up --build

The backend container runs database migrations and collectstatic on startup, then serves Django with Gunicorn using config.wsgi:application.

Notifications now use Server-Sent Events at /api/notifications/stream/.

Nginx disables buffering and cacheing for the SSE endpoint.
The current Gunicorn setup can serve SSE for MVP traffic, but each live stream consumes a worker while connected.
If notification concurrency grows, move the SSE endpoint to an async worker class or a dedicated ASGI process.