webadderall
f007984ebc
Preserve renderer state through mute and export transitions, gate hover previews on a composed frame, and align timeline bounds with authored zoom intervals. Improve settings, cursor and webcam controls, inline recording countdown, project recovery and safe library cleanup.
2.5 KiB
Recordly cloud sharing
Recordly's Publish menu can save the current edit as a local file or create a shared link. The account menu opens sign-in. Sharing renders an MP4 to a temporary file, uploads it to Recordly Share, finalizes its metadata, and removes the temporary file when the dialog closes.
Development defaults to the local endpoint when VITE_CLOUD_SHARE_ENDPOINT is unset:
http://localhost:8787/api/upload
The endpoint is intentionally not user-configurable. Packaged builds require an
explicit VITE_CLOUD_SHARE_ENDPOINT; without it, cloud sharing is unavailable.
Production releases target https://videos.recordly.dev/api/upload. The production
service must be deployed and verified before release. Publishing requires the
user's Recordly access token. No share API secret is exposed in the app. Hosted deployment and subscription
operations are maintained with the separate private service.
Publishing protocol
POST /api/uploadcreates a recording and share code.- Small files use
PUT /api/upload-data/:shareCode; files over 50 MB use multipart uploads in retryable 25 MB chunks. POST /api/metadata/:shareCodepublishes the title and creator notes.- The returned
/s/:shareCodeURL opens the complete viewing and feedback page.
The service provides R2 video storage, D1 metadata, range streaming, a responsive viewing page, timestamped comments, reactions, captions, password protection, expiry, and a private video library. See the service README for local and deployment instructions.
Comments
Anyone with a valid link can watch a public recording. Leaving timestamped feedback requires a signed-in account; Recordly Cloud uses the viewer’s verified Recordly account and profile name. The server derives comment authorship from the session, and viewers can edit or delete their own comments. Account and IP rate limits and the 2,000-character comment limit apply. Self-hosted viewers sign in to the account system configured by that service.
Third-party licensing
The hosting service is based on MIT-licensed open-source software. Required attribution and the complete license text are preserved in THIRD_PARTY_NOTICES.md and the vendored license.
The self-hosted worker is a single-owner library. Set OWNER_USER_ID to the owner’s Supabase user ID. Other accounts in the same Supabase project cannot administer the library. Missing owner configuration disables Supabase bearer access.