modeling-app/.env.development

VITE_KC_API_WS_MODELING_URL=wss://api.dev.kittycad.io/ws/modeling/commands
VITE_KC_API_BASE_URL=https://api.dev.kittycad.io
VITE_KC_SITE_BASE_URL=https://dev.kittycad.io
VITE_KC_CONNECTION_TIMEOUT_MS=5000
VITE_KC_CONNECTION_WEBRTC_REPORT_STATS_MS=30000
VITE_KC_SENTRY_DSN=https://a814f2f66734989a90367f48feee28ca@o1042111.ingest.sentry.io/4505789425844224
Configurable URL for the API (#205) * Configurable engine URL Fixes #206 * fix import.meta problem (#210) --------- Co-authored-by: Kurt Hutten <k.hutten@protonmail.ch> 2023-08-01 09:36:40 -05:00			`VITE_KC_API_WS_MODELING_URL=wss://api.dev.kittycad.io/ws/modeling/commands`
			`VITE_KC_API_BASE_URL=https://api.dev.kittycad.io`
Have separate SITE_URL env from API_URL (#234) 2023-08-07 13:07:40 -04:00			`VITE_KC_SITE_BASE_URL=https://dev.kittycad.io`
Make the timeout for a WebRTC/WebSocket connection pair configurable (#310) Signed-off-by: Paul Tagliamonte <paul@kittycad.io> 2023-08-23 16:49:04 -04:00			`VITE_KC_CONNECTION_TIMEOUT_MS=5000`
Add in Sentry, WebRTC Statistics (#345) Collect WebRTC Statistical Information Add in some instrumentation to track the duration of the setup phase, and set up a job to make periodic use of the WebRTC Statistics API to collect information about the connection (specifically, each track), including transport-level information, timing information and bandwidth information. Sentry isn't the best place for that information, but it'll work until we can work out a good long-term solution for it. Signed-off-by: Paul Tagliamonte <paul@kittycad.io> 2023-08-30 10:34:14 -04:00			`VITE_KC_CONNECTION_WEBRTC_REPORT_STATS_MS=30000`
			`VITE_KC_SENTRY_DSN=https://a814f2f66734989a90367f48feee28ca@o1042111.ingest.sentry.io/4505789425844224`