Developer Login
This is only UI gating (not real security). Use it to keep the portal clean for your team.
RTC media infrastructure endpoint: audio rooms, video calls, participant presence signals.
Not chat storage, not gifts/coins logic, not ranking engine — those belong in your backend.
Flutter/Web → Backend (auth & business) + WebSocket (chat/events) + LiveKit (media) + TURN (relay).
Don’t paste API secrets into frontend. Tokens must come from backend.
LiveKit (Flutter native WS): ws://livekit.ronniemarket.com:8443
TURN (UDP): turn:livekit.ronniemarket.com:3478?transport=udp
Token source: Your backend (Laravel/Node/etc.)
Web support: Requires HTTPS + WSS (recommended separate rtc subdomain)
Select your stack. These are global high-level steps (not full documentation).
Use Laravel to generate LiveKit tokens. Flutter receives url + token + ICE servers then connects.
- Backend: Auth user, decide role (speaker/listener), generate RTC token.
- Client: Call backend → connect to LiveKit → publish mic if speaker.
- Chat/gifts/presence: use your WebSocket or Laravel broadcasting separately.