Deployment & operations
Notes for running MeetOye on the shared Windows/IIS environment.
Production MeetOye runs on a shared Windows/IIS host with the Node services managed by PM2. A few environment-specific constraints matter when deploying.
Services & routing
- LiveKit signalling runs through a Node proxy (meetoye-livekit-proxy) on port 7443 — not IIS. Set LIVEKIT_PUBLIC_URL=wss://livekit.meetoye.com:7443.
- Raise the IIS maxQueryString on livekit.meetoye.com, or joins 404 and the room bounces back to the dashboard.
- The live API uses the meetoye_app database and the meetoye_user role.
Transactional email (recaps, notifications) is sent through a global MailService via Resend. The sender domain must be verified in Resend or sends fail.
lightbulb
The home shell is statically prerendered; HTML documents are served no-store so deploys show without a hard refresh, while hashed static chunks keep their long immutable cache.