feat: improve OpenList cloud storage support

This commit is contained in:
ShukeBta
2026-06-10 00:08:35 +08:00
parent 9f2d7a507b
commit 0f82cb3084
16 changed files with 635 additions and 50 deletions
+12 -4
View File
@@ -362,18 +362,26 @@ If qBittorrent also runs in Docker, mount the same host download directory as `/
With smart classification enabled, downloads are saved to folders such as `/downloads/动画电影`, `/downloads/国产剧`, and `/downloads/综艺`.
### Cloud Drives and CloudDrive2
### Cloud Drives, OpenList, and CloudDrive2
MediaStationGo supports Alist, WebDAV, 115, Quark, and CloudDrive2 as external storage backends. For most users, CloudDrive2 or Alist is the recommended bridge layer: CloudDrive2 already integrates many cloud drives such as 115, 123Pan, Aliyun Drive, and Quark, while MediaStationGo can use its WebDAV endpoint for browsing, library mounting, local-media upload, and authenticated proxy playback.
MediaStationGo supports OpenList, Alist, WebDAV, 115, Quark, and CloudDrive2 as external storage backends. For most users, OpenList, CloudDrive2, or Alist is the recommended bridge layer: they can integrate many cloud drives such as 115, 123Pan, Aliyun Drive, and Quark, while MediaStationGo can use OpenList/Alist APIs or WebDAV endpoints for browsing, library mounting, local-media upload, and authenticated proxy playback.
Typical setup:
Typical OpenList setup:
1. Mount your 115 / 123Pan / Aliyun / Quark drive inside OpenList.
2. Select `OpenList` in MediaStationGo → External Storage.
3. Set `OpenList Server URL` to the management/API endpoint, for example `http://NAS-IP:5244`.
4. Set `WebDAV URL` to the WebDAV endpoint, for example `http://NAS-IP:5244/dav/`.
5. Do not use `https://` unless OpenList is actually behind an HTTPS reverse proxy. `Propfind "https://...": http: server gave HTTP response to HTTPS client` means an HTTP service was entered as HTTPS.
Typical CloudDrive2 setup:
1. Mount your 115 / 123Pan / Aliyun / Quark drive inside CloudDrive2.
2. Select `CloudDrive2` in MediaStationGo → External Storage.
3. Fill the CloudDrive2 WebDAV URL, for example `http://host.docker.internal:19798/dav` or `http://NAS-IP:19798/dav`.
4. Save the config, then browse the cloud directory or mount it as a media library.
The native 115 adapter still supports cookie / QR login, directory browsing, and 302 playback. For local file upload, prefer CloudDrive2 / Alist bridging instead of maintaining every provider's private chunk-upload protocol inside this project.
The native 115 adapter still supports cookie / QR login, directory browsing, and 302 playback. For local file upload, prefer OpenList / CloudDrive2 / Alist bridging instead of maintaining every provider's private chunk-upload protocol inside this project.
---