Storage connectors
Attach release binaries via Google Drive, OneDrive, or a custom server instead of pushing large files through the core API on every upload.
Storage connectors link LicenPro to external file hosts. Use them when installers, delta packages, or release notes live on cloud drives or your own CDN—release records in LicenPro still point to version metadata while artifacts resolve from remote storage.
Storage lifecycle
- Connect — authenticate provider at Storage hub.
- Configure — pick folders, credentials, or custom server base URL.
- Upload / link — place binaries in provider UI or LicenPro storage browser.
- Bind to release — associate artifact path/id when editing a release.
- SDK update check — client resolves download URL via update API + storage metadata.
- Revoke — disconnect provider; existing release links may break until re-linked.
Storage hub
Sidebar: Storage. Connect external file hosts before you attach binaries to releases.
Provider comparison
- Google Drive — OAuth to Google; browse folders; upload/list/delete via
/api/Storage/…or Drive-specific routes. - OneDrive — Microsoft OAuth; similar list/upload semantics via
/api/OneDriveStorage/…. - Custom server — your HTTPS endpoint; LicenPro proxies list/upload/delete per
/api/CustomServerStorage/…; requires Pro guard in UI.
Operator workflow
- Open Storage from sidebar.
- Choose provider → complete OAuth or enter server URL + credentials.
- Verify test upload appears in provider browser.
- When publishing a release, attach artifact reference instead of embedding large blobs in API payloads.
- Validate SDK update path downloads from expected URL in staging.
Roles & plans
- Product owners — typically configure storage used by their releases.
- Custom server — may require Pro subscription (plan guard on route).
- System Admin — troubleshoot connector OAuth failures platform-wide.