Repository navigation
Realtime Setup
How live updates actually work across the stack, operationally. Architecture and rationale: Realtime and Notifications.
-
Backend:
chat.service.tsusesStreamChat.getInstancewithSTREAM_API_KEY/STREAM_API_SECRET. Appointment channels are windowed by appointment status; there's also network/colleague chat. Stream posts events back to the raw-body webhook/v1/chat/webhooks/stream(ChatWebhookController.handleStreamEvent). At boot,config/stream-upload-policy.tspushes a blocked-extension allowlist to Stream. -
Web:
features/chat/services/streamChatService.ts+chatService.ts;features/chat/hooks/useChatNotifications.tslistens toclient.on('message.new')and raises a browser Notification when the tab is hidden. The CSP allowlistschat.stream-io-api.com+wss:(Frontend Overview). -
Mobile:
stream-chat-react-nativeviasrc/features/chat/services/streamChatService.ts.
Beyond chat, the web app keeps itself fresh without a socket event bus:
-
Custom window events +
useSyncExternalStore: e.g.useAppointmentLockWindow.tssubscribes to ayc:appointment-lock-window-changedevent and thestorageevent so multiple tabs stay consistent;SessionInitializerruns aMutationObserverterminology rewriter keyed onyc:companion-terminology-changed. -
Bulk hydration on org change:
SessionInitializerfiresPromise.allSettled([...loadX({silent:true})])across all org-scoped Zustand stores whenever the primary org changes.
-
Mobile:
firebase-admin(server) → FCM → Notifee (device), routed via ayc://deep link. Setup: Notifications Setup. - Device tokens are registered/unregistered through
deviceToken.service.ts.
queues/index.ts (initQueues()) starts BullMQ queues on the shared Redis connection (queues/bull.config.ts), processed by src/workers: appointment no-show, task recurrence/reminder/schedule, and IDEXX lab sync/status/results. Redis env vars are shared with the rest of the app.
docs/guide/realtime-backend.md proposes a Redis Pub/Sub + Socket.IO EventBus that would fan org:{orgId}:events out to browsers, with a shared OrgEvent contract and a frontend hook to apply them. This is not implemented — socket.io is an installed dependency but no Socket.IO server exists in apps/backend, and there is no useRealtimeSync hook in the frontend. If you're wiring browser live-sync, that guide is the starting design; today, use the mechanisms above.
Home · Architecture · ADRs · Plans · Roadmap · Contributing · Main repo · DeepWiki · Discord
Yosemite Crew is a product of DuneXploration UG (haftungsbeschränkt). This wiki mirrors the repository; where a page and the repo disagree, the repo wins. See the Wiki Style Guide.
Product & Domain
Architecture
Applications
- Backend — Overview
- Frontend / PIMS Web — Overview
- Mobile — Overview
- Desktop PIMS Shell
- Developer Portal
- SuperAdmin
Design & Accessibility
Engineering Handbook
Decisions (ADRs)
Design Docs & Plans
Meta
Canonical code & docs: main repo · Auto-generated companion: DeepWiki