+
+
+
+
+ {{ t('post.contributors') }}
+-
+
-
+
+ + {{ contributor.name }} + + {{ contributor.name }} +
+
+
+ ![OpenList]()
+
+
+ + {{ landing.name }} +
+{{ landing.tagline }}
+ + + + +{{ source }}{{ t('download.down_source') }}:
- + +{{ t('download.down_source') }}:
+ +
@@ -86,8 +87,8 @@
+
+
+ (() => (lang.value in messages ? (lang.value as Locale) : 'en'))
+
+ function t(key: string): string {
+ let value: unknown = messages[locale.value]
+ for (const part of key.split('.'))
+ value =
+ value && typeof value === 'object' ? (value as Record)[part] : undefined
+ return typeof value === 'string' ? value : key
+ }
+
+ return { t, locale }
+}
diff --git a/.vitepress/theme/index.ts b/.vitepress/theme/index.ts
new file mode 100644
index 000000000..66e3b2331
--- /dev/null
+++ b/.vitepress/theme/index.ts
@@ -0,0 +1,33 @@
+import mediumZoom from 'medium-zoom'
+import type { Theme } from 'vitepress'
+import { useRoute } from 'vitepress'
+import DefaultTheme from 'vitepress/theme'
+import { nextTick, onMounted, watch } from 'vue'
+import 'virtual:group-icons.css'
+import './style.css'
+import BiliBili from './components/BiliBili.vue'
+import Mermaid from './components/Mermaid.vue'
+import OpenListDownload from './components/OpenListDownload.vue'
+import WorkInProgress from './components/WorkInProgress.vue'
+import Layout from './Layout.vue'
+
+export default {
+ extends: DefaultTheme,
+ Layout,
+ enhanceApp({ app }) {
+ app.component('BiliBili', BiliBili)
+ app.component('Mermaid', Mermaid)
+ app.component('OpenListDownload', OpenListDownload)
+ app.component('WorkInProgress', WorkInProgress)
+ },
+ setup() {
+ const route = useRoute()
+ const initZoom = () =>
+ mediumZoom('.vp-doc :not(a) > img:not(.no-zoom)', { background: 'var(--vp-c-bg)' })
+ onMounted(initZoom)
+ watch(
+ () => route.path,
+ () => nextTick(initZoom)
+ )
+ },
+} satisfies Theme
diff --git a/.vitepress/theme/language.ts b/.vitepress/theme/language.ts
new file mode 100644
index 000000000..dbf8d3a0f
--- /dev/null
+++ b/.vitepress/theme/language.ts
@@ -0,0 +1,83 @@
+import { useData } from 'vitepress'
+import { onMounted, watch } from 'vue'
+
+type Lang = 'en' | 'zh-CN'
+
+const STORAGE_KEY = 'openlist-docs-lang'
+/** preference saved by the old Valaxy site */
+const LEGACY_STORAGE_KEY = 'valaxy-lang'
+const BOT_RE = /bot|crawl|spider|slurp|headless|lighthouse|prerender/i
+
+function read(key: string): string | null {
+ try {
+ return localStorage.getItem(key)
+ } catch {
+ return null
+ }
+}
+
+function write(key: string, value: string) {
+ try {
+ localStorage.setItem(key, value)
+ } catch {
+ // storage can be unavailable (private mode, blocked cookies): just don't remember
+ }
+}
+
+function asLang(value: string | null): Lang | null {
+ return value === 'en' || value === 'zh-CN' ? value : null
+}
+
+function detectBrowserLang(): Lang {
+ const languages = navigator.languages?.length ? navigator.languages : [navigator.language]
+ for (const language of languages) {
+ if (/^zh\b/i.test(language)) return 'zh-CN'
+ if (/^en\b/i.test(language)) return 'en'
+ }
+ return 'en'
+}
+
+/** Same page in the other language: `/foo` (Chinese) <-> `/en/foo`. */
+function counterpart(pathname: string, base: string, target: Lang): string | null {
+ if (!pathname.startsWith(base)) return null
+ const rel = pathname.slice(base.length)
+ const isEn = rel === 'en' || rel.startsWith('en/')
+ if (target === 'en') return isEn ? null : `${base}en/${rel}`
+ return isEn ? base + rel.replace(/^en\/?/, '') : null
+}
+
+/**
+ * On landing, send visitors to the language they used last time (or their
+ * browser language on the first visit); remember the language they browse in.
+ */
+export function useLanguageRedirect() {
+ const { lang, page, site } = useData()
+
+ onMounted(() => {
+ const current = asLang(lang.value)
+ if (
+ !current ||
+ page.value.isNotFound ||
+ navigator.webdriver ||
+ BOT_RE.test(navigator.userAgent)
+ )
+ return
+
+ const preferred =
+ asLang(read(STORAGE_KEY)) ?? asLang(read(LEGACY_STORAGE_KEY)) ?? detectBrowserLang()
+ if (preferred !== current) {
+ const target = counterpart(location.pathname, site.value.base, preferred)
+ if (target) {
+ write(STORAGE_KEY, preferred)
+ location.replace(target + location.search + location.hash)
+ return
+ }
+ }
+ write(STORAGE_KEY, current)
+ })
+
+ watch(lang, value => {
+ const current = asLang(value)
+ if (current) write(STORAGE_KEY, current)
+ })
+}
diff --git a/.vitepress/theme/style.css b/.vitepress/theme/style.css
new file mode 100644
index 000000000..4ded515cc
--- /dev/null
+++ b/.vitepress/theme/style.css
@@ -0,0 +1,137 @@
+/* Brand colors */
+:root {
+ --vp-c-brand-1: hsl(196, 55%, 45%);
+ --vp-c-brand-2: hsl(196, 59%, 51%);
+ --vp-c-brand-3: hsl(196, 54%, 57%);
+ --vp-c-brand-soft: hsla(196, 100%, 70%, 0.14);
+
+ --vp-home-hero-name-color: transparent;
+ --vp-home-hero-name-background: linear-gradient(to right, #99f6e4, #38bdf8);
+ --vp-home-hero-image-background-image: linear-gradient(-45deg, #99f6e4 50%, #38bdf8 50%);
+ --vp-home-hero-image-filter: blur(56px);
+}
+
+.dark {
+ --vp-c-brand-1: hsl(196, 100%, 83%);
+ --vp-c-brand-2: hsl(196, 74%, 63%);
+ --vp-c-brand-3: hsl(196, 70%, 55%);
+ --vp-c-brand-soft: hsla(196, 100%, 70%, 0.16);
+
+ --vp-c-bg: hsl(196, 7%, 11%);
+ --vp-c-bg-alt: hsl(196, 4%, 9%);
+ --vp-c-bg-elv: hsl(196, 10%, 14%);
+ --vp-c-bg-soft: hsl(196, 10%, 14%);
+}
+
+@keyframes fly {
+ from {
+ transform: translateY(0.5em);
+ }
+
+ to {
+ transform: translateY(-0.5em);
+ }
+}
+
+.fly-animation {
+ animation: fly 0.8s ease-in-out infinite alternate;
+}
+
+/* Theme images:  , see .vitepress/plugins/theme-image.ts */
+.theme-image-container {
+ position: relative;
+ display: inline-block;
+ max-width: 100%;
+}
+
+.theme-image-light,
+.theme-image-dark {
+ max-width: 100%;
+ height: auto;
+ transition: opacity 0.3s ease-in-out;
+}
+
+.theme-image-container .theme-image-light {
+ display: block;
+}
+
+.theme-image-container .theme-image-dark {
+ display: none;
+ position: absolute;
+ top: 0;
+ left: 0;
+ width: 100%;
+}
+
+.dark .theme-image-container .theme-image-light {
+ display: none;
+}
+
+.dark .theme-image-container .theme-image-dark {
+ display: block;
+}
+
+img.theme-image-light {
+ display: block;
+}
+
+img.theme-image-dark {
+ display: none;
+}
+
+.dark img.theme-image-light {
+ display: none;
+}
+
+.dark img.theme-image-dark {
+ display: block;
+}
+
+/* medium-zoom above the nav bar */
+.medium-zoom-overlay {
+ z-index: 30;
+}
+
+.medium-zoom-image--opened {
+ z-index: 31;
+}
+
+/* Privacy policy & terms of service */
+.statement-page .vp-doc h1 {
+ margin-bottom: 2rem;
+ padding: 1rem 0;
+ border-radius: 1rem;
+ background: var(--vp-c-brand-3);
+ box-shadow: 0 0 0.5rem rgba(0, 0, 0, 0.3);
+ color: white;
+ text-align: center;
+}
+
+.statement-page .vp-doc h2 {
+ color: var(--vp-c-brand-1);
+}
+
+/*
+ * 768–959px: VitePress shows the whole nav menu there, but our seven items do not fit
+ * next to the search box. Collapse the search box to its icon and tighten the items.
+ */
+@media (min-width: 768px) and (max-width: 959px) {
+ .VPNavBar .DocSearch-Button {
+ width: auto !important;
+ padding: 0 10px !important;
+ }
+
+ .VPNavBar .DocSearch-Button .DocSearch-Search-Icon {
+ margin-right: 0 !important;
+ }
+
+ .VPNavBar .DocSearch-Button-Placeholder,
+ .VPNavBar .DocSearch-Button-Keys {
+ display: none !important;
+ }
+
+ .VPNavBarMenu .VPNavBarMenuLink,
+ .VPNavBarMenu .VPFlyout .button {
+ padding: 0 8px !important;
+ }
+}
diff --git a/utils/version.ts b/.vitepress/version.ts
similarity index 70%
rename from utils/version.ts
rename to .vitepress/version.ts
index 0935746d0..8cf9a9aaf 100644
--- a/utils/version.ts
+++ b/.vitepress/version.ts
@@ -1,5 +1,12 @@
let openListVersionCache: string | null = null
+/** the fields read from the GitHub release / npm package responses */
+interface VersionResponse {
+ tag_name?: string
+ version?: string
+ 'dist-tags'?: { latest?: string }
+}
+
// fetch the OpenList's latest version smartly
export const fetchOpenListVersion = async (): Promise => {
if (openListVersionCache) return openListVersionCache
@@ -8,22 +15,22 @@ export const fetchOpenListVersion = async (): Promise => {
// GitHub Releases
{
url: 'https://api.github.com/repos/OpenListTeam/OpenList/releases/latest',
- handler: (json: any) => json.tag_name,
+ handler: (json: VersionResponse) => json.tag_name,
},
// fallback to frontend version number
// npm registry
{
url: 'https://registry.npmjs.org/@openlist-frontend/openlist-frontend/latest',
- handler: (json: any) => `v${json.version}`,
+ handler: (json: VersionResponse) => `v${json.version}`,
},
{
url: 'https://registry.npmjs.org/@openlist-frontend/openlist-frontend',
- handler: (json: any) => `v${json['dist-tags'].latest}`,
+ handler: (json: VersionResponse) => `v${json['dist-tags']?.latest}`,
},
// unpkg
{
url: 'https://unpkg.com/@openlist-frontend/openlist-frontend/package.json',
- handler: (json: any) => `v${json.version}`,
+ handler: (json: VersionResponse) => `v${json.version}`,
},
]
@@ -39,7 +46,8 @@ export const fetchOpenListVersion = async (): Promise => {
const version = handler(json)
if (typeof version === 'string' && /^v?\d+\.\d+\.\d+$/.test(version)) {
- return (openListVersionCache = version.startsWith('v') ? version : `v${version}`)
+ openListVersionCache = version.startsWith('v') ? version : `v${version}`
+ return openListVersionCache
}
} catch (e) {
console.warn(`Failed to fetch version from ${url}`, e)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 79fb3d004..ef982fe30 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,39 +1,65 @@
# 文档编写说明
-- Frontmatter 说明
+本站使用 [VitePress](https://vitepress.dev/zh/) 构建，其 [Markdown 扩展](https://vitepress.dev/zh/guide/markdown) 均可直接使用。
+
+## 目录结构
+
+- `pages/`: 中文页面 (站点根路径)
+- `pages/en/`: 英文页面 (`/en/` 路径下)，与中文页面使用相同的相对路径，例如 `pages/guide/drivers/s3.md` 对应 `pages/en/guide/drivers/s3.md`
+- `pages/snippets/`、`pages/en/snippets/`: 可复用片段，通过 `` (英文页面为 `@/en/snippets/xxx.md`) 引入
+- `pages/public/`: 图片等静态资源，引用时以 `/` 开头，例如 `/img/xxx.png`
+- `.vitepress/`: 站点配置与主题
+
+修改页面时请同时更新中英文两个文件。
+
+## 页面格式
```md
---
-title:
- en: example
- zh-CN: 示例
categories:
- - example-category
+ - guide
+ - drivers
top: 1000
---
+
+# 示例
+
+正文……
```
其中:
-- `title`: 标题, 需要不同语言版本使用 `_` 分隔语言 ISO 编号
-- `categories`: 类别
+- 标题: 正文第一行的一级标题 (`# 标题`) 即为页面标题, 不要在 frontmatter 中添加 `title`.
+- `categories`: 类别, 多级类别对应侧边栏中的多级分组.
**必须添加类别**, 否则不会显示于侧边栏 (`sidebar`).
- 可用的类别包括:
+ 顶级类别包括 `guide`、`configuration`、`faq`、`seeds`、`api`、`ecosystem`; 常用的子类别包括:
- `installation`: 安装教程相关
- `drivers`: 驱动配置细节相关
- `advanced`: 高级操作相关
- - `api`: API 文档相关
- - `configuration`: 配置文件细节相关
- - `faq`: 常见问题相关
+
+ 新增类别时, 需要在 `.vitepress/config.mts` 的 `categoryText` 中添加中英文名称.
- `top`: 按 `top` 由高到低排列.
- 应当注意: 类别排序也是先按 `top` 由高到低排列的 (feature?).
+ 应当注意: 类别排序也是先按 `top` 由高到低排列的 (以类别中 `top` 最高的页面为准).
预留:
- 10000-9001: 安装教程相关
- 9000-8001: 驱动配置相关
-- valaxy 并不能识别子文件夹, 子文件夹必须添加 index.md 文件 (留空即可), 否则构建失败.
+## 注意事项
+
+- 容器嵌套时, 外层容器需要使用更多的冒号, 否则第一个 `:::` 会直接关闭外层容器:
+
+ ```md
+ :::: details 示例
+ ::: tip
+ 内层提示
+ :::
+ ::::
+ ```
+
+- 在图片链接后添加 `#light` / `#dark`, 图片只会在对应的颜色模式下显示.
+- 构建时会检查站内死链, 链接到目录首页时请以 `/` 结尾, 例如 `/guide/`.
diff --git a/README.cn.md b/README.cn.md
index f986ac027..e08c11e35 100644
--- a/README.cn.md
+++ b/README.cn.md
@@ -22,16 +22,14 @@ OpenList 是一个现代化的基于 Web 的文件管理解决方案，具有以
## 📖 文档
-这是 OpenList 的新文档。使用 Valaxy 构建。对于旧文档（基于 Alist Docs），请访问 [OpenList Docs Legacy](https://github.com/OpenListTeam/docs)。
+这是 OpenList 的新文档。使用 [VitePress](https://vitepress.dev/zh/) 构建。对于旧文档（基于 Alist Docs），请访问 [OpenList Docs Legacy](https://github.com/OpenListTeam/docs)。
## 🛠️ 开发
-本文档站点使用 [Valaxy](https://github.com/YunYouJun/valaxy) 和 [valaxy-theme-press](https://github.com/YunYouJun/valaxy/tree/main/packages/valaxy-theme-press) 构建。
-
### 环境要求
-- Node.js 18+
-- pnpm（推荐的包管理器）
+- Node.js 24+
+- [pnpm](https://pnpm.io/)（包管理器）
### 本地开发
@@ -47,16 +45,18 @@ pnpm install
pnpm dev
```
-文档站点将在 `http://localhost:4859` 可用。
+文档站点将在 `http://localhost:5173` 可用。
+
+中文页面位于 `pages/`，英文页面位于 `pages/en/`，页面组织方式见[贡献指南](./CONTRIBUTING.md)。
### 构建
```bash
-# 生产环境构建
+# 生产环境构建（输出到 dist/）
pnpm build
# 预览生产构建
-pnpm serve
+pnpm preview
```
## 🤝 贡献
diff --git a/README.md b/README.md
index 6d2fd3b81..e43866cd9 100644
--- a/README.md
+++ b/README.md
@@ -22,16 +22,14 @@ OpenList is a modern, web-based file management solution that allows you to:
## 📖 Documentation
-This is the new official documentation site for OpenList. It is built with Valaxy. For old documentation(based on Alist Docs) please visit [OpenList Docs Legacy](https://github.com/OpenListTeam/docs).
+This is the new official documentation site for OpenList. It is built with [VitePress](https://vitepress.dev/). For old documentation(based on Alist Docs) please visit [OpenList Docs Legacy](https://github.com/OpenListTeam/docs).
## 🛠️ Development
-This documentation site is built with [Valaxy](https://github.com/YunYouJun/valaxy) and [valaxy-theme-press](https://github.com/YunYouJun/valaxy/tree/main/packages/valaxy-theme-press).
-
### Prerequisites
-- Node.js 18+
-- pnpm (recommended package manager)
+- Node.js 24+
+- [pnpm](https://pnpm.io/) (package manager)
### Local Development
@@ -47,16 +45,18 @@ pnpm install
pnpm dev
```
-The documentation site will be available at `http://localhost:4859`.
+The documentation site will be available at `http://localhost:5173`.
+
+Chinese pages are in `pages/`, English pages are in `pages/en/`. See the [Contributing Guide](./CONTRIBUTING.md) for how pages are organized.
### Building
```bash
-# Build for production
+# Build for production (output: dist/)
pnpm build
# Preview production build
-pnpm serve
+pnpm preview
```
## 🤝 Contributing
diff --git a/assets/sites.ts b/assets/sites.ts
deleted file mode 100644
index 560b7f706..000000000
--- a/assets/sites.ts
+++ /dev/null
@@ -1 +0,0 @@
-export const sites = []
diff --git a/components/AddonGallery.vue b/components/AddonGallery.vue
deleted file mode 100644
index d3b477325..000000000
--- a/components/AddonGallery.vue
+++ /dev/null
@@ -1,65 +0,0 @@
-
-
-
-
-
-
-
-
diff --git a/components/AutoLanguageDetector.vue b/components/AutoLanguageDetector.vue
deleted file mode 100644
index 88de7ac62..000000000
--- a/components/AutoLanguageDetector.vue
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
diff --git a/components/BrandIcon.vue b/components/BrandIcon.vue
deleted file mode 100644
index 2c243d563..000000000
--- a/components/BrandIcon.vue
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
-
-
- {{ t(text) }}
-
-
-
diff --git a/components/PressGetStarted.vue b/components/PressGetStarted.vue
deleted file mode 100644
index e5dccbf5b..000000000
--- a/components/PressGetStarted.vue
+++ /dev/null
@@ -1,85 +0,0 @@
-
-
-
-
-
-
-
-
diff --git a/components/PressHome.vue b/components/PressHome.vue
deleted file mode 100644
index 7e7bdf1ef..000000000
--- a/components/PressHome.vue
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
-
- diff --git a/components/PressNavBar.vue b/components/PressNavBar.vue deleted file mode 100644 index 426657c1c..000000000 --- a/components/PressNavBar.vue +++ /dev/null @@ -1,109 +0,0 @@ - - - - - -
- {{ t(text) }}
-
-
-
-
diff --git a/components/ThemeImage.vue b/components/ThemeImage.vue
deleted file mode 100644
index c4b3dec0c..000000000
--- a/components/ThemeImage.vue
+++ /dev/null
@@ -1,68 +0,0 @@
-
-
-
- ![]()
-
-
-
diff --git a/components/ThemeImagePair.vue b/components/ThemeImagePair.vue
deleted file mode 100644
index c6f0b5e33..000000000
--- a/components/ThemeImagePair.vue
+++ /dev/null
@@ -1,123 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/layouts/home.vue b/layouts/home.vue
deleted file mode 100644
index 2e67333ae..000000000
--- a/layouts/home.vue
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
-
-
-
-
-
-
-
diff --git a/layouts/statement.vue b/layouts/statement.vue
deleted file mode 100644
index be3f8cc6b..000000000
--- a/layouts/statement.vue
+++ /dev/null
@@ -1,55 +0,0 @@
-
-
-
- /data/config.json`
-- Linux: one-click script directory, `/opt/openlist/data/config.json` or `/data/config.json`
-- Docker: `/data/config.json`
-- OpenWrt: modify config on server if using `luci-app-openlist` , otherwise `/data/config.json`
-- Other: `/data/config.json`
-
-:::
-
-::: zh-CN
::: tip
`config.json` 内配置文件修改后都需要重启 OpenList 才会生效
@@ -173,42 +156,14 @@ After modifying the configuration file, restart OpenList for changes to take eff
}
```
-## Field Explanation { lang="en" }
-
-## 字段说明 { lang="zh-CN" }
+## 字段说明
### force
-::: en
-By default OpenList reads the configuration from environment variables, set this field to `true` to force OpenList to read config from the configuration file.
-
-:::
-
-::: zh-CN
程序会优先从环境变量中读取配置，设置 `force` 为 `true` 会使程序忽略环境变量强制读取配置文件。
-:::
-
### site_url
-::: en
-The address of your OpenList server, such as `https://pan.example.com`. This address is essential for some features, and thus thry may not work properly if unset:
-
-- thumbnailing `LocalStorage`
-- previewing site after setting web proxy
-- displaying download address after setting web proxy
-- reverse-proxying to site sub directories
-- ...
-
-Do not include the slash \(`/`\) at the end of the address. For example:
-
-```diff
-+ "site_url": "https://openlist.example.com",
-- "site_url": "https://openlist.example.com/",
-```
-
-:::
-::: zh-CN
你的网站 URL，比如 `https://pan.example.com`，这个地址会在程序中的某些地方使用，如果不设置这个字段，一些功能可能无法正常工作，比如
- 本地存储的缩略图
@@ -224,26 +179,14 @@ URL 链接结尾请勿携带 `/`，参照如下示例，否则也将无法使用
- "site_url": "https://openlist.example.com/",
```
-:::
-
### cdn
-::: en
-The address of the CDN. Included `$version` values will be dynamically replaced by the version of OpenList. Existing dist resources are hosted on both npm and GitHub, which can be found at:
-:::
-::: zh-CN
CDN 地址，如果要使用 CDN，可以设置该字段，`$version` 会被动态替换为 `Openlist-Frontend` 的实际版本。
-:::
-
-
-::: en
-Thus it is possible to use any npm or ~~GitHub~~ CDN path for this field. Do not include the slash `/` at the end of the address. For example:
-:::
-::: zh-CN
所以你可以使用任何 npm 或 ~~GitHub~~ CDN 作为路径，结尾不要携带 `/`，例如：
-:::
- `https://registry.npmmirror.com/@openlist-frontend/openlist-frontend/$version/files/dist`
- `https://unpkg.com/@openlist-frontend/openlist-frontend@$version/dist`
@@ -255,115 +198,14 @@ Thus it is possible to use any npm or ~~GitHub~~ CDN path for this field. Do not
- ~~`https://cdn.jsdelivr.net/gh/OpenListTeam/OpenList-Frontend@$version/dist`~~
- ~~`https://jsd.onmicrosoft.cn/gh/OpenListTeam/OpenList-Frontend@$version/dist`~~
-::: en
-::: tip
-If you are using the lite version, please add `/lite` to the end of the URL. For example: `https://cdn.jsdelivr.net/gh/OpenListTeam/OpenList-Frontend@$version/dist/lite`
-:::
-::: zh-CN
::: tip
如果您使用 Lite 版本，请在地址后面添加 `/lite` 目录，如：`https://cdn.jsdelivr.net/npm/@openlist-frontend/openlist-frontend@$version/dist/lite`。
:::
-::: en
-Keep empty to use dist resources embedded in the program by default.
-:::
-::: zh-CN
默认情况下，您可以将其设置为空以使用程序内置 dist。
-:::
-
-#### CDN for Beta version { lang="en" }
-
-#### Beta 版本使用 CDN { lang="zh-CN" }
-
-::: en
-Since the frontend uses Vite for building, the generated JS files use a hash naming strategy. When code changes occur, the built file names change, making `index.html` files from different versions incompatible with each other.
-
-The OpenList backend needs to load `index.html` into memory for processing, including inserting code and modifying variables. If deployed only through Pages with modified API addresses, it would result in missing functionality and routing failures.
-
-To solve this problem, we've added the ability to fetch `index.html` from CDN for Beta versions and self-built versions, ensuring that JS files and `index.html` are properly matched.
-
-- **Release version**: Static resources are loaded through NPM CDN with fixed versions, so there's no need to request from CDN - the built-in `index.html` can be used directly
- - Note: Some NPM CDNs (like npmmirror) may prohibit access to HTML files, but Release versions don't depend on CDN's `index.html`, so they're unaffected
-- **Beta version**: Updates frequently, OpenListTeam doesn't upload to NPM, and no CDN is provided for Beta versions
-
-Since Beta versions don't have NPM CDN provided by OpenListTeam, you need to deploy it yourself:
-
-1. **Deploy frontend build artifacts**
- - Deploy build artifacts to a CDN platform (you can use Cloudflare Pages, EdgeOne Pages, etc.)
- - Configure necessary CORS headers, for example of `edgeone.json`:
-
- ```json
- {
- "headers": [
- {
- "source": "/*",
- "headers": [
- {
- "key": "Access-Control-Allow-Origin",
- "value": "*"
- },
- {
- "key": "Access-Control-Allow-Methods",
- "value": "GET, OPTIONS"
- },
- {
- "key": "Access-Control-Allow-Headers",
- "value": "Content-Type"
- }
- ]
- },
- {
- "source": "/**/*.mjs",
- "headers": [
- {
- "key": "Content-Type",
- "value": "application/javascript"
- }
- ]
- }
- ]
- }
- ```
-
- - Recommend using "copy + overwrite" deployment method, retaining old version resource files to ensure compatibility for versions not rebooted
-
-2. **Configure backend**
- - Add CDN configuration in `config.json`
- - The program will automatically fetch the latest `index.html` from CDN when starting
-
-3. **Version updates**
- - When you need to update the frontend, simply restart the backend program
-
-Here's a diagram for better understanding:
-```mermaid
-flowchart TD
- A[Program Initialization] --> B{CDN Configured?}
-
- B -->|Yes| D{Version Type?}
- B -->|No| E{Local dist_dir Configured?}
-
- E -->|No| F[Use Built-in index.html]
- E -->|Yes| G[Use index.html from Local dist_dir]
-
- D -->|Beta Version| H[Fetch index.html from CDN]
- D -->|Release Version| F
-
- H --> I{CDN Fetch Successful?}
- I -->|Success| J[Use CDN-fetched index.html]
- I -->|Failed| K[Resty Retry 3 Times]
- K -->|Success| J
- K -->|Still Failed| L[Program Exit, Wait for Restart]
+#### Beta 版本使用 CDN
- F --> M[Replace CDN, Site Info and Other Variables]
- G --> M
- J --> M
- M --> N[Return Page]
-```
-
-:::
-
-::: zh-CN
由于前端采用 Vite 构建，生成的 JS 文件使用哈希命名策略。当代码发生变更时，构建后的文件名会改变，这导致不同版本间的 `index.html` 文件无法互相兼容。
OpenList 后端需要将 `index.html` 加载到内存中进行处理，包括插入代码、修改变量等操作。如果仅通过 Pages 部署并修改 API 地址，会导致功能缺失和路由失效。
@@ -450,53 +292,16 @@ flowchart TD
M --> N[返回页面]
```
-:::
-
### jwt_secret
-::: en
-The secret used to sign the JWT token, randomly generated on first run.
-
-:::
-::: zh-CN
用于签署 JWT 令牌的密钥，第一次启动时随机生成。
-:::
-
### token_expires_in
-::: en
-User login expiration time, in hours.
-:::
-::: zh-CN
用户登录过期时间，单位：小时
-:::
### database
-::: en
-The database configuration, which is by default `sqlite3`. Available options are `sqlite3`, `mysql` and `postgres`.
-
-- The database options do not need to be modified if using `sqlite3`.
-
-```json
- "database": {
- "type": "sqlite3", //database type
- "host": "", //database host
- "port": 0, //database port
- "user": "", //database account
- "password": "", //database password
- "name": "", //database name
- "db_file": "data\\data.db", //Database location, used by sqlite3
- "table_prefix": "x_", //database table name prefix
- "ssl_mode": "", //To control the encryption options during the SSL handshake, the parameters can be searched by themselves, or check the answer from ChatGPT below
- "dsn": "" // https://github.com/alist-org/alist/pull/6031
- },
-```
-
-:::
-
-::: zh-CN
数据库配置，默认是 `sqlite3`，也可以使用 `mysql` 或者 `postgres`。
- 如果不使用 `MySQL` 或者 `postgres`，配置文件数据库选项不用修改
@@ -516,30 +321,6 @@ The database configuration, which is by default `sqlite3`. Available options are
},
```
-:::
-
-::: en
-::: details Expand to view details of `ssl_mode`
-If you don't know how to fill it in, then your server probably doesn't have SSL enabled, so just leave it blank.
-In MySQL, the `ssl_mode` parameter is used to specify the authentication mode of the SSL connection. Here are a few common options:
-
-- `DISABLED`: Disable SSL connections.
-- `PREFERRED`: Use an SSL connection if server has SSL enabled, and otherwise fallback to a normal connection.
-- `REQUIRED`: Force to use SSL connection and fail if the server does not support SSL connection.
-- `VERIFY_CA`: Force to use SSL connection and verify the authenticity of the server certificate.
-- `VERIFY_IDENTITY`: Force to use an SSL connection and verify the authenticity of the server certificate and that the name matches the connecting hostname.
- Additional, MySQL 5.x and 8.x have differences. If you are using databases provided by service providers, BTFM. If you deployed the database yourself, STFW.
- In PostgreSQL, the `ssl_mode` parameter is used to specify how the client uses SSL connections. Here are a few common options:
-- `disable`: Disable SSL connections.
-- `allow`: Allow SSL connections.
-- `prefer`: Use an SSL connection if server has SSL enabled, and otherwise fallback to a normal connection.
-- `require`: Force to use SSL connection and fail if the server does not support SSL connection.
-- `verify-ca`: Force to use SSL connection and verify the authenticity of the server certificate.
-- `verify-full`: Force to use an SSL connection and verify the authenticity of the server certificate and that the name matches the connecting hostname.
-
-:::
-
-::: zh-CN
::: details 展开查看 `ssl_mode` 参数选项
如果不知道如何填，那你的服务器应该也并没有开启SSL，留空即可。
在 MySQL 中，`ssl_mode` 参数是用于指定 SSL 连接的验证模式。以下是几种常见的选项：
@@ -564,16 +345,6 @@ In MySQL, the `ssl_mode` parameter is used to specify the authentication mode of
:::
-::: en
-::: details Notes on modifying the database when there is already data
-
-1. If you change the `sqlite` database to `mysql` database, it is first recommended to use the backup and recovery method.
-2. If you directly import `sqlite` data into `mysql`, you can view this video tutorial: [View tutorial](https://www.bilibili.com/video/BV1iV4y1T7kh)
- - Because when directly importing the cloud disk database table, the time of `sqlite` and the time of `mysql` are filled in differently, an error will be reported [please check the precautions and how to solve it](https://www.bilibili.com/video/BV1iV4y1T7kh?t=343.7)
-
-:::
-
-::: zh-CN
::: details 已有数据情况下修改数据库注意事项
1. 如果将`sqlite`数据库改为`mysql`数据库优先推荐使用备份再恢复的方法
@@ -584,23 +355,6 @@ In MySQL, the `ssl_mode` parameter is used to specify the authentication mode of
### meilisearch
-::: en
-
-```json
- "meilisearch": {
- "host": "http://localhost:7700", // meilisearch host, the default is the local machine
- "api_key": "", // if meilisearch's authentication is enabled, this is required
- "index": "" // meilisearch index uid
- },
-```
-
-- Documentation link：
-- Reference Links：
-
-:::
-
-::: zh-CN
-
```json
"meilisearch": {
"host": "http://localhost:7700", // meilisearch主机，默认使用的是本机
@@ -612,32 +366,8 @@ In MySQL, the `ssl_mode` parameter is used to specify the authentication mode of
- 文档链接：
- 参考链接：
-:::
-
### scheme
-::: en
-The configuration of scheme. Set this field if using HTTPS.
-
-- Remember to copy the certificate file to the data directory. Config example:
-
-```json
- "scheme": {
- "address": "0.0.0.0", // The http/https address to listen on, default `0.0.0.0`
- "http_port": 5244, // The http port to listen on, default `5244`, if you want to disable http, set it to `-1`
- "https_port": -1, // The https port to listen on, default `-1`, if you want to enable https, set it to non `-1`
- "force_https": false, // Whether the HTTPS protocol is forcibly, if it is set to True, the user can only access the website through HTTPS
- "cert_file": "data\\cert.crt", // Path of cert file
- "key_file": "data\\key.key", // Path of key file
- "unix_file": "", // Unix socket file path to listen on, default empty, if you want to use unix socket, set it to non empty
- "unix_file_perm": "", // Unix socket file permission, set to the appropriate permissions
- "enable_h2c": false // Support HTTP/2 Cleartext (H2C) protocol for openlist's http service. The cleartext HTTP/2 protocol supports nginx's grpc_pass after it is enabled - https://github.com/AlistGo/alist/pull/8294
- },
-```
-
-:::
-
-::: zh-CN
协议配置，如果要使用 HTTPS，可以设置该字段。
- 填写示例：记得把证书文件丢到 data 目录里面才会识别到喔~
@@ -656,49 +386,20 @@ The configuration of scheme. Set this field if using HTTPS.
},
```
-:::
-
### temp_dir
-::: en
-The directory to keep temporary files. By default OpenList uses `data/temp`.
-:::
-::: zh-CN
用于存放临时文件的目录。默认情况下，OpenList 使用 `data/temp`。
-:::
-
-::: en
-::: danger
-temp_dir is a temporary folder exclusive to alist. In order to prevent OpenList from generating garbage files when being interrupted, the directory will be cleared every time OpenList starts, so do not store anything in this directory or map this directory & subdirectories to directories in use when using Docker.
-:::
-::: zh-CN
::: danger
temp_dir 为 OpenList 独占的临时文件夹，为避免程序中断产生垃圾文件会在每次启动时清空，故请不要手动在此文件夹内放置任何内容，也不要在使用 docker 时将此文件夹及其子文件夹映射至正在使用的文件夹。
:::
### bleve_dir
-::: en
-Where data is stored when using **`bleve`** index.
-:::
-::: zh-CN
你使用 **`bleve`** 索引时，数据存放的位置
-:::
### dist_dir
-::: en
-If this option is set, the front-end files in the defined **local** external folder will be used as a priority.
-
-- Supports using front-end files from an external folder
-- Supports using other front-end files, while the back-end continues to use the original version of the application
-
-Upload the front-end files (dist) to the application's `data` folder, then fill in:
-
-:::
-
-::: zh-CN
如果设置此项，优先使用定义的**本地**外部文件夹下的前端文件。
- 支持使用外部文件夹中的前端文件
@@ -706,62 +407,12 @@ Upload the front-end files (dist) to the application's `data` folder, then fill
将前端文件（dist）上传到应用的 `data` 文件夹下，然后填写：
-:::
-
```json
"dist_dir": "data/dist",
```
### log
-::: en
-The log configuration. Set this field to save detailed logs of disable.
-
-```json
- "log": {
- "enable": true, // Whether OpenList should store logs
- "name": "data\\log\\log.log", // The path and name of the log file
- "max_size": 10, // the maximum size of a single log file, in MB. After reaching the specified size, the file will be automatically split.
- "max_backups": 5, // the number of log backups to keep. Old backups will be deleted automatically when the limit is exceeded.
- "max_age": 28, // The maximum number of days preserved in the log file, the log file that exceeds the number of days will be deleted
- "compress": false, // Whether to enable log file compression functions. After compression, the file size can be reduced, but you need to decompress when viewing, and the default is to close the state false
- "filter": { // skip some logs output, not enable by default
- "enable": false,
- "filters": [ // preset example
- {
- "cidr": "",
- "path": "/ping", // Health check
- "method": ""
- },
- {
- "cidr": "",
- "path": "",
- "method": "HEAD" // HEAD request
- },
- { // WebDav metadata
- "cidr": "",
- "path": "/dav/",
- "method": "PROPFIND"
- }
- ]
- },
-```
-
-Each filter acts as the following object:
-
-```json
-{
- "cidr": "",
- "path": "", // http path, If it starts with "/", it is an absolute path; if it does not start with "/", it is a relative path
- "method": "" // HTTP/webdav method, in uppercase
-}
-```
-
-Take note of the startup log to confirm the load, as detailed in the source code `server/middlewares/filtered_logger.go`.
-
-:::
-
-::: zh-CN
日志配置，如果要查看详细日志（或禁用它），可以设置该字段。
```json
@@ -807,24 +458,8 @@ Take note of the startup log to confirm the load, as detailed in the source code
注意查看启动日志以确认加载情况，具体实现详见源代码 `server/middlewares/filtered_logger.go`.
-:::
-
### delayed_start
-::: en
-
-Whether to delay OpenList startup.
-
-
-
-**Time unit: second**
-
-Generally this option is used when OpenList is configured to auto-start. The reason is that sometimes network takes some time to connect, so drivers requiring cannot start correctly after OpenList starts.
-
-:::
-
-::: zh-CN
-
是否延时启动，一般此功能常用于 OpenList 开机自启动选项。
@@ -833,126 +468,27 @@ Generally this option is used when OpenList is configured to auto-start. The rea
因为有时候网络连接的慢，导致 OpenList 启动过快后需要网络连接的驱动无法连接导致无法正常打开。
-:::
-
### max_connections
-::: en
-The maximum amount of connections at the same time. The default is 0, which is unlimited.
-
-- 10 or 20 is recommended for general devices such as N1(S905D).
-- Usage Scenarios: the device will crash if the device is bad at concurrency when picture mode is enabled.
-
-:::
-
-::: zh-CN
同时连接的最大数量。默认值为 0，表示无限制。
- 对于性能一般的设备，如 N1（S905D），推荐设置为 10 或 20。
- 使用场景：当启用图片模式时，如果设备的并发能力较差，设备可能会崩溃。
-:::
-
### max_concurrency
-::: en
-Limit the maximum concurrency of local agents. The default value is 64, and 0 means no limit.
-:::
-
-::: zh-CN
限制本地代理的最大并发，默认为64，0为不限制。
-:::
### tls_insecure_skip_verify
-::: en
-Whether not to verify the SSL certificate.
-
-If there is a problem with the certificate of the website used when this option is not enabled (such as not including the intermediate certificate, having the certificate expired, or forging the certificate, etc.), the service will not be available.
-
-When this option is enabled, please ensure the program is running in a safe network environment.
-:::
-
-::: zh-CN
是否不验证 SSL 证书。
如果在未启用此选项时使用的网站证书存在问题（如未包含中间证书、证书过期或证书伪造等），服务将无法使用。
启用此选项时，请确保在安全的网络环境中运行程序。
-:::
### tasks
-::: en
-Configuration for background task threads.
-
-```json
- "tasks": {
- "download": {
- "workers": 5,
- "max_retry": 1,
- "task_persistant": false
- },
- "transfer": {
- "workers": 5,
- "max_retry": 2,
- "task_persistant": false
- },
- "upload": {
- "workers": 5,
- "max_retry": 0,
- "task_persistant": false
- },
- "copy": {
- "workers": 5,
- "max_retry": 2,
- "task_persistant": false
- },
- "decompress": {
- "workers": 5,
- "max_retry": 2,
- "task_persistant": false
- },
- "decompress_upload": {
- "workers": 5,
- "max_retry": 2,
- "task_persistant": false
- },
- "allow_retry_canceled": false
- },
-```
-
-- **workers**: Number of task threads.
-- **max_retry**: Number of retries.
- - 0: Retries disabled.
-- **download**: Download task when downloading offline
-- **transfer**: upload transfer task after offline download is completed
-- **upload**: upload task
-- **copy**: copy the task
-- **decompress**：decompress the task
-- **decompress_upload**：decompress upload the task
-- **task_persistant**：The task is persistent and will not be cancelled after restarting `OpenList`
- - **download**：false
- - **transfer**：false
- - **upload**：false
- - **copy**：false
- - **decompress**：false
- - **decompress_upload**：false
-- **allow_retry_canceled**：Allow users to retry previously canceled tasks
-
----
-
-A new **transmission** configuration path is added to the background configuration: `/@manage/settings/traffic`
-
-- Supports limiting the number of threads and transmission uplink and downlink rates of **6 tasks**
-- ****
- Operation principle: If `settings/traffic` does not have a thread number field (first run or just upgraded from an old version), `settings/traffic` will be initialized with the value of the config configuration file. If `settings/traffic` has a value, the thread configuration information of config will be ignored
-- ****
-- Summary: For newly installed or upgraded versions, the values will be read from the configuration file to initialize the `traffic` configuration information. Subsequent modifications to the thread only need to be modified in the background.
-
-:::
-
-::: zh-CN
后台任务线程数量配置。
```json
@@ -1019,35 +555,8 @@ A new **transmission** configuration path is added to the background configurati
- ****
- 总结：新安装或者新升级的版本，会先从配置文件读取数值来初始化 `传输` 配置信息，后续修改线程只需要在后台修改就可以
-:::
-
### cors
-::: en
-Configuration for Cross-Origin Resource Sharing (CORS).
-
-```json
- "cors": {
- "allow_origins": [
- "*"
- ],
- "allow_methods": [
- "*"
- ],
- "allow_headers": [
- "*"
- ]
- }
-```
-
-- **allow_origins**: Allowed sources.
-- **allow_methods**: Allowed request methods.
-- **allow_headers**: Allowed request headers.
-
-Use it to understand it by yourself, and then configure it. If you do n’t know, please do n’t modify it at will. Use the default configuration.
-:::
-
-::: zh-CN
**跨源资源共享**配置
```json
@@ -1069,30 +578,9 @@ Use it to understand it by yourself, and then configure it. If you do n’t know
- **allow_headers**：允许的请求头
具体使用方式自行了解进行配置，如果不了解请勿随意修改，使用默认配置就可以。
-:::
### S3
-::: en
-
-```json
- "s3": {
- "enable": false,
- "port": 5246,
- "ssl": false
- }
-```
-
-- `enable`：Whether the S3 function is enabled, the default is not enabled
-- `port`：port
-- `SSL`：Enable the HTTPS certificate, not enabled by default
-
-Function introduction: [Click to view](../guide/advanced/s3.md)
-
-:::
-
-::: zh-CN
-
```json
"s3": {
"enable": false,
@@ -1107,43 +595,8 @@ Function introduction: [Click to view](../guide/advanced/s3.md)
功能介绍：[点击查看](../guide/advanced/s3.md)
-:::
-
### ftp
-::: en
-
-```json
- "ftp": {
- "enable": false,
- "listen": ":5221",
- "find_pasv_port_attempts": 50,
- "active_transfer_port_non_20": false,
- "idle_timeout": 900,
- "connection_timeout": 30,
- "disable_active_mode": false,
- "default_transfer_binary": false,
- "enable_active_conn_ip_check": true,
- "enable_pasv_conn_ip_check": true
- },
-```
-
-- `enable`: Whether the **ftp** function is enabled, not enabled by default
-- `listen`: port number
-- `find_pasv_port_attempts`: maximum number of attempts to re-find a port due to port conflicts during passive transmission
-- `active_transfer_port_non_20`: enable ports other than 20 as active transmission ports
-- `idle_timeout`: maximum idle time (seconds) when there is no client request
-- `connection_timeout`: connection timeout
-- `disable_active_mode`: disable active transmission mode
-- `default_transfer_binary`: transfer in binary mode by default
-- `enable_active_conn_ip_check`: perform IP check on the client side of the TCP connection of the data stream in active transmission mode
-- `enable_pasv_conn_ip_check`: perform IP check on the client side of the TCP connection of the data stream in passive transmission mode
-
-Other instructions: [Click to view](../guide/advanced/ftp.md)
-:::
-
-::: zh-CN
-
```json
"ftp": {
"enable": false,
@@ -1171,27 +624,9 @@ Other instructions: [Click to view](../guide/advanced/ftp.md)
- `enable_pasv_conn_ip_check`：被动传输模式下对数据流TCP连接的客户端进行IP检查
其它说明：[点击查看](../guide/advanced/ftp.md)
-:::
### sftp
-::: en
-
-```json
- "sftp": {
- "enable": false,
- "listen": ":5222"
- }
-```
-
-- `enable`: Whether the **sftp** function is enabled, not enabled by default
-- `listen`: port number
-
-Other instructions: [Click to view](../guide/advanced/ftp.md)
-:::
-
-::: zh-CN
-
```json
"sftp": {
"enable": false,
@@ -1203,25 +638,9 @@ Other instructions: [Click to view](../guide/advanced/ftp.md)
- `listen`：端口号
其它说明：[点击查看](../guide/advanced/ftp.md)
-:::
### mcp
-::: en
-
-```json
- "mcp": {
- "enable": false
- }
-```
-
-- `enable`: Whether the **MCP** endpoint is enabled, not enabled by default
-
-Other instructions: [Click to view](../guide/advanced/mcp.md)
-:::
-
-::: zh-CN
-
```json
"mcp": {
"enable": false
@@ -1231,24 +650,9 @@ Other instructions: [Click to view](../guide/advanced/mcp.md)
- `enable`：**MCP** 功能是否启用，默认未启用
其它说明：[点击查看](../guide/advanced/mcp.md)
-:::
### proxy
-::: en
-
-```json
- "proxy_address": "",
-```
-
-Supports HTTP proxy, HTTPS proxy, SOCKS4 proxy, SOCKS5 proxy, SOCKS5HOSTNAME proxy.
-
-Both IPv4 and IPv6 are supported.
-
-:::
-
-::: zh-CN
-
```json
"proxy_address": "",
```
@@ -1256,5 +660,3 @@ Both IPv4 and IPv6 are supported.
支持HTTP代理、HTTPS代理、SOCKS4代理、SOCKS5代理、SOCKS5HOSTNAME代理。
同时兼容IPv4和IPv6。
-
-:::
diff --git a/pages/configuration/global.md b/pages/configuration/global.md
index 4f20eba27..c48d3509b 100644
--- a/pages/configuration/global.md
+++ b/pages/configuration/global.md
@@ -1,31 +1,13 @@
---
-title:
- en: Global Configuration
- zh-CN: 全局设置
-# This is the icon of the page
-icon: iconfont icon-chrome
-# This control sidebar order
-# A page can have multiple categories
categories:
- configuration
-# A page can have multiple tags
top: 20
---
-## Hide files { lang="en" }
+# 全局设置
-## 隐藏文件 { lang="zh-CN" }
+## 隐藏文件
-::: en
-Match files hidden by a regular expression (`JavaScript`). Please do not fill it in casually, as incorrect expressions may cause the front-end page to crash.
-
-One regular expression per line.
-
-By default, there is an expression `/\/README.md/i`, which hides `README.md` from all directories.
-
-Note that this is not a true hide. The file will still appear in the API response list, but will not be displayed in the front-end interface. If you wish to truly hide the file, please refer to [metadata](../guide/advanced/meta.md).
-:::
-::: zh-CN
匹配由正则表达式（`JavaScript`）隐藏的文件。请勿随意填写，错误的表达式可能会导致前端页面崩溃。
每行填写一个正则表达式。
@@ -33,95 +15,34 @@ Note that this is not a true hide. The file will still appear in the API respons
默认情况下，已有一个表达式 `/\/README.md/i`，表示将 `README.md` 从所有目录中隐藏。
需要注意的是，这并不是真正的隐藏。该文件仍会出现在 API 返回的文件列表中，只是不显示在前端界面中。如果您想彻底隐藏文件，请参考[元信息](../guide/advanced/meta.md)。
-:::
-
-## Package download { lang="en" }
-
-## 打包下载 { lang="zh-CN" }
-::: en
-Whether to enable package download (default is true). **Not recommended, especially for large or numerous files.**
+## 打包下载
-- It is recommended to push files to Aria2 for downloading, as it supports maintaining the directory structure when saving the download folder.
-- For more details, see [What is the difference between the two Aria2](./other.md#other).
-
-:::
-::: zh-CN
是否开启前端文件打包下载（默认为开启）。**不推荐使用，尤其是文件数量多或体积大的情况。**
- 推荐将文件推送至 Aria2 进行下载，它支持在保存下载文件夹时保留目录结构。
- 了解详情，请查看 [两个 Aria2 的区别](./other.md#其他)。
-:::
-
-## Customize head { lang="en" }
-
-## 自定义头部 { lang="zh-CN" }
-
-::: en
-The content set here will be automatically inserted into the header of the webpage (not include the manage pages). You can reference scripts, CSS, etc., here to style the frontend of OpenList.
-
-- How to configure PWA（Desktop、Android、IOS）：**[alist/issues/6724](https://github.com/alist-org/alist/issues/6724#issuecomment-2220251541)**
+## 自定义头部
-:::
-::: zh-CN
在此处设置的内容会自动插入到网页头部位置（管理页面除外）。您可以在此处引用脚本、CSS等，对 OpenList 的前端进行美化。
- 如何配置PWA（Desktop、Android、IOS）：**[alist/issues/6724](https://github.com/alist-org/alist/issues/6724#issuecomment-2220251541)**
-:::
-
-## Customize body { lang="en" }
-
-## 自定义内容 { lang="zh-CN" }
+## 自定义内容
-::: en
-The content set here will be automatically inserted at the end of the webpage body. You can add icp information, visit statistics, etc., here.
-:::
-::: zh-CN
在此处设置的内容会自动插入到网页正文的末尾。您可以在此处添加备案信息、访问统计等。
-:::
-
-## Link expiration { lang="en" }
-## 直链有效期 { lang="zh-CN" }
+## 直链有效期
-::: en
-The expiration time of the direct link, in hours. If it equals 0, it will not expire. Default is 0.
-::: en
-::: warning
-Only the straight chain of the path with the password added will have an expiration time, otherwise it will not expire.Because the expiration time is added to the sign query parameter, and the path without adding the password will not check the sign.
-:::
-
-::: zh-CN
直接链接的过期时间，以小时为单位。如果为 0，则不会过期。默认值为 0。
-::: zh-CN
+
::: warning
只有加了密码的路径的直链才会有过期时间，否则不会过期。因为过期时间是加到sign查询参数中的，没有加密码的路径是不会检查sign的。
:::
-## Sign all { lang="en" }
-
-## 签名所有 { lang="zh-CN" }
-
-::: en
-Add signatures to the direct link of all files (whether with password or not), such as `https://xxxx.com/d/xx?sign=vUQ5KFXnwMseKnIUXGRcfoG3cEHzKFBiPGp1NriMDXA=:0`.
+## 签名所有
-If you need to close it, you can close it yourself, but you need to pay attention to security issues. After closing the signature, if the site can be accessed by the public network, the password may be bypassed to access private files.
-There are two other methods that also carry the `sign?xxx` parameter:
-
-1. Add Storage Select `Enable Signing`
-2. Meta Information Add Password
-
-The scope of the three methods: `Sign All` > `Meta Information Add Password` > Add Storage Select `Enable Signing`
-
-1. Sign All: If this option is turned on, the sign parameter will be carried regardless of whether meta-information is encrypted or not, and whether `Enable Signing` is checked when adding storage.
-2. Meta Information Add Password：Only files under this meta information path will carry the sign parameter.
- - If **Apply to sub folder** is turned on, all files in this path will carry the sign parameter
-3. Add Storage Select `Enable Signing`：Only this storage driver carries the sign parameter.
-
-:::
-::: zh-CN
向所有文件的直接链接添加签名（无论是否有密码），即 `https://openlist.example.com/d/xx?sign=vUQ5KFXnwMseKnIUXGRcfoG3cEHzKFBiPGp1NriMDXA=:0`。
若需要关闭，自行关闭即可，但需要注意安全问题。关闭签名后若站点能被公网访问，可能会被绕过密码访问私人文件。
@@ -138,112 +59,36 @@ The scope of the three methods: `Sign All` > `Meta Information Add Password` > A
- 如果**应用到子文件夹**开启，则该路径下的所有文件将携带该签名参数
3. 添加存储勾选`启用签名`：单独只这个存储驱动携带 sign 参数
-:::
-
-## Privacy regs { lang="en" }
+## 隐私内容正则表达式
-## 隐私内容正则表达式 { lang="zh-CN" }
-
-::: en
-What you don't want to show in the error message, One regular expression (in `Golang`) per line. The matched content will be replaced with `*` of the corresponding length.
-:::
-::: zh-CN
不想在错误消息中显示的内容，每行一个正则表达式（在 `Golang` 中）。匹配的内容将被替换为对应长度的`*`。
-:::
-
-## Ocr api { lang="en" }
-
-## Ocr 接口 { lang="zh-CN" }
-
-::: en
-Used to identify verification codes. You can deploy yourself: https://hub.docker.com/r/cloudlinksu/openlist-ocr-server.
-The default ocr api is deployed on the [Hugging Face](https://huggingface.co/spaces/Susus21/openlist-ocr/tree/main). You can clone the Hugging Face repository to build your own: [clone the Hugging Face repository](https://huggingface.co/spaces/Susus21/openlist-ocr/tree/main?duplicate=true).
+## Ocr 接口
-The hf domain name after successful self-construction is `https://{username}-{repositroy-name}.hf.space/ocr/file/json`.
-:::
-::: zh-CN
用于识别验证码。你可以自己部署：https://hub.docker.com/r/cloudlinksu/openlist-ocr-server。
默认的 ocr api 部署在 [Hugging Face](https://huggingface.co/spaces/Susus21/openlist-ocr/tree/main) 上。你可克隆 Hugging Face 仓库自建：[克隆Hugging Face仓库](https://huggingface.co/spaces/Susus21/openlist-ocr/tree/main?duplicate=true)。
自建成功后的 hf 域名为：`https://{username}-{repositroy-name}.hf.space/ocr/file/json`
-:::
-## Filename char mapping { lang="en" }
+## 文件名字符映射
-## 文件名字符映射 { lang="zh-CN" }
-
-::: en
-Map certain special characters, such as `/`, which is used as a path separator in OpenList. When file names contain `/`, it may cause issues like broken file paths or inability to view the files. By using this method, we can map and convert these characters to resolve such problems.
-:::
-::: zh-CN
映射一些特殊符号，例如 /，在 OpenList 中作为路径符号。由于某些文件名包含 /，可能会导致文件路径断开或无法查看等问题。通过这种方式，我们可以进行符号映射和转换，以解决此类问题。
-:::
```json
{ "/": "|", "xx1": "xx1", "xx2": "xx2" }
```
-## Forward direct link params { lang="en" }
-
-## 转发直链参数 { lang="zh-CN" }
+## 转发直链参数
-::: en
-After enabling, the parameters after `?` will be automatically appended to the end of the direct link URL.
-:::
-::: zh-CN
开启后，`?`后面的参数将自动添加到直链 URL 的末尾。
-:::
-
-## Ignore direct link params { lang="en" }
-## 忽略直链参数 { lang="zh-CN" }
+## 忽略直链参数
-::: en
-Ignore the parameters for forwarding direct links, such as `sign` and `openlist_ts`.
-:::
-::: zh-CN
忽略转发直链的参数，如 `sign,openlist_ts`。
-:::
-
-## Webauthn login enabled { lang="en" }
-
-## 启用 Webauthn 登录 { lang="zh-CN" }
-::: en
-**Web Authentication (WebAuthn)** is a new authentication method. You can enable it by following these steps:
+## 启用 Webauthn 登录
-1. **Enable WebAuthn Feature**: Go to the admin panel, navigate to `Settings` → `Global`, and enable the option `Enable WebAuthn Login`.
-2. **Bind WebAuthn Credentials**: Go to the `Profile` page in the admin panel and click `Add WebAuthn Credential` to bind your credentials.
-
- Supported authentication methods:
- - Local PIN code
- - Companion devices (e.g., smart bands, smartwatches)
- - Windows Hello options (e.g., facial recognition, fingerprint recognition)
-
-3. **Log in with WebAuthn**: After binding, you can log in using WebAuthn:
- - On the login page, click the login button on the far right.
- - Enter your username.
- - Click login.
- - Follow the prompts to complete WebAuthn verification (unlock the respective authentication method).
-
-::: tip WebAuthn only supports secure origins.
-
-**Supported environments:**
-
-- Websites with `https://` protocol
-- Localhost environment (`localhost`)
-
-**Unsupported environments:**
-
-- `http://` protocol
-- Local network IPs (e.g., `192.168.x.x`)
-- Local IPs (e.g., `127.0.0.1`)
-- Direct access via server IP
-
-:::
-::: zh-CN
**Web Authentication (WebAuthn)** 是一套新的身份验证方法。您可以按照以下步骤启用：
1. **启用 WebAuthn 功能**：进入后台`设置` → `全局`，开启`启用 Webauthn 登录`选项
@@ -276,76 +121,24 @@ Ignore the parameters for forwarding direct links, such as `sign` and `openlist_
:::
-## Allow previewing sharing files { lang="en" }
-
-## 允许预览分享文件 { lang="zh-CN" }
+## 允许预览分享文件
-::: en
-Enable the preview feature for files in share links.
-
-Please note that disabling this option will only hide preview methods (except Download) on the frontend, but cannot prevent users from invoking the relevant APIs.
-:::
-::: zh-CN
允许分享链接中文件的预览功能。
请注意：关闭该选项只会让前端不显示除 Download 以外的预览方式，并不能阻止用户调用相关 API。
-:::
-## Allow previewing sharing archives { lang="en" }
+## 允许预览分享的压缩文件
-## 允许预览分享的压缩文件 { lang="zh-CN" }
-
-::: en
-Enable the preview feature for archives in share links.
-
-Unlike the previous setting, disabling this option will prevent calls to the archive preview APIs for files in share links.
-:::
-::: zh-CN
允许分享链接中压缩文件的预览功能。
与上一项配置不同，关闭该选项会拦截对分享链接中压缩文件的预览相关请求。
-:::
-## Force proxy sharing files { lang="en" }
+## 强制代理分享文件链接
-## 强制代理分享文件链接 { lang="zh-CN" }
-
-::: en
-Enforce proxying for all file requests originating from share links.
-:::
-::: zh-CN
强制代理所有来自分享链接的文件请求
-:::
-
-## Share summary content { lang="en" }
-
-## 分享链接复制内容 { lang="zh-CN" }
-
-::: en
-The content copied by clicking "Copy Link" after sharing completion, coding in Handlebars template syntax.
-
-If you prefer copying the accessible link directly, try:
-
-- Preview link
-
-```handlebars
-{{base_url}}/@s/{{id}}
-```
-
-- Preview link with share code
-```handlebars
-{{base_url}}/@s/{{id}}{{#if pwd}}?pwd={{pwd}}{{/if}}
-```
+## 分享链接复制内容
-- direct download link (applies only to single-file shares)
-
-```handlebars
-{{base_url}}/sd/{{id}}{{#if pwd}}?pwd={{pwd}}{{/if}}
-```
-
-:::
-::: zh-CN
分享完成后点击“复制链接”复制的内容，使用 Handlebars 模板语法，默认内容的中文版：
```handlebars
@@ -386,45 +179,18 @@ If you prefer copying the accessible link directly, try:
{{base_url}}/sd/{{id}}{{#if pwd}}?pwd={{pwd}}{{/if}}
```
-:::
-
-## Handle hook after writing { lang="en" }
-
-## 写入操作后触发目录更新钩子 { lang="zh-CN" }
-
-::: en
-Whether to trigger the directory update hook after operations such as upload, rename, delete, move, copy, or extraction.
+## 写入操作后触发目录更新钩子
-Triggering the directory update hook will cause the index to update and activate the function of the [Strm](/guide/drivers/strm) driver to generate local files.
-:::
-::: zh-CN
上传、重命名、删除、移动、复制、解压操作后，是否触发目录更新钩子。
目录更新钩子触发将导致索引更新及[Strm](/guide/drivers/strm)驱动生成本地文件的功能触发。
-:::
-
-## Handle hook rate limit { lang="en" }
-## 目录更新钩子遍历限制速率 { lang="zh-CN" }
+## 目录更新钩子遍历限制速率
-::: en
-It is only meaningful when the [Handle hook after writing](/configuration/global#handle-hook-after-writing) is enabled. When the directory update hook is triggered, this limits the rate at which the driver API is called (unit: times/second; 0 means no restriction).
-:::
-::: zh-CN
仅当[写入操作后触发目录更新钩子](/configuration/global#写入操作后触发目录更新钩子)开启时有意义，触发目录更新钩子时，限制调用驱动 API 的速率（单位：次/秒，为 0 表示不限制）。
-:::
-
-## Ignore system files { lang="en" }
-## 忽略系统文件 { lang="zh-CN" }
+## 忽略系统文件
-::: en
-When enabled, attempts by users to upload certain system files will directly fail, thereby achieving filtering.
-
-The determination of whether a file is a system file is based on its filename.
-:::
-::: zh-CN
开启时，当用户尝试上传某些系统文件时会直接失败，从而实现过滤。
判断是否为系统文件的依据为文件名。
-:::
diff --git a/pages/configuration/index.md b/pages/configuration/index.md
index dd6b8e017..2ca782814 100644
--- a/pages/configuration/index.md
+++ b/pages/configuration/index.md
@@ -1,31 +1,11 @@
----
-title:
- en: Configuration
- zh-CN: 配置
----
+# 配置
---
-::: en
-
-- [Configuration file](./configuration/configuration)
-- [Site settings](./configuration/site)
-- [Style settings](./configuration/style)
-- [Preview settings](./configuration/preview)
-- [Global settings](./configuration/global)
-- [Other settings](./configuration/other)
-- [Side settings](./configuration/side)
-
-:::
-
-::: zh-CN
-
-- [配置文件](./configuration/configuration)
-- [站点设置](./configuration/site)
-- [样式设置](./configuration/style)
-- [预览设置](./configuration/preview)
-- [全局设置](./configuration/global)
-- [其他设置](./configuration/other)
-- [侧边栏设置](./configuration/side)
-
-:::
+- [配置文件](./configuration)
+- [站点设置](./site)
+- [样式设置](./style)
+- [预览设置](./preview)
+- [全局设置](./global)
+- [其他设置](./other)
+- [侧边栏设置](./side)
diff --git a/pages/configuration/other.md b/pages/configuration/other.md
index e7a5c0844..959e013c7 100644
--- a/pages/configuration/other.md
+++ b/pages/configuration/other.md
@@ -1,82 +1,34 @@
---
-title:
- en: Other Configuration
- zh-CN: 其他设置
-# This is the icon of the page
-icon: iconfont icon-snow
categories:
- configuration
-# A page can have multiple tags
top: 10
---
-## Aria2
-
-::: en
-Used for the offline download feature, which downloads an external resource outside of OpenList into the storage managed by OpenList.
-Set Aria2 uri and Aria2 for offline download.
+# 其他设置
-> `Aria2` needs to access the same directory as `OpenList`: `/opt/openlist/data/temp/aria2`. Assuming that both Aria2 and OpenList are independent containers, where OpenList mounts the directory `/etc/openlist/data:/opt/openlist/data`, Aria2 containers need to be additionally mounted under the path `/etc/openlist/data/temp/aria2:/opt/openlist/data/temp/aria2`.
+## Aria2
-:::
-::: zh-CN
这是用于离线下载功能，即：将一个OpenList外部的资源下载到OpenList所管理的存储中。
设置 Aria2 URI 以供离线下载。
> **`Aria2` 需要和`OpenList`访问同一目录: `/opt/openlist/data/temp/aria2`。假设您的Aria2和OpenList都是独立容器，其中OpenList挂载的目录为`/etc/openlist/data:/opt/openlist/data`，则Aria2容器需要额外挂载的`/etc/openlist/data/temp/aria2:/opt/openlist/data/temp/aria2`路径下。**
-:::
-
-### Aria2 地址 { lang="zh-CN" }
-
-### Aria2 uri { lang="en" }
+### Aria2 地址
-::: en
-The Aria2 RPC address used for offline downloading. The default value is: `http://localhost:6800/jsonrpc`.
-:::
-::: zh-CN
用于离线下载的 Aria2 RPC 地址。默认值为：`http://localhost:6800/jsonrpc`。
-:::
-### Aria2 秘钥 { lang="zh-CN" }
+### Aria2 秘钥
-### Aria2 secret { lang="en" }
-
-::: en
-The Aria2 RPC secret key used for offline downloading. The default value is empty.
-:::
-::: zh-CN
用于离线下载的 Aria2 RPC 秘钥。默认值为空。
-:::
## qBittorrent
-::: en
-Used to customize **qBittorrent** parameters to configure the client to use.
-
-The default value is: `http://admin:adminadmin@localhost:8080/`, you can modify it by referring to [specific instructions](../guide/advanced/offline-download.md#qbittorrent)
-:::
-::: zh-CN
用于自定义 **qBittorrent** 参数用来配置客户端中使用。
预设值为：`http://admin:adminadmin@localhost:8080/`，您可以参考 [具体说明](../guide/advanced/offline-download.md#qbittorrent) 进行修改。
-:::
-
-## 115、PikPak、Thunder { lang="en" }
-
-## 115、PikPak、迅雷 { lang="zh-CN" }
-
-::: en
-**You need to add the driver first, and then set the temporary directory in the settings.**
-Allow the use of offline download tools such as 115/PikPak/Thunder in any storage.
+## 115、PikPak、迅雷
-- Files will be downloaded directly to the destination dir if using the tool in 115/PikPak/Thunder storage.
-- Otherwise, files will be downloaded to a user-configured temp dir, and then transfered to the destination dir.
- - For example, on the front-end page of the `GoogleDrive` storage drive, when the `Pikpak offline-download` function is invoked, the file will first be downloaded to the Pikpak temporary folder directory set in the backend. Once the Pikpak offline download is complete, the file will be automatically transferred from Pikpak to `GoogleDrive`.
-
-:::
-::: zh-CN
**需要先添加对应的驱动，然后在后台设置临时目录。**
允许在任意存储使用 115/PikPak/迅雷 等离线下载工具。
@@ -85,36 +37,11 @@ Allow the use of offline download tools such as 115/PikPak/Thunder in any storag
- 否则，文件会下载至用户配置的临时目录中，然后转移至目标目录。
- 例如，在 `GoogleDrive` 存储驱动的前端页面中，调用 `Pikpak offline-download` 功能时，文件会先下载到后台设置的 Pikpak 临时文件夹目录。待 Pikpak 完成离线下载后，文件会自动从 Pikpak 转移到 `GoogleDrive`。
-:::
-
-### Token { lang="en" }
-
-## 令牌 { lang="zh-CN" }
+## 令牌
-::: en
-The token that can be used to access all APIs of the program. Unlike the token obtained after logging in with a username and password, this token is fixed and has no expiration time.
-:::
-::: zh-CN
可用于访问程序所有 API 的令牌。与账号密码登录后获取的不同，此令牌一般固定，且没有失效时间。
-:::
-
-### Other { lang="en" }
-
-### 其他 { lang="zh-CN" }
-::: en
-
-1. When using OpenList, you may notice two Aria2 options. What is the difference between them? [**Click here for detailed explanation**](../faq/why.md#what-is-the-difference-between-the-two-aria2)
-
-2. Supports using Aria2 to download folders while preserving the original directory structure.
- - **Configure Aria2**: Go to the bottom-right corner, click `Settings` → `Aria2 RPC Link` → Enter the `Aria2 RPC Key` (if available).
- - Aria2 will download files locally, so you only need to initiate the download on your local machine. It also supports pushing the download task to another computer, your own server, or other devices in your local network, as long as the target device has Aria2 installed and is connected to either the public internet or the local network.
-
- - **Start downloading**: Check the `Enable checkbox` in the bottom-right corner → Select the files/folders → Click `Download` at the bottom → `Send to Aria2`.
- - **Important notes**: It is recommended not to download too many files at once, such as thousands of folders or tens of thousands of files, as this may cause performance issues.
-
-:::
-::: zh-CN
+### 其他
1. 在使用时发现有两个 Aria2，那它们有什么区别呢？[**点击查看详情说明**](../faq/why.md#两个aria2有什么不同)
2. 支持使用 Aria2 下载文件夹并保持原有目录结构
@@ -123,5 +50,3 @@ The token that can be used to access all APIs of the program. Unlike the token o
- **开启下载**：右下角勾选 `开启复选框` → 选择文件/文件夹 → 点击底部 `下载` → `发送到 Aria2`
- **注意事项**：建议不要一次性下载过多文件，如同时下载上千个文件夹或成千上万个文件，以免导致性能问题。
-
-:::
diff --git a/pages/configuration/preview.md b/pages/configuration/preview.md
index 4bc7f0816..a06b4e037 100644
--- a/pages/configuration/preview.md
+++ b/pages/configuration/preview.md
@@ -1,136 +1,39 @@
---
-title:
- en: Preview Configuration
- zh-CN: 预览设置
-# This is the icon of the page
-icon: iconfont icon-preview
-# This control sidebar order
categories:
- configuration
-# A page can have multiple tags
top: 30
---
-## Text types { lang="en" }
+# 预览设置
-## 文本类型 { lang="zh-CN" }
+## 文本类型
-::: en
-The extensions of the files you want to preview as text, split by `,`, such as `txt,md,go,tsx`.
-:::
-::: zh-CN
要作为文本预览的文件扩展名，用 `,` 分隔，例如 `txt,md,go,tsx`。
-:::
-## Audio types { lang="en" }
+## 音频类型
-## 音频类型 { lang="zh-CN" }
-
-::: en
-The extensions of the files you want to preview as audio, split by `,`, such as `mp3,wav,m4a`.
-:::
-::: zh-CN
要作为音频预览的文件扩展名，以 `,` 分隔，例如 `mp3,wav,m4a`。
-:::
-
-## Video types { lang="en" }
-## 视频类型 { lang="zh-CN" }
+## 视频类型
-::: en
-The extensions of the files you want to preview as video, split by `,`, such as `mp4,webm,ogg`.
-:::
-::: zh-CN
要作为视频预览的文件扩展名，以 `,` 分隔，例如 `mp4,webm,ogg`。
-:::
-
-## Image types { lang="en" }
-## 图片类型 { lang="zh-CN" }
+## 图片类型
-::: en
-The extensions of the files you want to preview as image, split by `,`, such as `jpg,jpeg,png,gif,webp`.
-:::
-::: zh-CN
要作为图像预览的文件扩展名，以 `,` 分隔，例如 `jpg,jpeg,png,gif,webp`。
-:::
-### Proxy types { lang="en" }
+## 代理类型
-## 代理类型 { lang="zh-CN" }
-
-::: en
-The file extensions to be downloaded through the program proxy, split by `,`, such as `m3u8,url`.
-:::
-::: zh-CN
要通过程序代理下载的文件扩展名，以 `,` 分隔，例如 `m3u8,url`。
-:::
-### Proxy ignore headers { lang="en" }
+## 代理忽略头部
-## 代理忽略头部 { lang="zh-CN" }
-
-::: en
-Do not forward request headers, such as `authorization,referer`, when downloading through the program proxy.
-
-This can prevent download failures caused by header parameter leakage.
-:::
-::: zh-CN
当通过程序代理下载时不转发的请求标头，例如 `authorization,referer`。
可以避免请求头参数泄露导致下载失败。
-:::
-
-### External previews { lang="en" }
-
-## 外部预览 { lang="zh-CN" }
-
-::: en
-A json object that contains the external preview settings, It is defined as
-
-```typescript
-interface {
- [extensions: string]: {
- [name: string]: string //(url)
- }
-}
-```
-
-the first key `extensions` is the file extensions separated by `,` (if it starts with `/`, it will be considered a regular expression), and the value is also a `key-value` object, the key is the preview name, and the value is the external url.
-
-For the external URL, we provide some variables for you to use:
-
-Basic variable:
-
-- `$url`: the URL of file, such as `https://openlist.example.com/p/file.pdf`.
-- `$durl`: the direct URL of file, such as `https://oss.example.com/cloud/user/2020/01/01/file.pdf`.
-- `$name`: the file name
-
-Extended variables:
-Add [eb_] before the basic variable, where e means `encodeURIComponent`, b means `base64`, such as:
-
-- `$e_url`: encodeURIComponent($url)
-- `$b_url`: btoa($url)
-- `$eb_url`: encodeURIComponent(btoa($url))
-
-Finally, the `External previews` will displayed a `Open with` menu while current file matched the `extensions`.
-For example, set `External previews` to
-```json
-{
- "txt": {
- "Notepad": "notepad://$url"
- },
- "/.*/": {
- "VSCode": "vscode://$url"
- }
-}
-```
+## 外部预览
-when we enter a file with the extension `txt`, it will show:
-
-:::
-::: zh-CN
一个包含外部预览设置的 json 对象，定义为
```typescript
@@ -174,36 +77,9 @@ interface {
当我们输入一个扩展名为 `txt` 的文件时，它会显示：
-:::
-
-### Iframe previews { lang="en" }
-
-## Iframe 预览 { lang="zh-CN" }
-
-::: en
-Similar to `External previews`, but it will embed an iframe in current page directly.
-
-You need to enter a preview HTML page, and then pass the file address as a parameter to the page using a variable. The available variables are listed in the previous section.
-:::tip
-If you want to use self-deployed OnlyOffice to preview office files, you can add the configuration like this here:
-
-```json
-{
- "doc,docx,xls,xlsx,ppt,pptx": {
- "OnlyOffice": "you_only_office_url"
- }
-}
-```
-
-Deploying and using `OnlyOffice` Reference:
-
-- https://github.com/AlistGo/alist/discussions/3255
-- https://github.com/AlistGo/alist/discussions/8271
-
-:::
+## Iframe 预览
-::: zh-CN
类似于 `外部预览`，但它会直接在当前页面中嵌入 iframe。
您需要填入一个预览的 HTML 网页，然后将文件地址通过变量作为参数传给网页。可以使用的变量见上节。
@@ -227,82 +103,34 @@ Deploying and using `OnlyOffice` Reference:
:::
-### Audio cover { lang="en" }
-
-## 音频封面 { lang="zh-CN" }
+## 音频封面
-::: en
-The default audio cover.
-:::
-::: zh-CN
歌曲无播放封面时显示的默认封面。
-:::
-### Audio autoplay { lang="en" }
+## 自动播放音频
-## 自动播放音频 { lang="zh-CN" }
-
-::: en
-Whether to automatically play audio files.
-:::
-::: zh-CN
是否自动播放音频文件。
-:::
-### Video autoplay { lang="en" }
+## 自动播放视频
-## 自动播放视频 { lang="zh-CN" }
-
-::: en
-Whether to automatically play video files.
-:::
-::: zh-CN
是否自动播放视频文件。
-:::
-
-### Preview archives by default { lang="en" }
-## 默认情况下预览档案 { lang="zh-CN" }
+## 默认情况下预览档案
-::: en
-After enabling this option, compressed files will be previewed by default (as shown in the image below). Although it will consume some server bandwidth, a full download will not occur. If you wish to disable the preview for compressed files, turning off this option will change the default behavior to download mode.
-:::
-::: zh-CN
启用此选项后，默认会对压缩包格式的文件进行预览（如下图所示）。虽然会消耗一些服务器流量，但不会进行完整下载。如果您希望关闭压缩包格式的预览，关闭此选项后，默认行为将改为下载模式。
-:::
-### Readme autorender { lang="en" }
-
-## Readme 自动渲染 { lang="zh-CN" }
+## Readme 自动渲染
-::: en
-After closing, the content of files like readme.md will no longer be automatically rendered.
-
-By default, `readme.md`, `footer.md`, and `bottom.md` will be rendered at the bottom of the file, while `header.md`, `top.md`, and `index.md` will be rendered at the top of the file.
-:::
-::: zh-CN
关闭后，`readme.md` 等文件的内容将不会被自动渲染。
默认情况下，`readme.md`、`footer.md` 和 `bottom.md` 会渲染在文件底部，而 `header.md`、`top.md` 和 `index.md` 会渲染在文件顶部。
-:::
-
-### Filter readme scripts { lang="en" }
-## 过滤 Readme 文件中的脚本 { lang="zh-CN" }
-
-::: en
-Prevent virus script attacks. After turning it on, the contents of `readme.md` will be displayed in text form.
-
-- Including but not limited to strikethrough, tables, task lists, etc. displayed in text form
-- The specific effects are as follows:
- 
+## 过滤 Readme 文件中的脚本
-:::
-::: zh-CN
防止病毒脚本攻击，开启后会以文本形式显示 `readme.md` 内容。
- 包含但不限于 删除线、表格、任务列表等以文本形式展示
@@ -310,29 +138,8 @@ Prevent virus script attacks. After turning it on, the contents of `readme.md` w
-:::
-
-### Force preview { lang="en" }
-
-## 强制预览 { lang="zh-CN" }
-
-::: en
-We can force the preview type through the `type` query parameter.
-
-Available values:
-
-```
-UNKNOWN
-FOLDER
-VIDEO
-AUDIO
-TEXT
-IMAGE
-```
+## 强制预览
-Example: `http://yourdomain/test-file.ahk?type=text`
-:::
-::: zh-CN
可以通过 `type` 请求参数来强制设置预览类型。
可选值:
@@ -347,19 +154,9 @@ IMAGE
```
示例: `http://yourdomain/test-file.ahk?type=text`
-:::
-
-## Specify preview { lang="en" }
-## 指定预览 { lang="zh-CN" }
+## 指定预览
-::: en
-We can specify the preview through the `preview` query parameter. The parameter will be generated when you select a preview in the file page.
-
-Example: `http://yourdomain/test-file.ahk?preview=download`
-:::
-::: zh-CN
可以通过 `preview` 请求参数来指定预览的 `key`。此参数会在文件页面选择预览时生成。
示例: `http://yourdomain/test-file.ahk?preview=download`
-:::
diff --git a/pages/configuration/side.md b/pages/configuration/side.md
index ed62b9ed9..97b1c3c62 100644
--- a/pages/configuration/side.md
+++ b/pages/configuration/side.md
@@ -1,72 +1,11 @@
---
-title:
- en: Side Configuration
- zh-CN: 侧边栏设置
-# This is the icon of the page
-icon: fa-regular fa-sidebar-flip
categories:
- configuration
-# A page can have multiple tags
top: 0
---
-::: en
-We can see a icon on the lower right corner of the homepage. If your computer resolution is very high, the icon is likely to be smaller
-After the expand
+# 侧边栏设置
--
- Refresh
-
- The refresh we mentioned is not to use F5 to refresh the webpage, **but use this icon to refresh**, so that the files that just uploaded to the network disk can be refreshed out.
-
--
- New File
-
--
- New Folder
-
--
- Recursive Move
-
- Move all the files in the current directory and all files in the subfolder to the designated folder
- - :warning: Dangerous operation, please use it with caution.
-
--
- Remove Empty Folder
-
--
- Batch Rename
-
--
- Upload
-
- Open the upload modal.
-
--
- Offline download
-
- Open the offline download modal.
-
--
- Toggle Outline
-
- Toggle the outline for markdown viewer.
-
--
- Toggle Checkbox
-
- Select multiple files.
- - In the display of Toggle Checkbox, first trigger the selection operation to prevent jumping into a deeper folder
- - In the display of Toggle Checkbox, change it to hold down the `Alt` key and click to open the folder (macOS Press and hold the `Option` key)
-
--
- Local Settings
-
- Open the local settings.
-
-:::
-
-::: zh-CN
我们在主页右下角能看到一个 图标,如果你电脑分辨率很高 可能图标比较小
展开后分别是
@@ -120,43 +59,11 @@ After the expand
打开本地设置页面。
-:::
-
-::: en
-::: tip
-If you didn't find this feature, please update the version
-:::
-
-::: zh-CN
::: tip
如果你没有找到此功能，请更新版本
:::
-## Upload Modal { lang="en" }
-
-## 上传窗口 { lang="zh-CN" }
-
-::: en
-
-
-
-Drag files to the field to upload, or click `Choose Folder` or `Choose File` to select files to upload.
-
-There are two methods to upload files:
-
-1. **Stream**: directly puts the binary content of the file into the body, so that the backend can use very little memory, it seem to have no downsides.
-
-2. **Form**: is to wrap the file into formdata and upload it. The memory used by the backend will be more, but there is no limit on the size.
-
-There are the following options:
-
-- **Add as Task**: Create an upload task in the background.
-- **Overwrite existing File**: If the file already exists, it will be overwritten.
-- **Try rapid**: Upload the file with its checksum information, requires cloud storage support.
-
-:::
-
-::: zh-CN
+## 上传窗口
@@ -175,31 +82,7 @@ There are the following options:
- **尝试秒传**：在上传时携带文件的校验信息，需要网盘支持
-:::
-
-## Offline Download Modal { lang="en" }
-
-## 离线下载窗口 { lang="zh-CN" }
-
-::: en
-
-
-
-Download the file offline and upload it to the network disk directory you designated.
-
-If you want to keep the offline downloaded file, please add the link first, select the options below, and then start the offline download.
-
-**How to use**: Navigate to the target directory, then select "Offline Download" from the bottom-right corner.
-
-Supported offline download tools: `Aria2`, `qBittorrent`, `SimpleHttp`.
-
-**Note**: When using the offline download feature, OpenList must be installed and running on the corresponding device. Offline downloads cannot be performed across different devices.
-
-For more information, please refer to [Offline Download](../guide/advanced/offline-download.md).
-
-:::
-
-::: zh-CN
+## 离线下载窗口
@@ -215,53 +98,7 @@ For more information, please refer to [Offline Download](../guide/advanced/offli
详见：[离线下载](../guide/advanced/offline-download.md)。
-:::
-
-## Local Settings Modal { lang="en" }
-
-## 本地设置窗口 { lang="zh-CN" }
-
-::: en
-
-Local settings will be saved to the browser's local storage.
-
-1. **Aria2 RPC URL** and **Aria2 RPC secret**: This field is for entering the user's Aria2 information, which enables batch downloading on the client side, not on the server side.
-
-2. **Global default layout**: The selection of view selection in the upper right corner is to enter that folder to modify it only for the only folder. This setting can consistently take effect without using a folder setting.
-
-3. **Show folder in image view**: literal meaning
-
-4. **Show sidebar**: Add a list directory on the left side of the list like Windows Explorer, which can jump to a deep folder faster
-
-5. **Show file count message**: At the bottom of the page (in list view) or at the top (in grid or image view), display the total number of items in the current folder and how many items are selected.
-
-6. **Position of header & nav bar**: Is the logo and navigation bar displaying at the drop -down list?
- - **Normal**: No need to display
- - **Stick to top of page**: adsorb LOGO and navigation bar
- - **Only nav bar sticky**: Do not adsorb LOGO, only adsorb navigation bar
-
-7. **Grid item size** : Adjust the picture size in the Grid item mode. Default: 90.
-
-8. **List item filename overflow**: When the text is too long, the three state selection
- - **Ellipsis**: Default
- - **Scrollable**: PC users use the `Shift` + `mousewheel` on the file, if it is a mobile phone user sliding the file left and right
- - **Multi-line**
-
-9. **Open item on Checkbox**:
- - **Direct**: Open the file/enter the folder
- - **Double Click**
- - **Disable while checked**
- - With `Ctrl` or `Command` (macOS) hold
- - With `Alt` or `Option` (macOS) hold
- - If the button option does not take effect, please check whether the browser plugin conflict
-
- Tips: You can press the `Shift` key to select one, and then select one end. You can quickly select all the files in the middle
-
-10. **Language package selection** and **night mode and daytime mode switch**
-
-:::
-
-::: zh-CN
+## 本地设置窗口
本地设置会被保存到浏览器的 Local Storage 中。
@@ -298,5 +135,3 @@ Local settings will be saved to the browser's local storage.
Tips：可以按着 `Shift` 键选择一个开头，再选择一个结尾可以快速选择中间的全部
10. **语言包选择** 和 **夜间白天切换**
-
-:::
diff --git a/pages/configuration/site.md b/pages/configuration/site.md
index 1ebf2a6b8..30dc0f35d 100644
--- a/pages/configuration/site.md
+++ b/pages/configuration/site.md
@@ -1,58 +1,26 @@
---
-title:
- en: Site Configuration
- zh-CN: 网站设置
-# This is the icon of the page
-icon: iconfont icon-tab
-# A page can have multiple categories
categories:
- configuration
-# A page can have multiple tags
top: 50
---
-## Version { lang="en" }
+# 网站设置
-## 版本 { lang="zh-CN" }
+## 版本
-::: en
-The version of OpenList, readonly.
-:::
-::: zh-CN
OpenList 的版本，只读。
-:::
-## Site title { lang="en" }
+## 网站标题
-## 网站标题 { lang="zh-CN" }
-
-::: en
-The title of OpenList, such as `OpenList`.
-:::
-::: zh-CN
OpenList 的标题，例如 OpenList。
-:::
-
-## Announcement { lang="en" }
-
-## 公告 { lang="zh-CN" }
-
-::: en
-The announcement of OpenList, such as `### Hello\nWelcome to use OpenList`. We suggest you add a title in front of the content, such as `### Hello`, so that the content will not be covered by `Close Button`.
-
-- If you don't want to display it, you can clear the contents of the announcement to not display it.
-- If you think the `x` button in the upper right corner is in the way, you can use the following CSS to remove it
-:::
+## 公告
-::: zh-CN
OpenList 的公告，如 `### Hello\nWelcome to use OpenList`。我们建议您在内容前添加标题，例如 `### Hello`，以免内容被关闭按钮覆盖。
- 如想不显示，可以清空公告内内容即可不显示。
- 如果嫌右上角的 `x` 按钮碍事可以使用如下CSS去掉
-:::
-
```css
```
-## Pagination type { lang="en" }
-
-## 分页类型 { lang="zh-CN" }
-
-::: en
-
-- All: All files will be displayed at once.
-- Pagination: Show a `Paginator` at the bottom of the page.
-- Load more: Show a `Load more` button at the bottom of the page.
-- Auto load more: Automatically load more files when scrolling to the bottom of the page.
-
-:::
-::: zh-CN
+## 分页类型
- 全部：一次显示所有文件。
- 分页：在页面底部显示一个“分页器”。
- 加载更多：在页面底部显示“加载更多”按钮。
- 自动加载更多：滚动到页面底部时自动加载更多文件。
-:::
-
-## Default page size { lang="en" }
+## 默认每页文件数量
-## 默认每页文件数量 { lang="zh-CN" }
-
-::: en
-The default page size of the `openlist` if `Pagination type` doesn't set to `All`, such as `20`.
-:::
-::: zh-CN
OpenList 的默认每页文件数量，当 `Pagination type` 没有被设置为 `全部` 时生效，例如 `20`。
-:::
-
-## Allow indexing { lang="en" }
-## 允许索引 { lang="zh-CN" }
+## 允许索引
-::: en
-Whether to allow others to mount your OpenList to build the index, check it and enable it.
-
-The default is off, use with caution. (New features in version 3.8.0)
-:::
-
-::: zh-CN
是否允许其他人挂载你的OpenList后进行索引构建，勾选后开启。
**默认为关闭状态，谨慎使用。** （v3.8.0 新增功能）
-:::
-
-## Allow mounted { lang="en" }
-
-## 允许挂载 { lang="zh-CN" }
-::: en
-Whether to allow being mounted by other OpenList instances.
+## 允许挂载
-**The default is enabled. If you don't want to be mounted by others, it's recommended to disable this option.** (New feature in v3.16.3)
-:::
-
-::: zh-CN
是否允许被其它 OpenList 挂载。
**默认为开启状态，如果你不想被别人挂载建议关闭。**（v3.16.3新增功能）
-:::
## robots.txt
-::: en
-Crawler configuration/rules.
-
-The default is to allow crawlers to access all pages.
-
-`Allow: /` Indicates that the crawlers of search engines are allowed to visit all pages:
-
-```txt{2}
-User-agent: *
-Allow: /
-```
-
-If you want to prevent crawlers from accessing all pages, you can change it to this:
-
-```txt{2}
-User-agent: *
-Disallow: /
-```
-
-:::
-
-::: zh-CN
爬虫的配置/规则。
默认允许爬虫访问所有页面。
@@ -166,5 +71,3 @@ Allow: /
User-agent: *
Disallow: /
```
-
-:::
diff --git a/pages/configuration/style.md b/pages/configuration/style.md
index a48ae879b..63b85a166 100644
--- a/pages/configuration/style.md
+++ b/pages/configuration/style.md
@@ -1,98 +1,39 @@
---
-title:
- en: Style Configuration
- zh-CN: 样式设置
-# This is the icon of the page
-icon: iconfont icon-style
-# This control sidebar order
categories:
- configuration
-# A page can have multiple tags
top: 40
---
-## Logo
+# 样式设置
-::: en
-The logo is displayed in the upper left corner of the page. The default is the `OpenList logo`.
+## Logo
-You can set two different ones at night and during the day, one link per line.
-:::
-::: zh-CN
Logo 显示在页面的左上角。默认为 OpenList Logo。
可以分别设置夜间和白天两个不同的，方法一行一个链接。
-:::
-## Favicon { lang="en" }
+## 网站图标
-## 网站图标 { lang="zh-CN" }
-
-::: en
-The favicon is displayed in the browser tab. The default is the `OpenList logo`.
-:::
-::: zh-CN
网站图标（Favicon）显示在浏览器选项卡中。默认为 OpenList Logo。
-:::
-
-## Main color { lang="en" }
-## 主颜色 { lang="zh-CN" }
+## 主颜色
-::: en
-The main color is used to on the page. The default is `#1890ff`.
-:::
-::: zh-CN
全站页面的主要颜色。默认值为 `#1890ff`。
-:::
-## Home icon { lang="en" }
+## 首页图标
-## 首页图标 { lang="zh-CN" }
-
-::: en
-The home icon is displayed in the left of the navigation bar. The default is `🏠`.
-:::
-::: zh-CN
主页图标显示在导航栏的左侧。 默认是 `🏠`。
-:::
-
-## Home container { lang="en" }
-
-## 主容器 { lang="zh-CN" }
-
-::: en
-- Max 980px: the main width will set to `min(99%, 980px)`
-- Hope container: sets the max-width of the content to match the min-width of the current breakpoint, refer to https://openlistteam.github.io/hope-ui/docs/layout/container
-
-:::
-
-::: zh-CN
+## 主容器
- Max 980px：主宽度将设置为 `min(99%, 980px)`
- Hope 容器：设置内容的最大宽度以匹配当前断点的最小宽度，参考 https://openlistteam.github.io/hope-ui/docs/layout/container
-:::
-
-## Settings layout { lang="en" }
-
-## 设置布局 { lang="zh-CN" }
-
-::: en
-The layout of the settings items on the management page.
-
-- Responsive: grids next to each other
-- List style: one grid per row
-
-The default is: List
+## 设置布局
-:::
-::: zh-CN
管理页面中设置项的布局方式。
- 响应式：一个格子一个格子挨在一起的
- 列表：一行一个格子
默认为：列表
-:::
diff --git a/pages/ecosystem/index.md b/pages/ecosystem/index.md
index 97453e744..00b27662a 100644
--- a/pages/ecosystem/index.md
+++ b/pages/ecosystem/index.md
@@ -1,343 +1,174 @@
---
-title:
- en: OpenList Ecosystem
- zh-CN: OpenList 生态项目
categories:
- ecosystem
top: 1000
---
-::: en
-This page shows the OpenList ecosystem, including official projects and third-party projects
-:::
+# OpenList 生态项目
-::: zh-CN
本页面展示了OpenList的生态项目，包括官方项目和第三方项目
-:::
-## Official Projects { lang="en" }
+## 官方项目
-## 官方项目 { lang="zh-CN" }
+### [OpenList Docs ↗](./official_docs)
-### [OpenList Docs ↗](./ecosystem/official_docs)
-
-::: en
-Documentation based on Valaxy, supporting multiple styles and real-time builds from the GitHub repository.
-:::
-::: zh-CN
-基于Valaxy的文档，支持多种样式，基于GitHub仓库实时构建。
-:::
+基于 VitePress 的文档，基于 GitHub 仓库实时构建。
---
-### [OpenList Desktop ↗](./ecosystem/official_desktop)
+### [OpenList Desktop ↗](./official_desktop)
-::: en
-A cross-platform GUI management interface integrating OpenList and rclone, offering graphical configuration, monitoring, and service management features.
-:::
-::: zh-CN
整合了OpenList和rclone的跨平台GUI管理界面，提供图形化配置界面、监控和服务管理等实用功能。
-:::
---
-### [OpenList Mobile ↗](./ecosystem/official_mobile)
+### [OpenList Mobile ↗](./official_mobile)
-::: en
-A mobile file server application based on OpenList, built with Flutter framework. Turn your phone into a file server.
-:::
-::: zh-CN
基于OpenList的移动端文件服务器应用，使用Flutter框架开发。将您的手机变成文件服务器。
-:::
---
-### [OpenList APIPages ↗](./ecosystem/official_APIpage)
+### [OpenList APIPages ↗](./official_APIpage)
-::: en
-An open-source implementation of the online API functionality in OpenList, deployable on various servers, providing stable and privacy-protected API authentication services for cloud storage users.
-:::
-::: zh-CN
OpenList中在线API功能的开源实现，可灵活部署至多种服务器，可以为网盘用户提供稳定且有双向隐私保障的API鉴权服务。
-:::
---
-### [OpenList Proxy ↗](./ecosystem/official_proxy)
+### [OpenList Proxy ↗](./official_proxy)
-::: en
-OpenList traffic proxy program, which can use another server to proxy OpenList traffic.
-:::
-::: zh-CN
OpenList流量代理程序，可以利用另一台服务器代理OpenList的流量
-:::
-
-### [OpenList Worker ↗](./ecosystem/official_worker)
-
-:::: en
-The official TypeScript + Serverless port of OpenList running on Cloudflare Workers / EdgeOne / Alibaba Cloud ESA, reusing the official React 19 frontend.
-::::
-:::: zh-CN
-OpenList 官方的 TypeScript + Serverless 移植版，运行于 Cloudflare Workers / EdgeOne / 阿里云 ESA，复用官方 React 19 前端。
-::::
---
-## Third-Party Open Source Projects { lang="en" }
+### [OpenList Worker ↗](./official_worker/)
-## 第三方开源项目 { lang="zh-CN" }
+OpenList 官方的 TypeScript + Serverless 移植版，运行于 Cloudflare Workers / EdgeOne / 阿里云 ESA，复用官方 React 19 前端。
-:::: en
-::: tip
-Third-party open source projects are based on community open-source security. The following projects are not affiliated with OpenListTeam. Please evaluate the associated risks before deploying them to a production environment.
+---
-If you have a new project that is not listed here, you can submit it through [Issues](https://github.com/OpenListTeam/OpenList-Docs/issues) or [Pull Request](https://github.com/OpenListTeam/OpenList-Docs/pulls).
-:::
-::::
+## 第三方开源项目
-:::: zh-CN
::: tip
以下第三方开源项目均由社区开发并保持开源，与 OpenListTeam 无直接关联。在部署到生产环境前，请自行评估相关风险。
如果您有新的项目没有在此列出，可以通过 [Issues](https://github.com/OpenListTeam/OpenList-Docs/issues) 或 [Pull Request](https://github.com/OpenListTeam/OpenList-Docs/pulls) 提交。
-::::
+:::
### [sbwml/luci-app-openlist ↗](https://github.com/sbwml/luci-app-openlist)
-::: en
-Provides LuCI support for OpenList, suitable for OpenWRT-based router systems.
-
-Free and Open Source Software licensed under the MIT license.
-:::
-::::
-
-::: zh-CN
为 OpenList 提供 LuCI 支持，适用于基于 OpenWRT 的路由器系统。
自由开源软件，MIT 协议
-:::
---
### [giturass/openlist_termux ↗](https://github.com/giturass/openlist_termux/)
-::: en
-OpenList management script for Termux, used for convenient installation, updating, and management of OpenList in the Android Termux environment.
-
-Free and Open Source Software licensed under the MIT license.
-:::
-
-::: zh-CN
Termux 下的 OpenList 管理脚本，用于在 Android Termux 环境中便捷安装、更新和管理 OpenList.
自由开源软件，MIT协议
-:::
---
### [ypq123456789/openlist-manger ↗](https://github.com/ypq123456789/openlist-manger)
-::: en
-A cross-platform interactive Shell script for managing OpenList, supporting Linux, macOS, Windows (WSL), and Android Termux.
-
-Free and Open Source Software licensed under the MIT license.
-:::
-
-::: zh-CN
一个用于管理 OpenList 的跨平台交互式 Shell 脚本，支持 Linux、macOS、Windows (WSL) 和 Android Termux。
自由开源软件，MIT协议
-:::
---
### [Alien-Et/OpenList-Magisk ↗](https://github.com/Alien-Et/OpenList-Magisk)
-::: en
-The OpenList Magisk module integrates the OpenList file server into the Android system, running in a systemized manner through Magisk, supporting ARM and ARM64 architectures.
-
-Free and Open Source Software licensed under the MIT license.
-:::
-
-::: zh-CN
OpenList Magisk 模块将 OpenList 文件服务器集成到 Android 系统中，通过 Magisk 以系统化方式运行，支持 ARM 和 ARM64 架构。
自由开源软件，MIT 协议
-:::
---
### [qianye216/OpenList-Desktop ↗](https://github.com/qianye216/OpenList-Desktop)
-::: en
-OpenList Desktop is a cross-platform desktop client designed for OpenList (Alist) and Rclone. It provides a modern and user-friendly graphical interface that helps you easily manage Alist services and Rclone cloud storage mounts without needing to memorize and input tedious command-line instructions.
-
-Free and Open Source Software licensed under the GPLv3 license.
-:::
-
-::: zh-CN
OpenList Desktop 是一个为 OpenList (Alist) 和 Rclone 设计的跨平台桌面客户端。它提供了一个现代化且用户友好的图形界面，帮助您轻松管理 Alist 服务和 Rclone 云盘挂载，无需记忆和输入繁琐的命令行指令。
自由开源软件，GPLv3 协议
-:::
---
### [LeoHaoVIP/AListLiteAndroid ↗](https://github.com/LeoHaoVIP/AListLiteAndroid)
-::: en
-AListLite is an Android application that supports running OpenList services. Compared to the tutorial described in BV1ex4y157xJ, users can use OpenList services on Android devices (phones/TVs) without needing to install Termux.
-
-Free and Open Source Software licensed under the AGPLv3 license.
-:::
-
-::: zh-CN
AListLite 是一款支持运行 OpenList 服务的 Android 应用，相对于教程 BV1ex4y157xJ 中的描述，用户无需借助安装 Termux 即可实现在 Android 设备（手机/电视）上使用 OpenList 服务。
自由开源软件，AGPLv3 协议
-:::
---
### [outlook84/mpv-handler-openlist ↗](https://github.com/outlook84/mpv-handler-openlist)
-::: en
-This is a URL protocol handler (mpv://) designed for mpv or mpv.net media players on Windows platform. This tool is used to invoke mpv or mpv.net players from OpenList web pages to open video links.
-
-Free and Open Source Software licensed under the GPLv2 license.
-:::
-
-::: zh-CN
这是一个为 Windows 平台上的 mpv 或 mpv.net 媒体播放器设计的 URL 协议注册器 (mpv://)。该工具用于在 OpenList Web 网页上调用 mpv 或 mpv.net 播放器来打开视频链接。
自由开源软件，GPLv2 协议
-:::
---
### [outlook84/openlist-tvbox-gateway ↗](https://github.com/outlook84/openlist-tvbox-gateway)
-::: en
-OpenList gateway for TVBox, used to connect OpenList resources to TVBox-compatible clients.
-
-Free and Open Source Software licensed under the AGPLv3 license.
-:::
-
-::: zh-CN
适用于 TVBox 的 OpenList 网关，用于将 OpenList 资源接入兼容 TVBox 的客户端。
自由开源软件，AGPLv3 协议
-:::
---
### [moyanj/AList3SDK ↗](https://github.com/moyanj/AList3SDK)
-::: en
-A high-performance Python SDK for easy interaction with OpenList/AList services. Supports both asynchronous and synchronous APIs, and provides comprehensive type annotations!
-
-Free and Open Source Software licensed under the LGPL-2.1 license.
-:::
-
-::: zh-CN
一个高性能的 Python SDK，用于与 OpenList/AList 服务轻松交互。同时支持异步和同步 API，并提供完善的类型注解！
自由开源软件，LGPL-2.1协议
-:::
---
### [huancun/Openlist-EX-container ↗](https://github.com/huancun/Openlist-EX-container)
-::: en
-This project is an improved version based on Alist-EX-container.
-Integrates Openlist, Aria2, qBittorrent, Caddy reverse proxy, supports multi-arch one-click deployment, navigation page and multiple web panels, perfect for offline download and resource management.
-
-Free and Open Source Software licensed under the GPLv3 license.
-:::
-
-::: zh-CN
该项目基于 Alist-EX-container 改进。
集成 Openlist、Aria2、qBittorrent、Caddy 反向代理，支持多架构一键部署，带导航页和多种 Web 面板，适合离线下载和资源管理。
自由开源软件，GPLv3 协议
-:::
---
### [hienao/ostrm ↗](https://github.com/hienao/ostrm)
-::: en
-A full-stack application for converting OpenList file lists into STRM streaming media files. (Originally the openlist-strm project)
-
-Free and Open Source Software licensed under the GPLv3 license.
-:::
-
-::: zh-CN
一个用于将 OpenList 文件列表转换为 STRM 流媒体文件的全栈应用（原为 openlist-strm 项目）
自由开源软件，GPLv3协议
-:::
---
### [li-peifeng/iNoi ↗](https://github.com/li-peifeng/iNoi)
-::: en
-An open-source fork of OpenList focusing on stability.
-
-Free and Open Source Software licensed under the AGPLv3 license.
-:::
-
-::: zh-CN
一个 OpenList 的开源分支，以追求稳定为主
自由开源软件，AGPLv3协议
-:::
---
### [907739769/OpenList-strm-RuoYi ↗](https://github.com/907739769/OpenList-strm-RuoYi/)
-::: en
-An improved version of OpenList Strm based on RuoYi framework.
-
-Free and Open Source Software licensed under the MIT license.
-:::
-
-::: zh-CN
基于RuoYi框架升级的OpenList Strm 应用
自由开源软件，MIT协议
-:::
---
### [Liki4/qnap-openlist-webdav ↗](https://github.com/Liki4/qnap-openlist-webdav/)
-::: en
-QNAP OpenList | The third-party open-source QPKG version of OpenList.
-
-Free and Open Source Software licensed under the AGPLv3 license.
-:::
-
-::: zh-CN
QNAP OpenList | OpenList的第三方开源qpkg版本。
自由开源软件，AGPLv3协议
-:::
---
### [HisAtri/openlistapi ↗](https://github.com/HisAtri/openlistapi/)
-::: en
-An open-source Python client implementing the OpenList API.
-
-Free and Open Source Software licensed under the MIT license.
-:::
-
-::: zh-CN
实现了 OpenList API 的 Python 客户端。
自由开源软件，MIT协议
@@ -346,21 +177,14 @@ Free and Open Source Software licensed under the MIT license.
### [jiwangyihao/olist-cdn-preheat ↗](https://github.com/jiwangyihao/olist-cdn-preheat/)
-::: en
-OpenList dedicated CDN preheating tool. When used with EdgeOne/ESA origin-following redirection, it efficiently improves cache hit rates and accelerates site downloads.
-
-Free and Open Source Software licensed under the MPLv2 license.
-:::
-
-::: zh-CN
OpenList 专用 CDN 预热工具。搭配 EdgeOne/ESA 回源跟随重定向，高效提升缓存命中率，加速站点下载。
自由开源软件，MPLv2协议
-:::
+
+---
### [MY QNAP's OpenList ↗](https://www.myqnap.org/product/openlist/)
-::: zh-CN
QNAP存储库 MyQNAP 将 OpenList 应用进行分发并收取 6 美元费用。
我方已与 QNAP 法国团队取得联系，并根据 AGPL 协议及 CC 协议，要求对方提供应用的哈希值，或将该应用下架。
目前，沟通进展如下：
@@ -371,33 +195,6 @@ QNAP存储库 MyQNAP 将 OpenList 应用进行分发并收取 6 美元费用。
4. 基于上述情况，QNAP 已临时下架该应用，并将更新页面。展示哈希值后，OpenList 的下载与分发将恢复。
5. 截至目前，QNAP 暂未实际违反协议。我方为防范开源供应链风险而启动的调查行动已完成。
-:::
-::: en
-QNAP's MyQNAP repository distributes the OpenList application for a fee of $6.
-We have contacted the QNAP France team and, based on the AGPL and CC licenses, requested them to provide the hash values of the application or take it down.
-The communication progress is as follows:
-
-1. The application is provided by QNAP officially, not uploaded by users.
-2. The charging behavior is not for profit, so the CC license does not apply.
-3. According to the AGPL license, if the application has not been modified, hash values like MD5, SHA, etc. must be provided. Currently, QNAP states that the relevant work is in progress.
-4. Based on the above situation, QNAP has temporarily taken down the application and will update the page. Once the hash values are displayed, the download and distribution of OpenList will resume.
-5. As of now, QNAP has not actually violated the license. Our investigation initiated to prevent open-source supply chain risks has been completed.
-
-:::
-
-:::: en
-::: details History information (outdated，archived at 2026-01-22)
-The third-party closed-source QPKG version of OpenList.
-
-[Archived on 2025-7-13](https://web.archive.org/web/20250713005135/https://www.myqnap.org/product/openlist/)
-
-Proprietary software, paid license.
-
-Note: The source code is not open, violating the AGPLv3 license and the OpenList logo's CC BY-NC-SA 4.0 license.
-:::
-::::
-
-:::: zh-CN
::: details 历史信息（已过时，归档于2026-01-22）
OpenList的第三方闭源qpkg版本。
@@ -406,42 +203,18 @@ OpenList的第三方闭源qpkg版本。
专有软件，付费授权
注意：因没有开放源码，违反AGPLv3许可证、违反OpenList LOGO的CC BY-NC-SA 4.0许可。
-::::
-
-## Third-Party Proprietary Software { lang="en" }
-
-## 其他第三方项目 { lang="zh-CN" }
-
-:::: en
-::: danger
-The following lists several other third-party projects derived from OpenList that do not fall into the above categories.
-
-Any actions of these software/projects (including references to OpenList in their names, functionality design, content, or promotional methods) do not represent the stance of the OpenList project. The functionality, consequences of use, and related legal responsibilities are entirely borne by their respective developers or publishers, and the OpenList project assumes no responsibility.
:::
-::::
-:::: zh-CN
+## 其他第三方项目
+
::: danger
以下列出若干基于 OpenList 衍生的其他不符合上述分类的的第三方项目。
以下软件/项目的任何行为（包括其名称中对 OpenList 的引用、功能设计、内容及宣传方式）均**不代表** OpenList 项目的立场。软件功能、使用后果及相关法律责任完全由其开发者或发布方承担，OpenList 项目概不负责。
-::::
+:::
### [Yxiguan/OpenList_123](https://github.com/Yxiguan/OpenList_123)
-:::: en
-::: danger
-The third-party closed-source modified version of OpenList.
-
-[Archived on 2025-10-19](https://web.archive.org/web/20251019150201/https://github.com/Yxiguan/OpenList_123)
-
-Proprietary software, no license.
-
-Note: The source code is not open, violating the AGPLv3 license.
-:::
-::::
-
-:::: zh-CN
::: danger
OpenList的第三方闭源修改版本。
@@ -450,4 +223,4 @@ OpenList的第三方闭源修改版本。
专有软件，无授权
注意：因没有开放源码，违反AGPLv3许可证。
-::::
+:::
diff --git a/pages/ecosystem/official_APIpage.md b/pages/ecosystem/official_APIpage.md
index ed3fffbdd..842dd36b4 100644
--- a/pages/ecosystem/official_APIpage.md
+++ b/pages/ecosystem/official_APIpage.md
@@ -1,72 +1,20 @@
---
-title:
- en: OpenList APIPages
- zh-CN: OpenList APIPages
categories:
- ecosystem
- eco_official
top: 970
---
-## What is OpenList APIPages { lang="en"}
+# OpenList APIPages
-## OpenList APIPages 是什么 { lang="zh-CN" }
+## OpenList APIPages 是什么
### [OpenListTeam/OpenList-APIPages](https://github.com/OpenListTeam/OpenList-APIPages)
-:::en
-[OpenListTeam/OpenList-APIPages](https://github.com/OpenListTeam/OpenList-APIPages) is a utility website led by [@PIKACHUIM](https://github.com/PIKACHUIM) and collaboratively developed with other [main contributors](https://github.com/OpenListTeam/OpenList-APIPages/graphs/contributors). The frontend is primarily used for initial authorization and obtaining refresh tokens of cloud storage clients, while the backend mainly supports a feature called "Online API", which enables remote token refresh functionality while protecting developer client secrets.
-:::
-:::zh-CN
[OpenListTeam/OpenList-APIPages](https://github.com/OpenListTeam/OpenList-APIPages) 是一个由 [@PIKACHUIM](https://github.com/PIKACHUIM) 牵头，和其他[主要贡献者](https://github.com/OpenListTeam/OpenList-APIPages/graphs/contributors)共同协作完成的工具型网站，前端主要用于实现对网盘客户端的初始授权和刷新令牌，而后端则主要支撑了一个名为“在线API”的功能，可以在保护开发者客户端密钥的前提下，实现对用户令牌的远程刷新功能。
-:::
-
-## Why OpenList APIPages is needed { lang="en"}
-
-## 为什么需要 OpenList APIPages { lang="zh-CN" }
-
-:::en
-Cloud Storage Background:
-
-- Most domestic cloud storage services do not provide official API access to individuals, or the application process is cumbersome, which is not conducive to rapid deployment.
-- According to the cloud storage providers' management requirements, the obtained client keys must not be leaked.
-- User authorization is in the form of refresh tokens, which need to be periodically combined with client keys to obtain refreshed access tokens from the cloud storage servers.
-- API calls require the user's latest access tokens.
-
-Solution:
-
-- Community volunteers provide qualification certification and apply for API access permissions from cloud storage officials.
-- Use relay servers to protect client keys.
-- Periodically send refresh tokens to designated relay servers, which use built-in client keys to refresh access tokens.
-- The relay server sends access tokens back to the OpenList client.
-
-The relay server described above is the backend functionality of the Online API server/APIPages, which works as follows:
-
-```mermaid
-sequenceDiagram
- participant OpenList
- participant OnlineAPI as Online API Server
- participant Server as Cloud Storage Server
-
- OpenList ->> OnlineAPI: Refresh Token
- OnlineAPI ->> Server: Cloud Storage Client Key
- Server -->> OnlineAPI: Access Token
- OnlineAPI -->> OpenList: Access Token
- OpenList ->> Server: Access Token
- OpenList <<->> Server: Cloud Storage Data
-```
-
-The frontend part of APIPages also solves the following problems:
-
-- Initial authorization verification for different cloud storage services.
-- Authorization while protecting built-in client keys.
-- Authorization with custom client keys.
-- Providing callback addresses for custom client keys.
-- Other practical functions for cloud storage mounting.
+## 为什么需要 OpenList APIPages
-:::
-:::zh-CN
网盘背景：
- 大部分国内网盘没有对个人开放官方API调用的权限，或者申请过程繁琐，不利于快速部署。
@@ -104,44 +52,19 @@ APIPages的前端部分同时解决了如下问题：
- 提供自定义客户端密钥下的的回调地址。
- 其他网盘挂载的实用功能。
-:::
-
-## How to use OpenList APIPages { lang="en"}
-
-## 如何使用 OpenList APIPages { lang="zh-CN" }
+## 如何使用 OpenList APIPages
-
-
-After deployment, please log in to the [EdgeOne Functions console](https://console.tencentcloud.com/edgeone/pages) to modify environment variables. Please refer to the [Variable Description](#variable-description) section.
-
-- EdgeOne Functions China
-
-
-
-
-
-After deployment, please log in to the [EdgeOne Functions console](https://console.cloud.tencent.com/edgeone/pages) to modify environment variables. Please refer to the [Variable Description](#variable-description) section.
-
-- Cloudflare Workers Global
+## APIPages 的部署教程
-
- 
-
-
-After deployment, please log in to the [Cloudflare Workers console](https://dash.cloudflare.com/) to modify environment variables. Please refer to the [Variable Description](#variable-description) section.
-
-:::
-:::zh-CN
+### 一键部署
- EdgeOne Functions 国际站
@@ -214,87 +102,7 @@ After deployment, please log in to the [Cloudflare Workers console](https://dash
部署完成后，请登录[Cloudflare Worker后台](https://dash.cloudflare.com/)，修改环境变量，请参考[变量说明](#变量说明)部分
-:::
-
-### Container Deployment { lang="en" }
-
-### 容器部署 { lang="zh-CN" }
-
-:::en
-
-- Pull image
-
-```
-docker pull openlistteam/openlist_api_server
-```
-
-or
-
-```
-docker pull ghcr.io/openlistteam/openlist_api_server:latest
-```
-
-- Start project
-
-```
-docker run -d --name oplist-api-server \
- -p 3000:3000 \
- -e OPLIST_MAIN_URLS="api.example.com" \
- -e OPLIST_PROXY_API="gts.example.com" \
- -e OPLIST_ONEDRIVE_UID= `#optional` \
- -e OPLIST_ONEDRIVE_KEY= `#optional` \
- -e OPLIST_ALICLOUD_UID= `#optional` \
- -e OPLIST_ALICLOUD_KEY= `#optional` \
- -e OPLIST_BAIDUYUN_UID= `#optional` \
- -e OPLIST_BAIDUYUN_KEY= `#optional` \
- -e OPLIST_BAIDUYUN_EXT= `#optional` \
- -e OPLIST_CLOUD115_UID= `#optional` \
- -e OPLIST_CLOUD115_KEY= `#optional` \
- -e OPLIST_GOOGLEUI_UID= `#optional` \
- -e OPLIST_GOOGLEUI_KEY= `#optional` \
- -e OPLIST_YANDEXUI_UID= `#optional` \
- -e OPLIST_YANDEXUI_KEY= `#optional` \
- -e OPLIST_DROPBOXS_UID= `#optional` \
- -e OPLIST_DROPBOXS_KEY= `#optional` \
- -e OPLIST_QUARKPAN_UID= `#optional` \
- -e OPLIST_QUARKPAN_KEY= `#optional` \
- openlistteam/openlist_api_server:latest
-```
-
-- You can replace the image with ghcr:
-
- ```
- ghcr.io/openlistteam/openlist_api_server:latest
- ```
-
-- **Please make sure to modify your environment variables according to the environment variables below**
-
-- Environment Variable Description
-
-| Variable Name | Required | Variable Type | Variable Description |
-| --------------------- | -------- | ------------- | ------------------------------------------------------------- |
-| `OPLIST_MAIN_URLS` | Yes | string | Bind main domain, example: api.example.com |
-| `OPLIST_PROXY_API` | No | string | Nodes deployed in mainland China need to specify Google proxy |
-| `OPLIST_ONEDRIVE_UID` | No | string | OneDrive Client ID |
-| `OPLIST_ONEDRIVE_KEY` | No | string | OneDrive Client Secret |
-| `OPLIST_ALICLOUD_UID` | No | string | AliCloud Drive Developer AppID |
-| `OPLIST_ALICLOUD_KEY` | No | string | AliCloud Drive Developer AppKey |
-| `OPLIST_BAIDUYUN_UID` | No | string | Baidu NetDisk Application UID |
-| `OPLIST_BAIDUYUN_KEY` | No | string | Baidu NetDisk Application Secret AppKey |
-| `OPLIST_BAIDUYUN_EXT` | No | string | Baidu NetDisk Application SecretKey |
-| `OPLIST_CLOUD115_UID` | No | string | 115 NetDisk Application ID |
-| `OPLIST_CLOUD115_KEY` | No | string | 115 NetDisk Application Secret |
-| `OPLIST_GOOGLEUI_UID` | No | string | Google Client ID |
-| `OPLIST_GOOGLEUI_KEY` | No | string | Google Global API Key |
-| `OPLIST_YANDEXUI_UID` | No | string | Yandex Application ID |
-| `OPLIST_YANDEXUI_KEY` | No | string | Yandex Application Secret |
-| `OPLIST_DROPBOXS_UID` | No | string | Dropbox Application ID |
-| `OPLIST_DROPBOXS_KEY` | No | string | Dropbox Application Secret |
-| `OPLIST_QUARKPAN_UID` | No | string | QuarkPan Application ID |
-| `OPLIST_QUARKPAN_KEY` | No | string | QuarkPan Application Secret |
-
-:::
-:::zh-CN
+### 容器部署
- 拉取镜像
@@ -365,88 +173,7 @@ docker run -d --name oplist-api-server \
| `OPLIST_QUARKPAN_UID` | 否 | string | 夸克云盘x应用ID |
| `OPLIST_QUARKPAN_KEY` | 否 | string | 夸克云盘应用密钥 |
-:::
-
-### Edge Deployment { lang="en" }
-
-### 边缘部署 { lang="zh-CN" }
-
-:::en
-
-- Clone code
-
-```shell
-git clone https://github.com/OpenListTeam/OpenList-APIPages.git
-```
-
-- Modify configuration (CloudFlare only)
-
-Create and modify `wrangler.jsonc`
-
-```shell
-cp wrangler.example.jsonc wrangler.encrypt.jsonc
-```
-
-Modify variable information:
-
-- MAIN_URLS: Domain name for deployment callback address
-- Other parameters: Application information for each cloud storage service
-
-```
- "vars": {
- "MAIN_URLS": "api.example.com",
- "PROXY_API": "gts.example.com",
- "onedrive_uid": "*****************************",
- "onedrive_key": "*****************************",
- "alicloud_uid": "*****************************",
- "alicloud_key": "*****************************",
- "baiduyun_uid": "*****************************",
- "baiduyun_key": "*****************************",
- "baiduyun_ext": "*****************************",
- "cloud115_uid": "*****************************",
- "cloud115_key": "*****************************",
- "googleui_uid": "*****************************",
- "googleui_key": "*****************************",
- "yandexui_uid": "*****************************",
- "yandexui_key": "*****************************",
- "dropboxs_uid": "*****************************",
- "dropboxs_key": "*****************************",
- "quarkpan_uid": "*****************************",
- "quarkpan_key": "*****************************"
- },
-```
-
-- Test code
-
-```shell
-npm install
-
-# Run in Cloudflare Worker environment
-npm run dev-cf
-
-# Run in Edgeone Functions environment
-npm run dev-eo
-
-# Run in Node Service Work environment
-npm run dev-js
-
-```
-
-- Deploy project
-
-```shell
-# Deploy in Cloudflare Worker environment
-npm run deploy-cf
-
-# Deploy in Edgeone Functions environment
-npm run deploy-eo
-
-# Run locally in Node Service Work
-npm build-js && npm deploy-js
-```
-
-:::
-:::zh-CN
+### 边缘部署
- 克隆代码
@@ -520,70 +247,32 @@ npm run deploy-eo
npm build-js && npm deploy-js
```
-:::
-
-### Variable Description { lang="en" }
-
-### 变量说明 { lang="zh-CN" }
-
-:::en
-| Variable Name | Required | Variable Type | Variable Description |
-| -------------- | ---- | -------- |-------------------|
-| `MAIN_URLS` | Yes | string | Bind main domain, example: api.example.com |
-| `PROXY_API` | No | string | Nodes deployed in mainland China need to specify Google proxy |
-| `onedrive_uid` | No | string | OneDrive Client ID |
-| `onedrive_key` | No | string | OneDrive Client Secret |
-| `alicloud_uid` | No | string | AliCloud Drive Developer AppID |
-| `alicloud_key` | No | string | AliCloud Drive Developer AppKey |
-| `baiduyun_uid` | No | string | Baidu NetDisk Application ID |
-| `baiduyun_key` | No | string | Baidu NetDisk Application Secret AppKey |
-| `baiduyun_ext` | No | string | Baidu NetDisk Application SecretKey |
-| `cloud115_uid` | No | string | 115 NetDisk Application ID |
-| `cloud115_key` | No | string | 115 NetDisk Application Secret |
-| `googleui_uid` | No | string | Google Client ID |
-| `googleui_key` | No | string | Google Global API Key |
-| `yandexui_uid` | No | string | Yandex Application ID |
-| `yandexui_key` | No | string | Yandex Application Secret |
-| `dropboxs_uid` | No | string | Dropbox Application ID |
-| `dropboxs_key` | No | string | Dropbox Application Secret |
-| `quarkpan_uid` | No | string | QuarkPan Application ID |
-| `quarkpan_key` | No | string | QuarkPan Application Secret |
-
-:::
-:::zh-CN
-| 变量名称 | 必要 | 变量类型 | 变量说明 |
-| -------------- | ---- | -------- |-------------------|
-| `MAIN_URLS` | 是 | string | 绑定主域名，示例：api.example.com |
-| `PROXY_API` | 否 | string | 部署在大陆的节点需要指定代理谷歌 |
-| `onedrive_uid` | 否 | string | OneDrive 客户端ID |
-| `onedrive_key` | 否 | string | OneDrive 客户端密钥 |
-| `alicloud_uid` | 否 | string | 阿里云盘开发者AppID |
-| `alicloud_key` | 否 | string | 阿里云盘开发者AppKey |
-| `baiduyun_uid` | 否 | string | 百度网盘应用ID |
-| `baiduyun_key` | 否 | string | 百度网盘应用密钥AppKey |
-| `baiduyun_ext` | 否 | string | 百度网盘应用密钥SecretKey |
-| `cloud115_uid` | 否 | string | 115网盘应用ID |
-| `cloud115_key` | 否 | string | 115网盘应用密钥 |
-| `googleui_uid` | 否 | string | 谷歌客户端ID |
-| `googleui_key` | 否 | string | 谷歌全局API Key |
-| `yandexui_uid` | 否 | string | Yandex应用ID |
-| `yandexui_key` | 否 | string | Yandex应用密钥 |
-| `dropboxs_uid` | 否 | string | Dropboxx应用ID |
-| `dropboxs_key` | 否 | string | Dropbox应用密钥 |
-| `quarkpan_uid` | 否 | string | 夸克云盘x应用ID |
-| `quarkpan_key` | 否 | string | 夸克云盘应用密钥 |
-
-:::
+### 变量说明
+
+| 变量名称 | 必要 | 变量类型 | 变量说明 |
+| -------------- | ---- | -------- | --------------------------------- |
+| `MAIN_URLS` | 是 | string | 绑定主域名，示例：api.example.com |
+| `PROXY_API` | 否 | string | 部署在大陆的节点需要指定代理谷歌 |
+| `onedrive_uid` | 否 | string | OneDrive 客户端ID |
+| `onedrive_key` | 否 | string | OneDrive 客户端密钥 |
+| `alicloud_uid` | 否 | string | 阿里云盘开发者AppID |
+| `alicloud_key` | 否 | string | 阿里云盘开发者AppKey |
+| `baiduyun_uid` | 否 | string | 百度网盘应用ID |
+| `baiduyun_key` | 否 | string | 百度网盘应用密钥AppKey |
+| `baiduyun_ext` | 否 | string | 百度网盘应用密钥SecretKey |
+| `cloud115_uid` | 否 | string | 115网盘应用ID |
+| `cloud115_key` | 否 | string | 115网盘应用密钥 |
+| `googleui_uid` | 否 | string | 谷歌客户端ID |
+| `googleui_key` | 否 | string | 谷歌全局API Key |
+| `yandexui_uid` | 否 | string | Yandex应用ID |
+| `yandexui_key` | 否 | string | Yandex应用密钥 |
+| `dropboxs_uid` | 否 | string | Dropboxx应用ID |
+| `dropboxs_key` | 否 | string | Dropbox应用密钥 |
+| `quarkpan_uid` | 否 | string | 夸克云盘x应用ID |
+| `quarkpan_key` | 否 | string | 夸克云盘应用密钥 |
+
+## 社区 APIPages
-## Community APIPages { lang="en"}
-
-## 社区 APIPages { lang="zh-CN" }
-
-:::en
-:::tip
-The following servers are built and provided by community volunteers. Once used, user authorization credentials will inevitably be sent to the servers over the network. This project is licensed under AGPLv3 and only guarantees to provide the source code "as is". Users should verify the deployed content at their own discretion.
-:::
-:::zh-CN
:::tip
以下服务器由社区志愿者搭建并提供服务，一旦使用将不可避免的将用户授权凭证通过网络形式发送至服务器，本项目根据AGPLv3许可，只保证在源代码层面按“原样”提供，对于部署后的内容，请用户自行甄别。
:::
@@ -593,11 +282,4 @@ The following servers are built and provided by community volunteers. Once used,
......
-:::en
-[Welcome to submit more community servers](https://github.com/OpenListTeam/OpenList-Docs/pulls)
-
-:::
-:::zh-CN
[欢迎提交更多社区服务器](https://github.com/OpenListTeam/OpenList-Docs/pulls)
-
-:::
diff --git a/pages/ecosystem/official_desktop.md b/pages/ecosystem/official_desktop.md
index 33db949c2..ea938a4f3 100644
--- a/pages/ecosystem/official_desktop.md
+++ b/pages/ecosystem/official_desktop.md
@@ -1,48 +1,21 @@
---
-title:
- en: OpenList Desktop
- zh-CN: OpenList Desktop
categories:
- ecosystem
- eco_official
top: 980
---
-## What is OpenList Desktop { lang="en" }
+# OpenList Desktop
-## OpenList Desktop 是什么 { lang="zh-CN" }
+## OpenList Desktop 是什么
### [OpenListTeam/OpenList-Desktop](https://github.com/OpenListTeam/OpenList-Desktop)
-:::en
-[OpenListTeam/OpenList-Desktop](https://github.com/OpenListTeam/OpenList-Desktop) is a powerful cross-platform desktop application led by [@Kuingsmile](https://github.com/Kuingsmile) and collaboratively developed with other [main contributors](https://github.com/OpenListTeam/OpenList-Desktop/graphs/contributors). Built with Vue 3, Tauri, and Rust, it provides a user-friendly interface for managing OpenList services and performing local mounts via Rclone. The application serves as a comprehensive solution for managing OpenList file management services, mounting and managing cloud storage (WebDAV), monitoring service status and uptime, and providing system tray integration for background operations.
-
-:::
-
-:::zh-CN
[OpenListTeam/OpenList-Desktop](https://github.com/OpenListTeam/OpenList-Desktop) 是一个功能强大的跨平台桌面应用程序，由 [@Kuingsmile](https://github.com/Kuingsmile) 牵头，和其他[主要贡献者](https://github.com/OpenListTeam/OpenList-Desktop/graphs/contributors)共同协作完成。基于 Vue 3、Tauri 和 Rust 构建，为管理 OpenList 服务和通过 Rclone 进行本地挂载提供用户友好的界面。该应用程序是一个全面的解决方案，用于管理 OpenList 文件管理服务、挂载和管理云存储（WebDAV）、监控服务运行状态和提供系统托盘集成以进行后台操作。
-:::
-
-## Features { lang="en" }
-
-## 功能特性 { lang="zh-CN" }
-
-### Core Features { lang="en" }
+## 功能特性
-### 核心功能 { lang="zh-CN" }
-
-:::en
-
-- **OpenList Service Management**: Start, stop, and monitor OpenList core services
-- **Local Mounting**: Mount via Rclone to the local file system
-- **Real-time Monitoring**: Track service status, uptime, and performance metrics
-- **Process Management**: Advanced process control with auto-restart capabilities
-- **System Tray**: Background operation with system tray notifications
-
-:::
-
-:::zh-CN
+### 核心功能
- **OpenList 服务管理**：启动、停止和监控 OpenList 核心服务
- **本地挂载**：通过 Rclone 挂载至本地文件系统
@@ -50,23 +23,7 @@ top: 980
- **进程管理**：具有自动重启功能的高级进程控制
- **系统托盘**：带系统托盘通知的后台操作
-:::
-
-### Management Features { lang="en" }
-
-### 管理功能 { lang="zh-CN" }
-
-:::en
-
-- **Service Control**: Start/stop/restart OpenList and Rclone services
-- **Configuration Management**: GUI-based configuration for all services
-- **Log Monitoring**: Real-time log viewing and management
-- **Update Management**: Automatic update checking and installation
-- **Auto-startup**: Configure applications to start with system boot
-
-:::
-
-:::zh-CN
+### 管理功能
- **服务控制**：启动/停止/重启 OpenList 和 Rclone 服务
- **配置管理**：所有服务的基于 GUI 的配置
@@ -74,79 +31,23 @@ top: 980
- **更新管理**：自动更新检查和安装
- **自动启动**：配置应用程序与系统一起启动
-:::
-
-## Installation { lang="en" }
-
-## 安装 { lang="zh-CN" }
-
-### System Requirements { lang="en" }
-
-### 系统要求 { lang="zh-CN" }
-
-:::en
+## 安装
-- **Operating System**: Windows 10+, macOS 10.15+, or Linux (Ubuntu 18.04+)
-
-:::
-
-:::zh-CN
+### 系统要求
- **操作系统**：Windows 10+、macOS 10.15+ 或 Linux（Ubuntu 18.04+）
-:::
-
-### Download Options { lang="en" }
-
-### 下载选项 { lang="zh-CN" }
-
-#### GitHub Releases (Recommended) { lang="en" }
+### 下载选项
-#### GitHub 发行版（推荐） { lang="zh-CN" }
+#### GitHub 发行版（推荐）
-:::en
-Download the latest release from [GitHub Releases](https://github.com/OpenListTeam/OpenList-Desktop/releases):
-
-- **Windows**: `OpenList-Desktop_x.x.x_{arch}-setup.exe`
-- **macOS**: `OpenList-Desktop_x.x.x_{arch}.dmg`
-- **Linux**: `OpenList-Desktop_x.x.x_{arch}.deb` or `OpenList-Desktop_x.x.x_{arch}.rpm`
-
-:::
-
-:::zh-CN
从 [GitHub Releases](https://github.com/OpenListTeam/OpenList-Desktop/releases) 下载最新版本：
- **Windows**：`OpenList-Desktop_x.x.x_{arch}-setup.exe`
- **macOS**：`OpenList-Desktop_x.x.x_{arch}.dmg`
- **Linux**：`OpenList-Desktop_x.x.x_{arch}.deb` 或 `OpenList-Desktop_x.x.x_{arch}.rpm`
-:::
-
-#### Build from Source { lang="en" }
-
-#### 从源码构建 { lang="zh-CN" }
-
-:::en
-
-```bash
-# Clone the repository
-git clone https://github.com/OpenListTeam/OpenList-Desktop.git
-cd openlist-desktop
-
-# Install dependencies
-yarn install
-
-# Prepare development environment
-yarn run prebuild:dev
-
-# Build the application
-yarn run build
-yarn run tauri build
-```
-
-:::
-
-:::zh-CN
+#### 从源码构建
```bash
# 克隆仓库
@@ -164,98 +65,31 @@ yarn run build
yarn run tauri build
```
-:::
-
-### Installation Steps { lang="en" }
-
-### 安装步骤 { lang="zh-CN" }
-
-#### Windows { lang="en" }
-
-#### Windows { lang="zh-CN" }
+### 安装步骤
-##### Using Installer { lang="en" }
+#### Windows
-##### 使用安装程序 { lang="zh-CN" }
-
-:::en
-
-1. Download the `.exe` installer
-2. Run the installer as Administrator
-3. Follow the installation wizard
-4. Launch from Start Menu or Desktop shortcut
-
-:::
-
-:::zh-CN
+##### 使用安装程序
1. 下载 `.exe` 安装程序
2. 以管理员身份运行安装程序
3. 按照安装向导进行操作
4. 从开始菜单或桌面快捷方式启动
-:::
-
-##### Using Winget { lang="en" }
-
-##### 使用 Winget { lang="zh-CN" }
-
-:::en
+##### 使用 Winget
```bash
winget install OpenListTeam.OpenListDesktop
```
-:::
-
-:::zh-CN
-
-```bash
-winget install OpenListTeam.OpenListDesktop
-```
-
-:::
-
-#### macOS { lang="en" }
-
-#### macOS { lang="zh-CN" }
-
-:::en
-
-1. Download the `.dmg` file
-2. Open the DMG and drag OpenList Desktop to Applications
-3. Right-click and select "Open" (first time only)
-4. Grant necessary permissions when prompted
-
-:::
-
-:::zh-CN
+#### macOS
1. 下载 `.dmg` 文件
2. 打开 DMG 并将 OpenList Desktop 拖到应用程序文件夹
3. 右键单击并选择"打开"（仅首次）
4. 在提示时授予必要权限
-:::
-
-#### Linux { lang="en" }
-
-#### Linux { lang="zh-CN" }
-
-:::en
-
-1. Download the `.deb` or `.rpm` package
-2. Use your package manager to install:
-
- ```bash
- sudo dpkg -i OpenList-Desktop_x.x.x_amd64.deb
- # or
- sudo rpm -i OpenList-Desktop_x.x.x_amd64.rpm
- ```
-
-:::
-
-:::zh-CN
+#### Linux
1. 下载 `.deb` 或 `.rpm` 包
2. 使用包管理器安装：
@@ -266,27 +100,9 @@ winget install OpenListTeam.OpenListDesktop
sudo rpm -i OpenList-Desktop_x.x.x_amd64.rpm
```
-:::
-
-## Usage { lang="en" }
-
-## 使用说明 { lang="zh-CN" }
-
-### First Launch { lang="en" }
-
-### 首次启动 { lang="zh-CN" }
+## 使用说明
-:::en
-
-It is recommended to run OpenList Desktop with Administrator privileges on first launch to ensure proper service installation and configuration.
-
-1. **Initial Setup**: On first launch, the application will guide you through initial configuration
-2. **Service Installation**: Install the OpenList service when prompted
-3. **Storage Configuration**: Configure your first cloud storage connection
-
-:::
-
-:::zh-CN
+### 首次启动
建议在首次启动时通过管理员权限运行 OpenList Desktop，以确保正确安装和配置服务。
@@ -294,53 +110,16 @@ It is recommended to run OpenList Desktop with Administrator privileges on first
2. **服务安装**：在提示时安装 OpenList 服务
3. **存储配置**：配置您的第一个云存储连接
-:::
-
-### Basic Operations { lang="en" }
+### 基本操作
-### 基本操作 { lang="zh-CN" }
-
-#### Starting Services { lang="en" }
-
-#### 启动服务 { lang="zh-CN" }
-
-:::en
-
-```bash
-Dashboard → Quick Actions → Start OpenList Core
-Dashboard → Quick Actions → Start Rclone Backend
-```
-
-:::
-
-:::zh-CN
+#### 启动服务
```bash
仪表板 → 快速操作 → 启动 OpenList 核心
仪表板 → 快速操作 → 启动 Rclone 后端
```
-:::
-
-#### Adding Cloud Storage { lang="en" }
-
-#### 添加云存储 { lang="zh-CN" }
-
-:::en
-
-1. Navigate to **Mount** tab
-2. Click **Add Remote** button
-3. Configure storage settings:
- - **Name**: Unique identifier for your storage
- - **Type**: Storage provider (WebDAV)
- - **URL**: Storage endpoint URL
- - **Credentials**: Username and password
- - **Mount Point**: Local directory path
-4. Click **Save** and **Mount**
-
-:::
-
-:::zh-CN
+#### 添加云存储
1. 导航到 **挂载** 选项卡
2. 点击 **添加远程** 按钮
@@ -352,70 +131,15 @@ Dashboard → Quick Actions → Start Rclone Backend
- **挂载点**：本地目录路径
4. 点击 **保存** 和 **挂载**
-:::
-
-#### Monitoring Operations { lang="en" }
-
-#### 监控操作 { lang="zh-CN" }
-
-:::en
-
-- **Service Status**: Check the dashboard for service health indicators
-- **Logs**: Use the Logs tab to monitor system operations
-- **Performance**: View uptime and response metrics on the dashboard
-
-:::
-
-:::zh-CN
+#### 监控操作
- **服务状态**：检查仪表板上的服务健康指示器
- **日志**：使用日志选项卡监控系统操作
- **性能**：在仪表板上查看运行时间和响应指标
-:::
+## 本地开发
-## Local Development { lang="en" }
-
-## 本地开发 { lang="zh-CN" }
-
-### Prerequisites { lang="en" }
-
-### 环境要求 { lang="zh-CN" }
-
-:::en
-
-- **Node.js**: v22+ with yarn
-- **Rust**: Latest nightly version
-- **Git**: Version control
-
-1. **Clone the repository**
-
- ```bash
- git clone https://github.com/OpenListTeam/OpenList-Desktop.git
- cd openlist-desktop
- ```
-
-2. **Install dependencies**
-
- ```bash
- yarn install
- ```
-
-3. **Prepare development environment**
-
- ```bash
- yarn run prebuild:dev
- ```
-
-4. **Start development server**
-
- ```bash
- yarn tauri dev
- ```
-
-:::
-
-:::zh-CN
+### 环境要求
- **Node.js**：v22+ 和 yarn
- **Rust**：最新 nightly 版本
@@ -446,23 +170,7 @@ Dashboard → Quick Actions → Start Rclone Backend
yarn tauri dev
```
-:::
-
-### Building { lang="en" }
-
-### 构建 { lang="zh-CN" }
-
-:::en
-
-```bash
-# Build the application
-yarn run build
-yarn run tauri build
-```
-
-:::
-
-:::zh-CN
+### 构建
```bash
# 构建应用程序
@@ -470,31 +178,10 @@ yarn run build
yarn run tauri build
```
-:::
+## 许可证与法律
-## License & Legal { lang="en" }
+### 许可证
-## 许可证与法律 { lang="zh-CN" }
-
-### License { lang="en" }
-
-### 许可证 { lang="zh-CN" }
-
-:::en
-This desktop application project is licensed under the **[GNU General Public License v3.0 (GPL-3.0)](https://www.gnu.org/licenses/gpl-3.0.en.html)**.
-
-- **Freedom to Use**: You can use, modify, and distribute this application
-- **Copyleft**: Any derivative works must also be licensed under GPL-3.0
-- **Source Code**: You must provide source code when distributing the application
-- **Attribution**: You must preserve copyright notices and license information
-
-For the full license text, see the [LICENSE](https://github.com/OpenListTeam/OpenList-Desktop/blob/main/LICENSE) file.
-
-By contributing to this project, you agree that your contributions will be licensed under the same GPL-3.0 license.
-
-:::
-
-:::zh-CN
本桌面应用程序项目采用 **[GNU General Public License v3.0 (GPL-3.0)](https://www.gnu.org/licenses/gpl-3.0.en.html)** 许可证。
- **使用自由**：您可以使用、修改和分发此应用程序
@@ -505,5 +192,3 @@ By contributing to this project, you agree that your contributions will be licen
完整的许可证文本请参见 [LICENSE](https://github.com/OpenListTeam/OpenList-Desktop/blob/main/LICENSE) 文件。
通过为本项目做出贡献，您同意您的贡献将采用相同的 GPL-3.0 许可证。
-
-:::
diff --git a/pages/ecosystem/official_docs.md b/pages/ecosystem/official_docs.md
index a8cf7d714..9fdb3c5d2 100644
--- a/pages/ecosystem/official_docs.md
+++ b/pages/ecosystem/official_docs.md
@@ -1,101 +1,28 @@
---
-title:
- en: OpenList Docs
- zh-CN: OpenList Docs
categories:
- ecosystem
- eco_official
top: 990
---
-## What is OpenList Docs { lang="en" }
+# OpenList Docs
-## OpenList Docs 是什么 { lang="zh-CN" }
+## OpenList Docs 是什么
### [OpenListTeam/OpenList-Docs](https://github.com/OpenListTeam/OpenList-Docs)
-:::en
-[OpenListTeam/OpenList-Docs](https://github.com/OpenListTeam/OpenList-Docs) is the official documentation website for OpenList, led by [@cxw620](https://github.com/cxw620) and collaboratively developed with other [main contributors](https://github.com/OpenListTeam/OpenList-Docs/graphs/contributors). Built with Valaxy framework, it provides comprehensive documentation for OpenList, including installation guides, configuration instructions, API references, and ecosystem information. The documentation supports multiple languages and features real-time builds from the GitHub repository.
+[OpenListTeam/OpenList-Docs](https://github.com/OpenListTeam/OpenList-Docs) 是 OpenList 的官方文档网站，由 [@cxw620](https://github.com/cxw620) 牵头，和其他[主要贡献者](https://github.com/OpenListTeam/OpenList-Docs/graphs/contributors)共同协作完成。基于 VitePress 构建，为 OpenList 提供全面的文档，包括安装指南、配置说明、API 参考和生态系统信息。文档支持多种语言，并基于 GitHub 仓库实时构建。
-:::
+## 如何使用 OpenList Docs
-:::zh-CN
-[OpenListTeam/OpenList-Docs](https://github.com/OpenListTeam/OpenList-Docs) 是 OpenList 的官方文档网站，由 [@cxw620](https://github.com/cxw620) 牵头，和其他[主要贡献者](https://github.com/OpenListTeam/OpenList-Docs/graphs/contributors)共同协作完成。基于 Valaxy 框架构建，为 OpenList 提供全面的文档，包括安装指南、配置说明、API 参考和生态系统信息。文档支持多种语言，并基于 GitHub 仓库实时构建。
-
-:::
-
-## How to use OpenList Docs { lang="en" }
-
-## 如何使用 OpenList Docs { lang="zh-CN" }
-
-:::en
-You can directly access [doc.oplist.org.cn](https://doc.oplist.org.cn/) to view the documentation.
-
-:::
-
-:::zh-CN
可直接在线访问[doc.oplist.org.cn](https://doc.oplist.org.cn/) 查阅文档。
-:::
-
-## Local Development { lang="en" }
-
-### Prerequisites { lang="en" }
-
-:::en
-
-- **Node.js**: Required for running the development environment
-- **pnpm**: Recommended package manager
-- **Git**: For version control and cloning the repository
-
-1. **Clone the repository**
+## 本地开发
- ```bash
- git clone https://github.com/OpenListTeam/OpenList-Docs.git
- cd OpenList-Docs
- ```
-
-2. **Install dependencies**
+### 环境要求
- ```bash
- pnpm install
- ```
-
-3. **Start development server**
-
- ```bash
- pnpm dev
- ```
-
-4. **Open in browser**
-
- The documentation site will be available at `http://localhost:4859`
-
-:::
-
-### Building { lang="en" }
-
-:::en
-In Windows, you may need to run `npm install -g win-node-env` to solve the `NODE_OPTIONS` environment variable problem.
-
-```bash
-# Build static site
-pnpm build
-
-# Preview build
-pnpm serve
-```
-
-:::
-
-## 本地开发 { lang="zh-CN" }
-
-### 环境要求 { lang="zh-CN" }
-
-:::zh-CN
-
-- **Node.js**：运行开发环境所需
-- **pnpm**：推荐的包管理器
+- **Node.js** 24 或更高版本（见 `.nvmrc`）
+- **pnpm**：包管理器
- **Git**：用于版本控制和克隆仓库
1. **克隆仓库**
@@ -119,156 +46,60 @@ pnpm serve
4. **在浏览器中打开**
- 文档站点将在 `http://localhost:4859` 处可用
-
-:::
-
-### 构建 { lang="zh-CN" }
+ 文档站点将在 `http://localhost:5173` 可用
-:::zh-CN
-在Windows操作系统下，可能需要运行`npm install -g win-node-env`解决`NODE_OPTIONS`环境变量问题。
+### 构建
```bash
-# 构建静态站点
+# 构建静态站点到 dist/
pnpm build
-# 预览构建
-pnpm serve
+# 预览构建结果
+pnpm preview
```
-:::
-
-### Development Tips { lang="en" }
-
-:::en
-`:::tip` Markdown Parsing Issues
-When writing documentation, please note these important parsing rules:
+### 编写提示
-1. **Language Block Syntax**: For language-specific content blocks, only use one closing `:::` at the end:
+本站使用 [VitePress](https://vitepress.dev/zh/) 构建，其 [Markdown 扩展](https://vitepress.dev/zh/guide/markdown) 均可直接使用。
- 
- 
+1. **每种语言一个文件**：中文页面位于 `pages/`，英文页面位于 `pages/en/` 下相同的相对路径，例如 `pages/guide/drivers/s3.md` 与 `pages/en/guide/drivers/s3.md`。修改页面时请同时更新两个文件。
- The above should be written as:
+2. **页面标题**：正文第一行即为标题，使用一级标题（`# 标题`），不要在 frontmatter 中添加 `title`。
- 
- 
+3. **侧边栏**：frontmatter 中设置了 `categories` 的页面会显示在侧边栏，并按 `top` 由高到低排序：
- The language will automatically switch when encountering `:::en`.
+ ```md
+ ---
+ top: 895
+ categories:
+ - guide
+ - drivers
+ ---
-2. **Title Language Specification**: Titles must use `{ lang="en" }` syntax and cannot use language blocks:
-
- 
- 
-
- Do NOT use:
-
- 
- 
-
-3. **Text Format Convention**: For better readability in plain text environments, please follow the **English first, then Chinese** order when writing bilingual content. This makes it easier to observe and navigate the documentation structure in text editors and version control systems.
-
-4. **Line Break Before Closing `:::`**: Always add a line break before the closing `:::`, especially when using lists (`li`), otherwise formatting may be corrupted:
-
- 
- 
-
- The above should be written as:
-
- 
- 
-
-5. **Empty Line for Line Breaks**: Content needs an empty line to create line breaks. Without empty lines, content will render as continuous text:
-
- 
- 
-
- The above should be written as:
-
- 
- 
-
- Note: Lists (`li`) are not affected by this issue.
-
-:::
-
-### 开发提示 { lang="zh-CN" }
-
-:::zh-CN
-`:::tip` Markdown 解析问题
-在编写文档时，请注意以下重要的解析规则：
-
-1. **语言块语法**：对于特定语言的内容块，结尾只需要一个 `:::`：
-
- 
- 
-
- 上面的写法应该改为：
-
- 
- 
-
- 当遇到 `:::en` 时语言会自动切换。
-
-2. **标题语言指定**：标题必须使用 `{ lang="en" }` 语法，不能使用语言块：
-
- 
- 
-
- 不要使用：
-
- 
- 
-
-3. **文本格式约定**：为了方便在纯文本环境下的观察起见，在编写双语内容时请遵循**先英文后中文**的顺序。这样可以更容易在文本编辑器和版本控制系统中观察和导航文档结构。
-
-4. **结束块 `:::` 前换行**：结束块的 `:::` 前最好换行，尤其是使用了列表（`li`），否则会被格式化乱掉：
-
- 
- 
-
- 上面的写法应该改为：
-
- 
- 
-
-5. **内容换行需要空行**：内容需要空一行才能换行。没有空行的话，内容会渲染成连续的文本：
-
- 
- 
-
- 上面的写法应该改为：
-
- 
- 
-
- 注意：列表（`li`）不涉及这个问题。
-
-:::
-
-## License & Legal { lang="en" }
-
-### License { lang="en" }
-
-:::en
-This documentation project is licensed under the **[GNU Affero General Public License v3.0 (AGPL-3.0)](https://www.gnu.org/licenses/agpl-3.0.en.html)**.
+ # 对象存储（S3）
+ ```
-- **Freedom to Use**: You can use, modify, and distribute this documentation
-- **Copyleft**: Any derivative works must also be licensed under AGPL-3.0
-- **Network Use**: If you run a modified version on a server, you must provide the source code
-- **Attribution**: You must preserve copyright notices and license information
+4. **嵌套容器**：当 `::: tip` 等容器内还包含其他容器时，外层需要使用更多的冒号，否则第一个 `:::` 会直接关闭外层容器：
-For the full license text, see the [LICENSE](https://github.com/OpenListTeam/OpenList-Docs/blob/main/LICENSE) file.
+ ```md
+ :::: details 示例
+ ::: tip
+ 内层提示
+ :::
+ ::::
+ ```
-By contributing to this project, you agree that your contributions will be licensed under the same AGPL-3.0 license.
+5. **浅色 / 深色图片**：在图片链接后添加 `#light` / `#dark`，图片只会在对应的颜色模式下显示：
-:::
+ ```md
+ 
+ 
+ ```
-## 许可证与法律 { lang="zh-CN" }
+## 许可证与法律
-### 许可证 { lang="zh-CN" }
+### 许可证
-:::zh-CN
本文档项目采用 **[GNU Affero General Public License v3.0 (AGPL-3.0)](https://www.gnu.org/licenses/agpl-3.0.en.html)** 许可证。
- **使用自由**：您可以使用、修改和分发此文档
@@ -279,5 +110,3 @@ By contributing to this project, you agree that your contributions will be licen
完整的许可证文本请参见 [LICENSE](https://github.com/OpenListTeam/OpenList-Docs/blob/main/LICENSE) 文件。
通过为本项目做出贡献，您同意您的贡献将采用相同的 AGPL-3.0 许可证。
-
-:::
diff --git a/pages/ecosystem/official_mobile.md b/pages/ecosystem/official_mobile.md
index 1af52ea50..b5447819d 100644
--- a/pages/ecosystem/official_mobile.md
+++ b/pages/ecosystem/official_mobile.md
@@ -1,44 +1,19 @@
---
-title:
- en: OpenList Mobile
- zh-CN: OpenList Mobile
categories:
- ecosystem
- eco_official
top: 975
---
-## What is OpenList Mobile { lang="en" }
+# OpenList Mobile
-## OpenList Mobile 是什么 { lang="zh-CN" }
+## OpenList Mobile 是什么
### [OpenListTeam/OpenList-Mobile](https://github.com/OpenListTeam/OpenList-Mobile)
-:::en
-[OpenListTeam/OpenList-Mobile](https://github.com/OpenListTeam/OpenList-Mobile) is a mobile file server application based on [OpenList](https://github.com/OpenListTeam/OpenList), built with Flutter framework. It turns your phone into a powerful file server with LAN file sharing, remote access, and online management capabilities. The application is collaboratively developed by the [main contributors](https://github.com/OpenListTeam/OpenList-Mobile/graphs/contributors) and features automatic updates that sync with the latest OpenList releases daily.
-
-:::
-
-:::zh-CN
[OpenListTeam/OpenList-Mobile](https://github.com/OpenListTeam/OpenList-Mobile) 是一个基于 [OpenList](https://github.com/OpenListTeam/OpenList) 的移动端文件服务器应用，使用 Flutter 框架开发。它可以将您的手机变成一个强大的文件服务器，支持局域网文件共享、远程访问和在线管理功能。该应用由[主要贡献者](https://github.com/OpenListTeam/OpenList-Mobile/graphs/contributors)共同协作开发，具有自动更新功能，每日与最新的 OpenList 版本同步。
-:::
-
-## Features { lang="en" }
-
-## 功能特性 { lang="zh-CN" }
-
-:::en
-
-- **Mobile File Server**: Turn your mobile device into a file server
-- **LAN File Sharing**: Share files within local network
-- **Remote Access**: Access your files with internet connection
-- **Online Management**: Web-based file management interface
-- **Auto-Update**: Automatically syncs with latest OpenList releases
-
-:::
-
-:::zh-CN
+## 功能特性
- **移动文件服务器**：将您的移动设备变成文件服务器
- **局域网文件共享**：在本地网络内共享文件
@@ -46,134 +21,42 @@ top: 975
- **在线管理**：基于 Web 的文件管理界面
- **自动更新**：自动与最新的 OpenList 版本同步
-:::
-
-## Installation { lang="en" }
-
-## 安装 { lang="zh-CN" }
-
-### System Requirements { lang="en" }
-
-### 系统要求 { lang="zh-CN" }
-
-:::en
+## 安装
-- **Storage**: Minimum 100MB free space
-- **Permissions**: Storage access permission required
-
-:::
-
-:::zh-CN
+### 系统要求
- **存储空间**：至少 100MB 可用空间
- **权限**：需要存储访问权限
-:::
-
-### Download Options { lang="en" }
-
-### 下载选项 { lang="zh-CN" }
-
-#### GitHub Releases (Recommended) { lang="en" }
-
-#### GitHub 发行版（推荐） { lang="zh-CN" }
+### 下载选项
-:::en
-Download the latest release from [GitHub Releases](https://github.com/OpenListTeam/OpenList-Mobile/releases):
+#### GitHub 发行版（推荐）
-- **Stable Release**: [Latest Release](https://github.com/OpenListTeam/OpenList-Mobile/releases/latest) - Recommended for production use
-- **Development Build**: [Development Build](https://github.com/OpenListTeam/OpenList-Mobile/actions/workflows/build.yaml) - Latest features and fixes
-
-:::
-
-:::zh-CN
从 [GitHub Releases](https://github.com/OpenListTeam/OpenList-Mobile/releases) 下载最新版本：
- **稳定版本**：[发布版](https://github.com/OpenListTeam/OpenList-Mobile/releases/latest) - 推荐生产环境使用
- **开发版本**：[构建版](https://github.com/OpenListTeam/OpenList-Mobile/actions/workflows/build.yaml) - 最新功能和修复
-:::
-
-#### Auto-Update Feature { lang="en" }
-
-#### 自动更新功能 { lang="zh-CN" }
-
-:::en
-
-**Auto-Update**: [GitHub Actions](https://github.com/OpenListTeam/OpenList-Mobile/actions/workflows/sync_openlist.yaml) automatically checks for the latest [OpenList](https://github.com/OpenListTeam/OpenList/releases) version twice daily (5 AM & 5 PM) and builds releases, ensuring you always have access to the latest version.
-
-:::
-
-:::zh-CN
+#### 自动更新功能
**自动更新**：[GitHub Actions](https://github.com/OpenListTeam/OpenList-Mobile/actions/workflows/sync_openlist.yaml) 每日早晚五点自动检查最新的 [OpenList](https://github.com/OpenListTeam/OpenList/releases) 版本并构建发布，确保始终使用最新版本。
-:::
-
-### Installation Steps { lang="en" }
-
-### 安装步骤 { lang="zh-CN" }
-
-#### Android { lang="en" }
-
-#### Android { lang="zh-CN" }
+### 安装步骤
-:::en
-
-1. Download the `.apk` file from releases
-2. Enable "Install from unknown sources" in Android settings
-3. Install the APK file
-
-:::
-
-:::zh-CN
+#### Android
1. 从发布页面下载 `.apk` 文件
2. 在 Android 设置中启用"允许安装未知来源应用"
3. 安装 APK 文件
-:::
-
-#### iOS { lang="en" }
-
-#### iOS { lang="zh-CN" }
-
-:::en
-
-iOS support is currently experimental and still in development.
-
-:::
-
-:::zh-CN
+#### iOS
iOS 支持目前处于实验阶段，仍在开发中。
-:::
-
-## License & Legal { lang="en" }
-
-## 许可证与法律 { lang="zh-CN" }
-
-### License { lang="en" }
+## 许可证与法律
-### 许可证 { lang="zh-CN" }
+### 许可证
-:::en
-This mobile application project is licensed under the **[GNU Affero General Public License v3.0 (AGPL-3.0)](https://www.gnu.org/licenses/agpl-3.0.en.html)**.
-
-- **Freedom to Use**: You can use, modify, and distribute this application
-- **Copyleft**: Any derivative works must also be licensed under AGPL-3.0
-- **Network Use**: If you run a modified version on a server, you must provide source code to users
-- **Source Code**: You must provide source code when distributing the application
-- **Attribution**: You must preserve copyright notices and license information
-
-For the full license text, see the [LICENSE](https://github.com/OpenListTeam/OpenList-Mobile/blob/main/LICENSE) file.
-
-By contributing to this project, you agree that your contributions will be licensed under the same AGPL-3.0 license.
-
-:::
-
-:::zh-CN
本移动应用程序项目采用 **[GNU Affero General Public License v3.0 (AGPL-3.0)](https://www.gnu.org/licenses/agpl-3.0.en.html)** 许可证。
- **使用自由**：您可以使用、修改和分发此应用程序
@@ -185,5 +68,3 @@ By contributing to this project, you agree that your contributions will be licen
完整的许可证文本请参见 [LICENSE](https://github.com/OpenListTeam/OpenList-Mobile/blob/main/LICENSE) 文件。
通过为本项目做出贡献，您同意您的贡献将采用相同的 AGPL-3.0 许可证。
-
-:::
diff --git a/pages/ecosystem/official_proxy.md b/pages/ecosystem/official_proxy.md
index 509795787..c5098f46c 100644
--- a/pages/ecosystem/official_proxy.md
+++ b/pages/ecosystem/official_proxy.md
@@ -1,38 +1,18 @@
---
-title:
- en: OpenList Proxy
- zh-CN: OpenList Proxy
categories:
- ecosystem
- eco_official
top: 960
---
-## What is OpenList Proxy { lang="en" }
+# OpenList Proxy
-## OpenList Proxy 是什么 { lang="zh-CN" }
+## OpenList Proxy 是什么
-:::en
-[**OpenList Proxy**](https://github.com/OpenListTeam/OpenList-Proxy) is a simple implementation for proxying OpenList's **download traffic**. With this tool, you can isolate the server traffic of the OpenList deployment from the traffic required for downloads, thereby reducing the traffic consumption of the main server or speeding up downloads.
-
-:::
-:::zh-CN
[**OpenList Proxy**](https://github.com/OpenListTeam/OpenList-Proxy)，是一个用于代理OpenList的**下载流量**的简易实现，通过该工具，可以将部署OpenList的服务器流量和下载所需要的流量隔离开，从而降低对主服务器的流量消耗或加快下载速度。
-:::
-
-## How to use OpenList Proxy { lang="en" }
+## 如何使用 OpenList Proxy
-## 如何使用 OpenList Proxy { lang="zh-CN" }
-
-:::en
-:::danger
-Cloudflare has explicitly prohibited the use of Workers for proxy operations. Quick deployments implemented on CF-Worker should be used for **experimental** and **temporary testing** purposes only, and not for long-term or high-traffic.
-
-OpenList is not responsible for any consequences resulting from the use
-
-:::
-:::zh-CN
:::danger
CloudFlare已明确禁止使用Worker作为代理流量使用，对于在CF-Worker上实现的快速部署，应当时基于**实验性质**的**临时测试**，而非生产环境下使用长期、大流量使用。
@@ -40,33 +20,13 @@ OpenList对于使用该Worker造成的任何后果均不负责。
:::
-:::en
-For OpenList Proxy, we provide two deployment methods:
-
-- cf-worker
-- Binary File Deployment
-
-:::
-:::zh-CN
对于OpenList Proxy，我们提供了两种部署方式
- cf-worker
- 二进制文件部署
-:::
-
-### Cloudflare Worker { lang="en" }
+### ~~科赋锐~~Cloudflare Worker
-### ~~科赋锐~~Cloudflare Worker { lang="zh-CN" }
-
-:::en
-:::tip
-In the new version, environment-based configuration has been introduced. Please configure the environment variables as required after deployment.
-
-Do not use "/" at the end of the address.
-
-:::
-:::zh-CN
:::tip
在新版本中引入了基于环境的配置，请在部署完成后按照要求配置好环境变量。
@@ -74,35 +34,6 @@ Do not use "/" at the end of the address.
:::
-:::en
-
-- Simple Worker Deployment Tutorial On the Cloudflare homepage, select "Workers and Pages",
- then click "Create" and choose "Start from Hello World!".
- After deployment, select "Edit Code", go to here, replace the code, and click "Deploy" again.
-
-- (Optional) Configure Domain Go to the Worker configuration page, click "Settings", then click "Add" next to Domains and Routes. Enter the configured subdomain. Use a CNAME record for the corresponding subdomain to point to the workers.dev domain.
-
-- Configure Environment Variables Go to the Worker configuration page,
- click "Settings", then select "Add" next to Variables and Secrets.
- Copy the following into the variable names:
-
- ```env
- ADDRESS=https://your-openlist-server.com
- TOKEN=your-api-token-here
- WORKER_ADDRESS=https://your-worker-address
- DISABLE_SIGN=false
- ```
-
-- ADDRESS is the address of your OpenList instance, only ports 443 and 80 are supported.
- WORKER_ADDRESS is the address of the Worker. If you have bound a custom domain, use the custom domain. This is also the proxy address needed in OpenList.
- If DISABLE_SIGN is set to true, Proxy will not verify signatures, and anyone who knows the file path and Proxy address can access the file. Please use with caution.
- It is recommended to set TOKEN as a secret type. In OpenList, go to Settings → Others at the bottom; this token is long-term valid and has full permissions for OpenList.
-
-- CDN Configuration Suggestion: Keep ADDRESS and WORKER_ADDRESS configured as the origin addresses.
-
-:::
-:::zh-CN
-
- 部署worker简易教程
在Cloudflare的主页选择“Workers 和 Pages”，然后点击“创建”，选择“从Hello World！开始”
部署完成后选择“编辑代码”，进入[这里](https://github.com/OpenListTeam/OpenList-Proxy/blob/main/openlist-proxy.js)，将代码替换后再次点击“部署”。
@@ -130,49 +61,12 @@ Do not use "/" at the end of the address.
- 对于CDN的配置建议：`ADDRESS`、`WORKER_ADDRESS`配置保留为源站地址。
-:::
-
-### Binary File Deployment { lang="en" }
-
-### 二进制文件部署 { lang="zh-CN" }
-
-:::en
+### 二进制文件部署
-Download the [binary package](https://github.com/OpenListTeam/OpenList-Proxy/releases) and run the command `./openlist-proxy -help` to learn how to use it.
-:::
-:::zh-CN
下载[二进制包](https://github.com/OpenListTeam/OpenList-Proxy/releases)后，使用`./openlist-proxy -help`命令自行学习使用。
-:::
-
-## How OpenList Proxy Works { lang="en" }
-
-## OpenList Proxy 的工作原理 { lang="zh-CN" }
+## OpenList Proxy 的工作原理
-:::en
-OpenList Proxy works by proxying the OpenList API to isolate the download traffic of OpenList. Its working principle is as follows:
-
-```mermaid
-sequenceDiagram
- participant Client as Client
- participant Proxy as Cloudflare Worker
- participant OpenList as OpenList Server
- participant Storage as File Storage
-
- Client->>Proxy: Download Request (with signature)
- Proxy->>Proxy: Verify signature and expiration time
- Proxy->>OpenList: Request file link (/api/fs/link)
- OpenList-->>Proxy: Return real download address
- Proxy->>Storage: Request file content
- Storage-->>Proxy: Return file stream
- Proxy-->>Client: Forward file content
-```
-
-Proxy verifies the signature and expiration time to ensure the legitimacy of the request. It then requests the file link from the OpenList server to obtain the real download address. After that, Proxy requests the file storage service for the file content and forwards it to the client.
-
-Proxy's signature can be disabled by setting the `DISABLE_SIGN` environment variable or flag. If signature verification is disabled, Proxy will not check the signature and expiration time, allowing anyone who knows the file path and Proxy address to bypass OpenList's own signature verification (which can be configured in the management interface) to access the file. Please use this feature with caution.
-:::
-:::zh-CN
OpenList Proxy 通过对 OpenList 的 API 进行代理，来实现对 OpenList 的下载流量的隔离。其工作原理如下：
```mermaid
@@ -194,4 +88,3 @@ sequenceDiagram
Proxy 通过验证签名和过期时间，确保请求的合法性。然后，它向 OpenList 服务器请求文件链接，并获取真实的下载地址。接着，Proxy 请求文件存储服务获取文件内容，并将其转发给客户端。
Proxy的签名可以通过`DISABLE_SIGN`环境变量或flag来禁用，如果禁用签名，Proxy将不会验证签名和过期时间，这样任何人都可以通过知道文件路径和Proxy地址来绕过OpenList本身的签名验证（其本身的签名可以在管理界面配置）获取文件。请谨慎开启此功能。
-:::
diff --git a/pages/ecosystem/official_worker/about.md b/pages/ecosystem/official_worker/about.md
index 3ff06fb42..300138743 100644
--- a/pages/ecosystem/official_worker/about.md
+++ b/pages/ecosystem/official_worker/about.md
@@ -1,63 +1,26 @@
---
-title:
- en: FAQ
- zh-CN: 常见问题
categories:
- ecosystem
- eco_worker
top: 971
---
-## FAQ { lang="en" }
+# 常见问题
-## 常见问题 { lang="zh-CN" }
-
-:::en
-
-### The install wizard doesn't appear on first visit
-
-Make sure `ADMIN_PASS` is **not** set — when it is set, the worker auto-initializes and skips the wizard. Clear the variable and redeploy, then revisit the site.
-:::
-
-:::zh-CN
+## 常见问题
### 首次访问没有出现安装向导
确认 `ADMIN_PASS` **未配置**——配置后 Worker 会自动初始化并跳过向导。清除该变量后重新部署，再次访问即可进入向导。
-:::
---
-:::en
-
-### Cloudflare reports "unable to fetch repository content"
-
-You are trying to deploy directly from the upstream `OpenListTeam/OpenList-Worker` repository. Cloudflare Workers only allows deploying from repositories you own. [Fork](https://github.com/OpenListTeam/OpenList-Worker/fork) the project first, then connect your fork.
-:::
-
-:::zh-CN
-
### Cloudflare 提示"无法获取存储库内容"
你正在尝试直接从上游 `OpenListTeam/OpenList-Worker` 仓库部署。Cloudflare Workers 只允许部署你自己拥有的仓库。请先 [Fork](https://github.com/OpenListTeam/OpenList-Worker/fork) 项目，再连接你的 Fork 仓库。
-:::
-
---
-:::en
-
-### Settings are lost after redeployment / page refresh
-
-This usually means no persistent storage is configured. Check:
-
-1. `DB_DRIVER` is set (not `memory`)
-2. The corresponding binding (KV / D1 / Blob) is correctly bound in the platform dashboard
-3. For EdgeOne, the default `auto` driver should auto-detect Blob — if not, explicitly set `DB_DRIVER=blob`
- :::
-
-:::zh-CN
-
### 重新部署 / 刷新页面后设置丢失
通常意味着没有配置持久化存储。检查：
@@ -65,24 +28,9 @@ This usually means no persistent storage is configured. Check:
1. `DB_DRIVER` 已设置（不是 `memory`）
2. 对应绑定（KV / D1 / Blob）已在平台后台正确绑定
3. EdgeOne 默认的 `auto` 驱动应能自动探测 Blob——若不行，请显式设置 `DB_DRIVER=blob`
- :::
---
-:::en
-
-### How do I reset the admin password?
-
-If you can still log in, go to **Management → Users** to change the password.
-
-If you are locked out:
-
-1. Set the `ADMIN_PASS` environment variable to a new password and redeploy.
-2. After logging in, remove the variable and redeploy again to re-enable the install wizard on next cold start (or leave it set as a permanent password).
- :::
-
-:::zh-CN
-
### 如何重置管理员密码？
如果你还能登录，前往 **管理 → 用户** 修改密码即可。
@@ -91,24 +39,9 @@ If you are locked out:
1. 将 `ADMIN_PASS` 环境变量设为新密码并重新部署。
2. 登录后删除该变量再次部署，下次冷启动时将重新启用安装向导（或保留该变量作为永久密码）。
- :::
---
-:::en
-
-### CORS errors when accessing the API from a custom domain
-
-Add `ALLOW_URLS` as an environment variable with a comma-separated list of allowed origins, e.g.:
-
-```
-ALLOW_URLS=https://your-domain.com,https://www.your-domain.com
-```
-
-:::
-
-:::zh-CN
-
### 从自定义域名访问 API 时出现 CORS 错误
添加 `ALLOW_URLS` 环境变量，值为逗号分隔的允许来源列表，例如：
@@ -117,24 +50,8 @@ ALLOW_URLS=https://your-domain.com,https://www.your-domain.com
ALLOW_URLS=https://your-domain.com,https://www.your-domain.com
```
-:::
-
---
-:::en
-
-### `DB_FORMAT=sql` tables are not created automatically
-
-D1 tables are created via Drizzle migrations on first startup. Make sure:
-
-1. The D1 binding (`DB`) is correctly configured in `wrangler.toml` or the dashboard.
-2. After binding, trigger a cold start by redeploying.
-
-If using **Automatic resource provisioning**, omit `database_id` from the D1 binding and Wrangler (>= 4.45.0) will create the database automatically on deploy.
-:::
-
-:::zh-CN
-
### `DB_FORMAT=sql` 表未自动创建
D1 表通过 Drizzle 迁移在首次启动时创建。请确认：
@@ -143,23 +60,9 @@ D1 表通过 Drizzle 迁移在首次启动时创建。请确认：
2. 绑定后重新部署触发一次冷启动。
如果使用 **Automatic resource provisioning**，在 D1 绑定中省略 `database_id`，Wrangler（>= 4.45.0）会在部署时自动创建数据库。
-:::
---
-:::en
-
-### How do I migrate data from the Go backend to OpenList Worker?
-
-Use `DB_FORMAT=sql` + `DB_DRIVER=d1` (or `mysql`) with the fixed `x_` table prefix. The TS Worker and the Go backend share the same table schema, so you can:
-
-1. Export the Go backend's SQLite database.
-2. Import it into a Cloudflare D1 database via the Cloudflare dashboard or `wrangler d1 execute`.
-3. Configure the Worker to point to the same D1 database.
- :::
-
-:::zh-CN
-
### 如何将 Go 后端的数据迁移到 OpenList Worker？
使用固定的 `x_` 表名前缀，配合 `DB_FORMAT=sql` + `DB_DRIVER=d1`（或 `mysql`）。TS Worker 与 Go 后端共享相同的表 schema，因此：
@@ -167,42 +70,18 @@ Use `DB_FORMAT=sql` + `DB_DRIVER=d1` (or `mysql`) with the fixed `x_` table pref
1. 导出 Go 后端的 SQLite 数据库。
2. 通过 Cloudflare 控制台或 `wrangler d1 execute` 将其导入 Cloudflare D1 数据库。
3. 配置 Worker 指向同一个 D1 数据库即可。
- :::
---
-:::en
-
-### ESA EdgeKV settings revert after a few seconds
-
-This is caused by EdgeKV's eventual consistency. The Worker implements a module-level cache with a 60-second TTL to mitigate this. If the issue persists, wait ~60 seconds for the cache to expire and the setting to propagate across nodes.
-:::
-
-:::zh-CN
-
### 阿里云 ESA EdgeKV 设置几秒后回滚
这是 EdgeKV 最终一致性导致的。Worker 内置了 60 秒 TTL 的模块级缓存来缓解此问题。如果问题持续，等待约 60 秒让缓存过期、设置同步到各节点即可。
-:::
---
-:::en
-
-### Build fails with "pnpm: command not found"
-
-The deploy platform is using npm by default. Either:
-
-- Set the **install command** to `npm install --legacy-peer-deps` and **build command** to `npm run build`, or
-- Enable pnpm in the platform settings (e.g. Cloudflare Workers → Framework preset → set Node version to 18+)
- :::
-
-:::zh-CN
-
### 构建失败，提示 "pnpm: command not found"
部署平台默认使用 npm。可以：
- 将 **安装命令** 改为 `npm install --legacy-peer-deps`，**构建命令** 改为 `npm run build`，或者
- 在平台设置中启用 pnpm（例如 Cloudflare Workers → Framework preset → 设置 Node 版本为 18+）
- :::
diff --git a/pages/ecosystem/official_worker/basic.md b/pages/ecosystem/official_worker/basic.md
index 1b9f08d76..24a3a131e 100644
--- a/pages/ecosystem/official_worker/basic.md
+++ b/pages/ecosystem/official_worker/basic.md
@@ -1,125 +1,51 @@
---
-title:
- en: Architecture
- zh-CN: 设计架构
categories:
- ecosystem
- eco_worker
top: 978
---
-## Design Architecture { lang="en" }
+# 设计架构
-## 设计架构 { lang="zh-CN" }
+## 设计架构
-:::en
-OpenList Worker is a Serverless-first rewrite of the OpenList Go backend in TypeScript. The system is divided into three layers: edge runtime, data access, and frontend static assets.
-:::
-
-:::zh-CN
OpenList Worker 是将 OpenList Go 后端以 TypeScript 重写的 Serverless 优先架构。系统分为边缘运行时、数据访问和前端静态资源三层。
-:::
-
-## Tech Stack { lang="en" }
-
-## 技术栈 { lang="zh-CN" }
-
-### Backend { lang="en" }
-
-### 后端 { lang="zh-CN" }
-
-:::en
-| Component | Technology | Description |
-| :-------- | :--------- | :---------- |
-| HTTP framework | [Hono.js](https://hono.dev/) | Lightweight, edge-native web framework |
-| Runtime | Cloudflare Workers / EdgeOne Functions / ESA | Edge compute platforms |
-| Language | TypeScript | Fully typed, compiled via esbuild / Vite |
-| ORM | Drizzle ORM | Type-safe SQL query builder for D1 / MySQL |
-| Build tool | esbuild / Vite | Single-file Worker bundle |
-:::
-
-:::zh-CN
-| 组件 | 技术 | 说明 |
-| :--- | :--- | :--- |
-| HTTP 框架 | [Hono.js](https://hono.dev/) | 轻量级、边缘原生 Web 框架 |
-| 运行时 | Cloudflare Workers / EdgeOne 云函数 / ESA | 边缘计算平台 |
-| 语言 | TypeScript | 全类型，使用 esbuild / Vite 编译 |
-| ORM | Drizzle ORM | 为 D1 / MySQL 提供类型安全的 SQL 查询构建器 |
-| 构建工具 | esbuild / Vite | 单文件 Worker 产物 |
-:::
-
-### Frontend { lang="en" }
-
-### 前端 { lang="zh-CN" }
-
-:::en
-| Component | Technology | Description |
-| :-------- | :--------- | :---------- |
-| Framework | SolidJS + TypeScript | Reactive SPA frontend |
-| UI library | Hope UI (@hope-ui/solid) | Component library |
-| Build tool | Vite | Fast frontend build |
-| Bundled with | Workers Static Assets | Served from the same origin as the API |
-:::
-:::zh-CN
-| 组件 | 技术 | 说明 |
-| :--- | :--- | :--- |
-| 框架 | SolidJS + TypeScript | 响应式 SPA 前端 |
-| UI 库 | Hope UI（@hope-ui/solid） | 组件库 |
-| 构建工具 | Vite | 快速前端构建 |
-| 与 Worker 同源 | Workers Static Assets | API 与前端同源部署，无跨域问题 |
-:::
+## 技术栈
-## Data Storage { lang="en" }
+### 后端
-## 数据存储 { lang="zh-CN" }
+| 组件 | 技术 | 说明 |
+| :-------- | :---------------------------------------- | :------------------------------------------ |
+| HTTP 框架 | [Hono.js](https://hono.dev/) | 轻量级、边缘原生 Web 框架 |
+| 运行时 | Cloudflare Workers / EdgeOne 云函数 / ESA | 边缘计算平台 |
+| 语言 | TypeScript | 全类型，使用 esbuild / Vite 编译 |
+| ORM | Drizzle ORM | 为 D1 / MySQL 提供类型安全的 SQL 查询构建器 |
+| 构建工具 | esbuild / Vite | 单文件 Worker 产物 |
-### Storage Format (`DB_FORMAT`) { lang="en" }
+### 前端
-### 存储格式（`DB_FORMAT`） { lang="zh-CN" }
+| 组件 | 技术 | 说明 |
+| :------------- | :------------------------ | :----------------------------- |
+| 框架 | SolidJS + TypeScript | 响应式 SPA 前端 |
+| UI 库 | Hope UI（@hope-ui/solid） | 组件库 |
+| 构建工具 | Vite | 快速前端构建 |
+| 与 Worker 同源 | Workers Static Assets | API 与前端同源部署，无跨域问题 |
-:::en
-The `DB_FORMAT` variable controls how data is serialized:
+## 数据存储
-| Value | Description | Best for |
-| :-------------- | :---------------------------------------------------- | :-------------------------------------- |
-| `map` (default) | Whole object serialized as a single JSON value | KV / Blob storage |
-| `key` | Per-key storage, one record per entity | KV with high read frequency |
-| `sql` | Relational tables, identical schema to the Go backend | D1 / MySQL — enables Go ↔ TS migration |
+### 存储格式（`DB_FORMAT`）
-:::
-
-:::zh-CN
`DB_FORMAT` 控制数据序列化方式：
-| 值 | 说明 | 最适用场景 |
-| :------------ | :--------------------------------- | :----------------------------- |
-| `map`（默认） | 整对象序列化为单个 JSON 值 | KV / Blob 存储 |
-| `key` | 分 key 存储，每实体一条记录 | 高频读写 KV |
+| 值 | 说明 | 最适用场景 |
+| :------------ | :--------------------------------- | :---------------------------- |
+| `map`（默认） | 整对象序列化为单个 JSON 值 | KV / Blob 存储 |
+| `key` | 分 key 存储，每实体一条记录 | 高频读写 KV |
| `sql` | 关系表，与 Go 后端 schema 完全一致 | D1 / MySQL——支持 Go ↔ TS 迁移 |
-:::
-
-### Storage Driver (`DB_DRIVER`) { lang="en" }
-
-### 存储驱动（`DB_DRIVER`） { lang="zh-CN" }
-
-:::en
-The `DB_DRIVER` variable selects the physical storage backend:
-
-| Value | Platform | Description |
-| :--------------- | :----------------- | :------------------------------------------ |
-| `auto` (default) | Universal | Auto-detect: blob → cfkv → kv → d1 → memory |
-| `blob` | EdgeOne / ESA | EdgeOne Blob or Alibaba ESA Blob |
-| `cfkv` | Universal | Cloudflare KV via REST API (cross-platform) |
-| `kv` | Cloudflare Workers | Cloudflare KV binding |
-| `d1` | Cloudflare Workers | Cloudflare D1 (SQLite) |
-| `do` | Cloudflare Workers | Durable Objects (strong consistency) |
-| `mysql` | Node.js container | External MySQL / MariaDB |
+### 存储驱动（`DB_DRIVER`）
-:::
-
-:::zh-CN
`DB_DRIVER` 选择物理存储后端：
| 值 | 平台 | 说明 |
@@ -132,28 +58,8 @@ The `DB_DRIVER` variable selects the physical storage backend:
| `do` | Cloudflare Workers | Durable Objects（强一致性） |
| `mysql` | Node.js 容器 | 外部 MySQL / MariaDB |
-:::
-
-### SQL Table Alignment with Go Backend { lang="en" }
-
-### 与 Go 后端的 SQL 表对齐 { lang="zh-CN" }
-
-:::en
-When `DB_FORMAT = "sql"`, the TS Worker uses the same table names and schema as the Go backend (GORM, default prefix `x_`), so the two backends can share the same physical database:
+### 与 Go 后端的 SQL 表对齐
-| Go struct | Table name |
-| :------------ | :---------------- |
-| `SettingItem` | `x_setting_items` |
-| `SharingDB` | `x_sharing_dbs` |
-| `Storage` | `x_storages` |
-| `User` | `x_users` |
-| `Meta` | `x_metas` |
-| (TS only) | `x_plugins` |
-
-The prefix is fixed to `x_`, matching the Go backend default.
-:::
-
-:::zh-CN
当 `DB_FORMAT = "sql"` 时，TS Worker 使用与 Go 后端（GORM，默认前缀 `x_`）相同的表名与 schema，两个后端可共享同一物理数据库：
| Go 结构体 | 表名 |
@@ -166,35 +72,8 @@ The prefix is fixed to `x_`, matching the Go backend default.
| （仅 TS） | `x_plugins` |
表名前缀固定为 `x_`，与 Go 后端默认值一致。
-:::
-
-## Project Structure { lang="en" }
-
-## 项目结构 { lang="zh-CN" }
-:::en
-
-```
-OpenList-Worker/
-├── src/
-│ ├── backend/ # Hono.js Worker entry & backend logic
-│ │ ├── worker.ts # Cloudflare Workers entry
-│ │ ├── drivers/ # Storage driver implementations (kv / d1 / blob / mysql …)
-│ │ ├── server/ # Route registrations & middleware
-│ │ ├── pkg/ # Shared utilities & helpers
-│ │ └── internal/ # Core business logic (auth, storage, meta, …)
-│ └── frontend/ # Built-in frontend (SolidJS + Vite)
-├── dist/ # Build output (Worker bundle + frontend assets)
-├── esa-entry.ts # Alibaba Cloud ESA entry
-├── wrangler.toml # Cloudflare Workers configuration
-├── esa.jsonc # Alibaba Cloud ESA configuration
-├── edgeone.json # EdgeOne schedules configuration
-└── package.json
-```
-
-:::
-
-:::zh-CN
+## 项目结构
```
OpenList-Worker/
@@ -214,26 +93,11 @@ OpenList-Worker/
└── package.json
```
-:::
-
-## Supported Platforms { lang="en" }
-
-## 支持平台 { lang="zh-CN" }
-
-:::en
-| Platform | Entry | Persistence | Notes |
-| :------- | :---- | :---------- | :---- |
-| Cloudflare Workers | `worker.ts` | D1 / KV / DO | One-click deploy supported |
-| Tencent Cloud EdgeOne | `worker.ts` | Blob / KV | One-click deploy supported |
-| Alibaba Cloud ESA | `esa-entry.ts` | EdgeKV | Manual build & deploy |
-| Node.js container | `worker.ts` (with adapter) | MySQL | Self-hosted |
-:::
-
-:::zh-CN
-| 平台 | 入口 | 持久化 | 备注 |
-| :--- | :--- | :----- | :--- |
-| Cloudflare Workers | `worker.ts` | D1 / KV / DO | 支持一键部署 |
-| 腾讯云 EdgeOne | `worker.ts` | Blob / KV | 支持一键部署 |
-| 阿里云 ESA | `esa-entry.ts` | EdgeKV | 手动构建部署 |
-| Node.js 容器 | `worker.ts`（带适配层） | MySQL | 自托管 |
-:::
+## 支持平台
+
+| 平台 | 入口 | 持久化 | 备注 |
+| :----------------- | :---------------------- | :----------- | :----------- |
+| Cloudflare Workers | `worker.ts` | D1 / KV / DO | 支持一键部署 |
+| 腾讯云 EdgeOne | `worker.ts` | Blob / KV | 支持一键部署 |
+| 阿里云 ESA | `esa-entry.ts` | EdgeKV | 手动构建部署 |
+| Node.js 容器 | `worker.ts`（带适配层） | MySQL | 自托管 |
diff --git a/pages/ecosystem/official_worker/guide.md b/pages/ecosystem/official_worker/guide.md
index 154a09c95..d8db196a4 100644
--- a/pages/ecosystem/official_worker/guide.md
+++ b/pages/ecosystem/official_worker/guide.md
@@ -1,113 +1,38 @@
---
-title:
- en: Deployment
- zh-CN: 部署教程
categories:
- ecosystem
- eco_worker
top: 977
---
-## How to Deploy { lang="en" }
+# 部署教程
-## 部署方法 { lang="zh-CN" }
+## 部署方法
-:::: en
-For a detailed, step-by-step deployment guide (Cloudflare Workers / EdgeOne / ESA), see [OpenList Worker 部署指南](/guide/installation/worker).
-::::
-
-:::: zh-CN
详细的分步部署指南（Cloudflare Workers / EdgeOne / ESA）请参阅 [OpenList Worker 部署指南](/guide/installation/worker)。
-::::
-
-### One-click Deploy { lang="en" }
-### 一键部署 { lang="zh-CN" }
+### 一键部署
| EdgeOne 国际站 | EdgeOne 中国站 | Cloudflare Workers |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| [](https://edgeone.ai/pages/new?project-name=openlist-tsworker&repository-url=https://github.com/OpenListTeam/OpenList-Worker&install-command=pnpm%20install%20--no-frozen-lockfile&build-command=pnpm%20run%20build&output-directory=dist&env=JWT_SECRET) | [](https://console.cloud.tencent.com/edgeone/pages/new?project-name=openlist-tsworker&repository-url=https://github.com/OpenListTeam/OpenList-Worker&install-command=pnpm%20install%20--no-frozen-lockfile&build-command=pnpm%20run%20build&output-directory=dist&env=JWT_SECRET) | [](https://deploy.workers.cloudflare.com/?url=https://github.com/OpenListTeam/OpenList-Worker) |
-:::: en
-
-> **Note**: If Cloudflare reports "unable to fetch repository content", [Fork](https://github.com/OpenListTeam/OpenList-Worker/fork) the project first, then deploy via the GitHub repository connection.
-> ::::
-
-:::: zh-CN
-
> **注意**：若 Cloudflare 提示"无法获取存储库内容"，请先 [Fork](https://github.com/OpenListTeam/OpenList-Worker/fork) 本项目，再通过连接到 GitHub 仓库功能部署。
-> ::::
-:::: en
-For platform-specific step-by-step guides, see:
-
-- [Cloudflare Workers](./guide_cfw)
-- [Tencent Cloud EdgeOne](./guide_eom)
-- [Alibaba Cloud ESA](./guide_esa)
- ::::
-
-:::: zh-CN
各平台的分步部署教程，请参阅：
- [Cloudflare Workers](./guide_cfw)
- [腾讯云 EdgeOne](./guide_eom)
- [阿里云 ESA](./guide_esa)
- ::::
-
-### Initialization { lang="en" }
-### 部署后初始化 { lang="zh-CN" }
+### 部署后初始化
-:::: en
-::: tip
-After deployment, the first visit to the site automatically enters an **install wizard**. Set the admin account and password in the browser to complete initialization — no pre-configured `ADMIN_PASS` is required.
-:::
-::::
-
-:::: zh-CN
::: tip
部署完成后，首次访问站点会自动进入**安装向导**，在浏览器中设置管理员账号与密码即可完成初始化，无需预先配置 `ADMIN_PASS`。
:::
-::::
-
-### Local Development { lang="en" }
-
-### 本地开发 { lang="zh-CN" }
-
-:::: en
-**Prerequisites**
-
-- Node.js 18+ (pnpm recommended)
-- A Cloudflare account (for deploying to Workers)
-
-**Local development**
-```bash
-# 1. Install dependencies
-pnpm install
-
-# 2. Configure wrangler.toml (fill in JWT_SECRET, KV/D1 bindings)
-
-# 3. Start the dev server (auto fetch the official frontend and run the Worker)
-pnpm run dev:unified
-
-# or run the Worker only (frontend built separately)
-pnpm run dev:worker
-```
-
-**Production deploy**
+### 本地开发
-```bash
-# One-click deploy: ensure KV namespace exists → fetch official frontend → deploy to Cloudflare Workers
-pnpm run deploy
-
-# or deploy the Worker directly (skip KV check and frontend build)
-pnpm run deploy:worker
-```
-
-::::
-
-:::: zh-CN
**前置要求**
- Node.js 18+（推荐使用 pnpm）
@@ -137,5 +62,3 @@ pnpm run deploy
# 或直接部署 Worker（跳过 KV 检查与前端构建）
pnpm run deploy:worker
```
-
-::::
diff --git a/pages/ecosystem/official_worker/guide_cfw.md b/pages/ecosystem/official_worker/guide_cfw.md
index 0f4a9b76d..98687c571 100644
--- a/pages/ecosystem/official_worker/guide_cfw.md
+++ b/pages/ecosystem/official_worker/guide_cfw.md
@@ -1,117 +1,13 @@
---
-title:
- en: Deploy to Cloudflare Workers
- zh-CN: 部署教程 - Cloudflare Workers
categories:
- ecosystem
- eco_worker
top: 967
---
-## Deploy to Cloudflare Workers { lang="en" }
+# 部署教程 - Cloudflare Workers
-## 部署到 Cloudflare Workers { lang="zh-CN" }
-
-:::: en
-
-### Prerequisites
-
-- A [Cloudflare](https://dash.cloudflare.com/) account
-- A [GitHub](https://github.com/) account (for connecting the repository)
-- Node.js 18+ and pnpm (only required for local / Wrangler deploy)
-
-### Deploy methods
-
-You have two options to deploy to Cloudflare Workers:
-
-1. **One-click deploy** — click the **Deploy to Cloudflare Workers** button above.
-2. **Manual create via GitHub** — follow the steps below.
-
-### Step 1: Create an application & connect GitHub
-
-Open the Cloudflare Workers dashboard, click **Create application** in the top-right, and choose **Connect to GitHub**. Cloudflare will prompt you to authorize access to your GitHub account — click **Authorize** and select the account (or organization) that contains your fork.
-
-
-
-### Step 2: Select the repository
-
-Fork this project to your own GitHub account first, then select your forked Worker repository when creating the application.
-
-::: tip
-If you deploy directly using the upstream `OpenListTeam/OpenList-Worker` repository and Cloudflare reports "unable to fetch repository content", fork the project first and select your fork instead.
-:::
-
-
-
-### Step 3: Create the application
-
-Click **Create**. Keep the default build parameters and commands:
-
-- **Framework preset**: None / Workers
-- **Build command**: `pnpm run build`
-- **Deploy command**: `npx wrangler deploy`
-- **Production branch**: `main`
-
-Cloudflare will build the Worker and deploy it to a `*.workers.dev` subdomain.
-
-
-
-### Step 4: Configure environment variables
-
-Enter the Worker project you just created, open **Settings → Variables and secrets** (or **Runtime variables and secrets**), and add the environment variables.
-
-
-
-The required variables (`DB_FORMAT`, `DB_DRIVER`) and their optional combinations are described in the [Environment Variables](#environment-variables) section at the end of this page.
-
-### Step 5: Bind the storage binding
-
-If you selected KV or D1 as the driver, you need to bind the corresponding binding in **Settings → Bindings**:
-
-| Type | Variable name |
-| ---- | ------------- |
-| `d1` | `DB` |
-| `kv` | `KV` |
-| `do` | `DO` |
-
-
-
-::: tip Automatic D1 provisioning
-For D1, you can enable Cloudflare's **Automatic resource provisioning**: omit `database_id` in the D1 binding, and Wrangler (>= 4.45.0) auto-creates a D1 database with the same name and writes back the ID on deploy.
-:::
-
-### Step 6: Bind a custom domain
-
-Add your own domain in **Settings → Domains and Routes**, then create a CNAME record for the subdomain pointing to your `*.workers.dev` domain.
-
-
-
-### After deployment
-
-::: tip
-After deployment, the first visit to the site automatically enters an **install wizard**. Set the admin account and password in the browser to complete initialization — no pre-configured `ADMIN_PASS` is required.
-:::
-
-### Local / Wrangler deploy (alternative)
-
-If you prefer deploying via the command line:
-
-```bash
-# 1. Clone and install dependencies
-git clone https://github.com/OpenListTeam/OpenList-Worker.git
-cd OpenList-Worker
-pnpm install
-
-# 2. Configure wrangler.toml (JWT_SECRET, KV / D1 bindings)
-
-# 3. Deploy to Cloudflare Workers
-pnpm run deploy
-# or: pnpm run deploy:worker (skip frontend build)
-```
-
-::::
-
-:::: zh-CN
+## 部署到 Cloudflare Workers
### 前置要求
@@ -208,12 +104,4 @@ pnpm run deploy
# 或：pnpm run deploy:worker（跳过前端构建）
```
-::::
-
-::: en
-For a full list of environment variables and recommended configurations, see [Environment Variables](./guide_env).
-:::
-
-::: zh-CN
完整的环境变量说明与推荐配置组合，请参阅 [配置变量](./guide_env)。
-:::
diff --git a/pages/ecosystem/official_worker/guide_env.md b/pages/ecosystem/official_worker/guide_env.md
index 7e325379d..8371009b8 100644
--- a/pages/ecosystem/official_worker/guide_env.md
+++ b/pages/ecosystem/official_worker/guide_env.md
@@ -1,107 +1,13 @@
---
-title:
- en: Environment Variables
- zh-CN: 环境变量
categories:
- ecosystem
- eco_worker
top: 972
---
-## Environment Variables { lang="en" }
+# 环境变量
-## 配置变量 { lang="zh-CN" }
-
-:::en
-
-### Required variables
-
-The following parameters are required:
-
-| Parameter | Optional values | Description |
-| ----------- | ----------------------------------------------------------------- | ----------------------- |
-| `DB_FORMAT` | `map` (default) / `key` / `sql` | Data persistence format |
-| `DB_DRIVER` | `auto` (default) / `blob` / `cfkv` / `kv` / `d1` / `do` / `mysql` | Storage location |
-
-#### Security variables
-
-In addition to `DB_FORMAT` and `DB_DRIVER`, it is strongly recommended to configure the following security-related variables:
-
-| Variable | Required | Description |
-| ------------ | ----------- | ---------------------------------------------------------------------------------------------------------------------------- |
-| `JWT_SECRET` | Recommended | JWT signing key (≥16 chars), also used for data encryption and cron task auth. Auto-generated and persisted to KV when unset |
-| `ADMIN_PASS` | Optional | Skip the install wizard and auto-initialize the admin with this password |
-| `ALLOW_URLS` | Optional | Comma-separated CORS allowlist |
-
-#### Other optional variables
-
-| Variable | Default | Description |
-| ------------ | ---------- | ---------------------------------------------------------------- |
-| `MAX_UPLOAD` | `26214400` | Max size (bytes) for a whole upload (`/put`, `/form`) |
-| `MAX_UPPART` | `16777216` | Max size (bytes) per chunk in multipart upload |
-| `ASSET_URLS` | — | Frontend asset CDN base URL, supports the `$version` placeholder |
-| `ALLOW_SEED` | — | Allowlist of hosts permitted as seed-data sources |
-
-### Storage format differences
-
-| `DB_FORMAT` | Description |
-| ----------- | ---------------------------------------------------------------------------------------------------------------------------------- |
-| `map` | All data stored as a single JSON. Reads the whole object on every access — lower performance but best compatibility. |
-| `key` | Each record stored as a Key-Value pair, read on demand — decent compatibility and performance, but no indexing. |
-| `sql` | Data stored as SQL tables, fully identical to the Go backend. Supports indexing and full features, but multiple reads take longer. |
-
-### Storage driver differences
-
-| `DB_DRIVER` | Supported platform | Description |
-| ----------- | ------------------ | -------------------------------------------------------------------------- |
-| `auto` | Universal | Auto-detect, priority: blob → cfkv → kv → d1 → memory |
-| `blob` | EdgeOne / ESA | Persistence provided by EdgeOne or Alibaba ESA Blob, free |
-| `cfkv` | Universal | Cloudflare KV REST API, for remote access on platforms without persistence |
-| `kv` | CF / EO / ESA | KV database, fast and free |
-| `d1` | CF | D1 database, Cloudflare only |
-| `do` | CF | Durable Objects, Cloudflare only |
-| `mysql` | Universal | Connect to your own MySQL database |
-
-### Valid combinations
-
-| `DB_FORMAT` | `DB_DRIVER` | Description |
-| ----------- | ----------- | --------------------------------------------------------------------- |
-| `map` | `auto` | JSON storage, auto-selects blob / kv / d1 based on the platform |
-| `map` | `blob` | JSON storage via EdgeOne / ESA Blob (recommended for those platforms) |
-| `map` | `cfkv` | JSON storage via remote CF KV outside CF Workers |
-| `map` | `kv` | JSON storage via KV on CF Workers (recommended) |
-| `map` | `d1` | JSON storage via D1 on CF Workers (not recommended) |
-| `map` | `do` | JSON storage via DO on CF Workers (not recommended, may incur cost) |
-| `key` | `kv` | Key-Value storage via KV on CF Workers (recommended) |
-| `key` | `d1` | Key-Value storage via D1 on CF Workers (recommended) |
-| `key` | `mysql` | Key-Value storage via MySQL on CF Workers (not recommended) |
-| `sql` | `d1` | SQL-Table storage via D1 on CF Workers (recommended) |
-| `sql` | `mysql` | SQL-Table storage via MySQL |
-
-### Remote database configuration
-
-If you bound `cfkv`, set the following variables:
-
-| Variable | Description |
-| ------------ | ----------------------------------- |
-| `CF_ACCOUNT` | Cloudflare account ID |
-| `CF_KV_UUID` | Cloudflare KV namespace ID |
-| `CF_API_KEY` | Cloudflare API token with KV access |
-
-If you bound MySQL, set the following variables:
-
-| Variable | Description |
-| ------------ | ------------------------------------------------------------------------------------------------ |
-| `MYSQL_URL` | Connection string, e.g. `mysql://user:pass@host:3306/db`. When set, the fields below are ignored |
-| `MYSQL_HOST` | Database host |
-| `MYSQL_PORT` | Database port (`3306`) |
-| `MYSQL_USER` | Database user |
-| `MYSQL_PASS` | Database password |
-| `MYSQL_NAME` | Database name |
-
-:::
-
-:::zh-CN
+## 配置变量
### 必选变量
@@ -187,5 +93,3 @@ If you bound MySQL, set the following variables:
| `MYSQL_USER` | 数据库用户 |
| `MYSQL_PASS` | 数据库密码 |
| `MYSQL_NAME` | 数据库名称 |
-
-:::
diff --git a/pages/ecosystem/official_worker/guide_eom.md b/pages/ecosystem/official_worker/guide_eom.md
index 9c4d39fe5..ce328c37a 100644
--- a/pages/ecosystem/official_worker/guide_eom.md
+++ b/pages/ecosystem/official_worker/guide_eom.md
@@ -1,85 +1,13 @@
---
-title:
- en: Deploy to Tencent EdgeOne
- zh-CN: 部署教程 - Tencent EdgeOne
categories:
- ecosystem
- eco_worker
top: 966
---
-## Deploy to EdgeOne { lang="en" }
+# 部署教程 - Tencent EdgeOne
-## 部署到 EdgeOne { lang="zh-CN" }
-
-:::: en
-
-### Prerequisites
-
-- A [Tencent Cloud EdgeOne](https://console.edgeone.ai/makers) account
-- A GitHub account (for connecting the repository)
-
-### Step 1: Deploy the application
-
-Click the **EdgeOne** deploy button above and choose the international or China site:
-
-- [International console](https://console.edgeone.ai/makers)
-- [China console](https://console.cloud.tencent.com/edgeone/makers)
-
-### Step 2: Set environment variables
-
-Click **New application**, select the forked repository, configure the variables, then click **Start deployment**:
-
-
-
-Required variables (`DB_FORMAT`, `DB_DRIVER`) are described in the [Environment Variables](#environment-variables) section at the end of this page.
-
-::: tip Persistence
-EdgeOne Makers uses `@edgeone/pages-blob` for persistence. The default `auto` driver auto-detects Blob, so no extra configuration is needed. You can also explicitly set:
-
-- `DB_DRIVER = "blob"` with `DB_FORMAT = "map"` (JSON storage)
-- `DB_DRIVER = "kv"` with `DB_FORMAT = "key"` (Key-Value storage)
- :::
-
-### Step 3: Bind KV storage
-
-If you use KV storage in the environment variables, you must bind the `KV` variable to your namespace under **Storage → KV Storage**:
-
-
-
-### Step 4: Configure a custom domain
-
-After deployment, open **Domain management**, add a custom domain, then set up the CNAME record as required and enable SSL:
-
-
-
-### Step 5: Scheduled tasks
-
-EdgeOne supports scheduled refresh via `edgeone.json`. Set `cron_secret` in the payload to your `JWT_SECRET` value and configure the schedule:
-
-```jsonc
-{
- "schedules": [
- {
- "name": "token-refresh",
- "cron": "0 2 * * *",
- "path": "/api/task/refresh",
- "method": "POST",
- "payload": { "cron_secret": "" },
- "timezone": "Asia/Shanghai",
- },
- ],
-}
-```
-
-### After deployment
-
-::: tip
-After deployment, the first visit to the site automatically enters an **install wizard**. Set the admin account and password in the browser to complete initialization — no pre-configured `ADMIN_PASS` is required.
-:::
-::::
-
-:::: zh-CN
+## 部署到 EdgeOne
### 前置要求
@@ -144,12 +72,5 @@ EdgeOne 通过 `edgeone.json` 支持定时刷新。将 payload 中的 `cron_secr
::: tip
部署完成后，首次访问站点会自动进入**安装向导**，在浏览器中设置管理员账号与密码即可完成初始化，无需预先配置 `ADMIN_PASS`。
:::
-::::
-::: en
-For a full list of environment variables and recommended configurations, see [Environment Variables](./guide_env).
-:::
-
-::: zh-CN
完整的环境变量说明与推荐配置组合，请参阅 [配置变量](./guide_env)。
-:::
diff --git a/pages/ecosystem/official_worker/guide_esa.md b/pages/ecosystem/official_worker/guide_esa.md
index d9a8ad934..ee0704a06 100644
--- a/pages/ecosystem/official_worker/guide_esa.md
+++ b/pages/ecosystem/official_worker/guide_esa.md
@@ -1,52 +1,14 @@
---
-title:
- en: Deploy to Alibaba Cloud ESA
- zh-CN: 部署教程 - Alibaba Cloud ESA
categories:
- ecosystem
- eco_worker
top: 965
---
-## Deploy to Alibaba Cloud ESA { lang="en" }
+# 部署教程 - Alibaba Cloud ESA
-## 部署到阿里云 ESA { lang="zh-CN" }
+## 部署到阿里云 ESA
-:::: en
-OpenList Worker ships a dedicated ESA edge function entry (`esa-entry.ts`), which adapts Alibaba Cloud EdgeKV into the project's KV interface.
-
-### Build & deploy
-
-```bash
-# 1. Install dependencies
-pnpm install
-
-# 2. Build (produces dist/esa-entry.js)
-pnpm run build
-```
-
-`esa.jsonc` defines the edge function entry, install/build commands, and the static assets directory:
-
-```jsonc
-{
- "name": "openlist",
- "entry": "./dist/esa-entry.js",
- "installCommand": "pnpm install --no-frozen-lockfile",
- "buildCommand": "pnpm run build",
- "assets": { "directory": "./dist" },
-}
-```
-
-### KV namespace
-
-Configure the EdgeKV namespace via the `KV_NAMESPACE` environment variable (default `openlist`).
-
-:::tip
-ESA EdgeKV is eventually consistent. The entry implements a module-level TTL cache (60s) to avoid "saved settings revert after refresh" caused by cross-node sync delay.
-:::
-::::
-
-:::: zh-CN
OpenList Worker 内置了专用的 ESA 边缘函数入口（`esa-entry.ts`），将阿里云 EdgeKV 适配为项目的 KV 接口。
### 部署应用
@@ -78,12 +40,5 @@ pnpm run build
:::tip
ESA EdgeKV 是最终一致性的。入口实现了带 TTL（60 秒）的模块级缓存，避免跨节点同步延迟导致的「保存设置后刷新复原」问题。
:::
-::::
-:::en
-For a full list of environment variables and recommended configurations, see [Environment Variables](./guide_env).
-:::
-
-:::zh-CN
完整的环境变量说明与推荐配置组合，请参阅 [配置变量](./guide_env)。
-:::
diff --git a/pages/ecosystem/official_worker/index.md b/pages/ecosystem/official_worker/index.md
index cc71ffed0..46e31cea8 100644
--- a/pages/ecosystem/official_worker/index.md
+++ b/pages/ecosystem/official_worker/index.md
@@ -1,30 +1,16 @@
---
-title:
- en: Intro
- zh-CN: 项目介绍
categories:
- ecosystem
- eco_worker
top: 979
---
-## What is OpenList Worker { lang="en" }
+# 项目介绍
-## OpenList Worker 是什么 { lang="zh-CN" }
+## OpenList Worker 是什么
### [OpenListTeam/OpenList-Worker](https://github.com/OpenListTeam/OpenList-Worker)
-:::en
-[**OpenList Worker**](https://github.com/OpenListTeam/OpenList-Worker) (repo `OpenList-TSWorker`) is the official TypeScript + Serverless port of [OpenList](https://github.com/OpenListTeam/OpenList). The Go backend is rewritten as a TypeScript service running on edge platforms (Cloudflare Workers / EdgeOne Cloud Function / Alibaba Cloud ESA), while the frontend keeps the same interface and interaction as the official OpenList frontend.
-
-- **Backend**: Hono.js, runs on Cloudflare Workers / EdgeOne Functions / Alibaba Cloud ESA
-- **Frontend**: SolidJS + TypeScript, Hope UI, built with Vite
-- **Database**: Cloudflare D1 (SQLite), MySQL / MariaDB
-- **Cache**: Cloudflare KV / EdgeOne Blob / ESA EdgeKV (optional)
-- **License**: AGPL-3.0
- :::
-
-:::zh-CN
[**OpenList Worker**](https://github.com/OpenListTeam/OpenList-Worker)（仓库 `OpenList-TSWorker`）是官方 [OpenList](https://github.com/OpenListTeam/OpenList) 项目的 TypeScript + Serverless 架构移植版。后端由 Go 重写为运行于边缘平台（Cloudflare Workers / EdgeOne 云函数 / 阿里云 ESA）上的 TypeScript 服务，前端保持与官方 OpenList 前端一致的界面与交互。
- **后端**：Hono.js，运行于 Cloudflare Workers / EdgeOne 云函数 / 阿里云 ESA
@@ -32,30 +18,11 @@ top: 979
- **数据库**：Cloudflare D1（SQLite）、MySQL / MariaDB
- **缓存**：Cloudflare KV / EdgeOne Blob / ESA EdgeKV（可选）
- **许可证**：AGPL-3.0
- :::
-
-## Features { lang="en" }
-
-## 功能特性 { lang="zh-CN" }
-
-### Storage Aggregation { lang="en" }
-
-### 存储聚合 { lang="zh-CN" }
-
-:::en
-Built-in **81 storage drivers** to mount various storage backends out of the box:
-- **Domestic drives**: Aliyundrive (Open Platform / share), Quark (Open Platform / UC TV), Baidu (album), 115 (Open Platform / share), 123 (Open Platform / share), Tianyi Cloud, China Mobile Cloud, Xunlei, Tencent Weiyun, Lanzou, PikPak (share), Doubao, Teambition, WPS, Alidoc, etc.
-- **International drives**: Google Drive (album), OneDrive, Dropbox, MEGA, MediaFire, Proton Drive, Yandex Disk, TeraBox, etc.
-- **Object storage**: S3-compatible (AWS/OSS/COS/MinIO), UPYUN USS, Azure Blob, WebDAV, FTP, SFTP, SMB, IPFS, etc.
-- **Code hosting**: GitHub, GitHub Releases, CNB Releases
-- **Drive programs**: OpenList (share), AList V3, Cloudreve V3/V4, Kodbox, Seafile, Teldrive, Febbox, etc.
-- **Others**: NetEase Cloud Music, Misskey, Emby, Cloudflare image bed, etc.
+## 功能特性
-In addition to the real storages above, virtual/functional drivers such as `Local`, `Alias`, `UrlTree`, `AutoIndex`, `Strm`, `Crypt`, `Virtual`, `Chunk` are provided for local mount, address alias, URL lists, encrypted storage and chunking scenarios.
-:::
+### 存储聚合
-:::zh-CN
内置 **81 个存储驱动**，开箱即用地挂载各类存储后端：
- **国内网盘**：阿里云盘（开放平台/分享）、夸克网盘（开放平台/UC TV 版）、百度网盘（相册）、115 网盘（开放平台/分享）、123 云盘（开放平台/分享）、天翼云盘、中国移动云盘、迅雷云盘、腾讯微云、蓝奏云、PikPak（分享）、豆包网盘、Teambition 网盘、WPS 网盘、阿里文档等
@@ -66,24 +33,8 @@ In addition to the real storages above, virtual/functional drivers such as `Loca
- **其他驱动**：网易云音乐、Misskey、Emby、Cloudflare 图床等
除上述真实存储外，还提供 `Local`、`Alias`、`UrlTree`、`AutoIndex`、`Strm`、`Crypt`、`Virtual`、`Chunk` 等虚拟/功能型驱动，可用于本地挂载、地址别名、URL 列表、加密存储与分片等场景。
-:::
-### Core Capabilities { lang="en" }
-
-### 核心能力 { lang="zh-CN" }
-
-:::en
-
-- **File browsing**: unified directory tree browsing with online preview for images, videos, audio, documents, code, archives, etc.
-- **Upload & download**: cross-storage upload, batch download, streaming transfer and direct-link redirect.
-- **File sharing**: generate share links with expiration, password and permission control; support anonymous access and directory sharing.
-- **Full-text search**: quickly search files in indexed storages.
-- **Offline tasks**: background task queue for batch operations and async processing.
-- **External interfaces**: expose aggregated storage via WebDAV or S3-compatible protocol for mounting into third-party tools.
-- **MCP service**: provide a Model Context Protocol endpoint that can be integrated and called by AI assistants and other clients.
- :::
-
-:::zh-CN
+### 核心能力
- **文件浏览**：统一的目录树浏览，支持图片、视频、音频、文档、代码、压缩包等格式在线预览。
- **上传下载**：跨存储的上传、批量下载、流式传输与直链跳转。
@@ -92,82 +43,31 @@ In addition to the real storages above, virtual/functional drivers such as `Loca
- **离线任务**：后台任务队列，支持批量操作与异步处理。
- **外部接口**：将聚合存储以 WebDAV 或 S3 兼容协议对外暴露，便于挂载到第三方工具。
- **MCP 服务**：提供 Model Context Protocol 端点，可被 AI 助手等客户端集成调用。
- :::
-
-### Permission Management { lang="en" }
-
-### 权限管理 { lang="zh-CN" }
-:::en
-
-- **Access control**: role-based access control (RBAC), supporting user groups, directory-level read/write permissions and quotas.
-- **Authentication**: built-in account/password, TOTP verification, WebAuthn/FIDO login, SSO single sign-on and LDAP directory authentication.
-- **Security hardening**: JWT sessions, CSRF protection, clickjacking protection (X-Frame-Options), Content Security Policy (CSP).
-- **Health checks**: `/health` liveness probe and `/healthz` readiness probe for monitoring and alerting.
- :::
-
-:::zh-CN
+### 权限管理
- **权限管理**：基于角色的访问控制（RBAC），支持用户分组、目录级读写权限与配额。
- **认证方式**：内置账号密码，支持 TOTP 验证、WebAuthn/FIDO 登录、SSO 单点登录与 LDAP 目录认证。
- **安全加固**：JWT 会话、CSRF 防护、点击劫持防护（X-Frame-Options）、内容安全策略（CSP）。
- **健康检查**：提供 `/health` 存活探针与 `/healthz` 就绪探针，可用于监控与告警。
- :::
-
-### Supported Platforms { lang="en" }
-
-### 支持平台 { lang="zh-CN" }
-
-:::en
-
-- **Runtime platforms**: Cloudflare Workers, Tencent Cloud EdgeOne Functions, Alibaba Cloud ESA.
-- **Data storage**: Cloudflare D1 (SQLite) as primary, with external MySQL / MariaDB support.
-- **Persistent cache**: Cloudflare KV / EdgeOne Blob / ESA EdgeKV (optional), used for configuration persistence and caching.
-- **One-click deploy**: one-click deploy buttons + initialization for Cloudflare Workers, EdgeOne and Alibaba Cloud ESA.
- :::
-:::zh-CN
+### 支持平台
- **运行平台**：Cloudflare Workers、腾讯云 EdgeOne 云函数、阿里云 ESA。
- **数据存储**：Cloudflare D1（SQLite）为主，支持外部 MySQL / MariaDB。
- **持久缓存**：Cloudflare KV / EdgeOne Blob / ESA EdgeKV（可选），用于配置持久化与缓存。
- **一键部署**：支持 Cloudflare Workers、EdgeOne、阿里云 ESA 的一键部署按钮 + 初始化。
- :::
-## Documentation { lang="en" }
+## 文档导航
-## 文档导航 { lang="zh-CN" }
-
-:::en
-
-- [Design Architecture](./architecture) — Tech stack, data storage backend and supported platforms
-- [How to Deploy](./guide) — One-click deploy overview and local development
- - [Cloudflare Workers](./guide_cfw) — Step-by-step Cloudflare Workers deployment (with screenshots)
- - [EdgeOne](./guide_eom) — Tencent Cloud EdgeOne deployment
- - [Alibaba Cloud ESA](./guide_esa) — Alibaba Cloud ESA deployment
-- [Environment Variables](./guide_env) — `DB_FORMAT`, `DB_DRIVER` and all runtime variables
-- [FAQ](./faq) — Common issues and troubleshooting
- :::
-
-:::zh-CN
-
-- [设计架构](./architecture) — 技术栈、数据存储后端与支持平台
+- [设计架构](./basic) — 技术栈、数据存储后端与支持平台
- [部署方法](./guide) — 一键部署入口与本地开发
- [Cloudflare Workers](./guide_cfw) — 分步 Cloudflare Workers 部署教程（含截图）
- [EdgeOne](./guide_eom) — 腾讯云 EdgeOne 部署
- [阿里云 ESA](./guide_esa) — 阿里云 ESA 部署
- [配置变量](./guide_env) — `DB_FORMAT`、`DB_DRIVER` 及所有运行时变量
-- [常见问题](./faq) — 常见问题与排查
- :::
-
-## License { lang="en" }
-
-## 许可证 { lang="zh-CN" }
+- [常见问题](./about) — 常见问题与排查
-:::en
-`OpenList` is open-source software licensed under [AGPL-3.0](https://www.gnu.org/licenses/agpl-3.0.txt).
-:::
+## 许可证
-:::zh-CN
`OpenList` 是基于 [AGPL-3.0](https://www.gnu.org/licenses/agpl-3.0.txt) 许可证的开源软件。
-:::
diff --git a/pages/en/api/apidocs.md b/pages/en/api/apidocs.md
new file mode 100644
index 000000000..1a21d63aa
--- /dev/null
+++ b/pages/en/api/apidocs.md
@@ -0,0 +1,14 @@
+---
+top: 10
+categories:
+ - api
+---
+
+# API Documentation
+
+Visit [fox.oplist.org](https://fox.oplist.org) to view and interact with our API documentation online. Live debugging is supported.
+
+All contents, endpoints, and code provided by this API are licensed under the [GNU Affero General Public License v3 (AGPL-3.0)](https://www.gnu.org/licenses/agpl-3.0.html).
+
+
+
diff --git a/pages/en/api/index.md b/pages/en/api/index.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/pages/en/configuration/configuration.md b/pages/en/configuration/configuration.md
new file mode 100644
index 000000000..7119e368a
--- /dev/null
+++ b/pages/en/configuration/configuration.md
@@ -0,0 +1,656 @@
+---
+categories:
+ - configuration
+top: 70
+---
+
+# Configuration
+
+### Initial config
+
+::: tip
+After modifying the configuration file, restart OpenList for changes to take effect
+
+- Windows/macOS: `/data/config.json`
+- Linux: one-click script directory, `/opt/openlist/data/config.json` or `/data/config.json`
+- Docker: `/data/config.json`
+- OpenWrt: modify config on server if using `luci-app-openlist` , otherwise `/data/config.json`
+- Other: `/data/config.json`
+
+:::
+
+```json
+{
+ "force": false,
+ "site_url": "",
+ "cdn": "",
+ "jwt_secret": "random_generated",
+ "token_expires_in": 48,
+ "database": {
+ "type": "sqlite3",
+ "host": "",
+ "port": 0,
+ "user": "",
+ "password": "",
+ "name": "",
+ "db_file": "data\\data.db",
+ "table_prefix": "x_",
+ "ssl_mode": "",
+ "dsn": ""
+ },
+ "meilisearch": {
+ "host": "http://localhost:7700",
+ "api_key": "",
+ "index": "openlist"
+ },
+ "scheme": {
+ "address": "0.0.0.0",
+ "http_port": 5244,
+ "https_port": -1,
+ "force_https": false,
+ "cert_file": "",
+ "key_file": "",
+ "unix_file": "",
+ "unix_file_perm": "",
+ "enable_h2c": false
+ },
+ "temp_dir": "data\\temp",
+ "bleve_dir": "data\\bleve",
+ "dist_dir": "",
+ "log": {
+ "enable": true,
+ "name": "data\\log\\log.log",
+ "max_size": 50,
+ "max_backups": 30,
+ "max_age": 28,
+ "compress": false,
+ "filter": {
+ "enable": false,
+ "filters": [
+ {
+ "cidr": "",
+ "path": "/ping",
+ "method": ""
+ },
+ {
+ "cidr": "",
+ "path": "",
+ "method": "HEAD"
+ },
+ {
+ "cidr": "",
+ "path": "/dav/",
+ "method": "PROPFIND"
+ }
+ ]
+ }
+ },
+ "delayed_start": 0,
+ "max_connections": 0,
+ "max_concurrency": 64,
+ "tls_insecure_skip_verify": true,
+ "tasks": {
+ "download": {
+ "workers": 5,
+ "max_retry": 1,
+ "task_persistant": false
+ },
+ "transfer": {
+ "workers": 5,
+ "max_retry": 2,
+ "task_persistant": false
+ },
+ "upload": {
+ "workers": 5,
+ "max_retry": 0,
+ "task_persistant": false
+ },
+ "copy": {
+ "workers": 5,
+ "max_retry": 2,
+ "task_persistant": false
+ },
+ "decompress": {
+ "workers": 5,
+ "max_retry": 2,
+ "task_persistant": false
+ },
+ "decompress_upload": {
+ "workers": 5,
+ "max_retry": 2,
+ "task_persistant": false
+ },
+ "allow_retry_canceled": false
+ },
+ "cors": {
+ "allow_origins": ["*"],
+ "allow_methods": ["*"],
+ "allow_headers": ["*"]
+ },
+ "s3": {
+ "enable": false,
+ "port": 5246,
+ "ssl": false
+ },
+ "ftp": {
+ "enable": false,
+ "listen": ":5221",
+ "find_pasv_port_attempts": 50,
+ "active_transfer_port_non_20": false,
+ "idle_timeout": 900,
+ "connection_timeout": 30,
+ "disable_active_mode": false,
+ "default_transfer_binary": false,
+ "enable_active_conn_ip_check": true,
+ "enable_pasv_conn_ip_check": true
+ },
+ "sftp": {
+ "enable": false,
+ "listen": ":5222"
+ },
+ "mcp": {
+ "enable": false
+ },
+ "last_launched_version": "OpenList version",
+ "proxy_address": ""
+}
+```
+
+## Field Explanation
+
+### force
+
+By default OpenList reads the configuration from environment variables, set this field to `true` to force OpenList to read config from the configuration file.
+
+### site_url
+
+The address of your OpenList server, such as `https://pan.example.com`. This address is essential for some features, and thus thry may not work properly if unset:
+
+- thumbnailing `LocalStorage`
+- previewing site after setting web proxy
+- displaying download address after setting web proxy
+- reverse-proxying to site sub directories
+- ...
+
+Do not include the slash \(`/`\) at the end of the address. For example:
+
+```diff
++ "site_url": "https://openlist.example.com",
+- "site_url": "https://openlist.example.com/",
+```
+
+### cdn
+
+The address of the CDN. Included `$version` values will be dynamically replaced by the version of OpenList. Existing dist resources are hosted on both npm and GitHub, which can be found at:
+
+-
+-
+
+Thus it is possible to use any npm or ~~GitHub~~ CDN path for this field. Do not include the slash `/` at the end of the address. For example:
+
+- `https://registry.npmmirror.com/@openlist-frontend/openlist-frontend/$version/files/dist`
+- `https://unpkg.com/@openlist-frontend/openlist-frontend@$version/dist`
+- `https://cdn.jsdelivr.net/npm/@openlist-frontend/openlist-frontend@$version/dist`
+- `https://fastly.jsdelivr.net/npm/@openlist-frontend/openlist-frontend@$version/dist`
+- `https://gcore.jsdelivr.net/npm/@openlist-frontend/openlist-frontend@$version/dist`
+- `https://jsd.onmicrosoft.cn/npm/@openlist-frontend/openlist-frontend@$version/dist`
+
+- ~~`https://cdn.jsdelivr.net/gh/OpenListTeam/OpenList-Frontend@$version/dist`~~
+- ~~`https://jsd.onmicrosoft.cn/gh/OpenListTeam/OpenList-Frontend@$version/dist`~~
+
+::: tip
+If you are using the lite version, please add `/lite` to the end of the URL. For example: `https://cdn.jsdelivr.net/gh/OpenListTeam/OpenList-Frontend@$version/dist/lite`
+:::
+
+Keep empty to use dist resources embedded in the program by default.
+
+#### CDN for Beta version
+
+Since the frontend uses Vite for building, the generated JS files use a hash naming strategy. When code changes occur, the built file names change, making `index.html` files from different versions incompatible with each other.
+
+The OpenList backend needs to load `index.html` into memory for processing, including inserting code and modifying variables. If deployed only through Pages with modified API addresses, it would result in missing functionality and routing failures.
+
+To solve this problem, we've added the ability to fetch `index.html` from CDN for Beta versions and self-built versions, ensuring that JS files and `index.html` are properly matched.
+
+- **Release version**: Static resources are loaded through NPM CDN with fixed versions, so there's no need to request from CDN - the built-in `index.html` can be used directly
+ - Note: Some NPM CDNs (like npmmirror) may prohibit access to HTML files, but Release versions don't depend on CDN's `index.html`, so they're unaffected
+- **Beta version**: Updates frequently, OpenListTeam doesn't upload to NPM, and no CDN is provided for Beta versions
+
+Since Beta versions don't have NPM CDN provided by OpenListTeam, you need to deploy it yourself:
+
+1. **Deploy frontend build artifacts**
+ - Deploy build artifacts to a CDN platform (you can use Cloudflare Pages, EdgeOne Pages, etc.)
+ - Configure necessary CORS headers, for example of `edgeone.json`:
+
+ ```json
+ {
+ "headers": [
+ {
+ "source": "/*",
+ "headers": [
+ {
+ "key": "Access-Control-Allow-Origin",
+ "value": "*"
+ },
+ {
+ "key": "Access-Control-Allow-Methods",
+ "value": "GET, OPTIONS"
+ },
+ {
+ "key": "Access-Control-Allow-Headers",
+ "value": "Content-Type"
+ }
+ ]
+ },
+ {
+ "source": "/**/*.mjs",
+ "headers": [
+ {
+ "key": "Content-Type",
+ "value": "application/javascript"
+ }
+ ]
+ }
+ ]
+ }
+ ```
+
+ - Recommend using "copy + overwrite" deployment method, retaining old version resource files to ensure compatibility for versions not rebooted
+
+2. **Configure backend**
+ - Add CDN configuration in `config.json`
+ - The program will automatically fetch the latest `index.html` from CDN when starting
+
+3. **Version updates**
+ - When you need to update the frontend, simply restart the backend program
+
+Here's a diagram for better understanding:
+
+```mermaid
+flowchart TD
+ A[Program Initialization] --> B{CDN Configured?}
+
+ B -->|Yes| D{Version Type?}
+ B -->|No| E{Local dist_dir Configured?}
+
+ E -->|No| F[Use Built-in index.html]
+ E -->|Yes| G[Use index.html from Local dist_dir]
+
+ D -->|Beta Version| H[Fetch index.html from CDN]
+ D -->|Release Version| F
+
+ H --> I{CDN Fetch Successful?}
+ I -->|Success| J[Use CDN-fetched index.html]
+ I -->|Failed| K[Resty Retry 3 Times]
+ K -->|Success| J
+ K -->|Still Failed| L[Program Exit, Wait for Restart]
+
+ F --> M[Replace CDN, Site Info and Other Variables]
+ G --> M
+ J --> M
+ M --> N[Return Page]
+```
+
+### jwt_secret
+
+The secret used to sign the JWT token, randomly generated on first run.
+
+### token_expires_in
+
+User login expiration time, in hours.
+
+### database
+
+The database configuration, which is by default `sqlite3`. Available options are `sqlite3`, `mysql` and `postgres`.
+
+- The database options do not need to be modified if using `sqlite3`.
+
+```json
+ "database": {
+ "type": "sqlite3", //database type
+ "host": "", //database host
+ "port": 0, //database port
+ "user": "", //database account
+ "password": "", //database password
+ "name": "", //database name
+ "db_file": "data\\data.db", //Database location, used by sqlite3
+ "table_prefix": "x_", //database table name prefix
+ "ssl_mode": "", //To control the encryption options during the SSL handshake, the parameters can be searched by themselves, or check the answer from ChatGPT below
+ "dsn": "" // https://github.com/alist-org/alist/pull/6031
+ },
+```
+
+::: details Expand to view details of `ssl_mode`
+If you don't know how to fill it in, then your server probably doesn't have SSL enabled, so just leave it blank.
+In MySQL, the `ssl_mode` parameter is used to specify the authentication mode of the SSL connection. Here are a few common options:
+
+- `DISABLED`: Disable SSL connections.
+- `PREFERRED`: Use an SSL connection if server has SSL enabled, and otherwise fallback to a normal connection.
+- `REQUIRED`: Force to use SSL connection and fail if the server does not support SSL connection.
+- `VERIFY_CA`: Force to use SSL connection and verify the authenticity of the server certificate.
+- `VERIFY_IDENTITY`: Force to use an SSL connection and verify the authenticity of the server certificate and that the name matches the connecting hostname.
+ Additional, MySQL 5.x and 8.x have differences. If you are using databases provided by service providers, BTFM. If you deployed the database yourself, STFW.
+ In PostgreSQL, the `ssl_mode` parameter is used to specify how the client uses SSL connections. Here are a few common options:
+- `disable`: Disable SSL connections.
+- `allow`: Allow SSL connections.
+- `prefer`: Use an SSL connection if server has SSL enabled, and otherwise fallback to a normal connection.
+- `require`: Force to use SSL connection and fail if the server does not support SSL connection.
+- `verify-ca`: Force to use SSL connection and verify the authenticity of the server certificate.
+- `verify-full`: Force to use an SSL connection and verify the authenticity of the server certificate and that the name matches the connecting hostname.
+
+:::
+
+::: details Notes on modifying the database when there is already data
+
+1. If you change the `sqlite` database to `mysql` database, it is first recommended to use the backup and recovery method.
+2. If you directly import `sqlite` data into `mysql`, you can view this video tutorial: [View tutorial](https://www.bilibili.com/video/BV1iV4y1T7kh)
+ - Because when directly importing the cloud disk database table, the time of `sqlite` and the time of `mysql` are filled in differently, an error will be reported [please check the precautions and how to solve it](https://www.bilibili.com/video/BV1iV4y1T7kh?t=343.7)
+
+:::
+
+### meilisearch
+
+```json
+ "meilisearch": {
+ "host": "http://localhost:7700", // meilisearch host, the default is the local machine
+ "api_key": "", // if meilisearch's authentication is enabled, this is required
+ "index": "" // meilisearch index uid
+ },
+```
+
+- Documentation link：
+- Reference Links：
+
+### scheme
+
+The configuration of scheme. Set this field if using HTTPS.
+
+- Remember to copy the certificate file to the data directory. Config example:
+
+```json
+ "scheme": {
+ "address": "0.0.0.0", // The http/https address to listen on, default `0.0.0.0`
+ "http_port": 5244, // The http port to listen on, default `5244`, if you want to disable http, set it to `-1`
+ "https_port": -1, // The https port to listen on, default `-1`, if you want to enable https, set it to non `-1`
+ "force_https": false, // Whether the HTTPS protocol is forcibly, if it is set to True, the user can only access the website through HTTPS
+ "cert_file": "data\\cert.crt", // Path of cert file
+ "key_file": "data\\key.key", // Path of key file
+ "unix_file": "", // Unix socket file path to listen on, default empty, if you want to use unix socket, set it to non empty
+ "unix_file_perm": "", // Unix socket file permission, set to the appropriate permissions
+ "enable_h2c": false // Support HTTP/2 Cleartext (H2C) protocol for openlist's http service. The cleartext HTTP/2 protocol supports nginx's grpc_pass after it is enabled - https://github.com/AlistGo/alist/pull/8294
+ },
+```
+
+### temp_dir
+
+The directory to keep temporary files. By default OpenList uses `data/temp`.
+
+::: danger
+temp_dir is a temporary folder exclusive to alist. In order to prevent OpenList from generating garbage files when being interrupted, the directory will be cleared every time OpenList starts, so do not store anything in this directory or map this directory & subdirectories to directories in use when using Docker.
+:::
+
+### bleve_dir
+
+Where data is stored when using **`bleve`** index.
+
+### dist_dir
+
+If this option is set, the front-end files in the defined **local** external folder will be used as a priority.
+
+- Supports using front-end files from an external folder
+- Supports using other front-end files, while the back-end continues to use the original version of the application
+
+Upload the front-end files (dist) to the application's `data` folder, then fill in:
+
+```json
+ "dist_dir": "data/dist",
+```
+
+### log
+
+The log configuration. Set this field to save detailed logs of disable.
+
+```json
+ "log": {
+ "enable": true, // Whether OpenList should store logs
+ "name": "data\\log\\log.log", // The path and name of the log file
+ "max_size": 10, // the maximum size of a single log file, in MB. After reaching the specified size, the file will be automatically split.
+ "max_backups": 5, // the number of log backups to keep. Old backups will be deleted automatically when the limit is exceeded.
+ "max_age": 28, // The maximum number of days preserved in the log file, the log file that exceeds the number of days will be deleted
+ "compress": false, // Whether to enable log file compression functions. After compression, the file size can be reduced, but you need to decompress when viewing, and the default is to close the state false
+ "filter": { // skip some logs output, not enable by default
+ "enable": false,
+ "filters": [ // preset example
+ {
+ "cidr": "",
+ "path": "/ping", // Health check
+ "method": ""
+ },
+ {
+ "cidr": "",
+ "path": "",
+ "method": "HEAD" // HEAD request
+ },
+ { // WebDav metadata
+ "cidr": "",
+ "path": "/dav/",
+ "method": "PROPFIND"
+ }
+ ]
+ },
+```
+
+Each filter acts as the following object:
+
+```json
+{
+ "cidr": "",
+ "path": "", // http path, If it starts with "/", it is an absolute path; if it does not start with "/", it is a relative path
+ "method": "" // HTTP/webdav method, in uppercase
+}
+```
+
+Take note of the startup log to confirm the load, as detailed in the source code `server/middlewares/filtered_logger.go`.
+
+### delayed_start
+
+Whether to delay OpenList startup.
+
+
+
+**Time unit: second**
+
+Generally this option is used when OpenList is configured to auto-start. The reason is that sometimes network takes some time to connect, so drivers requiring cannot start correctly after OpenList starts.
+
+### max_connections
+
+The maximum amount of connections at the same time. The default is 0, which is unlimited.
+
+- 10 or 20 is recommended for general devices such as N1(S905D).
+- Usage Scenarios: the device will crash if the device is bad at concurrency when picture mode is enabled.
+
+### max_concurrency
+
+Limit the maximum concurrency of local agents. The default value is 64, and 0 means no limit.
+
+### tls_insecure_skip_verify
+
+Whether not to verify the SSL certificate.
+
+If there is a problem with the certificate of the website used when this option is not enabled (such as not including the intermediate certificate, having the certificate expired, or forging the certificate, etc.), the service will not be available.
+
+When this option is enabled, please ensure the program is running in a safe network environment.
+
+### tasks
+
+Configuration for background task threads.
+
+```json
+ "tasks": {
+ "download": {
+ "workers": 5,
+ "max_retry": 1,
+ "task_persistant": false
+ },
+ "transfer": {
+ "workers": 5,
+ "max_retry": 2,
+ "task_persistant": false
+ },
+ "upload": {
+ "workers": 5,
+ "max_retry": 0,
+ "task_persistant": false
+ },
+ "copy": {
+ "workers": 5,
+ "max_retry": 2,
+ "task_persistant": false
+ },
+ "decompress": {
+ "workers": 5,
+ "max_retry": 2,
+ "task_persistant": false
+ },
+ "decompress_upload": {
+ "workers": 5,
+ "max_retry": 2,
+ "task_persistant": false
+ },
+ "allow_retry_canceled": false
+ },
+```
+
+- **workers**: Number of task threads.
+- **max_retry**: Number of retries.
+ - 0: Retries disabled.
+- **download**: Download task when downloading offline
+- **transfer**: upload transfer task after offline download is completed
+- **upload**: upload task
+- **copy**: copy the task
+- **decompress**：decompress the task
+- **decompress_upload**：decompress upload the task
+- **task_persistant**：The task is persistent and will not be cancelled after restarting `OpenList`
+ - **download**：false
+ - **transfer**：false
+ - **upload**：false
+ - **copy**：false
+ - **decompress**：false
+ - **decompress_upload**：false
+- **allow_retry_canceled**：Allow users to retry previously canceled tasks
+
+---
+
+A new **transmission** configuration path is added to the background configuration: `/@manage/settings/traffic`
+
+- Supports limiting the number of threads and transmission uplink and downlink rates of **6 tasks**
+- ****
+ Operation principle: If `settings/traffic` does not have a thread number field (first run or just upgraded from an old version), `settings/traffic` will be initialized with the value of the config configuration file. If `settings/traffic` has a value, the thread configuration information of config will be ignored
+- ****
+- Summary: For newly installed or upgraded versions, the values will be read from the configuration file to initialize the `traffic` configuration information. Subsequent modifications to the thread only need to be modified in the background.
+
+### cors
+
+Configuration for Cross-Origin Resource Sharing (CORS).
+
+```json
+ "cors": {
+ "allow_origins": [
+ "*"
+ ],
+ "allow_methods": [
+ "*"
+ ],
+ "allow_headers": [
+ "*"
+ ]
+ }
+```
+
+- **allow_origins**: Allowed sources.
+- **allow_methods**: Allowed request methods.
+- **allow_headers**: Allowed request headers.
+
+Use it to understand it by yourself, and then configure it. If you do n’t know, please do n’t modify it at will. Use the default configuration.
+
+### S3
+
+```json
+ "s3": {
+ "enable": false,
+ "port": 5246,
+ "ssl": false
+ }
+```
+
+- `enable`：Whether the S3 function is enabled, the default is not enabled
+- `port`：port
+- `SSL`：Enable the HTTPS certificate, not enabled by default
+
+Function introduction: [Click to view](../guide/advanced/s3.md)
+
+### ftp
+
+```json
+ "ftp": {
+ "enable": false,
+ "listen": ":5221",
+ "find_pasv_port_attempts": 50,
+ "active_transfer_port_non_20": false,
+ "idle_timeout": 900,
+ "connection_timeout": 30,
+ "disable_active_mode": false,
+ "default_transfer_binary": false,
+ "enable_active_conn_ip_check": true,
+ "enable_pasv_conn_ip_check": true
+ },
+```
+
+- `enable`: Whether the **ftp** function is enabled, not enabled by default
+- `listen`: port number
+- `find_pasv_port_attempts`: maximum number of attempts to re-find a port due to port conflicts during passive transmission
+- `active_transfer_port_non_20`: enable ports other than 20 as active transmission ports
+- `idle_timeout`: maximum idle time (seconds) when there is no client request
+- `connection_timeout`: connection timeout
+- `disable_active_mode`: disable active transmission mode
+- `default_transfer_binary`: transfer in binary mode by default
+- `enable_active_conn_ip_check`: perform IP check on the client side of the TCP connection of the data stream in active transmission mode
+- `enable_pasv_conn_ip_check`: perform IP check on the client side of the TCP connection of the data stream in passive transmission mode
+
+Other instructions: [Click to view](../guide/advanced/ftp.md)
+
+### sftp
+
+```json
+ "sftp": {
+ "enable": false,
+ "listen": ":5222"
+ }
+```
+
+- `enable`: Whether the **sftp** function is enabled, not enabled by default
+- `listen`: port number
+
+Other instructions: [Click to view](../guide/advanced/ftp.md)
+
+### mcp
+
+```json
+ "mcp": {
+ "enable": false
+ }
+```
+
+- `enable`: Whether the **MCP** endpoint is enabled, not enabled by default
+
+Other instructions: [Click to view](../guide/advanced/mcp.md)
+
+### proxy
+
+```json
+ "proxy_address": "",
+```
+
+Supports HTTP proxy, HTTPS proxy, SOCKS4 proxy, SOCKS5 proxy, SOCKS5HOSTNAME proxy.
+
+Both IPv4 and IPv6 are supported.
diff --git a/pages/en/configuration/global.md b/pages/en/configuration/global.md
new file mode 100644
index 000000000..9ad871181
--- /dev/null
+++ b/pages/en/configuration/global.md
@@ -0,0 +1,177 @@
+---
+categories:
+ - configuration
+top: 20
+---
+
+# Global Configuration
+
+## Hide files
+
+Match files hidden by a regular expression (`JavaScript`). Please do not fill it in casually, as incorrect expressions may cause the front-end page to crash.
+
+One regular expression per line.
+
+By default, there is an expression `/\/README.md/i`, which hides `README.md` from all directories.
+
+Note that this is not a true hide. The file will still appear in the API response list, but will not be displayed in the front-end interface. If you wish to truly hide the file, please refer to [metadata](../guide/advanced/meta.md).
+
+## Package download
+
+Whether to enable package download (default is true). **Not recommended, especially for large or numerous files.**
+
+- It is recommended to push files to Aria2 for downloading, as it supports maintaining the directory structure when saving the download folder.
+- For more details, see [What is the difference between the two Aria2](./other.md#other).
+
+## Customize head
+
+The content set here will be automatically inserted into the header of the webpage (not include the manage pages). You can reference scripts, CSS, etc., here to style the frontend of OpenList.
+
+- How to configure PWA（Desktop、Android、IOS）：**[alist/issues/6724](https://github.com/alist-org/alist/issues/6724#issuecomment-2220251541)**
+
+## Customize body
+
+The content set here will be automatically inserted at the end of the webpage body. You can add icp information, visit statistics, etc., here.
+
+## Link expiration
+
+The expiration time of the direct link, in hours. If it equals 0, it will not expire. Default is 0.
+
+::: warning
+Only the straight chain of the path with the password added will have an expiration time, otherwise it will not expire.Because the expiration time is added to the sign query parameter, and the path without adding the password will not check the sign.
+:::
+
+## Sign all
+
+Add signatures to the direct link of all files (whether with password or not), such as `https://xxxx.com/d/xx?sign=vUQ5KFXnwMseKnIUXGRcfoG3cEHzKFBiPGp1NriMDXA=:0`.
+
+If you need to close it, you can close it yourself, but you need to pay attention to security issues. After closing the signature, if the site can be accessed by the public network, the password may be bypassed to access private files.
+There are two other methods that also carry the `sign?xxx` parameter:
+
+1. Add Storage Select `Enable Signing`
+2. Meta Information Add Password
+
+The scope of the three methods: `Sign All` > `Meta Information Add Password` > Add Storage Select `Enable Signing`
+
+1. Sign All: If this option is turned on, the sign parameter will be carried regardless of whether meta-information is encrypted or not, and whether `Enable Signing` is checked when adding storage.
+2. Meta Information Add Password：Only files under this meta information path will carry the sign parameter.
+ - If **Apply to sub folder** is turned on, all files in this path will carry the sign parameter
+3. Add Storage Select `Enable Signing`：Only this storage driver carries the sign parameter.
+
+## Privacy regs
+
+What you don't want to show in the error message, One regular expression (in `Golang`) per line. The matched content will be replaced with `*` of the corresponding length.
+
+## Ocr api
+
+Used to identify verification codes. You can deploy yourself: https://hub.docker.com/r/cloudlinksu/openlist-ocr-server.
+
+The default ocr api is deployed on the [Hugging Face](https://huggingface.co/spaces/Susus21/openlist-ocr/tree/main). You can clone the Hugging Face repository to build your own: [clone the Hugging Face repository](https://huggingface.co/spaces/Susus21/openlist-ocr/tree/main?duplicate=true).
+
+The hf domain name after successful self-construction is `https://{username}-{repositroy-name}.hf.space/ocr/file/json`.
+
+## Filename char mapping
+
+Map certain special characters, such as `/`, which is used as a path separator in OpenList. When file names contain `/`, it may cause issues like broken file paths or inability to view the files. By using this method, we can map and convert these characters to resolve such problems.
+
+```json
+{ "/": "|", "xx1": "xx1", "xx2": "xx2" }
+```
+
+## Forward direct link params
+
+After enabling, the parameters after `?` will be automatically appended to the end of the direct link URL.
+
+## Ignore direct link params
+
+Ignore the parameters for forwarding direct links, such as `sign` and `openlist_ts`.
+
+## Webauthn login enabled
+
+**Web Authentication (WebAuthn)** is a new authentication method. You can enable it by following these steps:
+
+1. **Enable WebAuthn Feature**: Go to the admin panel, navigate to `Settings` → `Global`, and enable the option `Enable WebAuthn Login`.
+2. **Bind WebAuthn Credentials**: Go to the `Profile` page in the admin panel and click `Add WebAuthn Credential` to bind your credentials.
+
+ Supported authentication methods:
+ - Local PIN code
+ - Companion devices (e.g., smart bands, smartwatches)
+ - Windows Hello options (e.g., facial recognition, fingerprint recognition)
+
+3. **Log in with WebAuthn**: After binding, you can log in using WebAuthn:
+ - On the login page, click the login button on the far right.
+ - Enter your username.
+ - Click login.
+ - Follow the prompts to complete WebAuthn verification (unlock the respective authentication method).
+
+::: tip WebAuthn only supports secure origins.
+
+**Supported environments:**
+
+- Websites with `https://` protocol
+- Localhost environment (`localhost`)
+
+**Unsupported environments:**
+
+- `http://` protocol
+- Local network IPs (e.g., `192.168.x.x`)
+- Local IPs (e.g., `127.0.0.1`)
+- Direct access via server IP
+
+:::
+
+## Allow previewing sharing files
+
+Enable the preview feature for files in share links.
+
+Please note that disabling this option will only hide preview methods (except Download) on the frontend, but cannot prevent users from invoking the relevant APIs.
+
+## Allow previewing sharing archives
+
+Enable the preview feature for archives in share links.
+
+Unlike the previous setting, disabling this option will prevent calls to the archive preview APIs for files in share links.
+
+## Force proxy sharing files
+
+Enforce proxying for all file requests originating from share links.
+
+## Share summary content
+
+The content copied by clicking "Copy Link" after sharing completion, coding in Handlebars template syntax.
+
+If you prefer copying the accessible link directly, try:
+
+- Preview link
+
+```handlebars
+{{base_url}}/@s/{{id}}
+```
+
+- Preview link with share code
+
+```handlebars
+{{base_url}}/@s/{{id}}{{#if pwd}}?pwd={{pwd}}{{/if}}
+```
+
+- direct download link (applies only to single-file shares)
+
+```handlebars
+{{base_url}}/sd/{{id}}{{#if pwd}}?pwd={{pwd}}{{/if}}
+```
+
+## Handle hook after writing
+
+Whether to trigger the directory update hook after operations such as upload, rename, delete, move, copy, or extraction.
+
+Triggering the directory update hook will cause the index to update and activate the function of the [Strm](/en/guide/drivers/strm) driver to generate local files.
+
+## Handle hook rate limit
+
+It is only meaningful when the [Handle hook after writing](/en/configuration/global#handle-hook-after-writing) is enabled. When the directory update hook is triggered, this limits the rate at which the driver API is called (unit: times/second; 0 means no restriction).
+
+## Ignore system files
+
+When enabled, attempts by users to upload certain system files will directly fail, thereby achieving filtering.
+
+The determination of whether a file is a system file is based on its filename.
diff --git a/pages/en/configuration/index.md b/pages/en/configuration/index.md
new file mode 100644
index 000000000..12e064860
--- /dev/null
+++ b/pages/en/configuration/index.md
@@ -0,0 +1,11 @@
+# Configuration
+
+---
+
+- [Configuration file](./configuration)
+- [Site settings](./site)
+- [Style settings](./style)
+- [Preview settings](./preview)
+- [Global settings](./global)
+- [Other settings](./other)
+- [Side settings](./side)
diff --git a/pages/en/configuration/other.md b/pages/en/configuration/other.md
new file mode 100644
index 000000000..966c1fbc3
--- /dev/null
+++ b/pages/en/configuration/other.md
@@ -0,0 +1,53 @@
+---
+categories:
+ - configuration
+top: 10
+---
+
+# Other Configuration
+
+## Aria2
+
+Used for the offline download feature, which downloads an external resource outside of OpenList into the storage managed by OpenList.
+Set Aria2 uri and Aria2 for offline download.
+
+> `Aria2` needs to access the same directory as `OpenList`: `/opt/openlist/data/temp/aria2`. Assuming that both Aria2 and OpenList are independent containers, where OpenList mounts the directory `/etc/openlist/data:/opt/openlist/data`, Aria2 containers need to be additionally mounted under the path `/etc/openlist/data/temp/aria2:/opt/openlist/data/temp/aria2`.
+
+### Aria2 uri
+
+The Aria2 RPC address used for offline downloading. The default value is: `http://localhost:6800/jsonrpc`.
+
+### Aria2 secret
+
+The Aria2 RPC secret key used for offline downloading. The default value is empty.
+
+## qBittorrent
+
+Used to customize **qBittorrent** parameters to configure the client to use.
+
+The default value is: `http://admin:adminadmin@localhost:8080/`, you can modify it by referring to [specific instructions](../guide/advanced/offline-download.md#qbittorrent)
+
+## 115、PikPak、Thunder
+
+**You need to add the driver first, and then set the temporary directory in the settings.**
+
+Allow the use of offline download tools such as 115/PikPak/Thunder in any storage.
+
+- Files will be downloaded directly to the destination dir if using the tool in 115/PikPak/Thunder storage.
+- Otherwise, files will be downloaded to a user-configured temp dir, and then transfered to the destination dir.
+ - For example, on the front-end page of the `GoogleDrive` storage drive, when the `Pikpak offline-download` function is invoked, the file will first be downloaded to the Pikpak temporary folder directory set in the backend. Once the Pikpak offline download is complete, the file will be automatically transferred from Pikpak to `GoogleDrive`.
+
+### Token
+
+The token that can be used to access all APIs of the program. Unlike the token obtained after logging in with a username and password, this token is fixed and has no expiration time.
+
+### Other
+
+1. When using OpenList, you may notice two Aria2 options. What is the difference between them? [**Click here for detailed explanation**](../faq/why.md#what-is-the-difference-between-the-two-aria2)
+
+2. Supports using Aria2 to download folders while preserving the original directory structure.
+ - **Configure Aria2**: Go to the bottom-right corner, click `Settings` → `Aria2 RPC Link` → Enter the `Aria2 RPC Key` (if available).
+ - Aria2 will download files locally, so you only need to initiate the download on your local machine. It also supports pushing the download task to another computer, your own server, or other devices in your local network, as long as the target device has Aria2 installed and is connected to either the public internet or the local network.
+
+ - **Start downloading**: Check the `Enable checkbox` in the bottom-right corner → Select the files/folders → Click `Download` at the bottom → `Send to Aria2`.
+ - **Important notes**: It is recommended not to download too many files at once, such as thousands of folders or tens of thousands of files, as this may cause performance issues.
diff --git a/pages/en/configuration/preview.md b/pages/en/configuration/preview.md
new file mode 100644
index 000000000..90417066e
--- /dev/null
+++ b/pages/en/configuration/preview.md
@@ -0,0 +1,160 @@
+---
+categories:
+ - configuration
+top: 30
+---
+
+# Preview Configuration
+
+## Text types
+
+The extensions of the files you want to preview as text, split by `,`, such as `txt,md,go,tsx`.
+
+## Audio types
+
+The extensions of the files you want to preview as audio, split by `,`, such as `mp3,wav,m4a`.
+
+## Video types
+
+The extensions of the files you want to preview as video, split by `,`, such as `mp4,webm,ogg`.
+
+## Image types
+
+The extensions of the files you want to preview as image, split by `,`, such as `jpg,jpeg,png,gif,webp`.
+
+### Proxy types
+
+The file extensions to be downloaded through the program proxy, split by `,`, such as `m3u8,url`.
+
+### Proxy ignore headers
+
+Do not forward request headers, such as `authorization,referer`, when downloading through the program proxy.
+
+This can prevent download failures caused by header parameter leakage.
+
+### External previews
+
+A json object that contains the external preview settings, It is defined as
+
+```typescript
+interface {
+ [extensions: string]: {
+ [name: string]: string //(url)
+ }
+}
+```
+
+the first key `extensions` is the file extensions separated by `,` (if it starts with `/`, it will be considered a regular expression), and the value is also a `key-value` object, the key is the preview name, and the value is the external url.
+
+For the external URL, we provide some variables for you to use:
+
+Basic variable:
+
+- `$url`: the URL of file, such as `https://openlist.example.com/p/file.pdf`.
+- `$durl`: the direct URL of file, such as `https://oss.example.com/cloud/user/2020/01/01/file.pdf`.
+- `$name`: the file name
+
+Extended variables:
+Add [eb_] before the basic variable, where e means `encodeURIComponent`, b means `base64`, such as:
+
+- `$e_url`: encodeURIComponent($url)
+- `$b_url`: btoa($url)
+- `$eb_url`: encodeURIComponent(btoa($url))
+
+Finally, the `External previews` will displayed a `Open with` menu while current file matched the `extensions`.
+For example, set `External previews` to
+
+```json
+{
+ "txt": {
+ "Notepad": "notepad://$url"
+ },
+ "/.*/": {
+ "VSCode": "vscode://$url"
+ }
+}
+```
+
+when we enter a file with the extension `txt`, it will show:
+
+
+### Iframe previews
+
+Similar to `External previews`, but it will embed an iframe in current page directly.
+
+You need to enter a preview HTML page, and then pass the file address as a parameter to the page using a variable. The available variables are listed in the previous section.
+
+:::tip
+If you want to use self-deployed OnlyOffice to preview office files, you can add the configuration like this here:
+
+```json
+{
+ "doc,docx,xls,xlsx,ppt,pptx": {
+ "OnlyOffice": "you_only_office_url"
+ }
+}
+```
+
+Deploying and using `OnlyOffice` Reference:
+
+- https://github.com/AlistGo/alist/discussions/3255
+- https://github.com/AlistGo/alist/discussions/8271
+
+:::
+
+### Audio cover
+
+The default audio cover.
+
+### Audio autoplay
+
+Whether to automatically play audio files.
+
+### Video autoplay
+
+Whether to automatically play video files.
+
+### Preview archives by default
+
+After enabling this option, compressed files will be previewed by default (as shown in the image below). Although it will consume some server bandwidth, a full download will not occur. If you wish to disable the preview for compressed files, turning off this option will change the default behavior to download mode.
+
+
+
+
+
+### Readme autorender
+
+After closing, the content of files like readme.md will no longer be automatically rendered.
+
+By default, `readme.md`, `footer.md`, and `bottom.md` will be rendered at the bottom of the file, while `header.md`, `top.md`, and `index.md` will be rendered at the top of the file.
+
+### Filter readme scripts
+
+Prevent virus script attacks. After turning it on, the contents of `readme.md` will be displayed in text form.
+
+- Including but not limited to strikethrough, tables, task lists, etc. displayed in text form
+- The specific effects are as follows:
+ 
+
+### Force preview
+
+We can force the preview type through the `type` query parameter.
+
+Available values:
+
+```
+UNKNOWN
+FOLDER
+VIDEO
+AUDIO
+TEXT
+IMAGE
+```
+
+Example: `http://yourdomain/test-file.ahk?type=text`
+
+## Specify preview
+
+We can specify the preview through the `preview` query parameter. The parameter will be generated when you select a preview in the file page.
+
+Example: `http://yourdomain/test-file.ahk?preview=download`
diff --git a/pages/en/configuration/side.md b/pages/en/configuration/side.md
new file mode 100644
index 000000000..1f296c30c
--- /dev/null
+++ b/pages/en/configuration/side.md
@@ -0,0 +1,136 @@
+---
+categories:
+ - configuration
+top: 0
+---
+
+# Side Configuration
+
+We can see a icon on the lower right corner of the homepage. If your computer resolution is very high, the icon is likely to be smaller
+After the expand
+
+-
+ Refresh
+
+ The refresh we mentioned is not to use F5 to refresh the webpage, **but use this icon to refresh**, so that the files that just uploaded to the network disk can be refreshed out.
+
+-
+ New File
+
+-
+ New Folder
+
+-
+ Recursive Move
+
+ Move all the files in the current directory and all files in the subfolder to the designated folder
+ - :warning: Dangerous operation, please use it with caution.
+
+-
+ Remove Empty Folder
+
+-
+ Batch Rename
+
+-
+ Upload
+
+ Open the upload modal.
+
+-
+ Offline download
+
+ Open the offline download modal.
+
+-
+ Toggle Outline
+
+ Toggle the outline for markdown viewer.
+
+-
+ Toggle Checkbox
+
+ Select multiple files.
+ - In the display of Toggle Checkbox, first trigger the selection operation to prevent jumping into a deeper folder
+ - In the display of Toggle Checkbox, change it to hold down the `Alt` key and click to open the folder (macOS Press and hold the `Option` key)
+
+-
+ Local Settings
+
+ Open the local settings.
+
+::: tip
+If you didn't find this feature, please update the version
+:::
+
+## Upload Modal
+
+
+
+Drag files to the field to upload, or click `Choose Folder` or `Choose File` to select files to upload.
+
+There are two methods to upload files:
+
+1. **Stream**: directly puts the binary content of the file into the body, so that the backend can use very little memory, it seem to have no downsides.
+
+2. **Form**: is to wrap the file into formdata and upload it. The memory used by the backend will be more, but there is no limit on the size.
+
+There are the following options:
+
+- **Add as Task**: Create an upload task in the background.
+- **Overwrite existing File**: If the file already exists, it will be overwritten.
+- **Try rapid**: Upload the file with its checksum information, requires cloud storage support.
+
+## Offline Download Modal
+
+
+
+Download the file offline and upload it to the network disk directory you designated.
+
+If you want to keep the offline downloaded file, please add the link first, select the options below, and then start the offline download.
+
+**How to use**: Navigate to the target directory, then select "Offline Download" from the bottom-right corner.
+
+Supported offline download tools: `Aria2`, `qBittorrent`, `SimpleHttp`.
+
+**Note**: When using the offline download feature, OpenList must be installed and running on the corresponding device. Offline downloads cannot be performed across different devices.
+
+For more information, please refer to [Offline Download](../guide/advanced/offline-download.md).
+
+## Local Settings Modal
+
+Local settings will be saved to the browser's local storage.
+
+1. **Aria2 RPC URL** and **Aria2 RPC secret**: This field is for entering the user's Aria2 information, which enables batch downloading on the client side, not on the server side.
+
+2. **Global default layout**: The selection of view selection in the upper right corner is to enter that folder to modify it only for the only folder. This setting can consistently take effect without using a folder setting.
+
+3. **Show folder in image view**: literal meaning
+
+4. **Show sidebar**: Add a list directory on the left side of the list like Windows Explorer, which can jump to a deep folder faster
+
+5. **Show file count message**: At the bottom of the page (in list view) or at the top (in grid or image view), display the total number of items in the current folder and how many items are selected.
+
+6. **Position of header & nav bar**: Is the logo and navigation bar displaying at the drop -down list?
+ - **Normal**: No need to display
+ - **Stick to top of page**: adsorb LOGO and navigation bar
+ - **Only nav bar sticky**: Do not adsorb LOGO, only adsorb navigation bar
+
+7. **Grid item size** : Adjust the picture size in the Grid item mode. Default: 90.
+
+8. **List item filename overflow**: When the text is too long, the three state selection
+ - **Ellipsis**: Default
+ - **Scrollable**: PC users use the `Shift` + `mousewheel` on the file, if it is a mobile phone user sliding the file left and right
+ - **Multi-line**
+
+9. **Open item on Checkbox**:
+ - **Direct**: Open the file/enter the folder
+ - **Double Click**
+ - **Disable while checked**
+ - With `Ctrl` or `Command` (macOS) hold
+ - With `Alt` or `Option` (macOS) hold
+ - If the button option does not take effect, please check whether the browser plugin conflict
+
+ Tips: You can press the `Shift` key to select one, and then select one end. You can quickly select all the files in the middle
+
+10. **Language package selection** and **night mode and daytime mode switch**
diff --git a/pages/en/configuration/site.md b/pages/en/configuration/site.md
new file mode 100644
index 000000000..465765c22
--- /dev/null
+++ b/pages/en/configuration/site.md
@@ -0,0 +1,73 @@
+---
+categories:
+ - configuration
+top: 50
+---
+
+# Site Configuration
+
+## Version
+
+The version of OpenList, readonly.
+
+## Site title
+
+The title of OpenList, such as `OpenList`.
+
+## Announcement
+
+The announcement of OpenList, such as `### Hello\nWelcome to use OpenList`. We suggest you add a title in front of the content, such as `### Hello`, so that the content will not be covered by `Close Button`.
+
+- If you don't want to display it, you can clear the contents of the announcement to not display it.
+- If you think the `x` button in the upper right corner is in the way, you can use the following CSS to remove it
+
+```css
+
+```
+
+## Pagination type
+
+- All: All files will be displayed at once.
+- Pagination: Show a `Paginator` at the bottom of the page.
+- Load more: Show a `Load more` button at the bottom of the page.
+- Auto load more: Automatically load more files when scrolling to the bottom of the page.
+
+## Default page size
+
+The default page size of the `openlist` if `Pagination type` doesn't set to `All`, such as `20`.
+
+## Allow indexing
+
+Whether to allow others to mount your OpenList to build the index, check it and enable it.
+
+The default is off, use with caution. (New features in version 3.8.0)
+
+## Allow mounted
+
+Whether to allow being mounted by other OpenList instances.
+
+**The default is enabled. If you don't want to be mounted by others, it's recommended to disable this option.** (New feature in v3.16.3)
+
+## robots.txt
+
+Crawler configuration/rules.
+
+The default is to allow crawlers to access all pages.
+
+`Allow: /` Indicates that the crawlers of search engines are allowed to visit all pages:
+
+```txt{2}
+User-agent: *
+Allow: /
+```
+
+If you want to prevent crawlers from accessing all pages, you can change it to this:
+
+```txt{2}
+User-agent: *
+Disallow: /
+```
diff --git a/pages/en/configuration/style.md b/pages/en/configuration/style.md
new file mode 100644
index 000000000..412db331e
--- /dev/null
+++ b/pages/en/configuration/style.md
@@ -0,0 +1,39 @@
+---
+categories:
+ - configuration
+top: 40
+---
+
+# Style Configuration
+
+## Logo
+
+The logo is displayed in the upper left corner of the page. The default is the `OpenList logo`.
+
+You can set two different ones at night and during the day, one link per line.
+
+## Favicon
+
+The favicon is displayed in the browser tab. The default is the `OpenList logo`.
+
+## Main color
+
+The main color is used to on the page. The default is `#1890ff`.
+
+## Home icon
+
+The home icon is displayed in the left of the navigation bar. The default is `🏠`.
+
+## Home container
+
+- Max 980px: the main width will set to `min(99%, 980px)`
+- Hope container: sets the max-width of the content to match the min-width of the current breakpoint, refer to https://openlistteam.github.io/hope-ui/docs/layout/container
+
+## Settings layout
+
+The layout of the settings items on the management page.
+
+- Responsive: grids next to each other
+- List style: one grid per row
+
+The default is: List
diff --git a/pages/en/ecosystem/index.md b/pages/en/ecosystem/index.md
new file mode 100644
index 000000000..908565a86
--- /dev/null
+++ b/pages/en/ecosystem/index.md
@@ -0,0 +1,226 @@
+---
+categories:
+ - ecosystem
+top: 1000
+---
+
+# OpenList Ecosystem
+
+This page shows the OpenList ecosystem, including official projects and third-party projects
+
+## Official Projects
+
+### [OpenList Docs ↗](./official_docs)
+
+Documentation based on VitePress, with real-time builds from the GitHub repository.
+
+---
+
+### [OpenList Desktop ↗](./official_desktop)
+
+A cross-platform GUI management interface integrating OpenList and rclone, offering graphical configuration, monitoring, and service management features.
+
+---
+
+### [OpenList Mobile ↗](./official_mobile)
+
+A mobile file server application based on OpenList, built with Flutter framework. Turn your phone into a file server.
+
+---
+
+### [OpenList APIPages ↗](./official_APIpage)
+
+An open-source implementation of the online API functionality in OpenList, deployable on various servers, providing stable and privacy-protected API authentication services for cloud storage users.
+
+---
+
+### [OpenList Proxy ↗](./official_proxy)
+
+OpenList traffic proxy program, which can use another server to proxy OpenList traffic.
+
+---
+
+### [OpenList Worker ↗](./official_worker/)
+
+The official TypeScript + Serverless port of OpenList running on Cloudflare Workers / EdgeOne / Alibaba Cloud ESA, reusing the official React 19 frontend.
+
+---
+
+## Third-Party Open Source Projects
+
+::: tip
+Third-party open source projects are based on community open-source security. The following projects are not affiliated with OpenListTeam. Please evaluate the associated risks before deploying them to a production environment.
+
+If you have a new project that is not listed here, you can submit it through [Issues](https://github.com/OpenListTeam/OpenList-Docs/issues) or [Pull Request](https://github.com/OpenListTeam/OpenList-Docs/pulls).
+:::
+
+### [sbwml/luci-app-openlist ↗](https://github.com/sbwml/luci-app-openlist)
+
+Provides LuCI support for OpenList, suitable for OpenWRT-based router systems.
+
+Free and Open Source Software licensed under the MIT license.
+
+---
+
+### [giturass/openlist_termux ↗](https://github.com/giturass/openlist_termux/)
+
+OpenList management script for Termux, used for convenient installation, updating, and management of OpenList in the Android Termux environment.
+
+Free and Open Source Software licensed under the MIT license.
+
+---
+
+### [ypq123456789/openlist-manger ↗](https://github.com/ypq123456789/openlist-manger)
+
+A cross-platform interactive Shell script for managing OpenList, supporting Linux, macOS, Windows (WSL), and Android Termux.
+
+Free and Open Source Software licensed under the MIT license.
+
+---
+
+### [Alien-Et/OpenList-Magisk ↗](https://github.com/Alien-Et/OpenList-Magisk)
+
+The OpenList Magisk module integrates the OpenList file server into the Android system, running in a systemized manner through Magisk, supporting ARM and ARM64 architectures.
+
+Free and Open Source Software licensed under the MIT license.
+
+---
+
+### [qianye216/OpenList-Desktop ↗](https://github.com/qianye216/OpenList-Desktop)
+
+OpenList Desktop is a cross-platform desktop client designed for OpenList (Alist) and Rclone. It provides a modern and user-friendly graphical interface that helps you easily manage Alist services and Rclone cloud storage mounts without needing to memorize and input tedious command-line instructions.
+
+Free and Open Source Software licensed under the GPLv3 license.
+
+---
+
+### [LeoHaoVIP/AListLiteAndroid ↗](https://github.com/LeoHaoVIP/AListLiteAndroid)
+
+AListLite is an Android application that supports running OpenList services. Compared to the tutorial described in BV1ex4y157xJ, users can use OpenList services on Android devices (phones/TVs) without needing to install Termux.
+
+Free and Open Source Software licensed under the AGPLv3 license.
+
+---
+
+### [outlook84/mpv-handler-openlist ↗](https://github.com/outlook84/mpv-handler-openlist)
+
+This is a URL protocol handler (mpv://) designed for mpv or mpv.net media players on Windows platform. This tool is used to invoke mpv or mpv.net players from OpenList web pages to open video links.
+
+Free and Open Source Software licensed under the GPLv2 license.
+
+---
+
+### [outlook84/openlist-tvbox-gateway ↗](https://github.com/outlook84/openlist-tvbox-gateway)
+
+OpenList gateway for TVBox, used to connect OpenList resources to TVBox-compatible clients.
+
+Free and Open Source Software licensed under the AGPLv3 license.
+
+---
+
+### [moyanj/AList3SDK ↗](https://github.com/moyanj/AList3SDK)
+
+A high-performance Python SDK for easy interaction with OpenList/AList services. Supports both asynchronous and synchronous APIs, and provides comprehensive type annotations!
+
+Free and Open Source Software licensed under the LGPL-2.1 license.
+
+---
+
+### [huancun/Openlist-EX-container ↗](https://github.com/huancun/Openlist-EX-container)
+
+This project is an improved version based on Alist-EX-container.
+Integrates Openlist, Aria2, qBittorrent, Caddy reverse proxy, supports multi-arch one-click deployment, navigation page and multiple web panels, perfect for offline download and resource management.
+
+Free and Open Source Software licensed under the GPLv3 license.
+
+---
+
+### [hienao/ostrm ↗](https://github.com/hienao/ostrm)
+
+A full-stack application for converting OpenList file lists into STRM streaming media files. (Originally the openlist-strm project)
+
+Free and Open Source Software licensed under the GPLv3 license.
+
+---
+
+### [li-peifeng/iNoi ↗](https://github.com/li-peifeng/iNoi)
+
+An open-source fork of OpenList focusing on stability.
+
+Free and Open Source Software licensed under the AGPLv3 license.
+
+---
+
+### [907739769/OpenList-strm-RuoYi ↗](https://github.com/907739769/OpenList-strm-RuoYi/)
+
+An improved version of OpenList Strm based on RuoYi framework.
+
+Free and Open Source Software licensed under the MIT license.
+
+---
+
+### [Liki4/qnap-openlist-webdav ↗](https://github.com/Liki4/qnap-openlist-webdav/)
+
+QNAP OpenList | The third-party open-source QPKG version of OpenList.
+
+Free and Open Source Software licensed under the AGPLv3 license.
+
+---
+
+### [HisAtri/openlistapi ↗](https://github.com/HisAtri/openlistapi/)
+
+An open-source Python client implementing the OpenList API.
+
+Free and Open Source Software licensed under the MIT license.
+
+---
+
+### [jiwangyihao/olist-cdn-preheat ↗](https://github.com/jiwangyihao/olist-cdn-preheat/)
+
+OpenList dedicated CDN preheating tool. When used with EdgeOne/ESA origin-following redirection, it efficiently improves cache hit rates and accelerates site downloads.
+
+Free and Open Source Software licensed under the MPLv2 license.
+
+---
+
+### [MY QNAP's OpenList ↗](https://www.myqnap.org/product/openlist/)
+
+QNAP's MyQNAP repository distributes the OpenList application for a fee of $6.
+We have contacted the QNAP France team and, based on the AGPL and CC licenses, requested them to provide the hash values of the application or take it down.
+The communication progress is as follows:
+
+1. The application is provided by QNAP officially, not uploaded by users.
+2. The charging behavior is not for profit, so the CC license does not apply.
+3. According to the AGPL license, if the application has not been modified, hash values like MD5, SHA, etc. must be provided. Currently, QNAP states that the relevant work is in progress.
+4. Based on the above situation, QNAP has temporarily taken down the application and will update the page. Once the hash values are displayed, the download and distribution of OpenList will resume.
+5. As of now, QNAP has not actually violated the license. Our investigation initiated to prevent open-source supply chain risks has been completed.
+
+::: details History information (outdated，archived at 2026-01-22)
+The third-party closed-source QPKG version of OpenList.
+
+[Archived on 2025-7-13](https://web.archive.org/web/20250713005135/https://www.myqnap.org/product/openlist/)
+
+Proprietary software, paid license.
+
+Note: The source code is not open, violating the AGPLv3 license and the OpenList logo's CC BY-NC-SA 4.0 license.
+:::
+
+## Third-Party Proprietary Software
+
+::: danger
+The following lists several other third-party projects derived from OpenList that do not fall into the above categories.
+
+Any actions of these software/projects (including references to OpenList in their names, functionality design, content, or promotional methods) do not represent the stance of the OpenList project. The functionality, consequences of use, and related legal responsibilities are entirely borne by their respective developers or publishers, and the OpenList project assumes no responsibility.
+:::
+
+### [Yxiguan/OpenList_123](https://github.com/Yxiguan/OpenList_123)
+
+::: danger
+The third-party closed-source modified version of OpenList.
+
+[Archived on 2025-10-19](https://web.archive.org/web/20251019150201/https://github.com/Yxiguan/OpenList_123)
+
+Proprietary software, no license.
+
+Note: The source code is not open, violating the AGPLv3 license.
+:::
diff --git a/pages/en/ecosystem/official_APIpage.md b/pages/en/ecosystem/official_APIpage.md
new file mode 100644
index 000000000..b508bde48
--- /dev/null
+++ b/pages/en/ecosystem/official_APIpage.md
@@ -0,0 +1,288 @@
+---
+categories:
+ - ecosystem
+ - eco_official
+top: 970
+---
+
+# OpenList APIPages
+
+## What is OpenList APIPages
+
+### [OpenListTeam/OpenList-APIPages](https://github.com/OpenListTeam/OpenList-APIPages)
+
+[OpenListTeam/OpenList-APIPages](https://github.com/OpenListTeam/OpenList-APIPages) is a utility website led by [@PIKACHUIM](https://github.com/PIKACHUIM) and collaboratively developed with other [main contributors](https://github.com/OpenListTeam/OpenList-APIPages/graphs/contributors). The frontend is primarily used for initial authorization and obtaining refresh tokens of cloud storage clients, while the backend mainly supports a feature called "Online API", which enables remote token refresh functionality while protecting developer client secrets.
+
+## Why OpenList APIPages is needed
+
+Cloud Storage Background:
+
+- Most domestic cloud storage services do not provide official API access to individuals, or the application process is cumbersome, which is not conducive to rapid deployment.
+- According to the cloud storage providers' management requirements, the obtained client keys must not be leaked.
+- User authorization is in the form of refresh tokens, which need to be periodically combined with client keys to obtain refreshed access tokens from the cloud storage servers.
+- API calls require the user's latest access tokens.
+
+Solution:
+
+- Community volunteers provide qualification certification and apply for API access permissions from cloud storage officials.
+- Use relay servers to protect client keys.
+- Periodically send refresh tokens to designated relay servers, which use built-in client keys to refresh access tokens.
+- The relay server sends access tokens back to the OpenList client.
+
+The relay server described above is the backend functionality of the Online API server/APIPages, which works as follows:
+
+```mermaid
+sequenceDiagram
+ participant OpenList
+ participant OnlineAPI as Online API Server
+ participant Server as Cloud Storage Server
+
+ OpenList ->> OnlineAPI: Refresh Token
+ OnlineAPI ->> Server: Cloud Storage Client Key
+ Server -->> OnlineAPI: Access Token
+ OnlineAPI -->> OpenList: Access Token
+ OpenList ->> Server: Access Token
+ OpenList <<->> Server: Cloud Storage Data
+```
+
+The frontend part of APIPages also solves the following problems:
+
+- Initial authorization verification for different cloud storage services.
+- Authorization while protecting built-in client keys.
+- Authorization with custom client keys.
+- Providing callback addresses for custom client keys.
+- Other practical functions for cloud storage mounting.
+
+## How to use OpenList APIPages
+
+, log in, and then disable the Device Lock..
+
+## When adding 189 Cloud PC storage: prompt need img validate code: verification code
+
+- Click Edit, write the verification code you just saw into the configuration and click Save
+- Click Edit and turn on the Do not use OCR button
+- Or build it yourself [**Ocr interface**](../configuration/global.md#ocr-api)
+- **189 Cloud** Driver has been replaced with sliding verification code because web login has been replaced.**No longer supports OCR and manual input**, if the verification code needs to be used, please use the addition of `Cookie to log in` or use the `189 Cloud PC` Driver. Note: The 189 Cloud Driver is different from the 189 Cloud PC Driver.
+
+## TLS handshake timeout? / read: connection reset by peer? / dns lookup failed? / connect: connection refused / Client.Timeout exceeded while awaiting headers? / no such host?
+
+For network problems such as these, please troubleshoot and solve them yourself.Don't create any issues for this.
+
+## How to add epub reading
+
+Background --> Settings --> Preview --> Iframe preview, written behind the PDF
+
+```html{2-5}
+ /*The comma below is also oh, don’t copy this comment, start copying from the second line*/
+,
+ "epub": {
+ "EPUB.js":"/static/epub.js/viewer.html?url=$e_url"
+ }
+```
+
+Version 3.7.x and higher already support ".epub" reading
+But you need to add it manually (because the database has already been created, it is not good to overwrite it for you, and you will make mistakes)
+If it is the first installation and startup (version 3.7.x and higher), no need to add it manually
+If the secondary directory reverse generation is set, please add the corresponding prefix in [site_url](../configuration/configuration.md#site-url), and then restart OpenList to take effect
+
+### How to quickly locate bugs
+
+If you find a bug, but the `log.log` log is not detailed, you can try to add the `--debug` parameter to start
+
+It is recommended to clear the log file `/log/log.log` in the **OpenList directory before starting with the `--debug` parameter**, so that developers can quickly locate problems later
+
+::: danger
+When using the `--debug` parameter to start, there will be some sensitive data such as **`account password, refresh token`**, etc., so if you need to desensitize before sending it to others
+:::
+
+- **Windows**：`openlist.exe server --debug`
+- **Linux**：`./openlist server --debug`
+- **Mac**: `./openlist server --debug`
+- **Docker**：`docker exec -it openlist ./openlist server --debug` (to be modified, because this command runs OpenList in an already started container, so it will not start a second OpenList)
+
+How to stop the relevant logs after startup? `Ctrl+C` can stop the program (or simply close the program directly)
diff --git a/pages/en/faq/index.md b/pages/en/faq/index.md
new file mode 100644
index 000000000..2e7933f58
--- /dev/null
+++ b/pages/en/faq/index.md
@@ -0,0 +1,3 @@
+# FAQ
+
+`
+ 2. `-`
+ 3. `:`
+ 4. `-::`
+
+ All port numbers must be between 1024 and 65535 (inclusive), and the starting port number of a range must be less than the ending port number.
+
+ For cases where this field is left blank, the server will choose any port between 1024 and 65535 for passive transfer and will not perform any mapping.
+ - Each "mapping group type 1" specifies a single port to be used for passive transfer, and no mapping will be performed for that port.
+ - Each "mapping group type 2" specifies a range of ports, and all ports in that range will be used for passive transfer without any mapping.
+ - Each "mapping group type 3" specifies a listening port to be used for passive transfer, and when the server selects this port, it will return the "response port number" to the client.
+ - "Mapping group type 4" requires that the two ranges before and after the colon `:` have equal lengths. Each "mapping group type 4" forms a one-to-one pairing of port numbers, where each pair is treated as a "mapping group type 3."
+
+ The following are legal formats:
+ - `1024`
+ - `4001-5000,5001-6000:50001-510004000:65535`
+
+ The following are illegal formats:
+ - `1023` (less than 1024)
+ - `65536` (greater than 65535)
+ - `4000, 5000` (space after the comma)
+ - `2000 - 3000 : 4000 - 5000` (spaces are illegal)
+ - `2000-2001:3000-3002` (unequal length of ranges)
+
+ If the field is invalid, the server will choose any port between 1024 and 65535 for passive transfer without performing any mapping.
+
+ The design of port mapping is intended to address the complexity of external port mapping. For example, if the server is running inside a Docker container and uses port 2000 for passive transfer, but Docker maps port 2000 inside the container to port 12000 on the host machine, you can achieve this mapping using the configuration `12000:2000`.
+
+```mermaid
+sequenceDiagram
+ participant Client
+ participant Port Mapping
+ participant Server
+ Client->>Server: Send EPSV command
+ Server-->>Client: Return 12000
+ Client->>Port Mapping: Connect to port 12000
+ Port Mapping->>Server: Forward to port 2000
+```
+
+If there are multiple layers of port mapping between the server and the client, only the port number closest to the client needs to be specified before the `:` symbol, and only the port number closest to the server needs to be specified after the `:` symbol. For example, in the following scenario, you can fill in `2000:5000`:
+
+```mermaid
+sequenceDiagram
+ participant Client
+ participant NAT Traversal Service
+ participant Soft Router Port Forwarding
+ participant Docker Container Port Mapping
+ participant OpenList Process
+ Client->>NAT Traversal Service: 2000
+ NAT Traversal Service->>Soft Router Port Forwarding: 3000
+ Soft Router Port Forwarding->>Docker Container Port Mapping: 4000
+ Docker Container Port Mapping->>OpenList Process: 5000
+```
+
+- FTP Proxy User-Agent Request Header
+
+ Some storage drivers require a User-Agent request header when accessing the FTP server. You can simply use any fake value for this header.
+
+- Force FTP Connection to Use Explicit TLS
+
+ Forces the use of the FTPS protocol, which only encrypts the data stream and not the control stream.
+ If the "Enable FTP Implicit TLS" option is enabled, this option will be ignored.
+
+ If no valid TLS private key and certificate are provided, and this option is not enabled, the server will only accept the FTP protocol.
+
+ If valid TLS private key and certificate are provided, but this option is not enabled, the server will accept both the FTP and FTPS protocols.
+
+ If no valid TLS private key and certificate are provided, but this option is enabled, the FTP server will fail to start.
+
+- Enable FTP Implicit TLS
+
+ Uses the FTPS protocol, which encrypts both the data stream and the control stream. This makes it incompatible with FTP and FTPS (explicit) protocols.
+
+ When this option is enabled, the "Force FTP Connection to Use Explicit TLS" option will be ignored.
+ If no valid TLS private key and certificate are provided but this option is enabled, the FTP server will fail to start.
+
+- FTP TLS Private Key Path
+
+ The path to the TLS private key file. Leaving it empty or providing an invalid path means TLS will not be enabled.
+
+ Enabling TLS may require the client to access the server using a domain name, though the "FTP Server Public Address" can still be an IP address.
+
+- FTP TLS Certificate Path
+
+ The path to the TLS certificate file. Leaving it empty or providing an invalid path means TLS will not be enabled.
+
+## SFTP Configurations
+
+| Field | Meaning | Example Value |
+| ------ | ------------------------------ | --------------------------------------------------------- |
+| enable | Whether enabled | `true` / `false` |
+| listen | (Allowed access IP mask)\:port | `":5222"` (default) / `"0.0.0.0:22"` / `"127.0.0.1:2222"` |
diff --git a/pages/en/guide/advanced/index.md b/pages/en/guide/advanced/index.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/pages/en/guide/advanced/ipa.md b/pages/en/guide/advanced/ipa.md
new file mode 100644
index 000000000..7bfd61b04
--- /dev/null
+++ b/pages/en/guide/advanced/ipa.md
@@ -0,0 +1,98 @@
+---
+categories:
+ - guide
+ - advanced
+top: 70
+---
+
+# IPA install
+
+## 1. IPA native installation
+
+You can directly upload the ipa file.
+But for **ios>=16**, you need to name the ipa file: `original file name@bundle-identifier.ipa`, that is, you need to add `@bundle-identifier` on the original basis, in which `bundle-identifier` is the `CFBundleIdentifier` of Info.plist in the IPA package. Such as:
+
+- aszs@rn.notes.best.ipa
+ Recommended to use [ipa-renamer](https://github.com/Xhofe/ipa-renamer) to rename your ipa files automatically and quickly.
+- If you are a mobile phone user, you can also rename the IPA file, but you must know the format mentioned above, but there is no mobile phone renaming software, please solve it yourself...
+
+### Tips
+
+- **.ipa installation requires https and a valid certificate** , not just a package can be installed without a signature
+ - How to change the name of the computer version
+
+ `
+3. Is there any benefit to this installation?
+ - See the flow chart below for explanation
+
+```mermaid
+---
+title: Is there any benefit to this installation?
+---
+flowchart TB
+ A-->B
+ subgraph A[original process]
+ C[First download the application from OpenList]-->D[find the downloaded software]
+ D-->E[click on the software and select share in the upper right corner]
+ E-->F[find the troll icon]
+ F-->G[jump into the troll software to install]
+ G-->H[install and delete the software]
+ end
+ subgraph B[troll process]
+ I[Click the OpenList troll install button and click the pop-up window prompt]-->J[enter the troll app and wait for download]
+ J-->K[after downloading, click the install button]
+ end
+```
diff --git a/pages/en/guide/advanced/mcp.md b/pages/en/guide/advanced/mcp.md
new file mode 100644
index 000000000..1adcd9ae1
--- /dev/null
+++ b/pages/en/guide/advanced/mcp.md
@@ -0,0 +1,157 @@
+---
+categories:
+ - guide
+ - advanced
+top: 20
+---
+
+# MCP
+
+[MCP (Model Context Protocol)](https://modelcontextprotocol.io) is an open protocol that standardizes how applications provide context and tools to Large Language Models (LLMs). OpenList implements MCP as a **Streamable HTTP** transport endpoint, enabling AI agents and MCP clients to interact with file storage.
+
+With the OpenList MCP endpoint, you can:
+
+- List files and directories
+- Get file or directory details
+- Obtain download links
+
+## How to Enable
+
+1. Open the [Configuration File](../../configuration/configuration.md#mcp)
+2. Set `mcp.enable` to `true`:
+
+```json{2}
+ "mcp": {
+ "enable": true
+ }
+```
+
+3. Restart OpenList for the change to take effect
+4. The MCP endpoint is now available at `http[s]://your-domain:port/mcp`
+
+## MCP Client Configuration
+
+To connect an MCP client (such as an AI coding agent that supports MCP) to OpenList, use the following configuration:
+
+**Transport type**: Streamable HTTP
+
+**URL**: `http[s]://your-domain:port/mcp`
+
+**Authentication**: Token Authentication. The token is your OpenList login token — include it directly in the `Authorization` header of each request (e.g. `Authorization: `). Do **NOT** add a `Bearer` prefix. Obtain the token from your OpenList account settings page or via the API.
+
+::: warning
+OpenList's authentication middleware reads the `Authorization` header value as-is. Adding a `Bearer ` prefix will result in authentication failure. Use `Authorization: ` only.
+:::
+
+**Protocol version**: `2025-11-25` (also compatible with `2025-06-18`)
+
+**Session handling**: A session is created on `initialize` and identified via the `MCP-Session-Id` response header. You must include this header in subsequent requests.
+
+## Available Tools
+
+### `openlist.fs.list`
+
+List files and directories under a mount path that the current user can access.
+
+**Parameters**:
+
+| Parameter | Type | Required | Description |
+| ---------- | --------- | -------- | ---------------------------------------------- |
+| `path` | `string` | Yes | Mount path to list, e.g. `"/"` or `"/movies"` |
+| `refresh` | `boolean` | No | Refresh the directory listing before returning |
+| `password` | `string` | No | Optional password for protected paths |
+| `page` | `integer` | No | 1-based page number (default: 1) |
+| `per_page` | `integer` | No | Page size (default: all items) |
+
+**Response**: Returns file list with name, size, type, modification time, thumbnail, hash info, and storage details.
+
+### `openlist.fs.get`
+
+Get file or directory details for a mount path that the current user can access.
+
+**Parameters**:
+
+| Parameter | Type | Required | Description |
+| ---------- | -------- | -------- | ------------------------------------------------ |
+| `path` | `string` | Yes | Mount path to inspect, e.g. `"/movies/demo.mp4"` |
+| `password` | `string` | No | Optional password for protected paths |
+
+**Response**: Returns file details including name, size, type, modification time, raw URL, readme, header, provider, and related files at the same level.
+
+### `openlist.fs.link`
+
+Return usable link information for a file path that the current user can access.
+
+**Parameters**:
+
+| Parameter | Type | Required | Description |
+| ---------- | -------- | -------- | ----------------------------------------------- |
+| `path` | `string` | Yes | File mount path, e.g. `"/movies/demo.mp4"` |
+| `password` | `string` | No | Optional password for protected paths |
+| `type` | `string` | No | Optional link type forwarded to storage drivers |
+
+**Response**: Returns link information including direct URL, proxy URL, download URL, HTTP headers, content length, concurrency, and part size (for multi-part downloads).
+
+## Protocol Details
+
+### Transport
+
+OpenList implements the MCP **Streamable HTTP** transport. The endpoint accepts:
+
+- `POST /mcp` — Main endpoint for all MCP JSON-RPC requests
+- `GET /mcp` — Returns `405 Method Not Allowed` with `Allow: POST, DELETE` (used for CORS preflight validation)
+- `DELETE /mcp` — Terminates an active session (requires `MCP-Session-Id` header)
+
+### Authentication
+
+The MCP endpoint reuses OpenList's authentication middleware. Requests must include a valid `Authorization` header with a valid user token. The session is bound to the authenticated user — a user cannot use sessions belonging to other users.
+
+### Session Lifecycle
+
+1. **Initialize**: Client sends `initialize` request. Server returns a `MCP-Session-Id` response header.
+2. **Notify Initialized**: Client sends `notifications/initialized` to mark the session as ready.
+3. **Tool Calls**: Client sends `tools/list` and `tools/call` requests with the `MCP-Session-Id` header.
+4. **Ping**: Client may send `ping` to keep the session alive.
+5. **Cleanup**: Sessions expire after 30 minutes of inactivity. Global maximum: 128 sessions per server, 16 sessions per user. The least recently used sessions are evicted first.
+
+### Protocol Version
+
+Supported protocol versions: `2025-11-25` (default), `2025-06-18`.
+
+The server returns its protocol version during `initialize` negotiation. Subsequent requests must carry a compatible `MCP-Protocol-Version` header matching the negotiated version.
+
+### Error Codes
+
+| Code | Meaning |
+| ------ | ---------------------------------- |
+| -32700 | Parse error |
+| -32600 | Invalid request |
+| -32601 | Method not found |
+| -32602 | Invalid params |
+| -32603 | Internal error |
+| -32000 | Bad request (missing headers, etc) |
+| -32001 | Session/user not found |
+| -32002 | Session not initialized |
+| -32003 | Permission error |
+
+## Example: Using with AI Coding Agents
+
+Many AI coding assistants support the MCP protocol and can be configured to use OpenList as a file system tool. Below is an example configuration (e.g., for VS Code or Claude Desktop):
+
+```json
+{
+ "mcpServers": {
+ "openlist": {
+ "type": "http",
+ "url": "https://your-domain:port/mcp",
+ "headers": {
+ "Authorization": "YOUR_OPENLIST_TOKEN"
+ }
+ }
+ }
+}
+```
+
+Replace `YOUR_OPENLIST_TOKEN` with your actual OpenList authentication token, which can be obtained from the OpenList management panel.
+
+> **Warning**: Do **NOT** prefix the token with `Bearer `. The `Authorization` header value must be the token itself, nothing else.
diff --git a/pages/en/guide/advanced/meta.md b/pages/en/guide/advanced/meta.md
new file mode 100644
index 000000000..2fdf1ee7e
--- /dev/null
+++ b/pages/en/guide/advanced/meta.md
@@ -0,0 +1,83 @@
+---
+categories:
+ - guide
+ - advanced
+top: 80
+---
+
+# Meta
+
+Most settings in meta information apply to `All Roles`. The `Read Users` and `Write Users` fields are exceptions — they allow you to restrict access to specific users.
+
+## Path
+
+The path for this meta to take effect.
+
+## Password
+
+Password required to access this path.
+
+- Meta information password will not take effect when accessed using `WebDav`
+
+::: danger Notes
+If you want the password to be effective in subfolders, please check `Apply to sub folder` after the password. Do not check `Write` and then check `Apply to sub folder`
+
+The correct check example is shown below. If you configure the options correctly, if you check the wrong option `Write` and then check `Apply to sub folder`, it will cause anyone to have permission to write dangerous operations
+
+
+
+
+
+:::
+
+## Read Users
+
+A whitelist of users allowed to read this path. If the list is non-empty, only the selected users can access the path; all other users will be denied access.
+
+- Users are selected by name in the management interface
+- Check `Apply to sub folder` to also restrict sub-directories
+
+## Write Users
+
+A whitelist of users allowed to write to this path. If the list is non-empty, only the selected users can perform write operations (upload, create, rename, move, delete) on this path.
+
+- Users are selected by name in the management interface
+- Check `Apply to sub folder` to also restrict sub-directories
+
+## Write Content Bypass
+
+Allow any user to make directory, create new file and upload files, bypassing user-level write permission checks.
+
+## Hide
+
+The objects to hide of this path, One regular expression (in `Golang`) per line
+
+- Meta information hiding can take effect when accessed using `WebDav`
+
+## Readme
+
+The Readme to render while enter this path, support markdown content or markdown link.
+
+- Show at bottom of list
+- The automatically rendered file name is: **`readme.md`**
+
+## Header
+
+The Readme to render while enter this path, support markdown content or markdown link.
+
+- Show at top of list
+- The automatically rendered file name is: **`top.md`**
+ - Files can not be displayed in the list, for example `readme.md` is not displayed in the list
+ - Backstage --> Settings --> Global --> Hidden files --> Add newline `/\/top.md/i`
+
+## Apply to sub folder
+
+Apply this meta to sub folder of specific path
+
+## :warning: Tips
+
+Regarding hidden, users without permissions can search for hidden folders/files, solutions:
+
+:white_check_mark: If you want to hide the folder in a folder, create a new Yuan information alone, and select the folder we want to hide,，Hidden if you want to hide everything, write directly`.*`
+
+:x: You cannot directly fill in the meta information of the root directory `/`, and then fill in the folder we want to hide, the error case [View details](https://github.com/alist-org/alist/issues/4494) > 
diff --git a/pages/en/guide/advanced/offline-download.md b/pages/en/guide/advanced/offline-download.md
new file mode 100644
index 000000000..e32cbaccd
--- /dev/null
+++ b/pages/en/guide/advanced/offline-download.md
@@ -0,0 +1,198 @@
+---
+categories:
+ - guide
+ - advanced
+top: 50
+---
+
+# Offline download
+
+## Please read this tip before use
+
+::: warning Please read the following tips carefully
+There are two kinds of software with offline download function
+
+The two usages are the same, and the software configuration is set in advance (see the following instructions for specific configuration),
+
+Then go back to the front-end interface, **find the folder you want to upload offline files to, and you can manually enter the folder**
+
+Then find the offline download button in the lower right corner, and choose to use Aria2 download or qBittorrent download (>v 3.11.0)
+
+If you use **docker**, please map the following two default paths by yourself. (mapped to the same directory on the host machine)
+
+- **/opt/openlist/data/temp/aria2**
+- **/opt/openlist/data/temp/qBittorrent**
+
+:::
+
+::: danger OpenList ≥ 3.42.0
+OpenList Version ≥ 3.42.0 View [Allow all cloud disks to call other cloud disks' offline download tools](../../configuration/other.md)
+
+- ≥ 3.42.0 If you want to use offline download, you need to configure a temporary folder in the background before you can use it (otherwise it will only show **SimpleHttp**)
+- manage ==> settings ==> other （ **https://example.com/@manage/settings/other** ）
+ - If you want to [use/configure] PikPak for offline downloading
+ 1. Mount PikPak storage
+ 2. Set Pikpak temp dir in the background
+ 3. Select any folder of this account as a temporary directory
+ - If multiple PikPaks are mounted and you want to use that account for offline downloading, then select the directory of that account as the temporary directory.
+
+**The following applies only to configuration instructions**
+
+:::
+
+### Aria2
+
+[**Click to view instructions for use**](../../configuration/other.md)
+
+### qBittorrent
+
+#### Docker Compose
+
+```yaml
+# docker-compose.yml
+services:
+ openlist:
+ image: 'openlistteam/openlist:latest'
+ container_name: openlist
+ volumes:
+ - ./config/openlist:/opt/openlist/data
+ - ./temp/qBittorrent:/opt/openlist/data/temp/qBittorrent
+ ports:
+ - '5244:5244'
+ environment:
+ - PUID=0
+ - PGID=0
+ - UMASK=022
+ restart: unless-stopped
+ networks:
+ openlist:
+ aliases:
+ - openlist
+ qbittorrent:
+ image: lscr.io/linuxserver/qbittorrent:latest
+ container_name: qbittorrent
+ environment:
+ - PUID=0
+ - PGID=0
+ - WEBUI_PORT=8080
+ volumes:
+ - ./config/qbittorrent:/config
+ - ./temp/qBittorrent:/opt/openlist/data/temp/qBittorrent
+ ports:
+ - 8080:8080
+ restart: unless-stopped
+ networks:
+ openlist:
+ aliases:
+ - qbittorrent
+networks:
+ openlist:
+```
+
+#### Windows
+
+(Here we take the Windows side as an example, I don’t know if there is one on the Linux side)
+First of all, we need to configure the default values on the client side of **`qBittorrent`**
+According to [source code](https://github.com/alist-org/alist/blob/main/internal/bootstrap/data/setting.go#L159-L162), we know that the default values are admin:adminadmin@localhost:8080/
+
+- **ip**: localhost
+- **port**: 8080
+- **user**: admin
+- **password**: adminadmin
+
+1. We fill in the above parameters into the **`qBittorrent`** client, after configuration, we go to the OpenList front end to download offline (**method refer to the description at the beginning**)
+ - If you are prompted after submitting the offline link: **Qbittorrent not ready**, try restarting both OpenList and qBittorrent
+2. Default value configuration view address: (The link may also change position based on subsequent optimization)
+ - **https://github.com/OpenListGo/alist/blob/main/internal/offline_download/qbit/qbit.go#L28**
+ - `{ *** Value: "http://admin:adminadmin@localhost:8080/", Type: conf.TypeString, *** } `
+
+3. Use **`qBittorrent`** to offline `.torrent` type files
+ - Although you cannot directly add offline `.torrent` type files, you can save the country with a curve Reference: [View method](https://github.com/alist-org/alist/issues/2459#issuecomment-1354870010)
+
+4. You can configure it yourself not to delete after the download is complete, but to do seeding, the default is `0`, and it will be deleted immediately after uploading
+ - Modification location: **OpenList background** --> **Settings** --> **Qbittorrent seedtime** option, set the time you need to configure, the unit is `minute`, after the set seeding time is reached, it will automatically delete
+
+5. **We can also customize, instead of using the default presets**
+ - Modification location: **OpenList Manage** --> **Settings** --> **Qbittorrent url** option, just follow the modification
+ 
+
+#### Precautions
+
+1. Appeared in the background qBittorrent task: **`torrent parse timeout`**, parsing timed out
+2. The torrent can be parsed, but **`The system cannot find the path specified.`** appears when uploading.
+
+ The above two methods are most likely caused by the qBittorrent software itself, probably because of the green version and the modified version that have undergone some functional castration modifications. It is recommended to go to the official website to download and install it to restore it (the conclusion drawn by myself after stepping on the pit)
+ - **qBittorrent** official website: **https://www.qbittorrent.org/**
+ - **qBittorrent-Enhanced-Edition** GitHub: **https://github.com/c0re100/qBittorrent-Enhanced-Edition**
+
+3. Because the `v2.8.3` API is used, the minimum version of qBittorrent should be `4.4.0beta2` or `4.3.8` official version
+4. If **qBittorrent** sets the ip where alist is located to be exempt from authentication, you can directly omit the user name and password before `@` (configured on the **qBittorrent** client side)
+ - 3 and 4 are not mentioned in the video.
+ **qBittorrent** Video Tutorials
+
+
`https://your.openlist.domain/api/auth/sso_callback?method=sso_get_token`
`https://your.openlist.domain/api/auth/sso_get_token`
`https://your.openlist.domain/api/auth/get_sso_id` | + | Valid post logout redirect URIs | Leave blank | + | Web origins | Leave blank | + + ::: + +##### 3.7.1.3. Retrieve JWT public key + +- In the left menu, find `Clients`, select the newly created Client to enter the settings page. +- In the Client settings page, switch to the `Keys` tab. +- Copy the content in the `Public Key` field for later use in OpenList configuration. +- If the public key is not visible, click `Generate RSA Keys` to generate it. + +##### 3.7.1.4. Retrieve Client Secret + +- In the Client settings page, switch to the `Credentials` tab. +- Copy the content in the `Client Secret` field for later use in OpenList configuration. + +#### 3.7.2. OpenList Setup + +Fill in the following parameters in OpenList's SSO configuration: + +- **SSO login enabled:** `yes` +- **SSO login platform:** `OIDC` +- **SSO client id:** Keycloak Client ID (from [Create Client](#_3-7-1-2-create-client) above) +- **SSO client secret:** Keycloak Client Secret (from [Retrieve Client Secret](#_3-7-1-4-retrieve-client-secret) above) +- **SSO oidc username key:** `preferred_username` or as per your Mapper settings +- **SSO organization name:** `master` (from [Create Realm](#_3-7-1-1-create-realm) above) +- **SSO application name:** `OpenList` (from [Create Client](#_3-7-1-2-create-client) above) +- **SSO endpoint name:** `https://your.keycloak.domain/realms/{realm-name}` (where realm-name matches the organization name) +- **SSO jwt public key:** from [Retrieve JWT public key](#_3-7-1-3-retrieve-jwt-public-key) above +- **SSO auto register as OpenList account:** Enable as needed +- **SSO compatibility mode:** `no` (enable if compatibility is required) + +Adjust claims and endpoints based on your specific Keycloak deployment if needed. +For detailed operations, refer to the [Keycloak official OIDC documentation](https://www.keycloak.org/documentation). diff --git a/pages/en/guide/advanced/strm.md b/pages/en/guide/advanced/strm.md new file mode 100644 index 000000000..b8407c602 --- /dev/null +++ b/pages/en/guide/advanced/strm.md @@ -0,0 +1,10 @@ +--- +categories: + - guide + - advanced +top: 10 +--- + +# Generate Strm + + diff --git a/pages/en/guide/advanced/user.md b/pages/en/guide/advanced/user.md new file mode 100644 index 000000000..e3f30e88c --- /dev/null +++ b/pages/en/guide/advanced/user.md @@ -0,0 +1,75 @@ +--- +categories: + - guide + - advanced +top: 140 +--- + +# User + +## Add user + +::: warning Security Notice +Adding a user may expose files and server-side capabilities to another account. Use a strong, unique password, grant only the minimum required permissions, and create accounts only for trusted users. Security incidents resulting from improper user or permission management are the administrator's responsibility. +::: + +## Username + +Username for login. + +## Password + +Password for login. +:::tip +Password is invalid for guest user. + +If you enter an incorrect password 6 times in a row, the current IP will be blocked for 30 minutes and you will not be able to enter your account and password to log in. However, it will not affect other IPs. It will only target IPs that entered 6 incorrect passwords. + +- Restarting will immediately remove the 30-minute ban time + +::: + +## Base path + +The root path that users see when he/she log in. + +Q: **How to allow a user to see multiple folder paths?** + +A: You can create a new [alias](alias.md) storage, add all the paths you need to show the user to the alias, and then point to the newly created alias storage in the user path + +## Permission + +- Can see hides: Can see the hides files and folders +- Access without password: Can access without password +- Add offline download tasks: Add offline download tasks + - ⚠️ Granting a user remote file read/write permissions also grants them the ability to access resources from the server's network context, including internal network addresses. Only grant this permission to fully trusted users. Internal network access resulting from improper permission assignment is not considered a security vulnerability. +- Mkdir or upload: Can make directory or upload files +- Rename: Can rename files and folders +- Move: Can move files and folders +- Copy: Can copy files and folders +- Delete: Can delete files and folders +- Webdav read: Can read files and folders with webdav +- Webdav manage: Can manage files and folders with webdav +- FTP read: Can read files and folders with FTP +- FTP manage: Can manage files and folders with FTP +- Read archives: Read the contents of the file in the compressed package + - After turning on this option, compressed package format files will be previewed by default (as shown in the figure below), which will consume some server traffic, but will not download them all. + - If you want to turn off the preferred preview of the compressed format, **Manage => Setting => Preview by default when opening archives**, this option is turned off, and the preference is the download mode +- Decompress: Decompress compressed package files online +  +  + +## Disabled + +After checking, this user will stop using it and cannot log in. The guest account is disabled by default. If you want to enable the guest account, please close it manually. + +## Tips + +1. Are you worried that visitors can see all files? [**Click to see how to set it up here**](../../faq/why.md#how-do-i-set-it-so-that-visitors-can-only-see-the-content-after-logging-in) +2. **`Guest user is disabled, login please`**: In order to protect your OpenList security, the guest access permission is closed, if you need guest access, open it yourself + - OpenList Manage --> users --> `guest` --> **Disable** uncheck +3. Question about **`Copy/Upload`** + - If you upload (including offline download and upload) large files, or upload a lot of files (hundreds or thousands), it is not recommended to use OpenList to operate, please go to the corresponding network disk official website to operate directly +4. Non-admin users can manage offline download, copy, upload and other operations in the background + - OpenList needs to be upgraded to,
+which is `249163533602609229`
+
+### Cookie acquisition method
+
+The following message is displayed when mounting a 115 cloud. This is because 115 has removed the three client applications of `Windows, Mac, and Linux`.
+
+```json
+{
+ "state": 0,
+ "error": "登录失败，系统已下架！如果你有电脑端的使用需求，我们诚挚邀请你下载体验115产品专属客户端“115浏览器”或在线使用“115网页端(115.com)”，畅享智能高效云生活。",
+ "errno": 0,
+ "message": "登录失败，系统已下架！如果你有电脑端的使用需求，我们诚挚邀请你下载体验115产品专属客户端“115浏览器”或在线使用“115网页端(115.com)”，畅享智能高效云生活。",
+ "code": 0
+}
+```
+
+The cookies you have obtained from these three devices cannot be used. Please obtain the cookies from other devices again to mount them.
+
+#### 1. QRCode scanning method login
+
+::: tip
+Still under active development, please stay tuned!
+:::
+
+#### 2. Log in by manually grabbing Cookies
+
+The `cookie` can be obtained from the browser with your 115 account logined, or packet capture.
+
+::: tip
+Please note that cookies should not end with `;`.
+:::
+
+
+ +#### 3. Get Cookies Using Python Script + +Expand the detailed description to view the tutorial and script source code + +Source code from：[**https://gist.github.com/ChenyangGao/d26a592a0aeb13465511c885d5c7ad61**](https://gist.github.com/ChenyangGao/d26a592a0aeb13465511c885d5c7ad61) + +::: details View source + +```python +#!/usr/bin/env python3 +"扫码获取 115 cookie" +__author__ = "ChenyangGao"
+__version__ = (0, 0, 2)
+__all__ = [
+ "AppEnum", "get_qrcode_token", "get_qrcode_status", "post_qrcode_result",
+ "get_qrcode", "login_with_qrcode",
+]
+if __name__ == "__main__":
+ from argparse import ArgumentParser, RawTextHelpFormatter
+ parser = ArgumentParser(description="""\
+扫码获取 115 cookie
+默认在命令行输出，需要安装 qrcode: pip install qrcode
+ - https://pypi.org/project/qrcode/
+可以指定 -o 或 --open-qrcode 直接打开图片扫码
+""", formatter_class=RawTextHelpFormatter)
+ parser.add_argument("app", nargs="?", choices=("web", "android", "ios", "linux", "mac", "windows", "tv", "alipaymini", "wechatmini", "qandroid"), default="web", help="选择一个 app 进行登录，注意：这会把已经登录的相同 app 踢下线")
+ parser.add_argument("-o", "--open-qrcode", action="store_true", help="打开二维码图片，而不是在命令行输出")
+ parser.add_argument("-v", "--version", action="store_true", help="输出版本号")
+ args = parser.parse_args()
+ if args.version:
+ print(".".join(map(str, __version__)))
+ raise SystemExit(0)
+from enum import Enum
+from json import loads
+from urllib.parse import urlencode
+from urllib.request import urlopen, Request
+AppEnum = Enum("AppEnum", "web, android, ios, linux, mac, windows, tv, alipaymini, wechatmini, qandroid")
+def get_enum_name(val, cls):
+ if isinstance(val, cls):
+ return val.name
+ try:
+ if isinstance(val, str):
+ return cls[val].name
+ except KeyError:
+ pass
+ return cls(val).name
+def get_qrcode_token():
+ """获取登录二维码，扫码可用
+ GET https://qrcodeapi.115.com/api/1.0/web/1.0/token/
+ :return: dict
+ """
+ api = "https://qrcodeapi.115.com/api/1.0/web/1.0/token/"
+ return loads(urlopen(api).read())
+def get_qrcode_status(payload):
+ """获取二维码的状态（未扫描、已扫描、已登录、已取消、已过期等）
+ GET https://qrcodeapi.115.com/get/status/
+ :param payload: 请求的查询参数，取自 `login_qrcode_token` 接口响应，有 3 个
+ - uid: str
+ - time: int
+ - sign: str
+ :return: dict
+ """
+ api = "https://qrcodeapi.115.com/get/status/?" + urlencode(payload)
+ return loads(urlopen(api).read())
+def post_qrcode_result(uid, app="web"):
+ """获取扫码登录的结果，并且绑定设备，包含 cookie
+ POST https://passportapi.115.com/app/1.0/{app}/1.0/login/qrcode/
+ :param uid: 二维码的 uid，取自 `login_qrcode_token` 接口响应
+ :param app: 扫码绑定的设备，可以是 int、str 或者 AppEnum
+ app 目前发现的可用值：
+ - 1, "web", AppEnum.web
+ - 2, "android", AppEnum.android
+ - 3, "ios", AppEnum.ios
+ - 4, "linux", AppEnum.linux
+ - 5, "mac", AppEnum.mac
+ - 6, "windows", AppEnum.windows
+ - 7, "tv", AppEnum.tv
+ - 8, "alipaymini", AppEnum.alipaymini
+ - 9, "wechatmini", AppEnum.wechatmini
+ - 10, "qandroid", AppEnum.qandroid
+ :return: dict，包含 cookie
+ """
+ app = get_enum_name(app, AppEnum)
+ payload = {"app": app, "account": uid}
+ api = "https://passportapi.115.com/app/1.0/%s/1.0/login/qrcode/" % app
+ return loads(urlopen(Request(api, data=urlencode(payload).encode("utf-8"), method="POST")).read())
+def get_qrcode(uid):
+ """获取二维码图片（注意不是链接）
+ :return: 一个文件对象，可以读取
+ """
+ url = "https://qrcodeapi.115.com/api/1.0/mac/1.0/qrcode?uid=%s" % uid
+ return urlopen(url)
+def login_with_qrcode(app="web", scan_in_console=True):
+ """用二维码登录
+ :param app: 扫码绑定的设备，可以是 int、str 或者 AppEnum
+ app 目前发现的可用值：
+ - 1, "web", AppEnum.web
+ - 2, "android", AppEnum.android
+ - 3, "ios", AppEnum.ios
+ - 4, "linux", AppEnum.linux
+ - 5, "mac", AppEnum.mac
+ - 6, "windows", AppEnum.windows
+ - 7, "tv", AppEnum.tv
+ - 8, "alipaymini", AppEnum.alipaymini
+ - 9, "wechatmini", AppEnum.wechatmini
+ - 10, "qandroid", AppEnum.qandroid
+ :return: dict，扫码登录结果
+ """
+ qrcode_token = get_qrcode_token()["data"]
+ qrcode = qrcode_token.pop("qrcode")
+ if scan_in_console:
+ try:
+ from qrcode import QRCode
+ except ModuleNotFoundError:
+ from sys import executable
+ from subprocess import run
+ run([executable, "-m", "pip", "install", "qrcode"], check=True)
+ from qrcode import QRCode # type: ignore
+ qr = QRCode(border=1)
+ qr.add_data(qrcode)
+ qr.print_ascii(tty=True)
+ else:
+ from atexit import register
+ from os import remove
+ from threading import Thread
+ from tempfile import NamedTemporaryFile
+ qrcode_image = get_qrcode(qrcode_token["uid"])
+ with NamedTemporaryFile(suffix=".png", delete=False) as f:
+ f.write(qrcode_image.read())
+ f.flush()
+ register(lambda: remove(f.name))
+ def open_qrcode():
+ platform = __import__("platform").system()
+ if platform == "Windows":
+ from os import startfile # type: ignore
+ startfile(f.name)
+ elif platform == "Darwin":
+ from subprocess import run
+ run(["open", f.name])
+ else:
+ from subprocess import run
+ run(["xdg-open", f.name])
+ Thread(target=open_qrcode).start()
+ while True:
+ try:
+ resp = get_qrcode_status(qrcode_token)
+ except TimeoutError:
+ continue
+ status = resp["data"].get("status")
+ if status == 0:
+ print("[status=0] qrcode: waiting")
+ elif status == 1:
+ print("[status=1] qrcode: scanned")
+ elif status == 2:
+ print("[status=2] qrcode: signed in")
+ break
+ elif status == -1:
+ raise OSError("[status=-1] qrcode: expired")
+ elif status == -2:
+ raise OSError("[status=-2] qrcode: canceled")
+ else:
+ raise OSError("qrcode: aborted with %r" % resp)
+ return post_qrcode_result(qrcode_token["uid"], app)
+if __name__ == "__main__":
+ resp = login_with_qrcode(args.app, scan_in_console=not args.open_qrcode)
+ print()
+ print("; ".join("%s=%s" % t for t in resp['data']['cookie'].items()))
+```
+
+:::
+
+1. You need to install [**Python 3.11.x**](https://www.python.org/downloads/) or above
+2. If the QR code cannot be displayed properly in the `CMD` and `powershell` terminals, you can use the `-o` parameter to generate an image to scan the code, or you need to install an additional terminal
+ 1. Use the `-o` parameter to generate the image method and scan the QR code to confirm
+ - ````python
+ python main.py wechatmini -o
+ ```
+ The devices that can be obtained are as follows. If you do not fill in the device, the default device on the `Web` side will be used
+ `Web`，`android`，`ios`，~~`linux`，`mac`，`windows`~~，`tv`，`alipaymini`，`wechatmini`，`qandroid`
+ ````
+ - `alipaymini` and `wechatmini` They are Alipay Mini Program and WeChat Mini Program.
+ - **Windows、Mac、Linux should not be able to use it anymore. The official client was recently removed from the shelves.**
+ - It is recommended to use some devices that you do not commonly use, otherwise logging in will crowd out the previous ones.
+ ***
+ 2. Additional installation terminal
+ - Windows Store：**https://apps.microsoft.com/detail/9n0dx20hk701?rtc=1&hl=zh-cn&gl=CN**
+ - GitHub Download：**https://github.com/microsoft/terminal/releases**
+ 3. Other ways, solve it yourself
+
+---
+
+Execute the command and obtain the QR code. Scan the QR code on the APP to obtain `Cookie`
+
+##### 3.1. Direct Execution
+
+```shell
+PS C:\Users\233\Desktop\115> python --version
+Python 3.12.2
+PS C:\Users\233\Desktop\115> python main.py wechatmini
+█▀▀▀▀▀▀▀█▀▀▀▀█▀███▀▀▀█▀█▀▀▀██▀█▀▀▀▀▀▀▀█
+█ █▀▀▀█ █ █▀▄▀█▄▀▀█▀█ ▄█▀▀ █▀█ █▀▀▀█ █
+█ █ █ █▀█ ▄ ▄▀▄ ▀ ▀▄ █▀▄▀█▀█ █ █ █
+█ ▀▀▀▀▀ █▀█ ▄▀▄ ▄ ▄ █ ▄▀▄▀█▀█▀█ ▀▀▀▀▀ █
+█▀██▀▀▀▀▀▀▀ ▄█ ▀█ █▀▀▀ █▀ ▄▄▄ ▀██▀█▀▀▀█
+██▄▀▀▄▀▀▀▀ ▄██▀▄██▀██▄█ █▀▀▀ ▀▀▀▄▄▀ ▄▀█
+█ ▀██▀████ ▀ ▀ ▀ █▀ ▀▀▄▄▀▄ █▄▀▄▄ ▀▀▀█
+█ ▄▀▀█▄▀█▀▀██ ▀▀▀▀ ▄▀ ▀███▀██▀▄▀▀▄▄ █
+██▄█ ▄▀▀█▄ ▀█▄▀▄▄ █ █▀ ▄▀▀ ▄▀█▀█▀█▀█
+███▄ █ ▀ ▀█ █▄ ▀▀▀▀█▀█▀█ ▄▀▀ ▄ █ ██▄█
+█ █▀▀▀█ █ ▄▄▀▄▄▀ █▄▄▀█▀ █▀▄█ ▀▀▀ ▀█▀ █
+█ █ █ █▄ ▄▀ █▀▀ ▀▄▀▀█▀▀ █ █ ▄█▀▄▄ ▀█
+█ ▀▀▀▀▀ █▀ █▄▀ ▀ ▄█▄ █▄▀▀█▄ ▀ ▀▄▄ ▄▄ █
+▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
+```
+
+Execute the command directly. The QR code will appear in the terminal for display.
+
+##### 3.2. Using the -o parameter
+
+```bash
+PS C:\Users\233\Desktop\115> python --version
+Python 3.12.2
+PS C:\Users\233\Desktop\115> python main.py wechatmini -o
+```
+
+After using the `-o` parameter, a QR code image will pop up automatically
+
+### Rapid upload
+
+- **v.3.27.0** version Enhanced Rapid upload: You can directly upload files with `Alibaba Cloud Disk Open` by copying
+ - The premise is to upload the file from 115 Rapid upload to Alibaba Cloud Disk Open, the file already exists in Alibaba Cloud Disk Open, otherwise it is a normal copy task.
+ - If you want to transfer 115 cloud disk files to Alibaba Cloud Disk in seconds, you need to turn on the Rapid upload option of Alibaba Cloud Disk, otherwise it will be uploaded in normal mode.
+ If you want to upload files using Miaochuan, it is recommended to build an OpenList locally on your home computer and add a `local storage` and `115 cloud disk` to copy Miaochuan to save resources.
+
+ +### Offline Download + +**v3.37.0** and above versions support calling `115 Cloud` offline download function in OpenList +Select in the lower right corner and select `115 Cloud` for offline download options + +- Support: `magnet`, `http`, `ed2k` links + Only 115 Cloud is supported for offline download. If it is not 115 Cloud, the following error message will be displayed, Although the offline download prompt was successfully added, an error will be prompted in the background. +- unsupported storage driver for offline download, only 115 Cloud is supported +  +- Some tips for using 115 offline downloads: + 1. Out of sync problems may occur (manual refresh in the lower right corner ) + 2. Currently, when the download is successful, completed tasks in the offline list are deleted. + 3. 115 Task URLs that are already in the offline list cannot be added again. +
+ +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` + +## 115 Share + + + +`Sharing link ID`1 and `Sharing link extraction code`2 How to obtain them respectively is clear at a glance. + +### Root folder ID + +The default is empty and the entire directory file is mounted. + +The folder IDs are the root folder ID and the subfolder ID respectively. The following demonstrates how to obtain the `shared root folder directory ID`1 and `other subfolder directory ID`2 respectively. + +#### 1. shared root folder directory ID + +Open developer mode (F12) and clear all requests first. Before we enter the folder, clear all requests first. + +Let's click on the root folder to enter. There will be a new request on the right, and then select `Load` to see the ID (cid) of our folder. + + + +#### 2. other subfolder directory ID + +Open developer mode (F12) and clear all requests first. Before we enter the folder, clear all requests first. + +There will be a new request on the right, then select `Preview` and expand it to see the IDs (cid) of other subfolders. + + + +### Error Tips + +For example, the 115 sharing link shown in the picture below has expired, but the sharing link can still be opened. + + + +But when adding and saving, the following error code will appear: + +`Failed init storage but storage is already created: failed init storage: failed to get share snap: json: cannot unmarshal number into Go struct field .data.shareinfo.share_state of type string ` + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/115_open.md b/pages/en/guide/drivers/115_open.md new file mode 100644 index 000000000..a2997b375 --- /dev/null +++ b/pages/en/guide/drivers/115_open.md @@ -0,0 +1,171 @@ +--- +top: 698 +categories: + - guide + - drivers +--- + +# 115 Open + +::: tip +Developed with the official [**115 Open Platform API**](https://open.115.com) +::: + + + +## 1. Necessary Conditions + +An **115** account is required. + +::: warning Note +The speed and stability are related to the local network environment, the network environment of the 115 server, and the performance of the machine running OpenList. +::: + +## 2. Preparation for Access + +### 2.1. Register an Application on the Open Platform (optional; no need to create if using the built-in key pair of OpenList/public welfare server/self-built server) + +::: tip +Please register the application according to the requirements of the 115 Open Platform. +::: + +Open Platform address: [115 Open Platform: https://open.115.com](https://open.115.com) + +### 2.2. Obtain Tokens + +1. Visit [api.oplist.org](https://api.oplist.org) **⚠️ If using a public welfare server/self-built server, visit the address of the public welfare server/self-built server**. + +2. Select **115 Network Disk Verification** from the drop-down box. + +  + +  + +3. If you are using the built-in key pair of `OpenList (or public welfare server/self-built server)` (i.e., you do not have application information from the 115 Open Platform), please configure according to `3.1`, `3.2`, and `3.3`: + + 3.1. Check `Use parameters provided by OpenList`. + + 3.2. Leave both `Client ID (ClientID/AppID)` and `Application Secret (AppKey/Secret)` blank. + + 3.3. Click the `Get Token` button. + +  + +  + +4. If you are using your own created OAuth client ID and secret, please configure according to `4.1`, `4.2`, and `4.3`: + + 4.1. Do not check `Use parameters provided by OpenList`. + + 4.2. Enter your `AppId` in `Client ID` and your `AppSecret` in `Application Secret`. + + 4.3. Click the `Get Token` button. + +  + +  + +5. In the pop-up window, log in to your 115 account and authorize OpenList to access your 115 network disk. + +  + +6. After successful authorization, the page will display your `Access Token` and `Refresh Token`. Please copy and save these two tokens. + +  + +  + +## 3. Adding 115 Network Disk to OpenList + +### 3.1. Configuration Instructions + +#### 3.1.1. Root Folder ID + +The default root directory ID is: `0` + +Open the 115 network disk official website, and when clicking to enter the folder to be set, click the number after `cid` in the URL. + +For example,
+
+The `root folder ID` of this folder is `249163533602609229`.
+
+### 3.2. Start Adding
+
+1. Open the management interface of OpenList and click `Storage` in the left menu.
+
+2. On the storage list page, click the `Add Storage` button in the upper right corner.
+
+3. Select the driver as `115 Open Platform`.
+
+ 
+
+ 
+
+4. Enter the mounting path, such as: `115`.
+
+5. Enter the root folder ID obtained above in `Root Folder ID` (please refer to [3.1.1. Root Folder ID](#_3-1-1-root-folder-id)).
+
+6. Enter the obtained `Refresh Token` and `Access Token` in the refresh token (if not obtained, please refer to [2. Preparation for Access](#_2-preparation-for-access)).
+ - 115's token refresh mechanism does not require AppKey and has IP-based rate limiting, so it is implemented using [local logic](https://github.com/OpenListTeam/115-sdk-go).
+
+7. Click the `Add` button to complete adding the 115 network disk.
+
+### 3.3. Method for Refreshing Access Token
+
+```mermaid
+sequenceDiagram
+ participant OpenList
+ participant 115
+ OpenList->>115: Post refresh_token
+ 115->>OpenList: Get new access_token and refresh_token
+```
+
+## 4. Notes
+
+::: warning Handling Method for Token Leakage
+If the Token is accidentally leaked, you can go to the 115 device login management to解除应用授权 (revoke application authorization).
+
+- 115 APP: [iOS, Android] versions need to be ≥ 35.11.0
+- 115 Web端: [https://115.com/?mode=device_manage](https://115.com/?mode=device_manage)
+
+ When it expires, the following content will be prompted:
+
+ ```json
+ failed get objs: failed to list objs: code: 40140116, message: no auth
+ ```
+
+An account can obtain two `Refresh tokens` in the same application. After the third acquisition, the first obtained `Refresh token` will expire. Using the first `Refresh token` will prompt the above error.
+:::
+
+## 5. Using Other APP IDs to Obtain Refresh Tokens (Not Yet Implemented)
+
+::: tip
+Under development, the tutorial has not been updated yet. Stay tuned!
+:::
+
+## 6. Mobile QR Code Authorization PKCE Mode (Not Yet Implemented)
+
+::: tip
+Under development, the tutorial has not been updated yet. Stay tuned!
+:::
+
+## 7. Default Download Method Used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/123.md b/pages/en/guide/drivers/123.md
new file mode 100644
index 000000000..bf7ede4e9
--- /dev/null
+++ b/pages/en/guide/drivers/123.md
@@ -0,0 +1,154 @@
+---
+top: 695
+categories:
+ - guide
+ - drivers
+---
+
+# 123 Pan / Share / Link
+
+
+
+::: warning
+123 Cloud Disk has implemented anti-leech measures for this **reverse-engineered driver**. To avoid unnecessary disputes, it is recommended that users choose the more standard 123 Open Platform driver. If you continue to use this driver, you need to enable a **local proxy** to prevent anti-leech detection.
+
+- [123 Open Platform](./123_open.md)
+
+:::
+
+## Personal
+
+Free user 1G traffic download, unlimited upload, multi-IP sharing is prohibited
+
+::: warning
+
+```json
+failed get objs: failed to list objs:当前账号存在安全风险，请使用短信验证码或者微信进行登录。
+```
+
+solution:
+
+- This is because the 123 cloud disk officially prohibits the mounting on strange devices, If you are mounted locally, `or` Windows Server server mount `to open the 123 cloud disk web page to log in or modify a password once
+
+:::
+
+https://www.123pan.com/
+
+Just fill in the account password.
+
+### Username
+
+The mobile phone number used to log in
+
+### Password
+
+The password used to log in
+
+### Root folder file_id
+
+Enter the folder you want to mount, the last string of the official website URL, such as:
+
+
+
+### Recommendations
+
+- It seems that the 123 API has a limited number of loads each time, so if you load hundreds of files in a folder at one time, an error may be reported
+- It is recommended to A useful approach is not to put too many sub-items in the same folder.
+
+## Link
+
+only adapted to the authentication function, the link also needs to be filled in by yourself, like [UrlTree](/en/guide/drivers/url_tree), fill in the direct link copied in 123 direct link.
+
+::: danger Please read this reminder carefully
+Since 123 Cloud Disk Direct Link is a paid service with a storage quota, if you decide to add more storage, please ensure you set up passwords, metadata, and other protective measures to prevent malicious traffic.
+
+After configuring these settings, test them in incognito mode to confirm everything is working correctly. If you fail to implement adequate anti-theft measures and experience malicious traffic overload, you will be held responsible for the consequences.
+
+:::
+
+First open **`123 Cloud Disk Direct Link Management`**: **https://www.123pan.com/DirectLink** Set an authentication key in the lower right corner, and then turn on the authentication status switch
+
+
+
+- Open Settings 123 Cloud Disk Settings: **https://www.123pan.com/Setting** and find the account ID [`1` label in the picture below]
+- How to activate direct link? (You need to activate membership to use it)
+ - Find the folder you want to open, right-click on `Enable Direct Link Space`, and after opening it, you will see a link icon in the folder [Tag `2` in the picture below]
+- How to get a direct link to a file? [Tag `3` in the picture below]
+ - Enter the folder that has 'enabled direct link space', find the file you need to obtain, right-click 'Get direct link', and fill in the OpenList configuration after obtaining it.
+ 
+
+### Fill in example
+
+- **Origin urls**：Fill in the direct link to the files we copied one by one
+ - It supports creating different folders like [UrlTree](/en/guide/drivers/url_tree), and supports filling in the file size and modification time (four options are provided for use, like the UrlTree filling, refer to the second example of the picture below)
+ - File size unit: `B` bytes. For example, if you want to write a 1MB file, it is 1048567 bytes. You can search for the specific byte conversion in your browser (you can leave it blank).
+ - File modification time: It is `Unix timestamp`. You can search in the browser for the specific conversion (you can leave it blank).
+
+ Fill in the format:
+
+ ```txt
+ [FileSize:][Modified:]URL
+ 127451136:1694101621:https://vip.123pan.cn/1812xxx499/123-link-Test/linuxqq_3.2.0-16736_mips64el.deb
+ [FileSize:]URL
+ 134847488:https://vip.123pan.cn/1812xxx499/123-link-Test/linuxqq_3.2.0-16736_loong64.deb
+ [Modified:]URL
+ 1694101621:https://vip.123pan.cn/1812xxx499/123-link-Test/linuxqq_3.2.0-16736_arm64.AppImage
+ URL
+ https://vip.123pan.cn/1812xxx499/123-link-Test/linuxqq_3.2.0-16736_x86_64.AppImage
+ ```
+
+- **Private key**：
+ - You can set up the direct link management page yourself and turn it on. Please turn it on.
+- **Uid**：
+ - Account ID in the account settings page
+- **Valid duration**：
+ - The file direct link validity period, in minutes, is filled in by default to 30 minutes
+
+
+
+
+
+## Share
+
+Fill in the driver's **`share key`** and optional **`share password`** (if there is a password, you need to fill in), the root folder ID defaults to `0` to display all files
+
+### Fill in the example
+
+
+
+### Share Password
+
+Fill in if you have it, don't if you don't
+
+### Root folder file_id
+
+The ID of the root directory of the shared link is `0`, displaying all files
+
+If you only want to display a certain folder, open the developer mode (F12) to clear all requests (maybe 123 prohibits debug debugging, you need to close this by yourself to continue)
+
+Find the request on the right side of the picture in the upper-level directory request of the directory you want to display, then click `Response`, find the format button `{}` below and format it, and you can see the relevant directory ID.
+
+If you are not sure whether the directory ID is correct or not, there is a directory name under the directory ID
+
+
+
+## The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/123_open.md b/pages/en/guide/drivers/123_open.md
new file mode 100644
index 000000000..eb2d378ba
--- /dev/null
+++ b/pages/en/guide/drivers/123_open.md
@@ -0,0 +1,120 @@
+---
+top: 696
+categories:
+ - guide
+ - drivers
+---
+
+# 123 Open
+
+https://www.123pan.com/developer
+
+
+
+## 1. Developer Application
+
+::: warning
+This driver uses the [developer authorization mode](https://123yunpan.yuque.com/org-wiki-123yunpan-muaork/cr6ced/hpengmyg32blkbg8), which grants direct management access to the cloud drive associated with the provided public/private key pair, , so you **must use your client id and client secret**.
+
+The acquired token counts as a login device
+
+:::
+
+**Application Method**: Visit the [123 Open Platform Official Website](https://www.123pan.com/developer), read the Developer Agreement, fill in the required fields marked with `*`, and apply for the `client_id` and `client_secret`.Typically, after your application is approved the keys will be sent to your email **remember to check your spam folder, and please keep the keys sent by email safe**.
+
+1. Sign the Developer Agreement
+
+2. Fill out the application materials
+
+3. Wait for the review notification
+
+**Reference Tutorial**: [OpenListTeam/discussions#55](https://github.com/orgs/OpenListTeam/discussions/55)
+
+### 2. Get UID
+
+The method to obtain the "Cloud Drive UID" required during the application process is as follows:
+
+1. **Log in to the 123 Cloud Drive web platform**
+
+ Visit the 123 Cloud Drive official website and log in with your account (phone number).
+
+2. **Go to the "Settings" page**
+
+ After logging in, click on the profile picture or username at the top right, and select "Settings" (or directly visit: ).
+
+3. **Find the "Account ID"**
+
+ In the "Account Settings" or "Security Settings" section, locate the "Account ID," which is your "Cloud Drive UID." Copy it and paste it into the application form.
+
+## 4. Add in OpenList
+
+### RefreshToken
+
+**keep it empty**
+
+### Client ID
+
+Enter your client ID
+
+### Client Secret
+
+Enter your client secret
+
+### Root Folder ID
+
+The default root directory ID is: `0`
+
+Open the official website of 123 Cloud Drive, navigate to the folder you want to set, and then click the number following `homeFilePath` in the URL.
+
+For example,
+
+API queries can also be used
+
+The `root folder ID` of this folder is `123456`.
+
+### Direct Link
+
+Disabled by default; returns standard download links. When enabled, returns CDN direct links, which require VIP access and will consume direct link traffic quota.
+
+Users must manually enable direct link space: Go to the 123 Cloud Drive official website, right-click a folder under the **root directory**, and select `Enable Direct Link Space (VIP)`.
+
+
+
+### Direct Link Private Key
+
+Prerequisite: Enable `Direct Link`.
+
+Leave empty to disable direct link authentication and return permanent direct links.
+
+To prevent your site resources from being maliciously downloaded or stolen, you can configure an "Authentication Key" in 123 Cloud Drive's **Direct Link** → **Basic Function Configuration** → **URL Authentication**, and then set **Authentication Status** to **Enabled**.
+
+After entering the key, the obtained direct links will automatically include authentication parameters.
+
+
+
+### Direct Link Valid Duration
+
+Prerequisite: Enable `Direct Link` and configure the `Direct Link Private Key`.
+
+Used to generate the expiration timestamp in the direct link authentication parameters.
+
+## The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[local proxy]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[302]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/139.md b/pages/en/guide/drivers/139.md
new file mode 100644
index 000000000..aab2d4867
--- /dev/null
+++ b/pages/en/guide/drivers/139.md
@@ -0,0 +1,219 @@
+---
+top: 692
+categories:
+ - guide
+ - drivers
+---
+
+# 139Yun
+
+
+
+Cloud disk address: ****
+:::
+
+### OpenList fill in examples
+
+- `Authorization`: fill in only the content after `Basic `.
+- New personal folder ID: enter the target folder first, then use the current `currentCatalogID`.
+
+
+
+
+
+## Share mount
+
+The `share` type allows you to mount shared content from other 139Yun users. You need a valid authorization to access download APIs.
+
+### LinkID format
+
+### LinkID 格式
+
+`LinkID` supports the following formats:
+
+- Single share: directly enter the share link ID
+- Password-protected share: `link_id#password`
+- Multiple shares: separate multiple entries with commas or new lines. For example: `share_a,share_b,share_c` or `share_a#pass1,share_b`
+
+### Get share link ID
+
+1. Open the share link in your browser, e.g. `https://yun.139.com/w/#/share/xxxxx`
+2. The path segment after `/share/` is the share link ID (e.g. `xxxxx`)
+3. If the share is password-protected, append `#password` after the link ID
+
+### Configuration
+
+- **Type**: `share`
+- **LinkID**: one or more share link IDs (see format above)
+- **Authorization** or **MailCookies + Username + Password**: required for authentication (same as other types)
+- **Root folder ID**: not used for share type. The share link ID in `LinkID` determines the mounted content.
+- **Cloud ID**: leave empty
+
+Notes:
+
+- Upload operations are not supported for the `share` type.
+- When mounting multiple shares, the root directory shows each share as a separate folder.
+- `${data_path}` resolves to the share root for path-based operations.
+
+## Download method
+
+The default download method is 302 redirection. If a player such as PotPlayer cannot play through 302, switch that mount to proxy mode or mount it through WebDAV with `WebDAV Native Proxy`.
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/163music.md b/pages/en/guide/drivers/163music.md
new file mode 100644
index 000000000..f42673f64
--- /dev/null
+++ b/pages/en/guide/drivers/163music.md
@@ -0,0 +1,51 @@
+---
+top: 677
+categories:
+ - guide
+ - drivers
+---
+
+# 163 Music Drive
+
+
+
+163 Music Drive can only upload music and other operations on the mobile phone, and the web page cannot operate
+
+## Cookie
+
+Open **https://music.163.com** and then open the F12 developer mode
+
+Open a request at will, just carry the `Cookie` to find the following two parameters and fill in the OpenList` Cookie`
+
+- **\_\_csrf** 、**MUSIC_U**
+ 
+
+## Song Limit
+
+You can only get 200 songs by default. If you exceed you, you can modify this option
+
+### Precautions
+
+1. If there are many list files, it is recommended to open pagination loading, otherwise it will not be loaded
+2. Cloud space can only upload audio format files, and cannot upload other format files
+
+### The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/189.md b/pages/en/guide/drivers/189.md
new file mode 100644
index 000000000..830fa4e08
--- /dev/null
+++ b/pages/en/guide/drivers/189.md
@@ -0,0 +1,105 @@
+---
+top: 694
+categories:
+ - guide
+ - drivers
+---
+
+# 189Cloud
+
+
+
+::: tip
+The web -side login has been replaced with sliding verification code, **no longer supports OCR or manual input**. If the verification code needs to be used, please use the add `Cookie` to log in
+
+If you encounter "Device ID does not exist, secondary device verification required",Open the 189 Account website at , log in, and then disable the Device Lock..
+
+:::
+
+## 189CloudTV
+
+Uses the TV interface of 189 Cloud Drive, with the fewest mounting steps.
+
+(Some users have reported throttling issues. If you experience video playback stuttering, black screens, or failure to load, please switch to the 189 Cloud PC client.)
+
+1. When mounting, select 189CloudTV. Leave the login parameters blank. If you are unsure, **just fill in the mount path**.
+
+2. After clicking save, simply return to the storage management page. You can choose to log in by scanning a QR code or click the link to log in (for link login, if you are unsure, it is recommended to **right-click the link and open it in a new window**).
+
+ 
+
+3. After entering, select SMS login. Once logged in, return to the storage management page. Disable and re-enable the storage to use it normally (you may need to refresh the page).
+
+ 
+
+## Personal Cloud
+
+### Username
+
+the phone number used to log in
+
+### Password
+
+password for login
+
+### Root folder ID
+
+The string at the end of the official website url, such as:
+
+- https://cloud.189.cn/web/main/file/folder/-11 -> `-11`
+- https://cloud.189.cn/web/main/file/folder/71398114617385472 -> `71398114617385472`
+
+ 
+
+### Family transfer
+
+Give 189 Cloud adds Personal's `Family Transfer option`, which is convenient for users without VIP, and a large number of family cloud spaces upload.
+
+- Note: The old upload interface family cloud will still limit the upload quantity, so `Rapid upload` and ` Old Upload` will not take effect
+
+## Family Cloud
+
+(189 Cloud PC Driver Only) Use a computer browser, open the developer tool (F12), switch the emulation device and select the mobile device
+
+Open https://h5.cloud.189.cn/main.html#/family, enter the folder you want to mount, you can see the request in the network, and then find the required parameters:
+
+
+
+### OpenList fill in examples：
+
+#### 189 Cloud
+
+Fill in the account1and password2,Then click one request in the request, just bring `Cookies`3, click on one at will Then fill in,Cookie expires time is unknown
+
+
+
+#### 189 CloudPC
+
+
+
+Video reference: **https://www.bilibili.com/video/BV16A4y197De**
+
+## suggestion
+
+It is recommended to use the 189 Cloud PC first, [**Notes click to view.**](../../faq/howto.md#when-adding-a-189-cloud-storage-the-device-id-does-not-exist-and-a-secondary-device-verification-is-required)
+
+### The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/alias.md b/pages/en/guide/drivers/alias.md
new file mode 100644
index 000000000..1e1eafee9
--- /dev/null
+++ b/pages/en/guide/drivers/alias.md
@@ -0,0 +1,10 @@
+---
+top: 997
+categories:
+ - guide
+ - drivers
+---
+
+# Alias
+
+
diff --git a/pages/en/guide/drivers/alias_text.md b/pages/en/guide/drivers/alias_text.md
new file mode 100644
index 000000000..abd6a59c8
--- /dev/null
+++ b/pages/en/guide/drivers/alias_text.md
@@ -0,0 +1,282 @@
+**Alias** is a feature that allows multiple different cloud drives or storage paths to be merged into a unified directory. By combining paths, content from different cloud drives or folders can be displayed in the same interface, simplifying access and management.
+
+For example: Cloud Drive Account 1 and Cloud Drive Account 2 both contain a folder named `Movies`, but the contents of these folders may not be identical.
+
+- **Previously (Virtual Path)**:
+
+ You could only mount them to two different paths separately, like:
+ - `CloudDrive1/Movies`, `CloudDrive2/Movies`
+ - `Movies/CloudDrive1`, `Movies/CloudDrive2`
+
+- **Now (Alias)**:
+
+ An aggregated folder (Movies) is provided, which can contain content from both Cloud Drive 1 and Cloud Drive 2 simultaneously.
+
+Folders with the same name will be automatically merged into one. The contents of the folder are the sum of the contents of all folders with the same name. Regarding how this driver handles files with the same name, please refer to the [Path conflict policies](/en/guide/drivers/alias#path-conflict-policies) section later.
+
+For Example:
+
+
+
+In the diagram, we can see that two different folders are merged into one. Files and folders with the same name are also combined, and unique ones are displayed separately.
+
+Example explanations:
+
+- **Example 1**: `riluo.jpg` is unique to Cloud Drive 1, so it is shown separately.
+- **Example 2**: Both folders contain a `video` folder, but the contents of these folders will be merged. Subfolders also follow the **same-name merging** display rule. Both folders contain two videos, but one of them has the same name. After merging according to the **same-name merging** rule, three video files will be displayed in total.
+
+## Paths filling method
+
+There are two ways to fill in:
+
+1. The first one is that you can only fill in the path of the subfolder and the folder with the same name must be used at the end. It is not recommended to use :x:
+ - Paths filling example:
+ ```
+ /file1/locala
+ /file2/localb
+ ```
+2. The second is to directly mount the root folder path, using the `renaming` method, it is strongly recommended to use :heavy_check_mark:
+ - Paths filling example:
+
+ ```
+ #Example 1 Directly write the root folder
+ merge: /file1
+ merge: /file2
+
+ #Example 2 Mount different path folders for merging
+ merge: /file1/localtest233
+ merge: /file2/videos/TV series
+ merge: /file3 2/TV/Domestic TV Series/Station XX
+ ```
+
+According to the second method, we can `merge` and display different folders, which is convenient and quick.
+
+## Path conflict policies
+
+The three configuration items—**Reading conflict policy**, **Writing conflict policy**, and **Putting conflict policy**—determine how the Alias handles files or folders with the same name and identical paths in the backend drivers. Their values and corresponding behaviors are as follows:
+
+### Reading conflict policy
+
+Determines the behavior for handling files with the same name when downloading, copying (as source files), and extracting (as source files) (excluding moving).
+
+- Get the file corresponding to the first conflict path: Select the file from the first available path (from top to bottom in the Paths) where the file exists.
+
+- Load balancing on a per-file basis: Randomly select one file from the available duplicates.
+
+- Load balancing on a per-part basis:
+ - During 302 downloads, copying, or extracting, it falls back to the **Load balancing on a per-file basis** strategy.
+ - When using local proxy downloads, each transmitted chunk is randomly assigned to one of the duplicate files. This requires the backend driver to support Range requests. For details on setting the chunk size, refer to the section [Download concurrency, Download part size](/en/guide/drivers/alias#download-concurrency-download-part-size).
+ - This policy achieves the actual effect as shown in the figure. It is important to note that this diagram is only intended to conveniently demonstrate the operation of this policy. The statement that "participating load-balanced files with the same name have different contents" is **not** a correct usage of this driver. OpenList does not guarantee stable or correct results under such circumstances, nor will it address any issues arising from this usage scenario. Furthermore, the actual minimum size for file splitting is 1 KiB, not 1 byte, so the effect depicted in the diagram will not occur in the stable version.
+
+ 
+
+::: tip
+When a copy operation involves multiple source paths and target paths, the Alias will first attempt to pair source and target paths that belong to the same drive. Only for target paths that cannot be matched in this way will the method specified by the **Reading conflict policy** be used to select a source path.
+
+For example, when copying:
+
+- `DriverA/source/file.txt`
+- `DriverB/source/file.txt`
+
+to:
+
+- `DriverB/target/`
+- `DriverA/target/`
+- `DriverC/target/`
+
+The Alias driver will perform the following operations:
+
+1. Copy `DriverA/source/file.txt` to `DriverA/target/`, since both are located in Driver A.
+2. Copy `DriverB/source/file.txt` to `DriverB/target/`, since both are located in Driver B.
+3. For `DriverC/target/`, which has no matching source in the same driver, select `file.txt` from either Driver A or Driver B according to the **Reading conflict policy**, and copy it to `DriverC/target/` via an upload operation (creating a copy task).
+
+:::
+
+::: tip
+The move operation involves a matching process similar to that of the copy operation. For target paths that cannot be matched with a source path from the same driver, the Alias will randomly select from the still-unmatched source paths to create a pairing (**one-to-one correspondence**). If the number of source paths exceeds the number of target paths, the unmatched source paths will be deleted. If the number of source paths is less than the number of target paths, the move operation will fail. The matching behavior for the move operation is not affected by the **Reading conflict policy**.
+
+For example, in the case described for the copy operation, since there is no source path corresponding to `DriverC/target/`, the move operation will fail.
+
+As another example, when moving:
+
+- `DriverA/source/file.txt`
+- `DriverB/source/file.txt`
+- `DriverD/source/file.txt`
+- `DriverE/source/file.txt`
+- `DriverG/source/file.txt`
+
+to:
+
+- `DriverA/target/`
+- `DriverB/target/`
+- `DriverC/target/`
+- `DriverF/target/`
+
+The Alias will perform the following operations:
+
+1. Move `DriverA/source/file.txt` to `DriverA/target/`.
+2. Move `DriverB/source/file.txt` to `DriverB/target/`.
+3. Randomly select one file from Driver D, E, or G, and move it to `DriverC/target/` (by creating a move task, which is essentially an upload followed by deletion). Let's assume E is selected.
+4. Randomly select one file from the remaining unmatched drivers (D or G), and move it to `DriverF/target/`. Let's assume G is selected.
+5. Delete `DriverD/source/file.txt`.
+
+:::
+
+### Writing conflict policy
+
+Determines the behavior for renaming or deleting files/folders with the same name, as well as creating folders within identically named folders.
+
+- **Disable writing**: Prohibits rename, delete, and folder creation operations.
+- **Write into the first conflict path**: Operates on the driver containing the target path that appears first (top to bottom) in the configured path list.
+- **Allow unique path**: Executes the operation only if the target path is unique (exists in only one backend path). Otherwise, the operation is prohibited.
+- **Allow full conflict paths**: Executes the operation only if the target path exists in **all** configured backend paths, applying the operation across all of them. Otherwise, the operation is prohibited.
+- **Allow unique path and full conflict paths**: Allows the operation when the target path is either unique or exists in all configured backend paths.
+- **Write into all conflict paths**: Forwards the operation to all backend paths where the target path exists.
+
+::: tip
+If the above explanation is unclear, you can refer to the following example.
+
+- In Driver A, the file exists: `file1.txt`
+- In Driver B, the files exist: `file1.txt`, `file2.txt`, `file3.txt`
+- In Driver C, the files exist: `file1.txt`, `file3.txt`
+
+Configured backend paths:
+
+```
+test:DriverA
+test:DriverB
+test:DriverC
+```
+
+Then:
+
+- Since the sub-path `/file1.txt` is valid in all configured paths (`DriverA/`, `DriverB/`, `DriverC/`), `/file1.txt` is referred to as a **full conflict path**.
+- Since the sub-path `/file2.txt` is valid only under the single backend path `DriverB/`, `/file2.txt` is referred to as a **non-conflict path** or **unique path**.
+- Since the sub-path `/file3.txt` exists under both `DriverB/` and `DriverC/`, and the number of backend paths where it exists is neither 1 nor the maximum (3), `/file3.txt` is neither a non-conflict path nor a full conflict path.
+
+When renaming any file to `file4.txt`, the corresponding files in the following drivers will be renamed:
+
+| Writing conflict policy | file1.txt | file2.txt | file3.txt |
+| ----------------------------------------- | ---------------------------- | --------- | ------------------ |
+| Disable writing | Fails | Fails | Fails |
+| Write into the first conflict path | Driver A | Driver B | Driver B |
+| Allow unique path | Fails | Driver B | Fails |
+| Allow full conflict paths | Driver A, Driver B, Driver C | Fails | Fails |
+| Allow unique path and full conflict paths | Driver A, Driver B, Driver C | Driver B | Fails |
+| Write into all conflict paths | Driver A, Driver B, Driver C | Driver B | Driver B, Driver C |
+
+:::
+
+### Putting conflict policy
+
+Determines the behavior for uploading to, copying to, moving to, or extracting to folders with the same name.
+
+- **Disable putting**, **Put into the first conflict path**, **Allow unique path**, **Allow full conflict paths**, **Allow unique path and full conflict paths**, **Put into all conflict paths**: These options function identically to their counterparts in the **Writing conflict policy**.
+- **Random load balancing**: Randomly selects one valid path for the upload.
+- **Weighted random load balancing based on remaining space**: Retrieves the remaining free space of all valid paths, skips paths that fail to report free space or have insufficient space for the file being uploaded, and then randomly selects from the remaining valid paths, weighting the choice by their remaining capacity. If none of the valid paths that successfully reported free space have enough capacity for the file, **a random selection is made from among the valid paths that failed to report capacity**.
+- **Strict weighted random load balancing based on remaining space**: Retrieves the remaining free space of all valid paths, skips paths that fail to report free space or have insufficient space for the file being uploaded, and then randomly selects from the remaining valid paths, weighting the choice by their remaining capacity. If none of the valid paths that successfully reported free space have enough capacity for the file, **an error message is returned directly**.
+
+::: tip
+The load balancing mechanisms within the **Reading conflict policy** and the **Putting conflict policy** are two largely unrelated features. Informally speaking, the load balancing in the **Reading conflict policy** is analogous to RAID 1, while the load balancing in the **Putting conflict policy** is analogous to RAID 0. For specific use cases of each, please refer to [Advanced / Load balancing](/en/guide/advanced/balance).
+
+If you've understood the above, you'll realize that enabling both **Reading Load Balancing** and **Putting Load Balancing** won't make load balancing more balanced. In fact, this configuration produces effects that are hardly any different from enabling only **Putting Load Balancing**.
+
+:::
+
+::: tip
+The legacy version of the Alias used three Boolean configuration items—**Writable**, **Protect same name**, and **Parallel write**—to implement path conflict policy functionality. The correspondence between the legacy configuration and the new configuration is as follows:
+
+- In the legacy configuration, the **Reading conflict policy** was always set to **Get the file corresponding to the first conflict path**.
+- In the legacy configuration, when **Writable** was disabled, both the **Writing conflict policy** and the **Putting conflict policy** were set to **Disabled**.
+- When **Writable** was enabled, the **Writing conflict policy** and the **Putting conflict policy** were both determined as follows:
+ | | Parallel write disabled | Parallel write enabled |
+ | -------------------------- | -------------------------------------- | ----------------------------------------- |
+ | Protect same name enabled | Allow unique path | Allow unique path and full conflict paths |
+ | Protect same name disabled | Write/Put into the first conflict path | Write/Put into all conflict paths |
+
+:::
+
+## File consistency check
+
+When enabled, the driver will filter out paths where the **size or hash value** differs from other copies during the process of collecting valid paths. This is a safety measure, and whether it is enabled has relatively minor impact. It is recommended to enable this option when using the **Load balancing on a per-part basis** reading policy.
+
+Regardless of whether this option is enabled, the Alias does not actively calculate file hashes. Instead, it performs a best-effort match using the hash values returned by the backend drivers.
+
+Different types of hash values returned by backend drivers will not lead to misjudgment. For example, if Driver 1 returns the MD5 of a file and Driver 2 returns the SHA1 of the file, even with this option enabled, the Alias will not consider either path from Driver 1 or Driver 2 invalid simply because the file's MD5 and SHA1 are not equal.
+
+## The download method to use
+
+When adding **`alias`**, `Web Proxy` and `Webdav Policy` are not modified by default. The storage path filled in the Paths path can be `302`, `Local Proxy`, `Download Proxy URL`, three modes Mixed Playback Mixed Playback is possible.
+
+If you checked `Web Proxy`, the storage filled in by the Paths path, if there is a 302 mode playback, it will be played in transit (local proxy mode) at that time, and it will become a proxy mode. If the Webdav policy is also changed, it will also change.
+
+Of course, it is up to you to choose whether to change the mode.
+
+### What if you don’t know how the cloud disks you added are different?
+
+1. You can go to the bottom of the corresponding document to view the document, there is a flow chart description
+ - If there is a 302, the 302 method is used by default. If there are only local proxy and download proxy URLs, the default is to use the local proxy, provided that you have not manually selected
+2. You can check when adding storage, select the corresponding storage to view, for example, let’s check the methods of Alibaba Cloud and 115 respectively
+ - As you can see from the figure below, Alibaba Cloud Disk has the option of `web proxy`, and `webdav policy` defaults to 302. It can be judged that Alibaba Cloud Disk uses the 302 method by default
+ - As you can see from the figure below, the 115 network disk does not have the option of `web proxy`, and the `webdav strategy` defaults to the local proxy. It can be judged that the 115 network disk uses the local proxy mode by default
+ 
+
+## Proxy Range
+
+You need to enable `Web Proxy` or` Webdav Native Proxy` to take effect. Currently only applicable to：`alias`、`139Yun`、`OpenList V3`.
+
+- The `139Yun` driver, when this option is enabled, can resolve issues that occur when a proxy is enabled but the download link does not return the correct HTTP status code, such as problems with video playback or lack of support for resume downloads.
+- The `Alias` driver is added to meet specific use cases, for example, when `139Yun` uses a 302 redirect. By enabling the `Alias` proxy, downloads can use `139Yun` with the 302 redirect, while video playback can use the proxy-enabled `Alias`, reducing unnecessary load.
+- The `OpenList` driver is added to support server-side OpenList mounting with `139Yun` using a 302 redirect. Locally, OpenList can be mounted via the proxy-enabled `OpenList` to access the server's OpenList for video playback, etc., to avoid consuming server bandwidth. This also allows for data-free video streaming on mobile networks.
+
+## Download concurrency, Download part size
+
+**Storage Settings:**
+
+- Alias (Alias) Drive
+- Local Proxy
+- Path: / Cloud Drive Mount Path
+- Download Concurrency: 10
+- Download Chunk Size: 1024
+
+**Effect:**
+
+- Client → OpenList Alias Drive: Uses 1 connection
+- OpenList Alias Drive → Cloud Drive: Supports 10 concurrent connections, with actual concurrency limited by the cloud drive.
+
+```mermaid
+graph LR
+ A[Client] -->|Connection 1| B[OpenList Alias Drive]
+ B -->|Concurrent Connection 1| C[Cloud Drive]
+ B -->|Concurrent Connection 2| C
+ B -->|Concurrent Connection 3| C
+ B -->|Concurrent Connection 4| C
+ B -->|Concurrent Connection 5| C
+ B -->|Concurrent Connection 6| C
+ B -->|Concurrent Connection 7| C
+ B -->|Concurrent Connection 8| C
+ B -->|Concurrent Connection 9| C
+ B -->|Concurrent Connection 10| C
+```
+
+- Single-threaded speed is slower, but it supports concurrency: Using the alias drive allows concurrent downloads, significantly improving speed.
+- Video watching and download acceleration: The experience is enhanced by increasing concurrency.
+- Copying from alias drive to other drives: File transfer is also accelerated in this case.
+
+**Friendly Reminder:** Please do not abuse this feature. Excessive use may cause abnormal activity on the cloud drive account, and you will bear the consequences.
+
+**Configuration Options:**
+
+- max_concurrency: Sets the maximum concurrency for the local proxy. The default is 64, and setting it to 0 means no limit on concurrency.
+
+## Other instructions
+
+If you are using `Windows`, the following situation will occur, and folders with different capitalization will also be regenerated.
+
+For example, Local 1 and Local 2 have a lowercase v for `video` respectively, and the folder OneDrive has an uppercase V `Video` folder.
+
+Then a lowercase video folder will be generated, which contains only `local 1, local 2` files merged by two folders.
+
+At the same time, the uppercase `Video` will gather the files of the three folders.
+
+This is because Windows is case-insensitive, video and Video will be considered as the same folder, you will not have this problem if you switch to Linux or Mac.
diff --git a/pages/en/guide/drivers/alidoc.md b/pages/en/guide/drivers/alidoc.md
new file mode 100644
index 000000000..a8abe5bbf
--- /dev/null
+++ b/pages/en/guide/drivers/alidoc.md
@@ -0,0 +1,78 @@
+---
+top: 677
+categories:
+ - guide
+ - drivers
+---
+
+# AliDoc
+
+::: danger Please read the notes carefully
+This driver is currently not officially maintained by the project team.
+:::
+
+Mount DingTalk Docs web storage in OpenList.
+
+Official website:
+
+- DingTalk Docs:
+
+### 2.2. Obtain Tokens
+
+1. Visit [api.oplist.org](https://api.oplist.org) **⚠️ If using a public welfare server/self-hosted server, visit the address of the public welfare server/self-hosted server.**
+
+2. Select **AliYun Drive App Login** from the drop-down menu.
+
+ 
+
+ 
+
+3. If you are using the built-in key pair of `OpenList (or public welfare server/self-hosted server)` (i.e., you do not have application information from the AliYun Drive Open Platform), configure according to `3.1`, `3.2`, and `3.3`:
+
+ 3.1. Check `Use parameters provided by OpenList`.
+
+ 3.2. Leave both `Client ID (ClientID/AppID)` and `App Secret (AppKey/Secret)` blank.
+
+ 3.3. Click the `Get Token` button.
+
+ 
+
+ 
+
+4. If you are using your own created OAuth client ID and secret, configure according to `4.1`, `4.2`, and `4.3`:
+
+ 4.1. Do not check `Use parameters provided by OpenList`.
+
+ 4.2. Enter your `AppId` in `Client ID` and your `AppSecret` in `App Secret`.
+
+ 4.3. Click the `Get Token` button.
+
+ 
+
+ 
+
+5. In the pop-up window, scan the code to log in to your AliYun Drive.
+
+ 
+
+6. After successful authorization, the page will display your `Access Token` and `Refresh Token`. Please copy and save these two tokens.
+
+ 
+
+ 
+
+## 3. Add AliYun Drive to OpenList
+
+### 3.1. Start Adding
+
+1. Open the OpenList management interface and click `Storage` in the left menu.
+
+2. On the storage list page, click the `Add Storage` button in the upper right corner.
+
+3. Select the driver as `AliYun Drive (Oauth2)`.
+
+4. Enter the mount path, such as `aliyun-drive`.
+
+5. Enter the root folder ID obtained above in `Root Folder ID`. If using the root directory, enter `root`. See [Configuration Instructions/Root Folder ID](#_3-2-1-root-folder-id).
+
+ 
+
+ 
+
+6. Enter the refresh token obtained above in the refresh token field (if not obtained, refer to [Preparation for Access](#_2-preparation-for-access)).
+
+7. If you are using the OAuth client ID and secret provided by `OpenList (or public welfare server/self-hosted server)`, configure according to `6.1`, `6.2`, and `6.3`:
+
+ 6.1. Check `Use online api`.
+
+ 6.2. Leave both `Client ID (ClientID/AppID)` and `App Secret (AppKey/Secret)` blank.
+
+ 6.3. Enter `https://api.oplist.org/alicloud/renewapi` in `Api url address`. If using a `public welfare server/self-hosted server`, enter the corresponding server address.
+
+ 
+
+ 
+
+8. If you are using your own created OAuth client ID and secret, configure according to `7.1`, `7.2`, and `7.3`:
+
+ 7.1. Do not check `Use online api`.
+
+ 7.2. Enter your `AppId` in `Client ID (ClientID/AppID)` and your `AppSecret` in `App Secret (AppKey/Secret)`. See [Configuration Instructions/Client ID, Secret](#_3-2-2-client-id-secret).
+
+ 7.3. Leave `Api url address` blank.
+
+ 
+
+ 
+
+9. In the `Instant Upload` option, select whether to enable the instant upload function (optional). See [Configuration Instructions/Instant Upload](#_3-2-3-instant-upload).
+
+10. In `Removal Method`, select the way to delete files (optional), default is recycle bin. See [Configuration Instructions/Removal Method](#_3-2-4-removal-method).
+
+11. In `Cloud Drive Type`, select the cloud drive type (optional), default is `Default`. See [Configuration Instructions/Cloud Drive Type](#_3-2-5-cloud-drive-type).
+
+12. In `Livp Download Format`, select the format for downloading live photos (optional), default is `Jpeg`. See [Configuration Instructions/Livp Download Format](#_3-2-6-livp-download-format).
+
+13. In `Internal Upload`, select whether to enable internal upload (optional), default is off. See [Configuration Instructions/Internal Upload](#_3-2-7-internal-upload).
+
+14. Click the `Add` button to complete adding AliYun Drive.
+
+### 3.2. Configuration Instructions
+
+#### 3.2.1. Root Folder ID
+
+The default is `root`, displaying all cloud drive contents. If you only want to display contents within a certain folder, change it to `file_id`.
+
+Open the AliYun Drive official website, and when clicking into the folder to be set, click the string after the URL.
+
+For example, https://www.alipan.com/drive/folder/5fe01e1830601baf774e4827a9fb8fb2b5bf7940
+
+The file_id of this folder is `5fe01e1830601baf774e4827a9fb8fb2b5bf7940`.
+
+
+
+#### 3.2.2. Client ID, Secret
+
+Normal users can leave it blank. If you have applied for official authorization, you can fill in your own. When blank, it defaults to using those provided by OpenList.
+
+- If using your own developer account, the Oauth token link must also be modified, and you must use your own developer account ID and secret to obtain the refresh token.
+
+#### 3.2.3. Instant Upload
+
+- **Version v.3.22.1** new feature.
+
+ Instant upload requires enabling `Instant Upload` when mounting. The prerequisite for instant upload is that the file already exists in AliYun Drive; otherwise, it will be a normal upload.
+
+ Instant upload calculates the file's `sha1` value (should be correct) without requiring you to calculate it. You just need to upload, and it will automatically calculate after upload completion.
+
+- It uses the interface provided by AliYun Drive's official API. For details, see :point_right: [**Instant Upload Logic**](https://www.yuque.com/aliyundrive/zpfszx/ezlzok#y7lyH).
+
+---
+
+- **Version v.3.27.0** enhances instant upload: files can be instantly transferred between `115 Network Disk` and AliYun Drive by direct copying.
+ - Prerequisite: To instantly transfer a file from AliYun Drive to 115, the file must already exist in 115; otherwise, it will be a normal copy task.
+ - If instantly transferring a file from 115 to AliYun Drive, enable the instant upload option for AliYun Drive; otherwise, it will be a normal upload.
+ It is recommended to locally deploy an OpenList on your home computer, add a `local storage` and `AliYun Drive`, and use copy instant upload to save resources.
+
+#### 3.2.4. Removal Method
+
+If not set, it defaults to deleting to the recycle bin. If space is insufficient, you need to manually clean the recycle bin. If a file is deleted by mistake, please go to the AliYun Drive official website client to retrieve it.
+
+- **Recycle Bin**: Deleting in OpenList will move the file to the network disk recycle bin, occupying cloud drive space, but it can be retrieved later if deleted by mistake.
+- **Delete**: Direct deletion without staying in the recycle bin, not occupying cloud drive space, but cannot be retrieved later if deleted by mistake.
+ - Note: Do not leak the Token obtained from AliYun Drive Open. If leaked by mistake, please immediately:
+ - **Open AliYun Drive app → My → Settings gear icon in the upper right corner → Privacy Settings → Authorization Management → Click OpenList to view and revoke authorization**.
+ - Then rescan the code to authorize for a new refresh token. Revoking authorization will invalidate all previously obtained tokens to protect your account security.
+
+#### 3.2.5. Cloud Drive Type
+
+You can select the cloud drive type according to your needs. When adding a driver using OpenList version v3.25.1 and above, the default selection is `Default`.
+
+- **Default**: For users with a talent level, it defaults to displaying `non-backup file` content; for users without a talent level, it defaults to displaying `backup file` content.
+- **Resource Library**: Corresponding to the `non-backup file content` of the cloud drive.
+- **Backup Disk**: Corresponding to the `backup files` of the cloud drive.
+ After AliYun Drive updated to version `6.0` in July 2024, the backup disk was changed to merge backup files and all files, but in terms of OpenAPI, it still distinguishes between `Resource Library` and `Backup Disk` types.
+ 
+
+#### 3.2.6. Livp Download Format
+
+That is, iOS `live` photos cannot be parsed by non-iOS systems, so they cannot be downloaded. Now, you can choose `Jpeg` or `Mov` according to your needs.
+
+- Jpeg: The cover of the `live` photo.
+- Mov: The video frame of the `live` photo when long-pressed.
+
+#### 3.2.7. Internal Upload
+
+If the server where OpenList is deployed is an AliYun ECS in the Beijing region, turning on this switch can improve file upload speed. Do not turn on this switch for servers that do not meet the requirements, otherwise, upload failures will occur.
+
+- Can `Internal Upload` be used on non-Beijing AliYun ECS? No, because AliYun Drive uses object storage in the Beijing region.
+
+## 4. Other Instructions
+
+### 4.1. Permission Scope
+
+OpenList only obtains cloud drive user (**name, avatar ¹**), (**file access permission ²**), and (**file write permission ³**), without obtaining phone number permission.
+
+Details can be viewed in the following two ways:
+
+1. The **prompt** when scanning the code to obtain the refresh token.
+2. Open **AliYun Drive app → My → Settings gear icon in the upper right corner → Privacy Settings → Authorization Management → Click OpenList** to view.
+ - You can manually revoke permissions at any time if not in use.
+
+### 4.2. About Video Playback
+
+The default player is AliYun Drive's built-in player - **Aliyun Video Previewer**.
+Videos uploaded to the cloud drive will be transcoded into H.264-encoded video streams through the transcoding service. (The benefit is that iOS can play them... Well, it should be like this.)
+
+- For newly uploaded videos, only the first 30s of the video is pre-transcoded by default. The first play will trigger full video transcoding. The transcoded video will be cached, and no retranscoding is needed for subsequent plays.
+- Videos shorter than 30s will not trigger pre-transcoding, and transcoding will only start when played for the first time.
+- Real-time transcoding takes some time.
+- Video qualities are: LD|SD|HD|FHD|QHD.
+
+### 4.3. Inability to View Office Suite Files
+
+> Q: Why can't Office suite files be viewed in AliYun Drive Open?
+>
+> A: ~~Because AliYun Drive has not opened the relevant API, so it cannot be viewed temporarily~~ (Stay tuned.)
+
+### 4.4. Subtitle Loading
+
+Q: How to load subtitles?
+
+A: AliYun Drive Open needs to use the **Aliyun Video Previewer** player, and currently only supports transcoding srt and vtt text format subtitles encapsulated in mkv.
+
+- Currently, only three languages are supported: eng, jpn, chi. Other languages will be lost.
+
+### 4.5. Common Issues
+
+1. ExceedCapacityForbidden
+
+ Q: When playing AliYun Drive videos online, it cannot play and prompts the error: **`ExceedCapacityForbidden`**.
+
+ A: **The user's capacity is exceeded**, restricting playback. You need to expand the capacity or delete unnecessary files to free up space
+ - In OpenList, it prompts: `ExceedCapacity Forbidden: Execeed Capactity Forbidden`.
+ - In AliYun Drive, it prompts: `云盘可用空间不足` (Insufficient available space in cloud drive).
+
+2. Transcoding in progress, please try again later.
+
+ Q: When viewing a video in AliYun Drive, it prompts `Transcoding in progress, please try again later`, and when mounting in OpenList, it prompts: `failed link: failed get link: UserNotAllowedAccessResource: user not allowed access resource for violation`.
+
+ A: It means the account has been frozen (previously, it was directly unable to log in). For specific situations, please check the red content notes at the top.
+
+## 5. The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/autoindex.md b/pages/en/guide/drivers/autoindex.md
new file mode 100644
index 000000000..73c115381
--- /dev/null
+++ b/pages/en/guide/drivers/autoindex.md
@@ -0,0 +1,79 @@
+---
+top: 350
+categories:
+ - guide
+ - drivers
+---
+
+# AutoIndex
+
+The AutoIndex driver is used to mount directory index pages built into HTTP servers, such as the [Nginx Source Index](https://nginx.org/download/) and [Redis Releases](https://download.redis.io/releases/).
+
+This driver essentially scrapes page information directly and requires manually specifying XPaths, making it suitable for scraping pages that are not directory index pages as well.
+
+## Setup Instructions
+
+- **URL:** The website address. If no scheme is included, `https://` will be automatically added. To mount a subpath, append it directly to the end of the URL. For example,
triggers related API operations Cloud Drive
Cloud Drive receives command and begins execution) + A[(Cloud Drive)] + B(You) + C[Use proxy URL] + D{Native proxy} + E==>A==>E + A==>|Directly transferring from cloud drive to you without any loss
302 downloads as fast as possible|B + A-->|Send the cloud disk to the use proxy URL first|C-->|After being forwarded to you by the proxy URL, your download speed depends on the speed of downloading, forwarding, and forwarding on the other end of the proxy URL|B + A-->|Send the cloud drive to the device running OpenList first|D-->|After being forwarded to you by the device running OpenList, your download speed depends on the speed of downloading, uploading, and forwarding on the end where OpenList is built|B +``` + +## Download proxy URL + +When the proxy is turned on without filling in this field, the local machine will be used for transfer by default. + +### 1. Cloudflare Workers + +Here’s the translation: + +You can use Cloudflare Workers as a proxy. Simply fill in your Cloudflare Workers address here. + +The code to set up Workers can be found at [https://github.com/OpenListTeam/OpenList-Proxy/blob/main/openlist-proxy.js](https://github.com/OpenListTeam/OpenList-Proxy/blob/main/openlist-proxy.js). When using it, you need to replace the following variables: + +- `ADDRESS`: Your OpenList address, which must include the protocol header and should not end with a `/`. For example, `https://pan.example.com`. + +- `TOKEN`: The [Token](../../configuration/other.md#token) of the admin account, which can be found in the “Other Settings” section of the OpenList admin page. + +- `WORKER_ADDRESS`: Your Worker address, which is usually the same as the **Download Proxy URL**. + + :warning: Cloudflare Workers free CDN support is only compatible with **http80** and **https443** ports (whether domestic or international), as tested by group members. + +When filling in the **Download Proxy URL** in the OpenList backend configuration, the link should not end with a `/`. + +Detailed text tutorial:
+
+### 2. Universal Binary
+
+You can use another machine as a proxy. Download the program from https://github.com/OpenListTeam/OpenList-Proxy/releases and check the usage instructions with `./openlist-proxy -help`.
+
+Detailed text tutorial:
+
+### 3. Developing on your own
+
+You can develop your own proxy program. The general steps are as follows:
+
+- When downloading, it will request `PROXY_URL/path?sign=sign_value`.
+- In the proxy program, validate the `sign`. The calculation method for `sign` is:
+
+```js
+const to_sign = `${path}:${expireTimeStamp}`
+const _sign = safeBase64(hmac_sha256(to_sign, TOKEN))
+const sign = `${_sign}:${expireTimeStamp}`
+```
+
+`TOKEN` is the [Token](../../configuration/other.md#token) of the administrator account, which can be obtained in the “Other Settings” section of the OpenList management page.
+
+- After validating the signature, request `HOST/api/fs/link` to obtain the file URL and the request headers to include.
+- Use the information to make the request and handle the response.
+
+## Sort related
+
+- **Sort by**: Sort by what
+- **Sort direction**: Whether the sort direction is ascending or descending
+
+::: info
+Some drives use their own sorting method, which may be different.
+:::
+
+## Extract folder
+
+- **Extract to front**: put all folders to the front when sorting
+- **Extract to back**: put all folders to the back when sorting
diff --git a/pages/en/guide/drivers/crypt.md b/pages/en/guide/drivers/crypt.md
new file mode 100644
index 000000000..d4df34c89
--- /dev/null
+++ b/pages/en/guide/drivers/crypt.md
@@ -0,0 +1,222 @@
+---
+top: 996
+categories:
+ - guide
+ - drivers
+---
+
+# Crypt
+
+The Crypt driver provides secure encryption for your files and folders, acting as a two-password-protected vault. Only users with the correct password and salt can access the encrypted content.
+
+**Key Features:**
+
+- File and folder encryption with multiple security levels
+- Password and salt-based protection
+- Compatible with rclone crypt
+- Supports various encryption modes for filenames and directories
+
+::: warning Important Security Notice
+
+1. Read this guide thoroughly before using the Crypt driver
+2. Test the configuration in a local environment before production deployment
+3. **Never modify the configuration after storing encrypted data** - this will make data lost
+4. Keep your password and salt values secure - losing them means losing access to your data
+
+Again, please read the documentation carefully; otherwise, any data loss will be at your own risk!
+:::
+
+## Setup Instructions
+
+1. **Create Storage Location**
+
+ Create an **empty folder** in your existing mounted drive to store encrypted files.
+
+2. **Configure Remote Path**
+
+ Enter the path of the empty folder in the `Remote path` field of your Crypt driver configuration.
+
+ **Example Configuration:**
+ - Original driver path: `/123`
+ - New empty folder: `/123/encrypted_storage`
+ - Remote path setting: `/123/encrypted_storage`
+
+3. **Upload Files**
+
+ Upload files to the newly created Crypt driver mount point. Only files uploaded through the Crypt driver will be encrypted.
+
+ **File Access:**
+ - **Encrypted files**: Located in the remote path, appear scrambled and cannot be opened directly
+ - **Decrypted access**: View and access files normally through the Crypt driver mount point
+
+### Basic Configuration Example
+
+For users new to encryption, use the following default configuration:
+
+
+
+::: danger Please make sure to read the following important notes carefully to ensure understanding!
+
+**Important Declaration:**
+
+- **Do not modify the configuration! Do not modify the configuration! Do not modify the configuration!** Once the configuration is saved, do not modify it again!!! This is repeated for emphasis!
+- **Password** and **Salt** must be remembered! After clicking save, they will be encrypted and cannot be displayed in plain text (the plain text in the image shows the state before saving).
+
+> [**Password Configuration Instructions**](#password)
+>
+> [**Salt Configuration Instructions**](#salt)
+
+---
+
+- **If you have not yet uploaded files within the Crypt driver**, you can modify the password and configuration. **Otherwise, do not modify!**
+- After modifying the configuration, Crypt will attempt to filter illegal files/directories, but illegal data will not be automatically deleted.
+ - **Illegal files/directories** refer to encrypted data generated with a different configuration.
+
+:::
+
+::: warning
+Regarding encryption combinations, there are 5 options available (actually 6), but it’s important to note that if only folder encryption is enabled without encrypting the file names, the configuration will not take effect (as shown in the first example below).
+
+| Filename Encryption | Directory Encryption | Status |
+| ------------------- | -------------------- | ---------- |
+| `Off` | `Enabled` | ❌ Invalid |
+| `Off` | `Disabled` | ✅ Valid |
+| `Standard` | `Disabled` | ✅ Valid |
+| `Standard` | `Enabled` | ✅ Valid |
+| `Obfuscate` | `Disabled` | ✅ Valid |
+| `Obfuscate` | `Enabled` | ✅ Valid |
+
+:::
+
+## Configuration Options
+
+### Filename Encryption
+
+**Default:** `Disabled`
+
+**Available Options:**
+
+| Mode | Security Level | Description |
+| ----------- | -------------- | ----------------------------------------------------------------------------- |
+| `Off` | None | Files keep original names with encrypted suffix (e.g., `file.txt.bin`) |
+| `Standard` | High | **Recommended** - Strong encryption with good security |
+| `Obfuscate` | Low | Simple obfuscation, supports long filenames but may create special characters |
+
+---
+
+In the image below, the left side shows file **name encryption** and folder **name encryption** enabled, while the right side shows the decrypted Crypt driver where files can be viewed.
+
+- **File name encryption not enabled**: Original name + encrypted suffix, as shown in the top left corner
+- **File name encryption enabled**: Fully encrypted file name, content cannot be recognized, as shown in the bottom left corner
+
+
+
+### Directory Name Encryption
+
+**Default:** `Disabled`
+
+Directory encryption requires filename encryption to be enabled. When activated, folder names are also encrypted for enhanced security.
+
+**Configuration Combinations:**
+
+| Filename Encryption | Directory Encryption | Status |
+| ------------------- | -------------------- | ---------- |
+| `Off` | `Enabled` | ❌ Invalid |
+| `Off` | `Disabled` | ✅ Valid |
+| `Standard` | `Disabled` | ✅ Valid |
+| `Standard` | `Enabled` | ✅ Valid |
+| `Obfuscate` | `Disabled` | ✅ Valid |
+| `Obfuscate` | `Enabled` | ✅ Valid |
+
+### Remote Path
+
+The storage location for encrypted files. Can be any mountable drive supported by OpenList.
+
+### Security Parameters
+
+::: danger
+After saving the configuration, both password and salt values are encrypted and cannot be displayed in plain text. Store them securely in a separate location.
+:::
+
+#### Password
+
+::: warning
+Note that passwords exported using `rclone config` are obfuscated and cannot be used directly. Please prefix the password with `___Obfuscated___` before use.
+For example, if the exported password is `abc123xyz`, it should be entered as `___Obfuscated___abc123xyz` in the Crypt driver. +::: + +Primary encryption key. **Must be remembered** - cannot be recovered if lost. + +#### Salt + +::: warning +Note that salts exported using `rclone config` are obfuscated and cannot be used directly. Please prefix the salt with `___Obfuscated___` before use.
+For example, if the exported salt is `abc123xyz`, it should be entered as `___Obfuscated___abc123xyz` in the Crypt driver. +::: + +Secondary encryption key, acts as an additional password layer. **Must be remembered** - cannot be recovered if lost. + +If you don't know what is salt, treat it as a second password. Optional but recommended + +### Advanced Options + +#### Encrypted Suffix + +**Default:** `.bin` + +Custom suffix for encrypted files (only used when filename encryption is disabled). Must start with a dot (e.g., `.abc`, `.encrypted`). + +#### Filename Encoding + +**Default:** `base64` + +**Warning:** Only modify if you understand the implications. Other encoding options are not thoroughly tested and may cause compatibility issues. + +For rclone compatibility, configure this setting in advanced options. + +## Advanced Usage + +### Rclone Compatibility + +The Crypt driver is fully compatible with [rclone crypt](https://rclone.org/crypt). + +**Important Notes:** + +- OpenList Crypt uses `filename_encoding = base64` by default for better long filename support, configure this setting in advanced options when using with rclone +- Case-insensitive filesystems (e.g., Windows with local storage) may cause issues + +## Troubleshooting + +### Startup Errors + +If Crypt shows errors during OpenList startup, it's likely because Crypt starts before its target path is available. + +**Solution:** Set a higher [order number](./common.md#order) for the Crypt driver to delay its initialization. + +### Data Access Issues + +If you cannot access previously encrypted data: + +1. Verify that the password and salt values are correct +2. Ensure the configuration hasn't been modified +3. Check that the remote path is accessible +4. Confirm the filename encoding setting matches your original configuration + +## The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + c1 + end + c1[local proxy]:::someclass==default===>a2[user equipment] + classDef someclass fill:#f96 + b1[Download proxy URL]-.alternative.->a2[user equipment] + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/degoo.md b/pages/en/guide/drivers/degoo.md new file mode 100644 index 000000000..76b707b06 --- /dev/null +++ b/pages/en/guide/drivers/degoo.md @@ -0,0 +1,55 @@ +--- +categories: + - guide + - drivers +top: 587 +--- + +# Degoo + +https://degoo.com/ + +**Authentication methods**: + +1. Username + Password +2. Refresh Token +3. Access Token + +In normal cases, you can log in with your username + password. If you encounter a 429 error, you can log in using tokens. You can obtain the token from the request body or header in your browser. + +## Username + +Your user's name. + +## Password + +Your user's password. + +## Refresh Token + +Refresh token for automatic token renewal, obtained automatically. + +## Access Token + +Access token for Degoo API, obtained automatically. + +## The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/develop.md b/pages/en/guide/drivers/develop.md new file mode 100644 index 000000000..6ff2c1a8e --- /dev/null +++ b/pages/en/guide/drivers/develop.md @@ -0,0 +1,11 @@ +--- +top: 100 +categories: + - guide + - drivers +--- + +# Contribute new storage driver + +Duplicate `drivers/template` to expand the new storage. Please read [CONTRIBUTING](https://github.com/OpenListTeam/OpenList/blob/main/CONTRIBUTING.md) for details. +The design of the driver part of OpenList is easy to expand, no need to modify other files, just create a new package under the back-end project drivers package and reference this package in the `all.go` file. diff --git a/pages/en/guide/drivers/doubao.md b/pages/en/guide/drivers/doubao.md new file mode 100644 index 000000000..d9b34312b --- /dev/null +++ b/pages/en/guide/drivers/doubao.md @@ -0,0 +1,58 @@ +--- +top: 676 +categories: + - guide + - drivers +--- + +# Doubao Drive + + + +Mount [Doubao Drive](https://www.doubao.com/chat/drive/) cloud storage. + +::: danger Security Risk + +Do not use 302 if the storage is public accessible. +Otherwise, the download link may leak sensitive information such as access token or signature. +Others may use the leaked link to **access all your files**. + +::: + +## Root folder ID + +The root folder ID is the parameter value displayed in the address bar when accessing Doubao Drive via a web page. For example, after accessing [Doubao Drive](https://www.doubao.com/chat/drive/), the address bar shows `https://www.doubao.com/chat/drive/AAAAAAAAAAAAAAAAAAAAAAAAAA?tab=myUpload`, where `AAAAAAAAAAAAAAAAAAAAAAAAAA` is the root folder ID. + + + +## Cookie + +Required. Web cookie. Used to refresh token and extract Authorization/DPoP tokens. + +Open browser developer tools, visit [Doubao Drive](https://www.doubao.com/drive/), log in to your account, check the `Network` tab, search for `biz_auth` and open it, find `Cookie` in the `Header`, copy the complete value and fill it in. + + + +OpenList will automatically extract other attributes from the Cookie. Please ensure that the Cookie contains the following key-value pairs: + +- `LARK_SUITE_DPOP` +- `LARK_SUITE_ACCESS_TOKEN` +- `feishu_dpop_keypair` (used for key generation, optional) + +## App ID + +必填，Doubao's App ID. The App ID may vary for different clients, please refer to the actual value. + +## DPoP Key Secret, Auth Client ID, Auth Scope, Auth SDK Source, Auth SDK Version + +Optional, for Token refresh. Please obtain it yourself, and refer to the actual value. + +## Share Link + +Whether to use share link for download. If enabled, OpenList will create share and request with anonymous user's token to create download link. This can reduce authorization leak. + +Please ensure you have filled all authentication options above before enabling this function. + +## Ignore JWT Check + +Whether to ignore JWT check to prevent time issue diff --git a/pages/en/guide/drivers/dropbox.md b/pages/en/guide/drivers/dropbox.md new file mode 100644 index 000000000..481156524 --- /dev/null +++ b/pages/en/guide/drivers/dropbox.md @@ -0,0 +1,119 @@ +--- +top: 590 +categories: + - guide + - drivers +--- + +# Dropbox + +Dropbox Official：https://www.dropbox.com/ + +## Get refresh token + +- **This drive does not support the online API mode provided by OpenList.** + +- The following tutorial applies when the option is kept disabled as shown below. + +  + +- If you create your own `Client ID` and `Secret`, remember to authorize them. + +The steps are as follows: + +1. First, [click here](https://www.dropbox.com/developers/apps?_tk=pilot_lp&_ad=topbar4&_camp=myapps) to enter the Dropbox app management page and click "Create App". + +  + +2. After entering the app, configure the app type as shown below. + +  + +3. You can get the id and secret in the red box: the upper one is the id, the lower one is the secret. + +  + +4. Configure the callback URL. If you are strict about permissions and do not want to use an external callback address, you can set a local address here, or use the one outside the red box. + +  + +5. Finally, go to the permissions configuration page to set the app's permissions. + +  + +6. [Click here](https://api.oplist.org/) to enter the token acquisition tool. Select Dropbox, fill in your id and secret, and after authorization you can get the refresh token. + +7. In the OpenList configuration page, enter the refresh token, id, and secret to use. Note that the refresh token is about 40-50 characters long. + + + +If you are highly privacy-conscious, Dropbox supports local callback. You can use the following script provided by GPT to quickly implement it, communicating only with Dropbox servers. + +::: warning +Since the callback address is local and you have not set up a real local callback server, please manually copy the authorization code from the browser address bar. + +**Please resolve Python environment issues yourself, or use the callback server provided above.** +::: + +```python +import requests +import webbrowser +# Please replace with your own Dropbox App information +CLIENT_ID = 'your_app_key' +CLIENT_SECRET = 'your_app_secret' +REDIRECT_URI = 'http://localhost:114514' +# Step 1: Get authorization code +auth_url = ( + f"https://www.dropbox.com/oauth2/authorize" + f"?client_id={CLIENT_ID}" + f"&redirect_uri={REDIRECT_URI}" + f"&response_type=code" + f"&token_access_type=offline" # Required: key parameter to get refresh_token +) +print("👉 Please visit the following link to authorize:\n") +print(auth_url) +webbrowser.open(auth_url) +auth_code = input("\n✅ After authorization, paste the code after ?code= in the redirected URL here:\n> ").strip() +# Step 2: Exchange for access_token + refresh_token +token_url = "https://api.dropboxapi.com/oauth2/token" +data = { + 'code': auth_code, + 'grant_type': 'authorization_code', + 'client_id': CLIENT_ID, + 'client_secret': CLIENT_SECRET, + 'redirect_uri': REDIRECT_URI +} +response = requests.post(token_url, data=data) +response.raise_for_status() +tokens = response.json() +# ✅ Only output the refresh token +print("\n🎉 Success! Your Dropbox refresh_token is:\n") +print(tokens.get("refresh_token")) +``` + +## Root folder file_id + +**Empty is the root directory**：display all files +**Single folder ID**：Enter the folder you need to display, copy the top link to fill in `/home` behind + + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/emby.md b/pages/en/guide/drivers/emby.md new file mode 100644 index 000000000..434ac4215 --- /dev/null +++ b/pages/en/guide/drivers/emby.md @@ -0,0 +1,54 @@ +--- +top: 493 +categories: + - guide + - drivers +--- + +# Emby + +Mount media resources from an Emby server. + +## URL + +Emby server address, for example: `http://127.0.0.1:8086`. + +## ApiKey + +Emby API Key. Use together with `UserID` for API authentication. + +## UserID + +Emby user ID. Used with `ApiKey`. + +## Username + +Emby account username. Used with `Password`. + +## Password + +Emby account password. Used with `Username`. + +## LinkMethod + +Choose link method: + +- `stream`: Streaming link (recommended) +- `download`: Direct download link + +Some Emby servers do not grant download permission. In that case, please use `stream`. + +## Authentication Method + +Use **one** of the following login methods: + +1. `ApiKey + UserID` +2. `Username + Password` + +Do not mix both methods at the same time. + +## Example Configuration + +- URL: `http://127.0.0.1:8086` +- LinkMethod: `stream` +- Authentication: choose one method only diff --git a/pages/en/guide/drivers/febbox.md b/pages/en/guide/drivers/febbox.md new file mode 100644 index 000000000..5e725220d --- /dev/null +++ b/pages/en/guide/drivers/febbox.md @@ -0,0 +1,57 @@ +--- +top: 591 +categories: + - guide + - drivers +--- + +# FebBox + +FebBox：https://www.febbox.com + +- The upload function is currently unavailable. + +## Root folder ID + +Root directory ID, default is `0`. + +Other directory IDs can be viewed in the top link address bar after entering the folder. + +- **https://www.febbox.com/console#/files?parent_id=66889900** + + Then the directory ID is `66889900` + +## `Client_id`、`Client_secret` + +Generate address：**https://www.febbox.com/open/clients** + +- The generated client ID and secret key are filled in in the opposite order to the OpenList, so be careful not to fill them in incorrectly. + +  + +## User IP + +**Optional**, the IP address of the user when downloading, quoting the official description + +> IP address, Optional parameter. Supports IPv6 format. After filling in, the best download server suitable for the IP location will be selected. If not filled in, the requested IP will be used. + +## The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/feiji.md b/pages/en/guide/drivers/feiji.md new file mode 100644 index 000000000..63989cb5a --- /dev/null +++ b/pages/en/guide/drivers/feiji.md @@ -0,0 +1,50 @@ +--- +top: 686 +categories: + - guide + - drivers +--- + +# FeiJi Cloud + +**https://feijipan.com/** + + + +::: danger +Feiji Cloud imposes login restrictions on 3rd-party platforms. Attempting to access its service via OpenList may result in your account being banned. Please proceed with caution! +::: + +## Root folder ID + +root folder ID the default is `0`，Other directory ID View the figure below obtaining method + + +## username、password + +Just fill in your own Feiji Cloud Account Password + +## Known issues + +The file size returned by iLanZou is in Kilo Bytes, not Bytes. Therefore, you cannot accurately determine if a file has been modified based on its size. Please pay attention to the configuration of your sync software. + +## The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/ftp.md b/pages/en/guide/drivers/ftp.md new file mode 100644 index 000000000..d4aefa2af --- /dev/null +++ b/pages/en/guide/drivers/ftp.md @@ -0,0 +1,47 @@ +--- +top: 898 +categories: + - guide + - drivers +--- + +# FTP + +### Address + +FTP address, need contains port. + +### Username + +FTP username + +### Password + +FTP password + +### Root folder path + +root folder , default `/`, same as local storage. + +## Enter directory before listing + +Whether to change into the target directory before listing files. Some FTP servers do not support listing files with a path argument directly. Enable this option to first `cd` into the directory and then `ls`, which can resolve such compatibility issues. Default: `false`. + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + c1 + end + c1[local proxy]:::someclass==default===>a2[user equipment] + classDef someclass fill:#f96 + b1[Download proxy URL]-.alternative.->a2[user equipment] + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/github.md b/pages/en/guide/drivers/github.md new file mode 100644 index 000000000..587366ca6 --- /dev/null +++ b/pages/en/guide/drivers/github.md @@ -0,0 +1,125 @@ +--- +top: 399 +categories: + - guide + - drivers +--- + +# GitHub API + +::: tip +GitHub API does not support operating files larger than 100MiB and folders containing more than 100,000 sub-items. + +All `.gitkeep` files will be managed by the driver and will be invisible to the user. + +Operations on submodules are currently not supported. +::: + +## Token + +1. Log in GitHub and visit.
+
+2. Select `Generate new token (Classic)`
+
+ 
+
+3. Fill the information. At least, select **repo**. And click `Generate token`.
+
+ 
+
+4. Copy the token and paste it into the `Token` field.
+
+ 
+
+## Owner
+
+The owner of the repository. For example, if the URL of the repository is `github.com/AAA/BBB`, fill in `AAA` here.
+
+## Repo
+
+The name of the repository. For example, if the URL of the repository is `github.com/AAA/BBB`, fill in `BBB` here.
+
+## Ref
+
+A branch, a tag or a commit SHA. Only when a branch name is filled in is the driver writable. It defaults to the default branch if not filled.
+
+## Gh Proxy
+
+Used to speed up downloading
+
+- Download the content of `Raw` and `archive` and change it to `https://gh-proxy.com/raw.githubusercontent.com`
+
+```
+https://gh-proxy.com/raw.githubusercontent.com
+```
+
+```
+https://ghfast.top/raw.githubusercontent.com
+```
+
+```
+https://ghproxy.net/raw.githubusercontent.com
+```
+
+## GPG private key
+
+GPG private key, used to provide commit verifications. Verified commits will be marked with a green "Verified" label on the GitHub webpage. Use the following command to obtain it. Leave blank if verifications are not needed.
+
+```bash
+gpg --export-secret-key -a
+```
+
+## GPG key passphrase
+
+Passphrase to the GPG private key. Leave blank if there is none.
+
+## Committer name
+
+Custom committer name, defaulting to the owner's of the token when not filled.
+
+## Committer email
+
+Custom committer name, defaulting to the owner's of the token when not filled.
+Required when "Committer name" is filled. Required to be empty when "Committer name" is empty.
+
+## Author name
+
+Custom author name, defaulting to the owner's of the token when not filled.
+
+## Author email
+
+Custom author name, defaulting to the owner's of the token when not filled.
+Required when "Author name" is filled. Required to be empty when "Author name" is empty.
+
+## commit message
+
+Custom commit message, supporting the following template variables：
+
+- `UserName`: the user operating the file.
+- `ObjName`: the name of the file (or the folder) operated.
+- `ObjPath`: the path to the file (or the folder) operated.
+- `ParentName`: the name of the parent folder of the file (or the folder) operated.
+- `ParentPath`: the path to the parent folder of the file (or the folder) operated.
+- `TargetName`: (when renaming) new name. (when copying and moving) the target folder name.
+- `TargetPath`: (when renaming) new path. (when copying and moving) the target path.
+
+### The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/github_releases.md b/pages/en/guide/drivers/github_releases.md
new file mode 100644
index 000000000..4eda6ee0f
--- /dev/null
+++ b/pages/en/guide/drivers/github_releases.md
@@ -0,0 +1,202 @@
+---
+top: 398
+categories:
+ - guide
+ - drivers
+---
+
+# GitHub Releases
+
+## Overview
+
+GitHub Releases driver allows you to mount GitHub repository releases as a file system, enabling direct access to release assets through a familiar directory structure.
+
+## API Rate Limits
+
+::: warning Rate Limits
+
+- **Unauthenticated requests**: 60 requests per hour
+- **Authenticated requests** (with token): 5,000 requests per hour
+
+We recommend using a personal access token to avoid hitting rate limits.
+:::
+
+## Repository Configuration
+
+### Basic Usage
+
+**Single Repository Mount**
+
+Mount a single repository to the root directory:
+
+```text
+OpenListTeam/OpenList
+```
+
+This is equivalent to:
+
+```text
+/:OpenListTeam/OpenList
+```
+
+### Multiple Repositories
+
+**Mount to Subdirectories**
+
+You can mount multiple repositories to different subdirectories:
+
+```text
+/openlist-gh:OpenListTeam/OpenList
+/openlist-frontend-gh:OpenListTeam/OpenList-Frontend
+```
+
+The leading `/` is optional:
+
+```text
+openlist-gh:OpenListTeam/OpenList
+openlist-frontend-gh:OpenListTeam/OpenList-Frontend
+```
+
+## Configuration Options
+
+### Personal Access Token
+
+**When to use:**
+
+- Required for accessing private repositories
+- Recommended to avoid rate limiting issues
+
+**How to get:**
+
+1. Log in to GitHub
+2. Visit: https://github.com/settings/tokens
+3. Generate a new token with appropriate permissions
+
+### Show All Versions
+
+**Disabled (default):**
+
+```
+openlist/
+├── openlist-linux-amd64.tar.gz
+└── openlist-windows-amd64.zip
+```
+
+**Enabled:**
+
+```
+openlist/
+├── v3.41.0/
+│ ├── openlist-linux-amd64.tar.gz
+│ └── openlist-windows-amd64.zip
+├── v3.40.0/
+│ ├── openlist-linux-amd64.tar.gz
+│ └── openlist-windows-amd64.zip
+└── v3.39.4/
+ ├── openlist-linux-amd64.tar.gz
+ └── openlist-windows-amd64.zip
+```
+
+When enabled, all available release versions are displayed in separate directories.
+
+### Pagination Control (Show All Versions)
+
+When "Show All Versions" is enabled, you can control the number of releases fetched via pagination:
+
+- **`per_page`**: Number of releases per page (default: `30`, max: `100`)
+- **`max_page`**: Maximum number of pages to fetch (`0` means unlimited)
+
+These settings help you avoid hitting API rate limits when repositories have a large number of releases.
+
+**Example:**
+
+To fetch at most 2 pages with 50 releases per page (up to 100 releases total):
+
+```text
+per_page = 50
+max_page = 2
+```
+
+::: tip
+A single unauthenticated request counts as 1 toward the 60 requests/hour limit. With `per_page=100` and `max_page=1`, fetching releases for a single repository costs only 1 request.
+:::
+
+### Show README Files
+
+**Disabled (default):**
+
+```
+openlist/
+├── openlist-linux-amd64.tar.gz
+└── openlist-windows-amd64.zip
+```
+
+**Enabled:**
+
+```
+openlist/
+├── v3.41.0/
+│ ├── openlist-linux-amd64.tar.gz
+│ └── openlist-windows-amd64.zip
+├── v3.40.0/
+│ ├── openlist-linux-amd64.tar.gz
+│ └── openlist-windows-amd64.zip
+├── LICENSE
+├── README.md
+└── README_cn.md
+```
+
+::: tip
+When enabled, README and LICENSE files from the repository are displayed alongside releases. However, folder size and modification time information will not be shown.
+:::
+
+## GitHub Proxy Settings
+
+Use GitHub proxy services to accelerate downloads in regions with limited GitHub access.
+
+**Configuration:**
+Replace the GitHub domain with a proxy service URL:
+
+```text
+https://gh-proxy.com/https://github.com
+```
+
+**Available Proxy Services:**
+
+| Service | URL |
+| ----------- | ----------------------------------------- |
+| GH-Proxy | `https://gh-proxy.com/https://github.com` |
+| GHProxy.net | `https://ghproxy.net/https://github.com` |
+| GHFast | `https://ghfast.top/https://github.com` |
+
+Example:
+
+```
+Before: https://github.com/owner/repo/releases/download/v1.0/file.zip
+After: https://ghproxy.net/https://github.com/owner/repo/releases/download/v1.0/file.zip
+```
+
+::: warning
+Proxy services are third-party and may have varying availability and performance.
+:::
+
+## The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/google_drive.md b/pages/en/guide/drivers/google_drive.md
new file mode 100644
index 000000000..00787d815
--- /dev/null
+++ b/pages/en/guide/drivers/google_drive.md
@@ -0,0 +1,179 @@
+---
+top: 597
+categories:
+ - guide
+ - drivers
+---
+
+# Google Drive
+
+Official website: https://drive.google.com/
+
+- Supports Team Drive (Enter the Team Drive directory ID for the Root Folder ID)
+
+## 1. Prerequisites
+
+1. The machine on which the OpenList service is deployed must be able to connect to Google Drive.
+
+2. The Google Drive API service must be enabled. For details on how to enable it, please refer to [Enabling the Google Drive API](#_2-1-enable-google-drive-api).
+
+ > For detailed steps, see [Google Workspace > Google Drive > Quick Start Guide](https://developers.google.com/workspace/drive/api/quickstart/js).
+
+## 2. Preparation
+
+### 2.1. Enable Google Drive API
+
+1. On the [Guide Page](https://developers.google.com/workspace/drive/api/quickstart/js), locate the `Enable the API` button and click to proceed to the quick activation interface. Follow the instructions and confirm the settings to complete the activation process.
+
+2. You can also visit the [Google Drive API Management Interface](https://console.cloud.google.com/apis/library/drive.googleapis.com). Find the `Enable` button at the top and click it; wait for the activation to complete.
+
+3. `Quotas and System Limits Management`(optional): Switch to the `Quotas and System Limits` tab and set appropriate quotas and limits based on your usage and requirements.
+
+### 2.2. Creating an OAuth Client (Optional; not required if using OpenList, a public welfare server, or a self-built server)
+
+1. On the [Credentials Page](https://console.cloud.google.com/apis/credentials?hl=en), click the `Create Credentials` dropdown menu and select and click `OAuth client ID`.
+ > If prompted with `To create an OAuth client ID, you must first configure the consent screen`, click the `Configure consent screen` button, and complete the creation of the `Brand Information` on the subsequent page, selecting `External` for the `Audience`. After completion, return to the Credentials page to continue creating the OAuth client ID.
+ > 
+2. In the pop-up window, select `Web Application` and enter the name of your application type.
+3. For the `Authorized redirect URIs`, enter `https://api.oplist.org/googleui/callback`. If you are using a self-built service or a non-profit organization, please enter the corresponding domain name, for example, `https://your-domain.com/googleui/callback`.
+4. Click the `Create` button to complete the creation of the OAuth client. Note: Make sure to copy and save the `Client ID` and `Client Secret`; you will need them later on.
+
+ 
+
+5. Add yourself as a test user: On the left side, find the `Audience` menu and click to enter it. Then, locate `Test Users` and click the `+ Add users` button. Enter your Google account email address and click `Save`.
+
+ 
+
+6. After completing the testing, you can publish your application: On the left side, find the `Audience` menu and click to enter it. Then, locate `Publication Status` and click the `Publish app` button. Confirm the publication to complete the application release process.
+
+ 
+
+### 2.3. Get `Access Token` and `Refresh Token`
+
+1. Open the [OpenList Google Authorization Page](https://api.oplist.org/). **⚠️ If you are using a public or self-hosted server, please proceed with that server.**
+
+2. In the dropdown menu on the page, select `GoogleDrive Login`.
+
+ 
+ 
+
+3. If you created an OAuth Client ID in the previous steps, please enter the Client ID and Client Secrets in the input fields below.
+
+ 
+ 
+
+ Otherwise, check the box ☑️ to use the API provided by OpenList. **⚠️ If you are using a public or self-hosted server, the built-in Client ID and Client Secrets of that server will be used.**
+
+ 
+ 
+
+4. Click the `Get Authorization` button. The system will redirect you to the Google Authorization page. Log in to your Google account and authorize OpenList to access your Google Drive.
+
+ 
+
+5. If a message appears stating `This app has not been verified by Google`, click `Advanced` and then click `Go to oplist.org (insecure)` to continue. (If you are using a public or self-hosted server, the domain name here should match the actual domain name of the service; please verify this carefully.)
+
+ 
+
+6. Pay attention to the permission information on the authorization page (within the red box in the image below). Make sure that the permission granted is only for accessing your Google Drive files. If you find that the permission includes access to something other than just your Google Drive files in the public service, please report an issue at [OpenListTeam/OpenList-Docs/issues](https://github.com/OpenListTeam/OpenList-Docs/issues).
+
+ 
+
+7. After authorization is successful, the system will provide you with a `Refresh Token` and an `Access Token`. Please copy and save these tokens, as they will be used in subsequent configurations.
+
+ 
+ 
+
+## 3. Add Google Drive in OpenList
+
+### 3.1. Configuration
+
+#### 3.1.1. Root Folder ID
+
+Similar to Aliyun Drive, it is the last string of the official website URL, such as:
+
+
+
+### 3.2. Start Adding
+
+1. Open the management interface of OpenList and click on `Storage` in the left menu.
+
+2. On the Storage List page, click the `Add Storage` button in the top right corner.
+
+3. Select `Google Drive` as the drive.
+
+ 
+ 
+
+4. Enter the mount path, for example: `google-drive`.
+
+5. In the `Root Folder ID` field, enter the root folder ID obtained earlier; if you are using the root directory, enter `root`.
+
+6. In the `Refresh Token` field, enter the refresh token obtained earlier (if not available, refer to [Preparing for Integration](#_2-preparation).
+
+7. If you are using the OAuth client ID and key provided by OpenList (or a public welfare server/self-built server), follow steps 7.1 and 7.2:
+
+ 7.1. Check the `Use online API` option to indicate that you want to use the online API provided by OpenList.
+
+ 7.2. Enter `https://api.oplist.org/googleui/renewapi` as the API URL; if it’s a public welfare server/self-built server, enter the corresponding server address.
+
+ 
+ 
+
+8. If you are using your own OAuth client ID and key, follow steps 8.1 and 8.2:
+
+ 8.1. Uncheck the `Use online API` option to indicate that you are using your own OAuth client ID and key.
+
+ 8.2. Enter your OAuth client ID in the `Client id` field and your OAuth Client secrets in the `Client secret` field.
+
+ 
+ 
+
+9. Click the `Add` button to complete the addition of Google Drive.
+
+## 4. About `Use online api` option
+
+### 4.1. AccessToken refresh method with own keys
+
+```mermaid
+sequenceDiagram
+ participant OpenList
+ participant GoogleDrive
+ OpenList->>GoogleDrive: Provide refresh token + built-in client ID and secret
+ GoogleDrive->>OpenList: Return new access token + refresh token
+```
+
+### 4.2. AccessToken refresh method without own keys
+
+```mermaid
+---
+title: How to refresh AccessToken via OnlineAPI?
+---
+sequenceDiagram
+ participant OpenList
+ participant OnlineAPI
+ participant GoogleDrive
+ OpenList->>OnlineAPI: Provide refresh token
+ OnlineAPI->>GoogleDrive: Provide refresh token + built-in client ID and secret
+ GoogleDrive->>OnlineAPI: Return new access token + refresh token
+ OnlineAPI->>OpenList: Return new access token + refresh token
+```
+
+## 5. The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ c1
+ end
+ c1[Local Proxy]:::someclass==Default===>a2[User Device]
+ classDef someclass fill:#f96
+ b1[Proxy URL]-.Alternative.->a2[User Device]
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/google_photos.md b/pages/en/guide/drivers/google_photos.md
new file mode 100644
index 000000000..292229af6
--- /dev/null
+++ b/pages/en/guide/drivers/google_photos.md
@@ -0,0 +1,73 @@
+---
+top: 596
+categories:
+ - guide
+ - drivers
+---
+
+# Google Photos
+
+::: tip
+Due to the adjustments made by Google Photos to its Library API in April this year (https://developers.google.com/photos/support/updates?hl=en), after successfully mounting Google Photos to openlist, you can actually only view the photos uploaded through openlist. You can no longer view the photos uploaded by users via the official Google Photos app or website as you could before.
+:::
+
+## Root folder file_id
+
+The root directory is root, and other directory IDs are unknown (~~It seems that a separate album cannot be mounted~~ It has not been resolved yet [**Reference**](https://github.com/alist-org/alist/discussions/3264#discussioncomment-4874536))
+
+## Get client_id, client_secret
+
+Get the tool https://api.oplist.org
+
+How to get your own `client_id (client ID) client_secret (client secret key)` Go to [**Google Drive**](./google_drive.md) which article
+
+::: tip
+
+Tip This app has not been verified by Google
+
+You have been authorized to use an app that is currently in beta. Do not proceed unless you know the developer who invited you.
+
+Let's click **Continue** on the left
+
+Remember to check this option, otherwise an error will be reported, as explained in the following precautions
+:::
+
+It is more convenient now. In fact, when obtaining Google cloud disk authorization, select the album permission at the same time, and the token obtained at that time can also be used to mount the album~ kill two birds with one stone
+
+Remember to enable **`Photos Library API`**
+
+- https://console.cloud.google.com/apis/library/photoslibrary.googleapis.com
+
+According to [above](https://api.oplist.org) obtained **client ID** and **secret key** and **refresh_token**
+
+We fill in **https://api.oplist.org** to get a single catalog ID for each of our Google Photos
+
+- Root file ID (that is, the album ID): default root, display all, if you only want to display a single album, you can fill in the album ID you want to display
+- After we fill in, there will also be an **`access_token`** below. This can also be filled in the OpenList background refresh token option and used. The refresh token obtained at the beginning can be used for both of them- [Explanation](https://github.com/alist-org/alist/discussions/3264#discussioncomment-5051171)
+
+## Two notes:
+
+1. failed get objs: failed to list objs: Request had insufficient authentication scopes.: []
+ - It's because you didn't check the album permission (see the picture mentioned above) `view and organize the content in your Google Photos media library, and upload content to the media library when obtaining authorization. Learn more`
+ - You get the `access_token` and the `refresh_token` without declearing the scope of `https://www.googleapis.com/auth/photoslibrary`
+2. failed get objs: failed to list objs: Photos Library API has not been used in project ... before or it is disabled. Enable it by visiting then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.: []
+ - because **`Photos Library API`** is not enabled in your project, Google Photos API
+
+### The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ c1
+ end
+ c1[local proxy]:::someclass==default===>a2[user equipment]
+ classDef someclass fill:#f96
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/guangyapan.md b/pages/en/guide/drivers/guangyapan.md
new file mode 100644
index 000000000..aaa5a7425
--- /dev/null
+++ b/pages/en/guide/drivers/guangyapan.md
@@ -0,0 +1,89 @@
+---
+top: 701
+categories:
+ - guide
+ - drivers
+---
+
+# GuangYaPan
+
+
+
+:::: warning
+This driver uses a **two-stage SMS login**. You need to provide a valid `client_id` before login. After completing the SMS login, `access_token` and `refresh_token` are saved automatically, and you can log in again with just `access_token` or `refresh_token`.
+::::
+
+## 1. Add in OpenList
+
+### Client ID
+
+**Required**. Fill in the `client_id` for the GuangYaPan API. This field must be provided, otherwise storage initialization will fail.
+
+### Phone Number
+
+The phone number used for SMS login, e.g. `+86 13800000000`.
+
+### Captcha Token
+
+Captcha token required by `/v1/auth/verification`. Leave it empty if no captcha is triggered.
+
+### Send Code
+
+Set it to `true` and save to send the SMS code. It auto-resets to `false` after sending.
+
+### Verify Code
+
+The SMS verification code you received. Fill it in and save to finish the login.
+
+### Verification ID
+
+Auto-generated after sending the SMS code. Do not edit it manually.
+
+### Access Token
+
+Bearer access token. It is saved automatically after SMS login. If you already have a valid `access_token` or `refresh_token`, you can fill it directly instead of doing the SMS login.
+
+### Refresh Token
+
+Refresh token for auto-login and auto-refresh. Saved automatically after SMS login.
+
+### Root Folder Path
+
+Full path in the GuangYaPan cloud drive, e.g. `/Movies/Anime`. Leave it empty to use the root directory.
+
+### Device ID
+
+Optional custom device id (32 hex chars). Auto-generated when empty.
+
+### Device Sign
+
+Optional custom `X-Device-Sign` header. Generated from `device_id` when empty.
+
+### Page Size / Order By / Sort Type
+
+- `Page Size`: file list page size, default `100`.
+- `Order By`: sort field used by the file list, options `0,1,2,3,4`, default `3`.
+- `Sort Type`: sort direction used by the file list, options `0,1`, default `1`.
+
+## 2. SMS Login Steps
+
+1. Fill in `client_id` and `phone_number` (and `captcha_token` if needed).
+2. Set `send_code` to `true`, then save. The storage will enter a "SMS sent" status and the `verification_id` is generated automatically.
+3. Fill in the received `verify_code`, then save again to finish the login. The `access_token` and `refresh_token` are saved automatically.
+
+## 3. Offline Download
+
+GuangYaPan supports calling its own offline download function from OpenList.
+
+1. Mount a GuangYaPan storage.
+2. In the backend **Settings** → **Other**, set the GuangYaPan temporary directory (choose any folder of this account).
+3. Go back to the frontend, enter the target folder, and choose **GuangYaPan** in the offline download option at the lower right corner.
+
+- Supports adding offline tasks via URL (e.g. `http`, `magnet` links).
+
+## 4. Precautions
+
+- `client_id` is required, otherwise storage initialization will fail.
+- The `verify_code` is one-time use and will be cleared after a successful login.
+- The driver does not support overwriting uploads (same-name files will not overwrite).
+- Login priority: `access_token` → `refresh_token` → SMS login.
diff --git a/pages/en/guide/drivers/halalcloud.md b/pages/en/guide/drivers/halalcloud.md
new file mode 100644
index 000000000..f66526de6
--- /dev/null
+++ b/pages/en/guide/drivers/halalcloud.md
@@ -0,0 +1,56 @@
+---
+top: 679
+categories:
+ - guide
+ - drivers
+---
+
+# halalcloud
+
+- `6盘（halalcloud）` Official website：[https://2dland.cn](https://2dland.cn/)
+ - Cloud Login：https://drive.2dland.cn
+- Official announcement, document address：https://2dland.yuque.com/r/organizations/homepage
+
+## Root folder file_id
+
+Top address bar path，Root folder file_id is:`/`
+Subfolder: `/A folder/C folder/C folder`
+
+## Fill in the example
+
+On the HalalCloud (6 盘) website, go to `User Center` and navigate to `Authorization Management`. Enter your HalalCloud account password to verify your identity.
+
+Create a new authorization (you can name it anything you like). Click `Confirm`, then copy and save the `Client ID` and `Client Secret`.
+
+
+
+In the OpenList admin panel, go to `Storage` and add a new driver. Select `HalalCloudOpen`, and enter the `Client ID` and `Client Secret` obtained from the previous step.
+
+## Other parameters
+
+- `Upload thread`: Upload threads (Default: 3, Range: 1-32)
+
+- `Host`: (Provided by default, no input required)
+
+- `WebDAV Policy`: Default is `302 Redirect`. Switch to `Local Proxy` if you encounter any issues.
+
+### The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/ilanzou.md b/pages/en/guide/drivers/ilanzou.md
new file mode 100644
index 000000000..ce47454b9
--- /dev/null
+++ b/pages/en/guide/drivers/ilanzou.md
@@ -0,0 +1,46 @@
+---
+top: 687
+categories:
+ - guide
+ - drivers
+---
+
+# iLanZou
+
+**https://ilanzou.com**
+
+
+
+## Root folder ID
+
+root folder ID the default is `0`，Other directory ID View the figure below obtaining method
+
+
+## username、password
+
+Just fill in your own NewLanzou Cloud Account Password
+
+## Known issues
+
+The file size returned by iLanZou is in Kilo Bytes, not Bytes. Therefore, you cannot accurately determine if a file has been modified based on its size. Please pay attention to the configuration of your sync software.
+
+## The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/index.md b/pages/en/guide/drivers/index.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/pages/en/guide/drivers/kodbox.md b/pages/en/guide/drivers/kodbox.md
new file mode 100644
index 000000000..e5f2ed091
--- /dev/null
+++ b/pages/en/guide/drivers/kodbox.md
@@ -0,0 +1,55 @@
+---
+top: 496
+categories:
+ - guide
+ - drivers
+---
+
+# KodBox
+
+Use this driver to mount a KodBox netdisk space to OpenList.
+
+## Root folder path
+
+Suppose you have a network disk space named `My Files`. If you remount the contents of the network disk space, you need to obtain the path corresponding to `My File`; if you re-display a name in the network disk space for For the directory of `abc`, you must obtain the path corresponding to `My File/abc`, and so on.
+
+Example: How to get the path of KodBox network disk space `My File`, the result path is `{source:5}`
+
+Open the KodBox network disk space in the browser. In the console mode, you can see the path corresponding to the network disk space. Do not leave it blank.
+
+
+## Address
+
+Your KodBox server address, e.g.
+
+- `https://kodcloud.cc`
+- `http://192.168.1.24:8000`
+
+## Username
+
+The email or username used to log in to your KodBox server.
+
+## Password
+
+The password for your email or username.
+
+### The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/lanzou.md b/pages/en/guide/drivers/lanzou.md
new file mode 100644
index 000000000..14c59afe1
--- /dev/null
+++ b/pages/en/guide/drivers/lanzou.md
@@ -0,0 +1,94 @@
+---
+top: 688
+categories:
+ - guide
+ - drivers
+---
+
+# LanZou Cloud
+
+
+
+Lanzuo Network Disk has three types of **modes (types)**, which are **Accounts**, **Cookie** and **Url**
+
+- **Account**: You can display all the files of your own cloud disk, you only need to fill in the account password, which will automatically help you refresh the cookie
+
+- **Cookie**: All files in the network disk can be displayed, but the cookie of the network disk needs to be provided
+
+- **Url**: only display the content in the link (you can mount it without providing a cookie)
+
+::: tip
+
+It is recommended to use the **Account** method to mount
+
+- Cookie mode needs to manually update Cookie
+
+:::
+
+## root folder ID
+
+Lanzuo cloud disk root directory ID, the default is `-1`，If you use `Url`Type to mount the root folder ID, please see the third item of [Fill in instructions](#fill-in-instructions)
+
+- **Additional Folder ID**
+ - Two ways to obtain (see the picture below)
+
+ 
+
+## Account
+
+Just fill in your own Lanzou Cloud Account Password
+
+## Cookie
+
+Log in to your [**Lanzuo Cloud Disk**](https://pc.woozooo.com/) account, then F12 to open the developer mode, you can find `Cookie`, there is no specific one, such as the left side of the picture Just click one and there will be `Cookie` in the blue part of the right picture.
+
+
+## Share link and share password
+
+- **Share link**: Randomly generate a share link in the Lanzuo cloud disk
+ - Small tip: **lanzouX** in the link, the last default **X** content sometimes cannot be opened in some areas, you can try to change it yourself, for example, change to i, x, u, t, etc. Anyway, try it out for yourself.
+- **Share password**: the password for the link
+
+## Repair file info
+
+If you need **WebDav** service, you need to open it
+
+## error message
+
+Use cookie type or account type to add prompt `not find file page param` error because lanzou changed the domain name
+
+- Solution: It is recommended to use account type to add
+ - Change the sharing link to `https://wwop.lanzoul.com` and save it. If it still doesn't work, refresh the lower right corner.
+ - lanzoul will also make changes in the future
+
+## Fill in instructions
+
+1. **Acount mode**: Type selects `account`, fill in` account` and `password` options, and the `root folder ID` (the default is all files of the root directory)
+2. **Cookie mode**: Type selects `Cookie`, fill in` Cookie`, and the `root folder ID` (the default is all files of the root directory)
+3. **URL mode**: Type selects `Url`, fill in` ShareUrl` and `root folder ID` and`Share Password (if there is a password)`
+ - The sharing link is :point_right: https://xxx.lanzou.com/aaabbbccc :point_left: in this format
+ - Fill in `ShareUrl`: https://xxx.lanzou.com
+ - Fill in `root folder ID`: aaabbbccc
+ - Share Password: if there is a password
+ 
+
+## The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/lenovo_nas_share.md b/pages/en/guide/drivers/lenovo_nas_share.md
new file mode 100644
index 000000000..c6c9a0476
--- /dev/null
+++ b/pages/en/guide/drivers/lenovo_nas_share.md
@@ -0,0 +1,59 @@
+---
+top: 494
+categories:
+ - guide
+ - drivers
+---
+
+# Lenovo Nas Share
+
+
+
+Need to purchase Lenovo devices **https://pc.lenovo.com.cn**
+
+## Root Folder ID
+
+Root Folder ID: Leave it blank
+
+Subfolder ID: Get as shown in the picture
+
+
+
+## Share ID and Share Password
+
+Example of share link: https://siot-share.lenovo.com.cn/s/#/eb.3N93ZbJsaAjerjdm4N Extraction code: `e5eu`
+
+- **Share ID**: Fill in the sharing link and automatically extract the string `eb.3N93ZbJsaAjerjdm4N` at the end of the sharing link
+- **Share Password**: The extraction code `e5eu`
+
+## Host Address
+
+The default uses the public network: **https://siot-share.lenovo.com.cn**
+
+(Not recommended) If you are using a local network, you can change it to the internal network address of the Lenovo device: **http://192.168.XX.XX**
+
+## Show Root Folder
+
+If unchecked and `Share ID` is empty, the folder ID of the first-level folder is automatically filled in.
+Taking the above picture as an example, the contents of the `OpenList` folder are directly displayed without displaying the `OpenList` folder.
+
+## The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/local.md b/pages/en/guide/drivers/local.md
new file mode 100644
index 000000000..c18af02d6
--- /dev/null
+++ b/pages/en/guide/drivers/local.md
@@ -0,0 +1,65 @@
+---
+top: 999
+categories:
+ - guide
+ - drivers
+---
+
+# Local storage
+
+Support mounting the directory of the local machine.
+
+## Root folder path
+
+The path of folder you wanted to mount. For example:
+
+- Linux: `/root`
+- Windows: `C:`
+
+## Local storage video thumbnail
+
+You need to use the `ffmpeg` tool to add.
+
+## Local storage PDF thumbnail on macOS
+
+On macOS, the Local storage driver can generate thumbnails from the first page of PDF files using the system Quick Look tool.
+
+To enable this feature:
+
+1. Enable `Thumbnail`.
+2. Enable `PDF thumbnail`.
+3. It is recommended to configure `Thumb cache folder` to avoid rendering the same PDF repeatedly.
+
+This feature is disabled by default and is only available when OpenList runs on macOS. Rendering is performed on cache misses and may consume additional CPU and memory.
+
+## Recycle bin path
+
+path to recycle bin, delete permanently if empty or keep 'delete permanently'
+
+If you fill in this path, you will move the file into the folder when deleting the local storage file, so that you have a chance to regret it.
+
+The method of filling in the above -mentioned mounting path is different from different system filling methods.
+
+If you don’t know if you fill in it correctly, you can test it yourself first and then use the production environment to use it yourself.
+
+- Linux: `/root`
+- Windows: `C:`
+
+## The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ c1
+ end
+ c1[local proxy]:::someclass==default===>a2[user equipment]
+ classDef someclass fill:#f96
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/mediafire.md b/pages/en/guide/drivers/mediafire.md
new file mode 100644
index 000000000..a72652628
--- /dev/null
+++ b/pages/en/guide/drivers/mediafire.md
@@ -0,0 +1,30 @@
+---
+top: 520
+categories:
+ - guide
+ - drivers
+---
+
+# MediaFire
+
+Mount [MediaFire](https://www.mediafire.com/) cloud storage.
+
+## Root folder path
+
+The default root directory for the path to mount mediafire, default is `/`.
+
+## Session Token
+
+Session Token
+
+Open the browser developer tools, visit [mediafire.com](https://www.mediafire.com/), log in to your account, go to the `Network` tab, open `get_session_token.php`, find `session_token` in the `Response`, and copy its value to fill in.
+
+
+
+## Cookie
+
+Web Cookie
+
+Open the browser developer tools, visit [mediafire.com](https://www.mediafire.com/), log in to your account, go to the `Network` tab, open `get_session_token.php`, find `Cookie` in the `Header`, and copy its value to fill in.
+
+
diff --git a/pages/en/guide/drivers/mediatrack.md b/pages/en/guide/drivers/mediatrack.md
new file mode 100644
index 000000000..89eeeaa1e
--- /dev/null
+++ b/pages/en/guide/drivers/mediatrack.md
@@ -0,0 +1,46 @@
+---
+top: 680
+categories:
+ - guide
+ - drivers
+---
+
+# Mediatrack
+
+**https://app.mediatrack.cn**
+
+### Access token
+
+You can get it in request header after logging in
+
+
+### Project id
+
+Get from official website url:
+
+
+### Root folder id
+
+Get it from the request after logging in
+
+
+### The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/mega.md b/pages/en/guide/drivers/mega.md
new file mode 100644
index 000000000..1d0f1de52
--- /dev/null
+++ b/pages/en/guide/drivers/mega.md
@@ -0,0 +1,64 @@
+---
+top: 592
+categories:
+ - guide
+ - drivers
+---
+
+# MEGA Disk
+
+::: warning
+Due to MEGA requires decryption to be performed on the OpenList server backend, **using proxy URL** with this driver cannot avoid server traffic consumption.
+:::
+
+MEGA official website: **https://mega.nz/login**
+
+### Mail
+
+MEGA login account
+
+### password
+
+login password
+
+## 2FA
+
+Non -filling options,If you open 2FA, you need to fill in it,If you don’t use 2FA, you don’t need to fill in it
+
+### Two fa secret
+
+**https://mega.nz/fm/account/security/two-factor-authentication**
+Click to enable `Enable two-factor authentication (2FA)` and then see a QR code, there is a string of letters below the QR code, This is `Two fa secret`, please record before scanning the code and do not lose it, Should the `Two-factor authentication (2FA) secret` be lost, you can unbinding and then retrieve a new 2FA QR code for setup.
+
+
+### Two fa code
+
+To enable 2-factor authentication, you need to install a app that support 2FA (such as [Google Authenticator](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2), [Microsoft Authenticator](https://support.microsoft.com/en-us/account-billing/download-and-install-the-microsoft-authenticator-app-351498fc-850a-45da-b7b6-27e523b8702a)), on your phone.
+Then login to OpenList manage and goto `Profile` page, click `Enable 2FA` button, scan the QR code with your 2FA app, and enter the code generated by your 2FA app.
+Scan the QR appearing on the screen. At the same time, this QR code is also [two-fa-secret](#two-fa-secret)
+
+
+ +## Fill in example: + + +
+ +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + c1 + end + c1[local proxy]:::someclass==default===>a2[user equipment] + classDef someclass fill:#f96 + b1[Download proxy URL]-.alternative.->a2[user equipment] + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/misskey.md b/pages/en/guide/drivers/misskey.md new file mode 100644 index 000000000..9788bcda3 --- /dev/null +++ b/pages/en/guide/drivers/misskey.md @@ -0,0 +1,17 @@ +--- +top: 588 +categories: + - guide + - drivers +--- + +# Misskey Drive + +## Instance URL + +The URL of your Misskey instance, whether self-hosted or in use. +For example, the official instance at `https://misskey.io` + +## Token + +Visit `https://{misskey-instance}/settings/api` to generate an access token. It requires the `read:drive` and `write:drive` permissions. diff --git a/pages/en/guide/drivers/mopan.md b/pages/en/guide/drivers/mopan.md new file mode 100644 index 000000000..dea6db66c --- /dev/null +++ b/pages/en/guide/drivers/mopan.md @@ -0,0 +1,50 @@ +--- +top: 691 +categories: + - guide + - drivers +--- + +# MoPan + + + +MoPan address：**https://mopan.sc.189.cn/mopan/#/downloadPc** + +- There is no web version, only `Android`, `iOS`, `PC-Win64bit`, `iPad`, and `TV`. + +## Sms code + +Enter the option of the mobile phone number and password when the first addition, and then enter the `SMS Code` input `send`, and then click Save to send it to you. + +## Root folder ID + +Do not fill in this option, it will automatically fill into the root directory + +- Due to encrypted requests, an appropriate method for obtaining folder IDs has not yet been found + +### Tips + +1. `root folder ID`,`equipment information`does not need to be filled in, will automatically help you fill +2. If you enter the send in [SMS Code] (#SMS-Code), it is found that it has been saved,Please click Edit to enter the verification code received + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/onedrive.md b/pages/en/guide/drivers/onedrive.md new file mode 100644 index 000000000..e0a92da35 --- /dev/null +++ b/pages/en/guide/drivers/onedrive.md @@ -0,0 +1,146 @@ +--- +top: 599 +categories: + - guide + - drivers +--- + +# OneDrive / Share + +:::tip + +- If you have global administrator permissions for a non-home edition, you can use the [OneDrive APP](onedrive_app.md) driver. +- If your account does not support the API, (for example, the school account has not verified the administrator, or the administrator has disabled the API), then you can also mount it through webdav. For details, see [webdav](webdav.md) + +::: + +## 1. Mounting using Online API's default application + +You do not need to create an application yourself by mounting in this way. + +1. Open and select the corresponding OneDrive version according to your account.
+
+2. Check "Use parameters provided by OpenList", click "Get Token", then log in to the OneDrive account you want to mount. After authorization, return to the page to get the refresh token.
+
+ 
+
+3. Go to the storage management interface of OpenList, select the OneDrive driver, check "Use online API", fill in the refresh token and you can mount it.
+
+ 
+
+## 2. Mounting by creating an application manually
+
+The application provided by OpenList API may experience issues such as request rate limits due to a high number of users. In this case, you can manually create an application.
+
+1. Navigate to the corresponding management page based on your account type.
+ - OneDrive Global：https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade
+ - OneDrive 21vianet：https://portal.azure.cn/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade
+ - OneDrive Germany：https://portal.microsoftazure.de/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade
+ - OneDrive US GOV：https://portal.azure.us/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade
+
+2. After logging in, select `Register Application`, enter `Name`, and select `Accounts and Individuals in Any Organization Directory` (note that you don't look at the location selection but the text here. Some people may be the middle option, don't select a single Tenant or other options, otherwise it will cause problems when logging in), enter the `Redirect URL` as `https://api.oplist.org/onedrive/callback`, click `Register`, and then you can get the `client_id`.
+
+ 
+
+3. After registering the application, select `Certificate and Password`, click `New Client Password`, enter a string of passwords, select the one with the longest time, and click `Add`.
+
+ (Note: The password entered after adding will disappear, please record the value of client_secret)
+
+ 
+
+4. Select `API Permissions`, click `MicroSoft Graph`, enter file in the `Select Permissions`, and check `Files.read` (Note: `Files.read` is a read-only minimum permission. The permission in the figure is larger, and the same can be done), click `Update Permission`.
+
+ 
+
+5. Fill in the `client_id` and `client_secret` obtained in the previous step into page, click `Get Token`.
+
+6. Go to OpenList's add storage page, uncheck "Use online API", and fill in the obtained `client_id`, `client_secret`, `Callback URL`, and `Refresh Token` in OpenList.
+
+## Parameters
+
+### Sharepoint site_id
+
+If you need to mount SharePoint, after completing the above steps, there will be an input field for the site address below the refresh token display. Enter the site address, click to get the `site_id`, and then fill the obtained information into the `site_id` field on the OpenList add storage page. Make sure `Is sharepoint` is enabled.
+
+### Root folder path
+
+The default is `/`, if you need to customize, just fill in the path, starting from the root path, the same as the local path, such as `/test`
+
+### Chunk size
+
+Upload chunk size (MiB). The default is `5`, which means `5 * 1024 * 1024 = 5,242,880` bytes. Make sure to use a size that is a multiple of 320 KiB (`327,680` bytes).
+
+### Custom host
+
+Custom accelerated download link. This is the domain name of your reverse-proxied OneDrive download API (for example, for personal accounts: `my.microsoftpersonalcontent.com`). Only domain replacement is supported here, not path replacement.
+
+::: warning
+
+- Only hostname replacement is supported, not path.
+- Be sure to properly isolate and only reverse proxy your own paths, otherwise your Cloudflare account may be banned!
+
+:::
+
+## The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
+
+## 3. OneDrive Share Url
+
+
+
+
+
+### Url
+
+The sharing link is the same as the example below and can be mounted. It can be obtained from E3, E5, A1, and A1P.
+
+```html
+https://connecthkuhk-my.sharepoint.com/:f:/g/personal/jhyang13_connect_hku_hk/EsEgHtGOWbJImxop6tF15FIBIH-ihrjuDclbrbmwWfY_RA?e=s6fitN
+```
+
+If it is OneDrive personal version, it will not work. The link is as follows
+
+```html
+https://onedrive.live.com/?cid=64EA5FCC7735E8C6&id=64EA5FCC7735E8C6%2117289
+```
+
+### Password
+
+It is the extraction code. If you have it, write it. If you don’t have it, don’t fill it in.
+
+### The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ c1
+ end
+ c1[local proxy]:::someclass==default===>a2[user equipment]
+ classDef someclass fill:#f96
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/onedrive_app.md b/pages/en/guide/drivers/onedrive_app.md
new file mode 100644
index 000000000..dc418747e
--- /dev/null
+++ b/pages/en/guide/drivers/onedrive_app.md
@@ -0,0 +1,173 @@
+---
+top: 598
+categories:
+ - guide
+ - drivers
+---
+
+# OneDrive APP
+
+## Benefits and Precautions
+
+1. The advantage is that the administrator is only authorized to log in once, and the same is used when adding parameters later. When adding, everything is the same except for the mailbox.
+ - For example, E5 has 25 5T accounts. After you log in and initialize in advance, you can directly use the parameters before the CV. You don’t have to get the refresh token every time as before, and it will expire after a long time
+ - A1, A1P, etc. can distribute more accounts (500 - **unlimited**)
+2. After the administrator authorizes in this way, he can view the account of each member in the organization at will, which will leak his own files
+ - It is recommended to apply for OneDrive E5 to get better
+
+::: tip
+It is not applicable to the home version. If you are in the configuration process, it does not match the options that appear in the tutorial. It may not be supported
+:::
+
+First log in with your personal or organizational account
+
+
+
+Login to get our `tenant ID`
+
+
+
+To log in to OneDrive (Operated by 21Vianet), please use this link
+
+
+
+## Create process
+
+::: danger Read the precautions carefully
+Please read carefully the following **`serial numbers , view in sequence`** , if there is any error, please feedback in time
+:::
+
+1. Register an application, choose the type yourself, it is recommended to choose the third
+2. Redirect URL (callback parameter), select Web as the type, and fill in the parameters **https://entra.microsoft.com/TokenAuthorize** ,Otherwise, it will not be able to authorize later. For OneDrive (Operated by 21Vianet), please use: **https://entra.microsoftonline.cn/TokenAuthorize**
+3. After filling out, click on the registration below and you can see it after jumping `client ID`
+ 
+
+Let's get a client secret key, just get it as shown in the figure below, remember `secret key` save in time, it will only appear once
+
+
+Once you have obtained the client secret key, go to authorize the **`API`** to be used, and follow the picture below to get it
+
+
+After the API is authorized, we go to authorize the organization application
+
+- Left sidebar ---> Enterprise applications ---> All applications ---> **{choose which application name we started to create}** ---> Permissions ---> Click for `xxxx `Grant admin consent
+ 
+
+matters needing attention
+
+- If you start to register the application, the callback parameters are not the same, you may get an error when you click Authorization, remember to write the same
+- How to check whether the authorization is successful. If it is not authorized, the page will prompt `The application has not been found to have the authorization of the administrator's permission`. After the authorization is successful, refresh the page and you will see three API permissions, as shown in the figure below
+ - The above is what it looks like when it is not authorized, and the following is what it looks like after authorization (just refresh the page after authorization)
+ 
+
+From the beginning to the present, we have obtained the following parameters: tenant ID1, registered application2, client ID/secret key3, authorization API/administrator API4
+Then open the browser and finally authorize it through the following format, which are `tenant ID` `client ID` `Callback URL` Change to your own final login to receive
+
+```html
+https://login.microsoftonline.com/{tenant ID or common}/adminConsent?client_id={client
+ID}&redirect_uri={Callback URL}
+```
+
+For OneDrive (Operated by 21Vianet), please use:
+
+```html
+https://login.partner.microsoftonline.cn/{tenant ID or common}/adminConsent?client_id={client
+ID}&redirect_uri={Callback URL}
+```
+
+
+If you log in according to the spelled link and find that you are redirected to a blank page, such as the sample code and picture below, the authorization is successful, don’t worry
+
+```
+https://entra.microsoft.com/TokenAuthorize?admin_consent=True&tenant={Tenant ID}#
+```
+
+
+
+## Fill in the example
+
+Fill in the values obtained in the above process one by one. If you don’t know which email address it is, you can find it by [**view all users of the organization**](#view-all-users-of-the-organization)
+
+
+; )`).
+
+## Add object storage examples and official documents
+
+`S3 Object Storage` includes but is not limited to these. There are many more, such as Microsoft and Google, which have not been added. There are no examples here because it is difficult to register and activate and cannot provide example tutorials. If you have an account, please contact us and provide an account and I will add it.
+
+### Alibaba
+
+[**Alibaba Cloud OSS Official Website**](https://oss.console.aliyun.com/)
+
+[**Comparison Table of Endpoints in Different Regions of OSS under Public Cloud**](https://help.aliyun.com/document_detail/31837.html)
+
+::: tip
+OpenList needs to skip `referer` to mount **Alibaba Cloud Disk**. If you do not allow `referer` to be empty in anti-leech, it will not work, because Alibaba Cloud Disk uses Alibaba Cloud OSS (in Beijing area)
+
+In fact, the `Region|Region` option can be written as `Endpoint`, but for the sake of specification, let’s write it according to the comparison table.:::
+:::
+
+Fill in example:
+
+
+
+### Tencent
+
+[**Tencent Cloud COS Official Website**](https://console.cloud.tencent.com/cos)
+
+[**Collection Table of Endpoints in Each Region of COS under the Public Cloud**](https://cloud.tencent.com/document/product/436/6224)
+
+Fill in example:
+
+
+
+### VolcEngine
+
+[**VolcEngine TOS Official Website**](https://console.volcengine.com/tos)
+
+[**Collection Table of Endpoints in Each Region of COS under the Public Cloud**](https://www.volcengine.com/docs/6349/107356)
+
+Fill in example:
+
+
+
+### Tianyi
+
+[**Tianyi Cloud OOS Official Website**](https://oos-cn.ctyun.cn/oos/ctyun/consoleBucket.html)
+
+[**Comparison Table of Endpoints of OOS Regions under Public Cloud**](https://www.ctyun.cn/document/10026693/10027878)
+
+Fill in example:
+
+
+
+### Baidu
+
+[**Baidu Cloud BOS official website**](https://console.bce.baidu.com/bos)
+
+[**Self-configure Bucket’s Referer whitelist permissions**](https://cloud.baidu.com/doc/BOS/s/Bk6kqu8eq#Setrefererwhitelist)
+
+[**comparison table of Region and Endpoint of BOS under public cloud**](https://intl.cloud.baidu.com/doc/BOS/s/xjwvyq9l4-en)
+
+**Endpoint comparison table compatible with AWS S3**[**Click to view details**](https://cloud.baidu.com/doc/BOS/s/xjwvyq9l4)
+
+Fill in example:
+
+
+
+### Qiniu
+
+[**Qiniu Cloud Kodo official website**](https://portal.qiniu.com/kodo/bucket)
+
+[**Region and Endpoint comparison table of Kodo under the public cloud**](https://developer.qiniu.com/kodo/4088/s3-access-domainname)
+
+Fill in example:
+
+
+
+### Huawei
+
+[**HUAWEI CLOUD OBS Official Website**](https://www.huaweicloud.com/intl/en-us/)
+
+[**Check the Region and Endpoint comparison table of OBS under the public cloud**](https://developer.huaweicloud.com/intl/en-us/endpoint), the secret key AK/SK[acquire](https://console.huaweicloud.com/iam/?region=cn-north-4#/mine/accessKey) to set by yourself.
+
+Fill in example:
+
+
+
+### JD
+
+[**JD CLOUD OBS Official Website**](https://www.jdcloud.com/cn/products/object-storage-service)
+
+Advantages: [free 10G](https://www.jdcloud.com/cn/activity/oss), support IPV6
+
+Disadvantages: need to precharge 100 to open，However, after the pre-deposit is completed, the object storage is activated, and the pre-deposited amount can still be used after withdrawal.
+
+[**Region and Endpoint comparison table of Kodo under the public cloud**](https://docs.jdcloud.com/cn/object-storage-service/oss-endpont-list)
+
+Fill in example:
+
+
+
+### Doge
+
+[**Doge Cloud OSS Official Website**](https://www.dogecloud.com/product/oss)，If you want to add Doge, use a separate `DogeCloud` driver to add, please do not use the `S3` the driver
+
+Region Code：
+
+```json
+// 0: 上海（华东），1: 北京（华北），2: 广州（华南），3: 成都（西南）
+```
+
+
+
+### 139
+
+[**139 CLOUD EOS Official Website**](https://console.ecloud.10086.cn/api/page/eos-console-web/CIDC-RP-00/eos/bucket?productType=os&v=new)
+
+[**Region and Endpoint comparison table of Kodo under the public cloud**](https://ecloud.10086.cn/op-help-center/doc/article/48082)
+
+Fill in example:
+
+
+
+### upyun
+
+[**Yupyun USS Official Website**](https://console.upyun.com/services/file/):[Click here to configure USS](./uss.md)
+
+### Amazon
+
+[**Amazon S3 Official Website**](https://s3.console.aws.amazon.com/s3/)
+
+The endpoint URL contains the name of the region where the bucket is located
+
+Example 1, if your bucket is in the US East (Ohio) region
+
+Then the format of the Endpoint URL is **`s3.us-east-2.amazonaws.com/your-bucket-name`**
+
+Region parameter: **`us-east-2`**
+
+Bucket name: **`your-bucket-name`** (your own bucket name)
+
+Example 2, my storage bucket is `Tokyo`, and the name of the storage bucket is `cdn-aw`, then the complete parameter filling is as follows
+
+1. **Endpoint**: s3.ap-northeast-1.amazonaws.com
+2. **Region**: ap-northeast-1
+3. **Bucket Name**: cdn-aw
+
+Let's take a look at the complete parameter filling example
+
+Fill in example:
+
+
+
+### Cloudflare R2
+
+[**Cloudflare R2 Official Website**](https://dash.cloudflare.com/)
+
+**Endpoint**: The S3 endpoint is available via the **`https://.r2.cloudflarestorage.com`** endpoint.
+
+**`ACCOUNT_ID`**: This account ID can be seen everywhere, and the simplest is the position at the top of the browser. The string of IDs behind the website link is your account ID.
+
+填写示例：
+
+
+
+### Backblaze B2
+
+[**B2 Official Website**](https://secure.backblaze.com/b2_buckets.htm)
+
+The full name is **`Backblaze`**, no verification information is required, and it is said that the first 10G is free.
+
+Fill in example:
+
+
+
+### Scaleway
+
+[**Scaleway Official Website**](https://console.scaleway.com/object-storage/buckets)
+
+Card required, verification information
+
+[**Region and Endpoint comparison table of Kodo under the public cloud**](https://www.scaleway.com/en/docs/storage/object/concepts/#object-storage)
+
+Fill in example:
+
+
+
+### Minio
+
+Those who use `Minio` self-built object storage should know how to obtain the ID and secret key, so I won’t talk about it here.
+
+You only need to fill in the four options of bucket name, access key ID, security access key, and Endpoint, and leave the region empty.
+
+**Endpoint：`http(s)://your-server:9001/`**, You can use IP or domain name
+
+Finally, remember to enable **`Force Path Style`** to use, otherwise it cannot be used [Click to view details](https://github.com/alist-org/alist/discussions/4920#discussioncomment-6635452)
+
+Fill in example:
+
+
+
+### Google Cloud
+
+I assume you already have a Google Cloud account, so let’s go directly to the Google Cloud Storage settings page:
+
+Then you will enter the following page:
+
+
+
+You can see Endpoint and Access Key on this page, you need to select an account and create an Access Key
+
+
+
+Access Key/Secret will be displayed on the new page, They will only be displayed this time. Please save them properly.
+
+
+
+At this point, the EndPoint, access key Id, and security access key required by OpenList have been obtained. Please view the remaining buckets and regions in the corresponding buckets.
+
+
+
+### Intranet access
+
+The server and object storage need to be in the same region, currently only supports `Alibaba Cloud OSS`. For example, if you are `Alibaba Cloud Hangzhou Server` and `Alibaba OSS in Hangzhou`, you can use it.
+
+- Previous behavior (taking Aliyun OSS as an example):
+ - Download link without custom host (using internal endpoint):
+
+ ```
+ https://.oss-cn-beijing-internal.aliyuncs.com/?X-Amz-Algorithm=***&X-Amz-Credential=***...
+ ```
+
+ - Download link within custom host (using external endpoint, the following link is **invalid**):
+
+ ```
+ https://.oss-cn-beijing.aliyuncs.com/
+ ```
+
+- Current behavior when `EnableCustomHostPresign` is `false`: Same as previous
+
+- Current behavior when `EnableCustomHostPresign` is `true` :
+ - Download link within custom host (using external endpoint, the following link is **valid**):
+
+ ```
+ https://.oss-cn-beijing.aliyuncs.com/?X-Amz-Algorithm=***&X-Amz-Credential=***...
+ ```
+
+### How to solve the problem of files with the same name as the folder
+
+After mounting the object storage and opening the folder, there is always a file with the same name as the folder that cannot be deleted or opened
+
+- The solution is to change the `List object version` in the configuration to V2, as shown in the following figure
+ 
+
+### The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/seafile.md b/pages/en/guide/drivers/seafile.md
new file mode 100644
index 000000000..d9aa0d195
--- /dev/null
+++ b/pages/en/guide/drivers/seafile.md
@@ -0,0 +1,74 @@
+---
+top: 495
+categories:
+ - guide
+ - drivers
+---
+
+# Seafile
+
+Seafile uses libraries as a unit for version control and synchronization.
+
+Use this driver to mount a Seafile repository to OpenList, encrypted libraries are supported.
+
+## Root folder path
+
+1. If the `RepoId` is not set, this configuration specifies the name and sub-path of the library to access, defaulting to the root path: `/`, indicating displaying all libraries. Suppose you have a library named `example`, if you only want to mount the contents of this library, you can set this item to `/example`; if you only want to display a directory named `abc` within this library, you can set this item to `/example/abc`, and so on.
+2. If the `RepoId` is set, this configuration is used to set the directory within the specified library, defaulting to the root directory: `/`.
+
+## Address
+
+Your Seafile server address, e.g.
+
+- `https://seacloud.cc`
+- `http://192.168.1.24:8000`
+
+## Username
+
+The email or username used to log in to your Seafile server.
+
+## Password
+
+The password for your email or username.
+
+## Token
+
+Applicable to certain Seafile cloud storage systems integrated with enterprise/school unified authentication. For such cloud storage systems, there is no need to enter the username and password; only the token information needs to be filled in. Taking Tsinghua Cloud Disk as an example, the following steps can be used to obtain the token: `cookie` → `seahub_auth` → `"student ID@tsinghua.edu.cn@random string"`, where the random string is the token.
+
+## RepoId (Library ID)
+
+Seafile library ID, such as: `86fc6316-3f2a-4c64-b6f5-d4d2b341bc9a`
+
+- Open the Seafile library in a browser, and you can see the library ID in the address bar.
+- Can be left empty, if left empty, all visible libraries for the specified account will be displayed.
+
+## RepoPwd (Library Password)
+
+Set the password used to access encrypted libraries, leave blank if no encrypted libraries are present.
+
+After configuring this item, OpenList will use this password to access all encrypted libraries for the specified account, without affecting access to unencrypted libraries. If you have multiple encrypted libraries using the same password, they can all be accessed normally.
+
+Different passwords for different libraries within a storage are not currently supported. If you have such a requirement, you can add multiple Seafile storage to achieve this, allowing you to specify different passwords for accessing different encrypted libraries.
+
+If you still cannot access files within encrypted libraries after setting the library password, please check if the password and other configurations above are correct. It is recommended to restart OpenList after modifying this password configuration to avoid caching issues.
+
+### The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/sftp.md b/pages/en/guide/drivers/sftp.md
new file mode 100644
index 000000000..cd883b40d
--- /dev/null
+++ b/pages/en/guide/drivers/sftp.md
@@ -0,0 +1,49 @@
+---
+top: 897
+categories:
+ - guide
+ - drivers
+---
+
+# SFTP
+
+即通过 SSH 协议访问文件。
+
+## 地址
+
+SSH 地址，需要包含端口。
+
+## 用户名
+
+SSH 用户名
+
+## 密码
+
+SSH 密码
+
+## 私钥
+
+使用私钥验证而不是密码。
+
+## 根文件夹ID
+
+挂载的根路径
+
+## 默认使用的下载方式
+
+```mermaid
+---
+title: 默认使用的哪种下载方式？
+---
+flowchart TB
+ style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ c1
+ end
+ c1[本机代理]:::someclass==默认===>a2[用户设备]
+ classDef someclass fill:#f96
+ b1[代理URL]-.备选.->a2[用户设备]
+ click b1 "../drivers/common.html#webdav-策略"
+ click c1 "../drivers/common.html#webdav-策略"
+```
diff --git a/pages/en/guide/drivers/smb.md b/pages/en/guide/drivers/smb.md
new file mode 100644
index 000000000..5389d81d4
--- /dev/null
+++ b/pages/en/guide/drivers/smb.md
@@ -0,0 +1,32 @@
+---
+top: 896
+categories:
+ - guide
+ - drivers
+---
+
+# SMB
+
+It is to mount smb to OpenList, instead of sharing OpenList through smb, instead of sharing smb like webdav.
+Because there are no related equipment and services, it is impossible to test. You can test it yourself according to the method provided in the **`GitHub Discussions`** discussion
+**https://github.com/alist-org/alist/discussions/2215#discussioncomment-4104018**
+Wait for the more detailed tutorials to be supplemented after the relevant equipment or services are available, or wait for the PR of the boss who has no problem with the test.
+
+## The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ c1
+ end
+ c1[local proxy]:::someclass==default===>a2[user equipment]
+ classDef someclass fill:#f96
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/storage-list.md b/pages/en/guide/drivers/storage-list.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/pages/en/guide/drivers/strm.md b/pages/en/guide/drivers/strm.md
new file mode 100644
index 000000000..3ba57d36c
--- /dev/null
+++ b/pages/en/guide/drivers/strm.md
@@ -0,0 +1,10 @@
+---
+top: 990
+categories:
+ - guide
+ - drivers
+---
+
+# Strm
+
+
diff --git a/pages/en/guide/drivers/strm_text.md b/pages/en/guide/drivers/strm_text.md
new file mode 100644
index 000000000..f1285d45a
--- /dev/null
+++ b/pages/en/guide/drivers/strm_text.md
@@ -0,0 +1,100 @@
+**Strm** is a driver that allows you to convert supported files from multiple cloud drives into .strm files.
+
+::: warning Important Notes
+Please understand the function of strm files before use
+
+Only the **`Download Preview (Read-Only)`** operation is supported. Other operations such as **Copy, Delete, Rename,
+Offline Download, Upload** are **not supported**.
+
+Strm uses a local proxy method, and during the **`Download Preview (Read-Only)`** operation, it will consume traffic
+from the deployed machine (depending on the number of files; individual files typically consume less than 100KB).
+:::
+
+### Parameter Descriptions
+
+#### Path
+
+The full path in OpenList where .strm files should be generated.
+Examples:
+
+```
+/115_open/Video
+/kuake_open/Video
+```
+
+#### Site URL
+
+The URL prefix for the generated .strm files.
+
+For example, if the directory /115_open/Video contains the file:`/电影/再见，李可乐 (2023)/再见，李可乐 (2023) - 2160p.mkv`
+
+And you enter http://localhost:5244 as the Site URL, the generated .strm file will point to:
+`http://localhost:5244/d/115_open/Video/电影/再见，李可乐 (2023)/再见，李可乐 (2023) - 2160p.strm`
+
+This field is optional. If left blank, the current access URL will be used as the default prefix.
+
+#### File Type Filter
+
+Specify which file types should be included for .strm generation.
+
+The following types are built-in:
+
+```
+Video Type
+mp4,mkv,flv,avi,wmv,ts,rmv,web
+
+Audio Type
+mp3,flac,aac,wav,ogg,m4a,wma,alac
+```
+
+You can add more types as needed. Use **commas (,)** to separate multiple file types.
+
+#### Encode Path
+
+Whether to enable URL path encoding.
+
+If disabled, the .strm URL will be:
+
+```
+http://localhost:5244/d/Video/电影/再见，李可乐 (2023)/再见，李可乐 (2023) - 2160p.strm
+```
+
+If enabled, it will be:
+
+```
+http://localhost:5244/d/Video/%E7%94%B5%E5%BD%B1/%E5%86%8D%E8%A7%81%EF%BC%8C%E6%9D%8E%E5%8F%AF%E4%B9%90%20(2023)/%E5%86%8D%E8%A7%81%EF%BC%8C%E6%9D%8E%E5%8F%AF%E4%B9%90%20(2023)%20-%202160p.mkv
+```
+
+#### Without Url
+
+The generated strm file will not contain URL prefixes
+
+#### SaveStrmToLocal
+
+When enabled, accessing a directory within or mounted by the Strm driver will save the Strm files locally
+
+#### SaveStrmLocalPath
+
+The local directory path where Strm files are stored.
+
+#### KeepLocalDownloadFile
+
+::: warning
+Warning: Deprecated parameter, removed in version 4.1.9 and will be removed in future versions
+:::
+
+#### Local Save Mode
+
+- `Insert Mode`: Only generate files that do not exist locally; existing local files will not be modified.
+- `Update Mode`: Generate files that do not exist locally and update the content of existing local files to the latest
+ version.
+- `Sync Mode`: Based on Update Mode, additionally delete local files that no longer exist on the cloud drive.
+
+> if you need scraper software to read local strm files and generate metadata files, please choose `Update Mode` to ensure that the content of local strm files is up to date and metadata files are not deleted
+
+### Actively generate local files
+
+The local file generation feature only takes effect when users access the corresponding directory. To recursively generate files for all paths, you can use the **Manually Scan** function, located under `Manage Page / Indices / Manually Scan`. In the **Path to scan** field, enter the **mount path of the Strm driver**, and in the **Rate limit** field, specify the API rate limit for the scanning process. Click start and wait for completion.
+
+Enabling the [Global Settings / Handle hook after writing](/en/configuration/global#handle-hook-after-writing) allows local files to be automatically generated after performing upload, rename, delete, move, copy, or extraction operations either under the original driver.
+Scheduled or automatic local file generation by listening for driver changes is not currently supported.
diff --git a/pages/en/guide/drivers/teambition.md b/pages/en/guide/drivers/teambition.md
new file mode 100644
index 000000000..ecdbcc5c9
--- /dev/null
+++ b/pages/en/guide/drivers/teambition.md
@@ -0,0 +1,43 @@
+---
+top: 681
+categories:
+ - guide
+ - drivers
+---
+
+# Teambition
+
+
+
+Teambition project file, supports Chinese server and international server.
+
+## Cookies
+
+After login, the validity period is unknown
+
+
+## Project ID and root folder id
+
+Get it from the URL after logging in
+
+
+## The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/teldrive.md b/pages/en/guide/drivers/teldrive.md
new file mode 100644
index 000000000..eca0f3395
--- /dev/null
+++ b/pages/en/guide/drivers/teldrive.md
@@ -0,0 +1,82 @@
+---
+top: 586
+categories:
+ - guide
+ - drivers
+---
+
+# Teldrive
+
+
+
+Teldrive is a Telegram-based cloud storage app maintained by a third-party open-source project: [tgdrive/teldrive](https://github.com/tgdrive/teldrive).
+
+**Highlights**
+
+- Unlimited storage
+- No file size limit
+- If you don’t subscribe to Telegram Premium, bandwidth is limited, and speed depends on the distance and bandwidth quality between your account’s data center (DC1–DC5) and the Teldrive server.
+
+Backend deployment requires a **Telegram API (not Bot API)**. See the official guide: [Teldrive installation](https://teldrive-docs.pages.dev/docs/getting-started/prerequisites)
+
+## Address
+
+Enter the base URL of your Teldrive backend **without** a trailing slash.
+
+Example: `https://teldrive.example.com`
+
+## Authentication (Cookie)
+
+Only **Cookie** authentication is supported.
+
+After logging in to the Teldrive web UI, grab the cookie from your browser.
+
+The cookie should **start with** `access_token=` and is a JWT.
+
+
+
+::: tip
+You only need the string **containing** `access_token=`.
+:::
+
+## Download methods
+
+**Note**: If `Use Share Link` is enabled, a shared file link is created and the download URL is valid for **1 hour**.
+
+Otherwise, you need to enable OpenList's `Web Proxy`.
+
+## Chunk size
+
+Upload chunk size in **MiB**.
+
+Default: `10` (10 MiB). If large uploads fail, try a smaller value.
+
+If the chunk size is larger than the file size, the file is uploaded in a single thread without chunking.
+
+## Upload Concurrency
+
+Concurrent upload threads. Default: `4`.
+
+Adjust based on available memory. A handy estimate is:
+`memory ≈ chunk_size × concurrency`
+
+## The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/terabox.md b/pages/en/guide/drivers/terabox.md
new file mode 100644
index 000000000..039059fbc
--- /dev/null
+++ b/pages/en/guide/drivers/terabox.md
@@ -0,0 +1,67 @@
+---
+top: 594
+categories:
+ - guide
+ - drivers
+---
+
+# Terabox
+
+
+
+https://www.terabox.com/
+
+## Refresh Token
+
+~~[**Click here to log in**](https://www.terabox.com/) to obtain a refresh token~~
+Since F12 is currently disabled on the web page, we can first open F12 on another page and turn on the `Network` → `Preserve log` option.
+
+Then enter https://www.terabox.com in the address bar of this tab to enter the webpage, you can see the reserved request, and then find **`Cookie`** from the reserved request. + +
+ +## Download Api + +**Download api needs to choose `Crack`** ，before you can use +
+ +## Root folder id + +- Root folder id is `/` +- Mount other single subdirectories, put a picture for reference + -
+
+## Download error using Proxy Url link
+
+Using [**Proxy Url**](common.md#download-proxy-url) to download error
+
+```json
+{
+ "error_code": 31211,
+ "error_msg": "access denied"
+}
+```
+
+View specific reasons：**[https://github.com/alist-org/alist/issues/6508](https://github.com/alist-org/alist/issues/6508#issuecomment-2171762705)**
+
+ +## The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/thunder.md b/pages/en/guide/drivers/thunder.md new file mode 100644 index 000000000..7c81ff4f3 --- /dev/null +++ b/pages/en/guide/drivers/thunder.md @@ -0,0 +1,498 @@ +--- +top: 685 +categories: + - guide + - drivers +--- + +# Thunder Cloud Disk + + + +::: tip +Please use `Thunder` directly instead of `ThunderExpert` if you are not good at it. + +`ThunderExpert` mainly provides more free settings and realizes more login methods + +--- + +`Thunder X` serves overseas users. As of the time of document release, only the Android version is available. Other versions have not yet been released. + +- Thunder X has sufficient speed even without membership. Future changes are unknown. +- Using the APP may require a proxy, but not when mounted on OpenList. + +--- + +`Thunder Browser`：Currently only supports mobile phones (Android, iOS) + +- **https://x.xunlei.com/** +- If you log in to OpenList, the mobile phone will be kicked offline. On the contrary, if you log in to OpenList first and then log in to the mobile phone, OpenList will be kicked offline but there will be no prompt + +::: + +## 1. Thunder + +### Username + +That is, the mobile phone number, email, and username used for login (there is a probability that you cannot log in, you need to try) + +1. Before obtaining the verification code, do not include the `+86` country code when entering the phone number. +2. After obtaining the verification code, the phone number must include the `+86` country code, for example: +8613722223333. + +### Password + +password for login + +
+ +### Credit Key + +After saving for the first time, an error will occur. This is normal. Please go to the storage management interface. + + + +Copy all the content above. + +[Click here to enter](https://i.xunlei.com/xlcaptcha/android.html) + +After entering, open the developer tools (usually by pressing F12), go to the console, and enter `reviewCb()`. **Paste all the previously copied content, including the curly braces,** inside the parentheses, as shown below: + + + +Move the cursor to **after the parentheses** and press Enter. + + + +The webpage will automatically redirect to the mobile number verification page. + +After completing the verification, the page **will not** refresh automatically. Please check the console. The `creditkey` shown below is the required key. + + +Copy it to the storage management, and you can mount it normally. + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + c1 + end + c1[local proxy]:::someclass==default===>a2[user equipment] + classDef someclass fill:#f96 + b1[Download proxy URL]-.alternative.->a2[user equipment] + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` + +## 2. ThunderExpert + +::: tip +If Xunlei needs to download, you must specify UserAgent (same as DownUserAgent below). Or use the proxy function in this program to transfer. +::: + +### Login Type + +1. When selecting User, you only need to fill in the username and password + - User You need to bring the `+86` area code, for example +8613722223333 fill in like this +2. **RefreshToken**: Just fill in RefreshToken when selecting RefreshToken + +### Signature Type + +**Algorithms**：When selecting Algorithms, just fill in the Algorithms (it is difficult to obtain, and needs to be reversed) + +**Captcha sign**: Only fill in CaptchaSign and Timestamp when selecting CaptchaSign + +``` +//signature algorithm +str = ClientID + ClientVersion + PackageName + DeviceID + Timestamp +for (Algorithm in Algorithms) { + str = md5(str + Algorithm) +} +CaptchaSign = "1." + str +``` + +Login type and Sign type recommended options + + + +### DeviceID + +The value calculated by md5 is used to determine the logged in device + +### ClientID, ClientSecret, ClientVersion, PackageName + +It is related to the signature, fill in according to the actual situation + +### UserAgent + +UserAgent used by API requests, may be inaccessible or speed limited if the setting is incorrect + +### DownUserAgent + +The User Agent used for downloading, if the setting is wrong, it will not be downloaded (it will be used when the agent is turned on) Fixed parameters: + +`Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36` + +### Key data acquisition process + +Obtain Xunlei request data through network analysis tools (packet capture tools) --- Please read the following information carefully + +Open Xunlei and log in to your account (the picture below uses the PC client to operate, and the web terminal is also available) + +Included in the request https://xluser-ssl.xunlei.com/v1/shield/captcha/init + +CaptchaSign, Timestamp, DeviceID, ClientID, ClientVersion, PackageName, User-Agent + +**Note**: After obtaining the information of the two pictures, slowly select the data from the two data captured and fill in it + +After logging in to Thunder and opening the packet capture tool, it is possible that the information of **v1/shield/captcha/init** cannot be immediately obtained at this time. + +Do not close the Xunlei PC client and the packet capture tool, just wait, it will refresh automatically after **5 minutes** + +You will see the parameters as shown in the figure below, and you can fill in it according to the acquisition (if you can't see it clearly, you can right-click to copy the picture and link it to the browser to open a new window) + +See **v1/shield/captcha/init** and grab it, please **immediately don't delay for a second** Right-click Xunlei in the taskbar in the lower right corner to exit, exit completely and then reopen to get \* \*Figure II\*\* + + + +Restarting Thunder will refresh the token + +The request to https://xluser-ssl.xunlei.com/v1/auth/token contains RefreshToken (please use the returned value), ClientSecret (does not exist on the web side) + + +Figure 1 contains **7** parameters | Figure 1 contains **2** parameters | a fixed parameter (Down UserAgent), ten parameters and 3 options and a mount path, just write and save, before saving Remember to check~ + +When the `Video URL` option is enabled, it will attempt to replace the original link with the media link returned by the API. Currently, the official platform throttles the download link for **non-members**, but video streaming is not throttled. Therefore, by replacing the link, you can avoid throttling, which applies to both **OpenList** media file downloads and streaming. For regular files, you can also bypass the throttling by renaming the file extension to a media format (e.g., `.mp4`). + +The **Expert Edition** does not enable the `Video URL` option by default, as it is intended for users who configure detailed parameters themselves, and they should be aware of the significance of this option. Hence, it is not enabled by default. For **Xunlei X** users, this option is enabled by default, primarily for the convenience of less experienced users. + +### ThunderExpert complete parameter filling demo: + + + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` + +## 3. Thunder X + +::: danger +At present, the official will ban frequent API calls. Please use with caution and bear the consequences. +::: + +### username、password + +The mailbox and password used for login +
+ +### CaptchaToken + +It will be filled automatically without filling in manually +
+ +### Root folder id + +The default is the full directory of the empty display, If you want to use a subfolder to make the root directory, grab the request to get it + +- In the request in the package`https://api-pan.xunleix.com/drive/v1/files?parent_id=&page_token=&filters=`，you can get the following parameters + - `文件夹ID（id）` + - `文件夹名称（name）` + - `父文件夹ID（parent_id）` +- The `folder ID` obtained in the root directory (for example : `我接收的文件`、`我的云盘`、`高速云下载`), **This will change with different account numbers, there is no the same value, In the request in the package** +  + +### Use video url + +When the `Video URL` option is enabled, it will attempt to replace the original link with the media link returned by the API. Currently, the official platform throttles the download link for **non-members**, but video streaming is not throttled. Therefore, by replacing the link, you can avoid throttling, which applies to both **OpenList** media file downloads and streaming. For regular files, you can also bypass the throttling by renaming the file extension to a media format (e.g., `.mp4`). + +The **Expert Edition** does not enable the `Video URL` option by default, as it is intended for users who configure detailed parameters themselves, and they should be aware of the significance of this option. Hence, it is not enabled by default. For **Xunlei X** users, this option is enabled by default, primarily for the convenience of less experienced users. + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` + +## 4. Thunder X Expert + +::: danger +At present, the official will ban frequent API calls. Please use with caution and bear the consequences. +::: + +### username、password + +The mailbox and password used for login +
+ +### CaptchaToken + +It will be filled automatically without filling in manually +
+ +### Root folder id + +The default is the full directory of the empty display, If you want to use a subfolder to make the root directory, grab the request to get it + +- In the request in the package`https://api-pan.xunleix.com/drive/v1/files?parent_id=&page_token=&filters=`，you can get the following parameters + - `文件夹ID（id）` + - `文件夹名称（name）` + - `父文件夹ID（parent_id）` +- The `folder ID` obtained in the root directory (for example : `我接收的文件`、`我的云盘`、`高速云下载`), **This will change with different account numbers, there is no the same value, In the request in the package** +  + +### Login Type + +- `User`: Only fill in the username and password +- `Refresh token`: Just fill in`RefreshToken` + +### Sign Type + +- `Algorithms`：Choose `Algorithms` Just fill in `Algorithms` (It has been automatically filled. You do n’t have to fill in it yourself. You only need to fill in the username and password.When the algorithm is not invalidated) +- `Captcha sign`: Choose `Captcha sign` Just fill in `Captcha sign` and `Timestamp` + +### Part of parameter Packet Capture description + +- `Captcha token`：No need to fill in +- `Device id`：The value calculated by MD5 is used to judge the login device +- `Client id`, `Client secret`, `Client version`, `Package name`：It related to the signature, fill in according to the actual situation + +--- + +- `User agent`：API requests `User agent`, setting errors may not access or speed limit +- `Download user agent`：When downloading, use the `user agent `,If the setting error cannot be downloaded (the agent will use it) + - `User agent` and `Download user agent`：You can fill it out by yourself. If you don’t know how to fill it out, you can leave it blank and it will be automatically filled in. + +--- + +In the request in the package `https://xluser-ssl.xunleix.com/v1/shield/captcha/init`，you can get the following parameters6 + +- `Client id`、`Device id`、`Captcha sign` +- `Package name`、`Client version`、`Timestamp` + +  + + In the request in the package `https://xluser-ssl.xunleix.com/v1/auth/signin`, you can get the following parameters2 + - `Client id`、`Client secret` +  + +### Use video url + +When the `Video URL` option is enabled, it will attempt to replace the original link with the media link returned by the API. Currently, the official platform throttles the download link for **non-members**, but video streaming is not throttled. Therefore, by replacing the link, you can avoid throttling, which applies to both **OpenList** media file downloads and streaming. For regular files, you can also bypass the throttling by renaming the file extension to a media format (e.g., `.mp4`). + +The **Expert Edition** does not enable the `Video URL` option by default, as it is intended for users who configure detailed parameters themselves, and they should be aware of the significance of this option. Hence, it is not enabled by default. For **Xunlei X** users, this option is enabled by default, primarily for the convenience of less experienced users. + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` + +## 5. Thunder Browser + +### username、password + +Mobile phone number, email, username, and password used to log in + +- When filling in the mobile phone number, please bring the `+86` area code, for example `+8613822334455` + +### CaptchaToken + +It will be filled automatically without filling in manually + +### Root folder id + +The default is the full directory of the empty display, If you want to use a subfolder to make the root directory, grab the request to get it + +- In the request in the package`https://x-api-pan.xunlei.com/drive/v1/files?parent_id&page_token&space=`，you can get the following parameters + - `文件夹ID（id）` + - `文件夹名称（name）` + - `父文件夹ID（parent_id）` +- The `folder ID` obtained in the root directory (for example : `来自分享`、`超级保险箱`), **This will change with different account numbers, there is no the same value, In the request in the package** +  + +### Safe password + +Thunder Browser Safe password + +- Files in Safe password can only be deleted directly and cannot be deleted to the recycle bin, so the [**Deletion method**](#remove-way) below has nothing to do with this configuration. + +### Remove way + +**Trash**：Use OpenList to delete files and then move them to the Recycle Bin. If you delete them accidentally, you can restore them through Thunder Cloud Disk. +**Delete**：Deleting it directly cannot restore it. + +### Use video url + +When the `Video URL` option is enabled, it will attempt to replace the original link with the media link returned by the API. Currently, the official platform throttles the download link for **non-members**, but video streaming is not throttled. Therefore, by replacing the link, you can avoid throttling, which applies to both **OpenList** media file downloads and streaming. For regular files, you can also bypass the throttling by renaming the file extension to a media format (e.g., `.mp4`). + +The **Expert Edition** does not enable the `Video URL` option by default, as it is intended for users who configure detailed parameters themselves, and they should be aware of the significance of this option. Hence, it is not enabled by default. For **Xunlei X** users, this option is enabled by default, primarily for the convenience of less experienced users. + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` + +## 6. Thunder Browser Expert + +### username、password + +Mobile phone number, email, username, and password used to log in + +- When filling in the mobile phone number, please bring the `+86` area code, for example `+8613822334455` + +### CaptchaToken + +It will be filled automatically without filling in manually +
+ +### Root folder id + +The default is the full directory of the empty display, If you want to use a subfolder to make the root directory, grab the request to get it + +- In the request in the package`https://x-api-pan.xunlei.com/drive/v1/files?parent_id&page_token&space=`，you can get the following parameters + - `文件夹ID（id）` + - `文件夹名称（name）` + - `父文件夹ID（parent_id）` +- The `folder ID` obtained in the root directory (for example : `来自分享`、`超级保险箱`), **This will change with different account numbers, there is no the same value, In the request in the package** +  + +### Safe password + +Thunder Browser Safe password + +- Files in Safe password can only be deleted directly and cannot be deleted to the recycle bin, so the [**Deletion method**](#remove-way-1) below has nothing to do with this configuration. + +### Remove way + +**Trash**：Use OpenList to delete files and then move them to the Recycle Bin. If you delete them accidentally, you can restore them through Thunder Cloud +**Delete**：Deleting it directly cannot restore it. + +### Login Type + +- `User`: Only fill in the username and password +- `Refresh token`: Just fill in`RefreshToken` + +### Sign Type + +- `Algorithms`：Choose `Algorithms` Just fill in `Algorithms` (It has been automatically filled. You do n’t have to fill in it yourself. You only need to fill in the username and password.When the algorithm is not invalidated) +- `Captcha sign`: Choose `Captcha sign` Just fill in `Captcha sign` and `Timestamp` + +### Part of parameter Packet Capture description + +- `Captcha token`：No need to fill in +- `Device id`：The value calculated by MD5 is used to judge the login device +- `Client id`, `Client secret`, `Client version`, `Package name`：It related to the signature, fill in according to the actual situation + +--- + +- `User agent`：API requests `User agent`, setting errors may not access or speed limit +- `Download user agent`：When downloading, use the `user agent `,If the setting error cannot be downloaded (the agent will use it) + - `User agent` and `Download user agent`：You can fill it out by yourself. If you don’t know how to fill it out, you can leave it blank and it will be automatically filled in. + +--- + +In the request in the package `https://xluser-ssl.xunlei.com/v1/shield/captcha/init`，you can get the following parameters6 + +- `Client id`、`Device id`、`Captcha sign` +- `Package name`、`Client version`、`Timestamp` +  + + In the request in the package `https://xluser-ssl.xunlei.com/v1/auth/signin/token`, you can get the following parameters3 + - `Client id`、`Client secret`、`Refresh token` + +  + +### Use video url + +When the `Video URL` option is enabled, it will attempt to replace the original link with the media link returned by the API. Currently, the official platform throttles the download link for **non-members**, but video streaming is not throttled. Therefore, by replacing the link, you can avoid throttling, which applies to both **OpenList** media file downloads and streaming. For regular files, you can also bypass the throttling by renaming the file extension to a media format (e.g., `.mp4`). + +The **Expert Edition** does not enable the `Video URL` option by default, as it is intended for users who configure detailed parameters themselves, and they should be aware of the significance of this option. Hence, it is not enabled by default. For **Xunlei X** users, this option is enabled by default, primarily for the convenience of less experienced users. + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/uc.md b/pages/en/guide/drivers/uc.md new file mode 100644 index 000000000..7f6cf7d67 --- /dev/null +++ b/pages/en/guide/drivers/uc.md @@ -0,0 +1,85 @@ +--- +top: 683 +categories: + - guide + - drivers +--- + +# UC / TV + + + +## UC Cloud + +**https://drive.uc.cn/** + +### Cookie + +Press F12 to open "Debug", select "Network", select any request on the left, and find the one with the `Cookie` parameter. + + +### Root Folder ID + +Root Folder ID is `0` + +- After entering the folder, get the directory ID in the top address bar. If the subdirectory is deeper, the directory ID will be at the back of the address bar. Just write the subdirectory ID you want to mount. +  + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + c1 + end + c1[local proxy]:::someclass==default===>a2[user equipment] + classDef someclass fill:#f96 + b1[Download proxy URL]-.alternative.->a2[user equipment] + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` + +## UC TV + +The TV version supports `302`, but only `List` and `Download` operations are supported. Other operations are not supported (the interface does not support it). + +### Add method + +1. Select the `UC TV` driver, fill in the mounting path, and then save +2. Return to the all driver page and use the mobile APP to scan the QR code (If the QR code is not displayed, click on `Table Layout` in the upper right corner of the driver to switch from list mode to table mode) +3. After scanning the QR code to confirm, disable the driver, then enable the `driver` to use it. + - `Refresh token`、`Device id`、`Query token`,It will be filled in automatically, no manual filling is required - Please do not edit manually and modify it +  + +### Root Folder ID + +Root Folder ID is `0` + +- After entering the folder, get the directory ID in the top address bar. If the subdirectory is deeper, the directory ID will be at the back of the address bar. Just write the subdirectory ID you want to mount. +  + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/url_tree.md b/pages/en/guide/drivers/url_tree.md new file mode 100644 index 000000000..d53b55613 --- /dev/null +++ b/pages/en/guide/drivers/url_tree.md @@ -0,0 +1,248 @@ +--- +top: 998 +categories: + - guide + - drivers +--- + +# UrlTree + +:::tip +**`地址树-UrlTree`** 是什么? 是用来挂载单个文件链接的，详情可以查看 **→→→[原需求说明](https://github.com/alist-org/alist/issues/3268)←←←** +::: + +## 可写 + +打开后可以对此驱动进行`新建文件夹`、`移动`、`重命名`、`复制`、`删除`、`PutURL` + +- 当用户在实现该接口的驱动中尝试使用SimpleHttp进行离线下载时，将不会调用离线下载工具。 相反，将调用驱动程序的 `PutURL` 方法。 +- **https://github.com/AlistGo/alist/pull/7779** + +
+ +## 用法 + +具体的用法大概讲解一下，建议将下面不同用法都看看越往后越进阶玩法 + +别看写的看起来很难很啰嗦实际上自己操作一下秒懂。 + +1. 最简单的用法，直接写链接即可 + +**输入** + +``` +http://pic.rmb.bdstatic.com/bjh/aff9c9c8817d943d6857a73188958d45.jpeg +https://raw.githubusercontent.com/OpenListTeam/OpenList/main/README_cn.md +``` + +**输出** + +``` +│ aff9c9c8817d943d6857a73188958d45.jpeg +│ README_cn.md +``` + +2. 有文件的同时，也可以创建文件夹第一个代码示例，也可以创建多个文件夹第二个代码示例 + +**输入** + +``` +http://pic.rmb.bdstatic.com/bjh/aff9c9c8817d943d6857a73188958d45.jpeg +folder: + http://pic.rmb.bdstatic.com/bjh/aff9c9c8817d943d6857a73188958d45.jpeg + https://raw.githubusercontent.com/OpenListTeam/OpenList/main/README_cn.md +``` + +``` +http://pic.rmb.bdstatic.com/bjh/aff9c9c8817d943d6857a73188958d45.jpeg +folder: + http://pic.rmb.bdstatic.com/bjh/aff9c9c8817d943d6857a73188958d45.jpeg + https://raw.githubusercontent.com/OpenListTeam/OpenList/main/README_cn.md +http://pic.rmb.bdstatic.com/bjh/a66923e9bfefd03c2998ee998d3b55e7.jpeg +folder2: + http://pic.rmb.bdstatic.com/bjh/e919290bf3b8396817d369cedf33b8cd.jpeg + https://raw.githubusercontent.com/OpenListTeam/OpenList/main/CONTRIBUTING.md +``` + +**输出** + +``` +│ aff9c9c8817d943d6857a73188958d45.jpeg +└─folder + aff9c9c8817d943d6857a73188958d45.jpeg + README_cn.md +``` + +``` +│ aff9c9c8817d943d6857a73188958d45.jpeg +├─folder +│ aff9c9c8817d943d6857a73188958d45.jpeg +│ README_cn.md +│ +├─ a66923e9bfefd03c2998ee998d3b55e7.jpeg +│ +└─folder2 + CONTRIBUTING.md + e919290bf3b8396817d369cedf33b8cd.jpeg +``` + +开头要空两个空格~ + +3. 可以将文件资源二次命名，实际上下载的还是原来的，并且可以填写文件大小 + +格式：`新命名的名字.后缀:文件大小:链接.后缀` + +``` +新名称.jpeg:1024:http://pic.rmb.bdstatic.com/bjh/aff9c9c8817d943d6857a73188958d45.jpeg +新名称2.md:2048:https://raw.githubusercontent.com/OpenListTeam/OpenList/main/README_cn.md +``` + +文件大小不用写也是可以重新命名的 + +``` +新名称.jpeg:http://pic.rmb.bdstatic.com/bjh/aff9c9c8817d943d6857a73188958d45.jpeg +新名称2.md:https://raw.githubusercontent.com/OpenListTeam/OpenList/main/README_cn.md +``` + +@tab 4 + +4. 多个层级目录套娃玩法 + +- 第一层目录文件夹不需要空格，但是第一层目录里面的文件需要空两个空格 + +``` +folder: + http://pic.rmb.bdstatic.com/bjh/aff9c9c8817d943d6857a73188958d45.jpeg + https://raw.githubusercontent.com/OpenListTeam/OpenList/main/README_cn.md +``` + +- 如果你写好第一层了还想在第一个文件夹里面再套一个那就在这个文件夹下面套一层，写法如下，很简单 + - 目录进行空两格，文件加两个空格就是四个，如果继续想往下套一层继续加2个空格即可 + +``` +folder11: + http://pic.rmb.bdstatic.com/bjh/111.jpeg + folder111: + http://pic.rmb.bdstatic.com/bjh/111.jpeg + folder1111: + http://pic.rmb.bdstatic.com/bjh/111.jpeg + folder222: + http://pic.rmb.bdstatic.com/bjh/222.jpeg + folder2222: + http://pic.rmb.bdstatic.com/bjh/222.jpeg +folder22: + http://pic.rmb.bdstatic.com/bjh/222.jpeg + folder222: + http://pic.rmb.bdstatic.com/bjh/222.jpeg + folder2222: + http://pic.rmb.bdstatic.com/bjh/2223.jpeg +folder33: + http://pic.rmb.bdstatic.com/bjh/333.jpeg + folder333: + http://pic.rmb.bdstatic.com/bjh/333.jpeg + folder3333: + http://pic.rmb.bdstatic.com/bjh/333.jpeg +``` + +- 不建议的写法，像 **`2.jpeg，5.jpeg`** 这样写法，建议想往哪一层文件夹就去哪一层文件夹按照格式增加链接，不要像下面这样写 + +**错误写法** + +``` +folder22: + http://pic.rmb.bdstatic.com/bjh/222.jpeg + folder222: + http://pic.rmb.bdstatic.com/bjh/222.jpeg + folder2222: + http://pic.rmb.bdstatic.com/bjh/2222.jpeg + folder22222: + http://pic.rmb.bdstatic.com/bjh/2222.jpeg + folder222222: + http://pic.rmb.bdstatic.com/bjh/2222.jpeg + http://pic.rmb.bdstatic.com/bjh/2.jpeg + http://pic.rmb.bdstatic.com/bjh/5.jpeg +``` + +**正确写法** + +像 **`2.jpeg，5.jpeg`** 这样文件添加时候，添加到对应的目录里面去，分别对应的是 `folder222 和 folder22222` 两个文件夹 + +``` +folder22: + http://pic.rmb.bdstatic.com/bjh/222.jpeg + folder222: + http://pic.rmb.bdstatic.com/bjh/222.jpeg + http://pic.rmb.bdstatic.com/bjh/2.jpeg + folder2222: + http://pic.rmb.bdstatic.com/bjh/2222.jpeg + folder22222: + http://pic.rmb.bdstatic.com/bjh/2222.jpeg + http://pic.rmb.bdstatic.com/bjh/5.jpeg + folder222222: + http://pic.rmb.bdstatic.com/bjh/2222.jpeg +``` + +5. 全部整合起来的举例用法，有常规的，有分类，有重命名，有标注文件大小 + +``` +https://jsd.example.com/gh/OpenListTeam/OpenList/README.md +文档: + Readme.md:https://pic.rmb.bdstatic.com/bjh/说明.md + Doc: + 文档.doc:https://pic.rmb.bdstatic.com/bjh/测试文档.doc + pdf: + pdf2.pdf:https://pic.rmb.bdstatic.com/bjh/测试.pdf + Excel: + 表格3.xlsx:https://pic.rmb.bdstatic.com/bjh/测试表格.xlsx +视频: + https://pic.rmb.bdstatic.com/bjh/222.jpeg + 电视剧: + https://pic.rmb.bdstatic.com/bjh/222.pm4 + 电影: + https://pic.rmb.bdstatic.com/bjh/222.flv +音乐: + https://pic.rmb.bdstatic.com/bjh/222.jpeg + 古典: + https://pic.rmb.bdstatic.com/bjh/222.mp3 + 轻音乐: + https://pic.rmb.bdstatic.com/bjh/222.flac + https://pic.rmb.bdstatic.com/bjh/222.wav +软件: + https://pic.rmb.bdstatic.com/bjh/222.jpeg + PJ: + xx软件.exe:252525:https://pic.rmb.bdstatic.com/bjh/222.exe + xx安装包.zip:259555:https://pic.rmb.bdstatic.com/bjh/222.zip + IPA: + GPT.ipa:https://pic.rmb.bdstatic.com/bjh/222.ipa + APK: + P图.apk:https://pic.rmb.bdstatic.com/bjh/222.apk +``` + +## 提示 + +1. 如果你点击下载发现没有跳转到下载而是预览，这是因为是根据你原本链接来决定的,例如你原本的链接就是下载他就会跳转到下载 +2. 如果你一个文件夹内有相同的文件，会合并只显示一个，默认使用预览查看下载的是你靠上(前)也就是顶部的文件 + - Tips:请勿同时在一个目录内新建两个同名的文件/夹哦~就像你在资源管理器新建两个一样的文件/夹 都会提醒你不能重复 +3. 如果你在添加时在同级目录下写了两个相同的文件夹名字，会合并成一个文件夹但是合并后靠后(下)的文件夹的文件不会显示，但是可以通过浏览器地址栏访问（参考上一条的提示） +4. 排序默认是按照你填写从上到下依次排序的和 `OpenList-别名`的一样 + +### 默认使用的下载方式 + +```mermaid +--- +title: 默认使用的哪种下载方式？ +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|默认|a2[用户设备] + classDef someclass fill:#f96 + c1[本机代理]-.备选.->a2[用户设备] + b1[代理URL]-.备选.->a2[用户设备] + click a1 "../drivers/common.html#webdav-策略" + click b1 "../drivers/common.html#webdav-策略" + click c1 "../drivers/common.html#webdav-策略" +``` diff --git a/pages/en/guide/drivers/uss.md b/pages/en/guide/drivers/uss.md new file mode 100644 index 000000000..33fc787f6 --- /dev/null +++ b/pages/en/guide/drivers/uss.md @@ -0,0 +1,77 @@ +--- +top: 894 +categories: + - guide + - drivers +--- + +# UPYUN Storage Service + +::: tip +When using the **302 redirect** strategy, the `_upd` and `_upt` parameters are automatically appended to the URL. If **"Parameter Follow"** is enabled in the Upyun console, the CDN nodes will treat these parameters as part of the file path, resulting in a **404 Not Found** error for existing files. + +Solutions: + +- Method 1: In the Upyun console, under **"Cache Control"**, change **"Parameter Follow"** to **"Parameter Not Follow"**. + +- Method 2: Set the WebDAV policy of OpenList to **"Local Proxy"**. This mode avoids appending interfering parameters but will increase the server's data transfer. + ::: + +UPYUN Storage Service，refer to as USS，[**Yupyun USS Official Website**](https://console.upyun.com/services/file/) + +### BucKet + +UPYUN Storage Service Name + +### Endpoint + +Accelerated domain name (default TEST domain or bound domain, not CNAME domain) +If you use http protocol, please add `http://` protocol header. +The test domain name provided by upyun is not accessible in some network and does not support https, so it is recommended to use your own bound domain name. + +### Operator name + +Operator name + +### Operator password + +Operator password + +### Root folder path + +Root path, if not filled, it defaults to the root directory. + +### Sign url expire + +The validity period of the signed download address is 4 hours by default. + +## Example of filling in details + +::: tip +If you want to use the official test domain name, you must manually add http For example: http://xxx.test.upcdn.net +If you want to use HTTPS, of course, you can also add your own domain name, for example: https://you.xxx.com +permission is turned on by itself, and the read permission must be turned on！ +::: + + + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/webdav.md b/pages/en/guide/drivers/webdav.md new file mode 100644 index 000000000..ccfa381dd --- /dev/null +++ b/pages/en/guide/drivers/webdav.md @@ -0,0 +1,85 @@ +--- +top: 899 +categories: + - guide + - drivers +--- + +# WebDav + +## Address + +WebDAV root address + +## Username + +username + +## Password + +password + +## Root folder path + +The path of fodler you want to mount, same as join in address + +## Tls insecure skip verify + +Whether to skip SSL certificate verification. If your WebDAV server uses a self-signed certificate, you may need to enable this option. Enabling it will reduce security, please use it with caution. + +## Support 302 redirect + +In general, WebDAV servers return the file content directly. Due to the need for authorization, only proxy downloads are possible. However, some servers redirect to the actual file address, such as OpenList `WebDav Policy`'s `302 Redirect`. + +The `Web Proxy` option in WebDAV storage settings is enabled by default. If disabled, OpenList will attempt to obtain the redirected address and return it to the user device for direct download. + +Prerequisites: + +1. The WebDAV server must support returning 302; if it returns 200, this feature cannot be used, and disabling Web Proxy will make it unusable. +2. The returned 302 address must be publicly accessible and must not require authorization information; otherwise, the user device cannot download it. +3. Disable the `Web Proxy` option in the storage settings. + +## OneDrive/SharePoint + +Select the vendor as sharepoint, and support the international version/21Vianet. + +For OneDrive/SharePoint, you can obtain the WebDAV root address through [this tool](https://tool.example.com/onedrive/webdav). If you want to mount the specified directory, you can join it later. + +The username is the OneDrive account email, and the password is the OneDrive account password. + +## Error message + +- **failed get objs: failed to list objs: PROPFIND/根目录：403** + + Need to log in to [Entra ID](https://entra.microsoft.com/#view/Microsoft_AAD_IAM/TenantOverview.ReactView?Microsoft_AAD_IAM_legacyAADRedirect=true) + + Find 'Manage Security Default' and click to disable it(❗ Note: Closing this option will disable the Authenticator verification for the domain) + +  + + Another situation is that the corresponding OneDrive account has not been used for a long time, which will also prompt this problem. Try to log in to the account again from the OneDrive web page. The system will prompt you to change the password. After updating the password, try again with the changed password. + +- **failed link: failed get link: redirect failed, status: 200** + + This error indicates that the WebDAV server does not support 302 redirects. You need to enable the `Web Proxy` option in the storage settings to use proxy downloads. + +## The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[local proxy]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[302]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/weiyun.md b/pages/en/guide/drivers/weiyun.md new file mode 100644 index 000000000..b3db39498 --- /dev/null +++ b/pages/en/guide/drivers/weiyun.md @@ -0,0 +1,60 @@ +--- +top: 682 +categories: + - guide + - drivers +--- + +# Tencent weiyun + + + +Tencent Weiyun official website: **https://www.weiyun.com** + +::: tip Weiyun login validity period reminder + +- QQ: The login can only keep alive for 48 hours at present, and the cookie has to be replaced +- WeChat: no such problem, use token + It is recommended to use WeChat to log in + +::: + +## Root folder file_id + +1. Display the root directory, **`leave blank`**, you don’t need to fill in, the program will automatically fill in +2. If only a single folder ID is displayed, select the folder to be displayed, Copy the ID behind the top address bar + +  + +## Cookie + +After logging in to Weiyun, **Open the developer debugging tool (F12)**, find the request that carries the cookie in any request, copy and fill in it. + +- The token obtained by WeChat login is longer than the cookie field of QQ login +- QQ WeChat fills in the `Cookie` field value, and you can see it by just looking for a request + +  + +## Other notes + +1. The copy function cannot be used +2. **It is recommended not to share Weiyun with the outside world. After all, it is bound to your own QQ number. If you have a major loss to QQ or other things after being blocked/frozen, you will be responsible for the consequences** + +## The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + c1 + end + c1[local proxy]:::someclass==default===>a2[user equipment] + classDef someclass fill:#f96 + b1[Download proxy URL]-.alternative.->a2[user equipment] + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/wopan.md b/pages/en/guide/drivers/wopan.md new file mode 100644 index 000000000..018be2240 --- /dev/null +++ b/pages/en/guide/drivers/wopan.md @@ -0,0 +1,78 @@ +--- +top: 693 +categories: + - guide + - drivers +--- + +# WoPan + + + +[https://pan.wo.cn/](https://pan.wo.cn/) + +## GetToken + +::: tip +The difference between the two token acquisition methods: + +- Method 1: **Token valid for seven days** Logging in to the web version of China Unicom Cloud Drive will disconnect and invalidate the mount point on OpenList's side. However, logging in to the mobile version is fine, and thereby you can have both open simultaneously. + +- Method 2: **Token valid for two months** There isn't any problem to log into the Unicom Cloud Drive. However, it will be kicked off if you log in on the mobile side. + +::: + +### Method 1 + +1. Open developer tools +2. Open the official website to login
+3. Find the Apps tab in Developer Tools and select Session Storage:
+ 
+4. Follow the arrows in the diagram to find the `Refresh Token` and the `Access Token`
+
+## Root folder ID
+
+- **Personal cloud：**：**0**
+ - Single folder ID：Unknown (wait for replenishment)
+- **Family cloud**：Unknown (wait for replenishment)
+ - Family cloud Single folder ID：Unknown (wait for replenishment)
+
+## Type
+
+Personal cloud：Put the `family ID` blank is the personal cloud
+Family cloud：add `Family ID` Log in to the [SmartHome] -> [我的] -> [您的家], click"+" [Invite] -> [微信邀请], send the link to yourself, open it and copy all the text after 'groupId='.
+
+## OpenList fill in examples：
+
+Data obtained by using tools `Refresh_token Fill in the refresh token`, `Access_token fills in access_token`
+
+
+## The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/wps.md b/pages/en/guide/drivers/wps.md
new file mode 100644
index 000000000..4118a2617
--- /dev/null
+++ b/pages/en/guide/drivers/wps.md
@@ -0,0 +1,48 @@
+---
+top: 675
+categories:
+ - guide
+ - drivers
+---
+
+# WPS
+
+
+
+OpenList supports mounting WPS cloud document (which is also called KDocs) web.
+
+Official websites:
+
+- KDocs (Personal):
+
+ Label
+ org.openlist
+ KeepAlive
+ ProcessType
+ Background
+ RunAtLoad
+ WorkingDirectory
+ path/to/working/dir
+ ProgramArguments
+
+ path_openlist/openlist
+ server
+
+
+
+```
+
+Then, execute `launchctl load ~/Library/LaunchAgents/org.openlist.plist` to load the configuration, now you can use these commands to manage the program:
+
+- Start: `launchctl start ~/Library/LaunchAgents/org.openlist.plist`
+- Close: `launchctl stop ~/Library/LaunchAgents/org.openlist.plist`
+- Unload configuration: `launchctl unload ~/Library/LaunchAgents/org.openlist.plist`
+
+### Windows
+
+#### Method One
+
+1. Download the newest `nssm` from https://nssm.cc/download.
+2. Unzip the archive and go to the diretory of `nssm.exe`.
+3. Hold Shift and right click on the blank space, then release and press S or select "powershell here", you should now see a blue window named "Windows PowerShell".
+4. Type `.\nssm.exe install openlist`.
+5. Select the path of `openlist.exe` for "Path", e.g. `D:\openlist\openlist.exe`; type `server` for "Argument".
+6. You can custom "Display Name", "Description" and "Startup Type" in "Details" tab.
+7. Go to "I/O" tab and select a file for both "Output (stdout)" and "Output (stderr)", e.g. `D:\openlist\stdout.log`. The file itself (`stdout.log`) may not exist, but the folder (`D:\openlist`) must exist.
+8. Click on "Install Service".
+ You can now start the service from services.msc or task manager.
+
+#### Method Two
+
+Use **`.VBS`** script to start and stop, create two scripts respectively `start.vbs` and `stop.vbs`.
+Just double-click to start it in the folder at the same level as the OpenList startup program, don't worry about no response, just go to the browser to access it.
+
+::: info Two startup scripts
+**start.vbs**
+
+```bash title="vbscript"
+Dim ws
+Set ws = Wscript.CreateObject("Wscript.Shell")
+ws.run "openlist.exe server",vbhide
+Wscript.quit
+```
+
+**stop.vbs**
+
+```bash title="vbscript"
+Dim ws
+Set ws = Wscript.CreateObject("Wscript.Shell")
+ws.run "taskkill /f /im openlist.exe",0
+Wscript.quit
+```
+
+1. If the script will not be created, you can download it yourself: [**Script Download**](https://www.alipan.com/s/DHPMhRtKUzY/folder/63e0961eae317bd4d4d945cda69dbb00f9837fb7)
+2. If the script will not be used, you can watch the video: [**reference video**](https://www.bilibili.com/video/BV1wWYTzdE4B)
+ How to realize Windows startup automatically, you can refer to the script mentioned above to use the video (second).
+
+:::
+
+::: info
+For all platform, you can use follow command to silent start, stop and restart. (v3.4.0 and later)
+
+```bash
+openlist start
+openlist stop
+openlist restart
+```
+
+:::
+
+## How to update
+
+Download the new version of OpenList and replace the previous one.
diff --git a/pages/en/guide/installation/paas.md b/pages/en/guide/installation/paas.md
new file mode 100644
index 000000000..98b430173
--- /dev/null
+++ b/pages/en/guide/installation/paas.md
@@ -0,0 +1,73 @@
+---
+top: 30
+categories:
+ - guide
+ - installation
+---
+
+# PaaS
+
+::: tip
+The documentation may not be updated in a timely manner. Please make adjustments based on the key information and the current deployment interface of the platform.
+:::
+
+## ClawCloud
+
+### One-click deployment
+
+::: danger
+Due to the removal of `PUID`/`PGID` environment variable support for better container specifications in [OpenList v4.1.1](https://github.com/OpenListTeam/OpenList/releases/tag/v4.1.1), ClawCloud platform will not be able to function properly due to lack of permission to write data (including using images or app in App Store).
+
+As of October 20 2025, ClawCloud has not yet merged our Deployment Template. One-click deployment is temporarily unavailable. If you want to deploy on ClawCloud, please refer to [#1209 (comment)](https://github.com/OpenListTeam/OpenList/issues/1209#issuecomment-3243803024).
+:::
+
+Click the button below to [deploy to Claw Cloud](https://template.run.claw.cloud/?openapp=system-fastdeploy%3FtemplateName%3Dopenlist). It can also be found in App Launchpad.
+
+[](https://template.run.claw.cloud/?openapp=system-fastdeploy%3FtemplateName%3Dopenlist)
+
+### Manual deployment
+
+#### Key Information
+
+| Name | Value | Description |
+| :--------------- | :-------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Application Name | openlist | Application name |
+| Image | openlistteam/openlist:latest-lite | Image, please make sure to use the one with **lite**, otherwise the error `Pod ephemeral local storage usage exceeds the total limit of containers 100Mi.` may occur |
+| Replicas | 1 | Number of replicas, set to 1 |
+| CPU | 0.2 | Number of CPU cores, set according to your own needs |
+| Memory | 256M | Memory size, set according to your own needs |
+| Container Port | 5244 | Mapped port, which is `5244` if you have not modified the startup command or configuration |
+| Public Access | Y | Enable external access |
+| Custom Domain | - | If you have your own domain name, set it according to the prompts; if not, keep the default. Please make sure to use **https** for the protocol |
+| Local Storage | - | Persistent volume |
+| -- Capacity | 1 | Capacity |
+| -- Mount Path | /opt/openlist/data | Configured mapped directory, which is `/opt/openlist/data` if you have not modified the startup command or configuration |
+
+#### Reference Diagram
+
+
+
+
diff --git a/pages/en/guide/installation/reverse-proxy.md b/pages/en/guide/installation/reverse-proxy.md
new file mode 100644
index 000000000..fc65cc71e
--- /dev/null
+++ b/pages/en/guide/installation/reverse-proxy.md
@@ -0,0 +1,137 @@
+---
+top: 10
+categories:
+ - guide
+ - installation
+---
+
+# Reverse proxy
+
+OpenList listens to port 5244 by default. If modified, please also update the port number in the configuration below.
+
+If you are using **reverse proxy**, please ensure that the correct `Host` header is passed, as OpenList will generate the URL based on this information.
+
+If the `Host` header is unavailable, you can use the higher-priority `X-Forwarded-Host` header (non-standard header). If the issue persists, configure the [site_url](../../configuration/configuration.md#site-url).
+
+If you want to use a **sub folder**, you should configure the [site_url](../../configuration/configuration.md#site-url). Refer to [reverse proxy with sub folder](../../faq/howto.md#how-to-reverse-proxy-with-sub-directory).
+
+:::warning
+If you need to proxy to a non-standard port, make sure to pass the `domain:port` information through the `Host` or `X-Forwarded-Host` header, otherwise the port will be lost in URLs!
+:::
+
+## nginx
+
+https://nginx.org/en/docs/http/ngx_http_proxy_module.html
+
+Add in the `server` field of the website configuration file:
+
+```nginx
+location / {
+ proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+ proxy_set_header X-Forwarded-Proto $scheme;
+ proxy_set_header Host $http_host;
+ proxy_set_header X-Real-IP $remote_addr;
+ proxy_set_header Range $http_range;
+ proxy_set_header If-Range $http_if_range;
+ proxy_redirect off;
+ proxy_pass http://127.0.0.1:5244;
+ proxy_http_version 1.1;
+ # the max size of file to upload
+ client_max_body_size 20000m;
+}
+```
+
+::: warning
+If you use the aaPanel, be sure to delete the following default configuration:
+
+```nginx
+location ~ ^/(\.user.ini|\.htaccess|\.git|\.svn|\.project|LICENSE|README.md
+location ~ .\*\.(gif|jpg|jpeg|png|bmp|swf)$
+location ~ .\*\.(js|css)?$
+```
+
+Disable Nginx caching in `/www/server/nginx/conf/proxy.conf` or the corresponding website configuration file. Otherwise, with the default configuration, when accessing large files, Nginx will attempt to cache the remote file locally first, resulting in playback failures.
+
+```nginx
+proxy_cache cache_one; # Remove this line
+proxy_max_temp_file_size 0; # Add this line
+```
+
+:::
+
+::: tip Nginx Host Variables Differences
+
+| Variable | Description | Includes Port | Notes |
+| -------------------- | ------------------------------------------------ | ------------- | ---------------------------------------------------------------------------------------------------- |
+| `$http_host` | The original `Host` request header | Yes | If the `Host` request header is missing, the value will be empty; not recommended for best practices |
+| `$host` | Server name from the `Host` request header field | No | Defaults to the server's `server_name` if `Host` field is missing |
+| `$host:$server_port` | Server name + port | Yes | Use this combination when you need to use a non-default port (other than 80 or 443) |
+
+:::
+
+If HTTP/3 is needed, the corresponding `Host` line should be modified to:
+
+```nginx
+proxy_set_header Host $host:$server_port;
+```
+
+This modified configuration will be compatible with requests using HTTP/2 or lower versions.
+
+## Apache
+
+Add the anti-generation configuration item `ProxyPass` under the `VirtualHost` field, such as:
+
+```xml
+
+ ServerName myapp.example.com
+ ServerAdmin webmaster@example.com
+ DocumentRoot /www/myapp/public
+ AllowEncodedSlashes NoDecode
+ ProxyPreserveHost On
+ ProxyPass "/" "http://127.0.0.1:5244/" nocanon
+ ProxyPassReverse "/" "http://127.0.0.1:5244/" nocanon
+
+```
+
+## Caddy
+
+Add the reverse proxy configuration item `reverse_proxy` under the `Caddyfile` file, for example:
+
+```
+:80 {
+ reverse_proxy 127.0.0.1:5244
+}
+```
+
+If deployed on a server that is functioning properly on port 443 and accessed using a domain name, it is recommended to use this configuration to let Caddy automatically request a certificate:
+
+（Replace example.com with your own resolved domain name）
+
+```
+example.com {
+ reverse_proxy 127.0.0.1:5244
+}
+```
+
+## Tutorial: Setting up Reverse Proxy in aaPanel
+
+1. Login to the aaPanel and add a new website.
+
+::
+
+
+
+2. Modify the website settings.
+
+
+
+3. Remove the default panel code.
+
+
+
+
+4. Add the reverse proxy.
+
+
+
+> If you need to apply for an `SSL certificate`, you can first apply for the certificate in the `SSL` option, and then set up the reverse proxy. Alternatively, you can set up the reverse proxy first, disable the proxy function, apply for an `SSL` certificate, and then enable the proxy again.
diff --git a/pages/en/guide/installation/script.md b/pages/en/guide/installation/script.md
new file mode 100644
index 000000000..1ffce149b
--- /dev/null
+++ b/pages/en/guide/installation/script.md
@@ -0,0 +1,107 @@
+---
+top: 70
+categories:
+ - guide
+ - installation
+---
+
+# One-click Script
+
+Requirements:
+
+- Linux with systemd or OpenRC
+- Root privileges for installation
+- `curl`, `tar` installed
+- Architectures listed in the [download page](download)
+
+## Latest
+
+### Install
+
+::: code-group
+
+```bash [🌍Global]
+curl -fsSL https://res.oplist.org/script/v4.sh > install-openlist-v4.sh && sudo bash install-openlist-v4.sh
+```
+
+```bash [🇨🇳CN]
+curl -fsSL https://res.oplist.org.cn/script/v4.sh > install-openlist-v4.sh && sudo bash install-openlist-v4.sh
+```
+
+```bash [GitHub]
+curl -fsSL https://raw.githubusercontent.com/OpenListTeam/OpenList-Resource/refs/heads/main/script/v4.sh > install-openlist-v4.sh && sudo bash install-openlist-v4.sh
+```
+
+:::
+
+```bash
+欢迎使用 OpenList 管理脚本
+
+基础功能：
+1、安装 OpenList
+2、更新 OpenList
+3、卸载 OpenList
+-------------------
+服务管理：
+4、查看状态
+5、密码管理
+6、启动 OpenList
+7、停止 OpenList
+8、重启 OpenList
+-------------------
+配置管理：
+9、备份配置
+10、恢复配置
+-------------------
+高级选项：
+11、Docker 管理
+12、定时更新
+13、系统状态
+14、关于
+-------------------
+0、退出脚本
+```
+
+根据界面提示，输入`1`即可安装
+
+### openlist-manager
+
+::: tip
+**It can only be used after the installation is complete.**
+:::
+
+Use command: `openlist` or `openlist-manager`
+
+```bash
+欢迎使用 OpenList 管理脚本
+
+基础功能：
+1、安装 OpenList
+2、更新 OpenList
+3、卸载 OpenList
+-------------------
+服务管理：
+4、查看状态
+5、密码管理
+6、启动 OpenList
+7、停止 OpenList
+8、重启 OpenList
+-------------------
+配置管理：
+9、备份配置
+10、恢复配置
+-------------------
+高级选项：
+11、Docker 管理
+12、定时更新
+13、系统状态
+14、关于
+-------------------
+0、退出脚本
+```
+
+### FAQ
+
+1. Q: The architecture I am using is listed as supported on the download page, why does the installation script say it is not?
+
+ A: This is because the installation script is currently unable to recognise your CPU architecture. To help us add CPU architecture recognition to the installation script, please submit the output of the `arch` and `uname -m` commands to the issue page.
diff --git a/pages/en/guide/installation/source.md b/pages/en/guide/installation/source.md
new file mode 100644
index 000000000..6b3b68b71
--- /dev/null
+++ b/pages/en/guide/installation/source.md
@@ -0,0 +1,108 @@
+---
+top: 20
+categories:
+ - guide
+ - installation
+---
+
+# Run from source
+
+:::danger
+This step is only for users who need to modify the source code by themselves. If you don't understand, please skip it.
+:::
+
+## Environmental preparation
+
+First, you need to have an environment of `git`, `nodejs>=24`, `pnpm`, `golang>=1.24`, `gcc`
+
+On **Windows**, use Scoop:
+
+```powershell
+scoop install git nodejs-lts pnpm go mingw-winlibs
+```
+
+On **Linux/macOS**, use Homebrew:
+
+```bash
+# Debian / Ubuntu
+sudo apt install git curl build-essential
+
+# Fedora / RH
+sudo dnf install @development-tools
+# sudo yum groupinstall "Development Tools"
+
+# Arch
+sudo pacman -S git curl base-devel
+
+# macOS
+xcode-select --install
+
+# Install nodejs and golang use Homebrew for newer version
+curl -o- https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh | bash
+brew install node@24 go
+corepack enable pnpm
+```
+
+## Building the frontend
+
+```bash
+git clone https://github.com/OpenListTeam/OpenList-Frontend.git
+cd OpenList-Frontend
+pnpm install && pnpm build
+```
+
+## Build the backend
+
+Clone `https://github.com/OpenListTeam/OpenList` for this project, copy the `dist` directory of the previous step to the `public` directory under the project, and then:
+
+```bash
+appName="openlist"
+builtAt="$(date +'%F %T %z')"
+goVersion=$(go version | sed 's/go version //')
+gitAuthor=$(git show -s --format='format:%aN <%ae>' HEAD)
+gitCommit=$(git log --pretty=format:"%h" -1)
+version=$(git describe --long --tags --dirty --always)
+webVersion=$(curl -s --max-time 5 "https://api.github.com/repos/OpenListTeam/OpenList-Frontend/releases/latest" -L | grep '"tag_name":' | sed -E 's/.*"([^"]+)".*/\1/' | sed 's/^v//')
+if [ -z "$webVersion" ]; then
+ webVersion="0.0.0"
+fi
+ldflags="\
+-w -s \
+-X 'github.com/OpenListTeam/OpenList/v4/internal/conf.BuiltAt=$builtAt' \
+-X 'github.com/OpenListTeam/OpenList/v4/internal/conf.GoVersion=$goVersion' \
+-X 'github.com/OpenListTeam/OpenList/v4/internal/conf.GitAuthor=$gitAuthor' \
+-X 'github.com/OpenListTeam/OpenList/v4/internal/conf.GitCommit=$gitCommit' \
+-X 'github.com/OpenListTeam/OpenList/v4/internal/conf.Version=$version' \
+-X 'github.com/OpenListTeam/OpenList/v4/internal/conf.WebVersion=$webVersion' \
+"
+go build -ldflags="$ldflags" .
+```
+
+::: details compilation tutorial videos you may need
+Windows version: **https://www.bilibili.com/video/BV1Xr4y1z723** (Although it is V2 version, it is the same as V3 version..)
+Linux version: **https://www.bilibili.com/video/BV1GW4y1s742**
+Compile documents: **https://www.yuque.com/anwenya/alist/glqlhu**
+:::
+
+## Building within Docker
+
+Install Docker, clone the repository, then navigate to the root directory of the repository. No further preparation is required.
+
+#### Basic
+
+```bash
+docker build -t openlistteam/openlist:beta .
+```
+
+#### build-arg
+
+```bash
+docker build -t openlistteam/openlist:beta-ffmpeg --build-arg INSTALL_FFMPEG=true .
+```
+
+Available build args:
+
+| | Desc |
+| :-------------------- | -------------- |
+| `INSTALL_FFMPEG=true` | Install ffmpeg |
+| `INSTALL_ARIA2=true` | Install aria2 |
diff --git a/pages/en/guide/installation/truenas.md b/pages/en/guide/installation/truenas.md
new file mode 100644
index 000000000..e4d3c636c
--- /dev/null
+++ b/pages/en/guide/installation/truenas.md
@@ -0,0 +1,88 @@
+---
+top: 44
+categories:
+ - guide
+ - installation
+---
+
+# Use TrueNAS Scale
+
+## Install the App
+
+Since OpenList is not officially available in the TrueNAS Apps catalog, you must use the **Custom App** feature to install it.
+
+Follow these steps to deploy OpenList via the **Install iX App** wizard:
+
+1. **Application Name**
+ Enter a name for your application (e.g., `openlist`). Keep the default version unless you require a specific tag.
+
+ 
+
+2. **Image Configuration**
+ - **Repository**: `openlistteam/openlist`
+ - **Tag**: `latest` (or specify another version if needed)
+ Leave all other fields at their defaults.
+
+ 
+
+3. **Container Configuration**
+ - **Environment Variables**:
+ Add a new variable:
+ - Name: `UMASK`
+ - Value: `022`
+ - **Restart Policy**: Select `Unless Stopped` to ensure automatic restart on failure.
+ - **Entrypoint**: Leave unchanged — it is pre-configured.
+ Other settings may be adjusted as desired.
+
+ 
+
+4. **Device**
+ No device passthrough is required for basic operation. Keep defaults.
+
+5. **Security Context Configuration**
+ - ✅ Check **Custom User**
+ - Set **UID** and **GID** to match a non-root user with permissions to access your storage volumes.
+ Default: `568/568` (apps/apps) — recommended for security.
+ - ⚠️ Avoid using `root` (UID/GID = 0) unless absolutely necessary — it poses a security risk.
+ > 💡 If you plan to use an **ixVolume** later, ensure this user has write permissions to the target dataset.
+
+ 
+
+6. **Network Configuration**
+ - Add a port mapping:
+ - **Host Port**: Any unused port (e.g., `10544`)
+ - **Container Port**: `5244`
+ - **Host IP**: `0.0.0.0` (accessible from any network) or restrict to a local IP if preferred.
+ Add additional mappings only if exposing other services.
+
+ 
+
+7. **Portal Configuration**
+ - **Port**: Match the Host Port from Step 6 (e.g., `10544`)
+ - **Name**: Optional — set to something descriptive like “OpenList Web UI”
+ Once saved, a **Web UI** button will appear on the Apps page.
+
+ 
+
+8. **Storage Configuration**
+ - ✅ **Mandatory**: At least one volume must be configured.
+ - Click **Add** → Select storage type (`ixVolume` recommended for persistence).
+ - **Mount Path**: `/opt/openlist/data`
+ - Ensure the container’s user (from Step 5) has **write permissions** to this location.
+ - Optionally add more volumes for logs, configs, etc.
+
+ > 📌 Tip: Use **ixVolume** instead of host paths when possible — it ensures better integration with TrueNAS backup and snapshot features.
+
+ 
+
+9. **Labels Configuration**
+ Skip — not required for basic operation.
+
+10. **Resources Configuration** _(Optional)_
+ Set CPU/memory limits if you wish to constrain resource usage (e.g., 1 core, 512MB RAM).
+
+ 
+
+11. **Final Step**
+ Click **Install** to deploy the OpenList container.
+ Wait for status to turn green → then click **Web UI** to access the interface.
diff --git a/pages/en/guide/installation/worker.md b/pages/en/guide/installation/worker.md
new file mode 100644
index 000000000..172341173
--- /dev/null
+++ b/pages/en/guide/installation/worker.md
@@ -0,0 +1,257 @@
+---
+top: 40
+categories:
+ - guide
+ - installation
+---
+
+# OpenList Worker
+
+## What is OpenList Worker
+
+[**OpenList Worker**](https://github.com/OpenListTeam/OpenList-Worker)（仓库 `OpenList-TSWorker`）是 OpenList 官方的 TypeScript + Serverless 移植版。后端由 Go 重写为运行于边缘平台上的 TypeScript 服务，前端复用官方 [OpenList-Frontend](https://github.com/OpenListTeam/OpenList-Frontend)（SolidJS），无需自备服务器即可一键部署。
+
+- **后端**：Hono.js（TypeScript）
+- **运行平台**：Cloudflare Workers / EdgeOne Functions / Alibaba Cloud ESA / Vercel / AWS Lambda
+- **数据库**：Cloudflare D1（SQLite）、MySQL / MariaDB / PostgreSQL / SQL Server、Cloudflare KV
+- **许可证**：AGPL-3.0
+
+## Supported Platforms
+
+| Platform | Persistence | One-click | Notes |
+| :--------------------------------- | :---------------- | :-------: | :------------------------------- |
+| Cloudflare Workers | D1 / KV / JSON | ✅ | Recommended, global edge network |
+| EdgeOne Makers（国际站 / 中国站） | EdgeOne Blob / KV | ✅ | Tencent Cloud edge platform |
+| Alibaba Cloud ESA | EdgeKV | ✅ | Alibaba edge function |
+| Vercel | In-memory（JSON） | — | No persistence by default |
+| AWS Lambda（Serverless Framework） | In-memory（JSON） | — | `serverless.yml` |
+
+## One-click Deploy
+
+Click the button below to deploy to the corresponding platform:
+
+| EdgeOne Makers · 国际站 | EdgeOne Makers · 中国站 | Cloudflare Workers · 全球站 |
+| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
+| [](https://edgeone.ai/pages/new?project-name=openlist-tsworker&repository-url=https://github.com/OpenListTeam/OpenList-Worker&install-command=pnpm%20install%20--no-frozen-lockfile&build-command=pnpm%20run%20build&output-directory=dist&env=JWT_SECRET) | [](https://console.cloud.tencent.com/edgeone/pages/new?project-name=openlist-tsworker&repository-url=https://github.com/OpenListTeam/OpenList-Worker&install-command=pnpm%20install%20--no-frozen-lockfile&build-command=pnpm%20run%20build&output-directory=dist&env=JWT_SECRET) | [](https://deploy.workers.cloudflare.com/?url=https://github.com/OpenListTeam/OpenList-Worker) |
+
+> If Cloudflare prompts `无法获取存储库内容`（cannot fetch repository content）, fork this project first, then deploy by connecting to the GitHub repository.
+
+## Initialization
+
+::: tip
+After deployment, the first visit to the site automatically enters an **installation wizard**. Set the admin account and password in the browser to complete initialization — no pre-configured `ADMIN_PASS` is required.
+:::
+
+## Environment Variables
+
+| Variable | Required | Default | Description |
+| :----------------------------------------------------------------------- | :---------- | :--------- | :--------------------------------------------------------------------------------------------------------------- |
+| `JWT_SECRET` | Recommended | — | JWT signing key, also used for data encryption and cron task auth. Auto-generated and persisted to KV when unset |
+| `DB_FORMAT` | Optional | `map` | Storage format: `map` (whole JSON) / `key` (per-key) / `sql` (relational, Go-compatible) |
+| `DB_DRIVER` | Optional | `auto` | Database driver: `auto` / `blob` / `cfkv` / `kv` / `d1` / `do` / `mysql` |
+| `CF_ACCOUNT` | Optional | — | Cloudflare account ID (required for `cfkv` mode) |
+| `CF_KV_UUID` | Optional | — | Cloudflare KV namespace ID (required for `cfkv` mode) |
+| `CF_API_KEY` | Optional | — | Cloudflare API token (required for `cfkv` mode) |
+| `MYSQL_URL` | Optional | — | MySQL connection string (or use `MYSQL_*` fields below) |
+| `MYSQL_HOST` / `MYSQL_PORT` / `MYSQL_USER` / `MYSQL_PASS` / `MYSQL_NAME` | Optional | — | MySQL connection fields (`DB_DRIVER = mysql`) |
+| `ADMIN_PASS` | Optional | — | Skip the install wizard and auto-initialize admin with this password |
+| `ALLOW_URLS` | Optional | — | Comma-separated CORS allowlist |
+| `MAX_UPLOAD` | Optional | `26214400` | Max size (bytes) for a whole upload (`/put`, `/form`) |
+| `MAX_UPPART` | Optional | `16777216` | Max size (bytes) per chunk in multipart upload |
+| `ASSET_URLS` | Optional | — | Frontend asset CDN base URL, supports the `$version` placeholder |
+| `ALLOW_SEED` | Optional | — | Allowlist of hosts permitted as seed-data sources |
+
+## Data Backend（DB_FORMAT & DB_DRIVER）
+
+OpenList Worker separates persistence into two orthogonal layers:
+
+- **`DB_FORMAT`** — how data is serialized and stored
+- **`DB_DRIVER`** — which underlying storage system is used
+
+### `DB_FORMAT`（data storage format）
+
+| Value | Description |
+| :--------------- | :-------------------------------------------------------------------------- |
+| `map`（default） | Whole object serialized as a single JSON value, ideal for KV / Blob storage |
+| `key` | Per-key storage, one record per entity (avoids large JSON) |
+| `sql` | Relational tables, fully compatible with the Go backend (for D1 / MySQL) |
+
+### `DB_DRIVER`（database driver）
+
+| Value | Description | Suitable platform |
+| :---------------- | :---------------------------------------------------------------------------- | :------------------------ |
+| `auto`（default） | Auto-detect available driver（priority: blob → cfkv → kv → d1 → memory） | Universal, works anywhere |
+| `blob` | Tencent EdgeOne Blob / Alibaba ESA Blob | EdgeOne / ESA |
+| `cfkv` | Cloudflare KV REST API（requires `CF_ACCOUNT` / `CF_KV_UUID` / `CF_API_KEY`） | External / cross-account |
+| `kv` | Cloudflare KV binding | Cloudflare Workers |
+| `d1` | Cloudflare D1 (SQLite) | Cloudflare Workers |
+| `do` | Cloudflare Durable Objects (SQLite) | Cloudflare Workers |
+| `mysql` | External MySQL | Node.js container runtime |
+
+### Recommended combinations
+
+```bash
+# Cloudflare Workers + D1 (recommended, SQL format compatible with Go backend)
+DB_FORMAT=sql
+DB_DRIVER=d1
+```
+
+> **Backward compatibility:** the legacy `DB_DRIVER=json` auto-converts to `DB_FORMAT=map` + auto-detected driver.
+
+#### Table naming (SQL format)
+
+The `sql` format uses columnar tables with the same naming strategy as the Go backend's GORM: snake*case + pluralized table names, plus the fixed `x*` prefix.
+
+| Go struct | Table name |
+| :------------ | :---------------- |
+| `SettingItem` | `x_setting_items` |
+| `SharingDB` | `x_sharing_dbs` |
+| `Storage` | `x_storages` |
+| `User` | `x_users` |
+| `Meta` | `x_metas` |
+| _(TS only)_ | `x_plugins` |
+
+The prefix is fixed to `x_` (matching the Go backend default), so no extra configuration is needed to share the same physical database with the Go backend.
+
+## Deploy to Cloudflare Workers
+
+### Prerequisites
+
+- A [Cloudflare](https://dash.cloudflare.com/) account
+- Node.js 18+ and pnpm
+
+### Option 1: One-click deploy
+
+Click the **Deploy to Cloudflare Workers** button above. If it prompts that the repository cannot be fetched, fork the project first and deploy via the GitHub repository connection.
+
+### Option 2: Manual deploy with Wrangler
+
+```bash
+# 1. Clone and install dependencies
+git clone https://github.com/OpenListTeam/OpenList-Worker.git
+cd OpenList-Worker
+pnpm install
+
+# 2. Configure wrangler.jsonc (JWT_SECRET, KV / D1 bindings)
+
+# 3. Deploy to Cloudflare Workers
+pnpm run deploy:worker
+# or: pnpm run deploy (builds frontend + deploys backend)
+```
+
+### D1 database
+
+Use Cloudflare's _Automatic resource provisioning_: omit `database_id` in `wrangler.d1.jsonc`, and wrangler (>= 4.45.0) auto-creates a D1 database with the same name and writes back the ID on deploy:
+
+```jsonc
+{
+ "vars": { "DB_FORMAT": "sql", "DB_DRIVER": "d1" },
+ "d1_databases": [{ "binding": "DB", "database_name": "openlist-data-base" }],
+}
+```
+
+After deployment, configure the KV namespace binding and environment variables in the [Worker dashboard](https://dash.cloudflare.com/).
+
+## Deploy to EdgeOne
+
+### One-click deploy
+
+Click the **EdgeOne** deploy button above, choose the international or China site:
+
+- [International console](https://console.edgeone.ai/makers)
+- [China console](https://console.cloud.tencent.com/edgeone/makers)
+
+### Persistence
+
+EdgeOne Makers uses `@edgeone/pages-blob` for persistence. The default `auto` driver auto-detects Blob. You can also explicitly set `DB_DRIVER = "blob"` (with `DB_FORMAT = "map"`) or `DB_DRIVER = "kv"` (with `DB_FORMAT = "key"`).
+
+### Scheduled tasks
+
+EdgeOne supports scheduled refresh via `edgeone.json`. Set `cron_secret` in the payload to your `JWT_SECRET` value, and configure the schedule:
+
+```jsonc
+{
+ "schedules": [
+ {
+ "name": "token-refresh",
+ "cron": "0 2 * * *",
+ "path": "/api/task/refresh",
+ "method": "POST",
+ "payload": { "cron_secret": "" },
+ "timezone": "Asia/Shanghai",
+ },
+ ],
+}
+```
+
+## Deploy to Alibaba Cloud ESA
+
+OpenList Worker ships a dedicated ESA edge function entry (`esa-entry.ts`), which adapts Alibaba Cloud EdgeKV into the project's KV interface.
+
+### Build & deploy
+
+```bash
+# 1. Install dependencies
+pnpm install
+
+# 2. Build (produces dist/esa-entry.js)
+pnpm run build
+```
+
+`esa.jsonc` defines the edge function entry, install/build commands, and static assets directory:
+
+```jsonc
+{
+ "name": "openlist",
+ "entry": "./dist/esa-entry.js",
+ "installCommand": "pnpm install --no-frozen-lockfile",
+ "buildCommand": "pnpm run build",
+ "assets": { "directory": "./dist" },
+}
+```
+
+### KV namespace
+
+Configure the EdgeKV namespace via the `KV_NAMESPACE` environment variable (default `openlist`).
+
+::: tip
+ESA EdgeKV is eventually consistent. The entry implements a module-level TTL cache (60s) to avoid "saved settings revert after refresh" caused by cross-node sync delay.
+:::
+
+## Local Development
+
+```bash
+# 1. Install backend dependencies
+pnpm install
+
+# 2. Fetch frontend and run the backend (unified dev server)
+pnpm run dev:unified
+
+# Or run the worker directly (frontend built separately)
+pnpm run dev:worker
+```
+
+## Production Deploy
+
+```bash
+# One-click deploy (frontend build + backend deploy to Cloudflare Workers)
+pnpm run deploy
+```
+
+## Troubleshooting
+
+::: details Cloudflare prompts "cannot fetch repository content"
+Fork the project first, then deploy by connecting to the GitHub repository instead of the direct one-click URL.
+:::
+
+::: details Settings revert after save (ESA / EdgeOne)
+This is usually a KV/CDN cache consistency issue. The entry already forces `no-cache` on `/api/*` GET responses and implements a module-level KV cache. If it persists, check that your KV namespace is correctly bound and not read-only.
+:::
+
+::: details How do I reset the admin password?
+The admin password is set during the install wizard. To reset, you can set `ADMIN_PASS` temporarily and redeploy, or clear the persisted config and re-run the wizard.
+:::
+
+## Repository
+
+- [OpenListTeam/OpenList-Worker](https://github.com/OpenListTeam/OpenList-Worker)
diff --git a/pages/en/guide/migrate.md b/pages/en/guide/migrate.md
new file mode 100644
index 000000000..13f860ea6
--- /dev/null
+++ b/pages/en/guide/migrate.md
@@ -0,0 +1,113 @@
+---
+categories:
+ - guide
+top: 99999
+---
+
+# Migrate from AList V3
+
+::: danger
+Smooth migration is not compatible with Alist v3.46 and higher versions. If you want to migrate, please avoid upgrading to a higher version.
+:::
+
+## 1. Revoke Authorization for Alist API
+
+As the API service provided by the original author may have been taken over by a third party, there is a risk of information leakage or account bans. If you have concerns, it is recommended to revoke authorization or log in again to ensure your security.
+
+Since it's not possible to provide detailed steps for every platform, we invite helpful users to visit [https://github.com/OpenListTeam/OpenList-Docs](https://github.com/OpenListTeam/OpenList-Docs) and share screenshots of the authorization revocation process.
+
+The following content is provided by helpful online users in [OpenListTeam/OpenList-Docs#5](https://github.com/OpenListTeam/OpenList-Docs/issues/5) and [OpenListTeam/OpenList-Docs#6](https://github.com/OpenListTeam/OpenList-Docs/issues/6). We thank them for their contributions!🙏✨💖
+
+::: info The following methods only apply to cloud drives mounted using officially supported Open API methods.
+:::
+
+::: tip Quick overview of how to revoke authorization for each cloud drive ♿️
+
+- **Baidu Netdisk App** - My - Settings - Account Management - Authorization Management - Alist - Revoke Authorization
+- **Aliyun Drive** - My - Upper right gear icon - Privacy Settings - Authorization Management - Alist - Revoke Authorization
+- **115 APP** - Life (scroll down) - Account & Security - Multi-device Login Management - Third-party Login
+- **China Unicom Cloud** - Check login account on webpage - Future recommendation: follow tutorial for packet capture login
+- **Baidu Photo** - Avatar - App Settings - Account Management - Authorization Management
+- **JianGuoYun** - Upper left three lines - Settings - Third-party App Management - Revoke Authorization
+- **OneDrive** - https://account.live.com/consent/Manage - Revoke Authorization
+
+:::
+
+### Aliyun Drive
+
+1. Log in to Aliyun Drive
+2. Visit the link: [https://www.alipan.com/o/oauth/auth-list](https://www.alipan.com/o/oauth/auth-list)
+ 
+3. Find Alist under “**Authorized Cloud Services**,” click to enter, then click "**Revoke Authorization**"
+ 
+4. Successfully revoked
+ 
+
+### Aliyun Drive APP
+
+
+
+### Baidu Netdisk
+
+1. Log in to Baidu Netdisk
+2. Visit the link: [https://passport.baidu.com/v6/appAuthority](https://passport.baidu.com/v6/appAuthority)
+ 
+3. Find Alist in Authorization Management, click to enter, then click "**Revoke Authorization**"
+ 
+4. Successfully revoked
+
+### Baidu Netdisk APP
+
+
+
+### OneDrive Business
+
+Link: https://entra.microsoft.com/#view/Microsoft_AAD_RegisteredApps/ApplicationsListBlade/quickStartType~/null/sourceType/Microsoft_AAD_IAM?Microsoft_AAD_IAM_legacyAADRedirect=true
+
+
+
+### OneDrive Personal
+
+Link: https://account.live.com/consent/Manage
+
+
+
+### Google Drive
+
+Link: https://console.cloud.google.com
+
+
+
+
+
+
+
+## 2. Backup Configuration Files
+
+Use the [Backup & Restore](/en/guide/advanced/backup) function to back up the configuration files to your local device.
+
+Additionally, you will need to back up the `data` folder from Alist V3, which contains site configuration files and the database.
+
+## 3. Uninstall Alist V3
+
+Uninstall according to the method you used for installation.
+
+## 4. Install OpenList
+
+Follow the instructions provided in the documentation to install OpenList.
+
+::: danger
+If you are using Docker for deployment, make sure to modify the Volume mapping by changing the configuration file path from `/opt/alist/data` to `/opt/openlist/data`. Otherwise, your configuration files will be lost after updating the version and rebuilding the container!
+
+In addition, it is recommended to delete the previous container and then recreate it to avoid failure to run due to environmental changes.
+:::
+
+## 5. Restore Configuration Files
+
+If your Alist V3 version is below v3.46, you can migrate directly—keeping the previous `data` folder and only replacing the OpenList binary files.
+
+Otherwise, use the [Backup & Restore](/en/guide/advanced/backup) function to restore the backed-up configuration files to OpenList.
+
+## 6. Reset Settings
+
+Once in OpenList’s admin panel, on each settings page, click the `Load Default Settings` button at the bottom, then click `Save`.
diff --git a/pages/en/index.md b/pages/en/index.md
new file mode 100644
index 000000000..52f5b8510
--- /dev/null
+++ b/pages/en/index.md
@@ -0,0 +1,28 @@
+---
+layout: home
+title: OpenList
+titleTemplate: OpenList Docs
+description: OpenList is a resilient, community-driven file list program that supports multiple cloud storage platforms. Built as a secure fork of AList with enhanced security and long-term governance.
+comment: false
+
+# rendered by .vitepress/theme/components/HomeHero.vue
+landing:
+ name: OpenList
+ tagline: |-
+ 🗂️ A file list program that supports multiple storage,
+ powered by Gin and SolidJS!
+ actions:
+ - theme: brand
+ text: Get Started
+ link: /en/guide/
+ - theme: alt
+ text: View GitHub
+ link: https://github.com/OpenListTeam/OpenList
+ links:
+ - text: Disclaimer
+ link: /en/terms#disclaimer
+ - text: Terms of Service
+ link: /en/terms
+ - text: Privacy Policy
+ link: /en/privacy
+---
diff --git a/pages/en/privacy.md b/pages/en/privacy.md
new file mode 100644
index 000000000..db229faa3
--- /dev/null
+++ b/pages/en/privacy.md
@@ -0,0 +1,21 @@
+---
+sidebar: false
+aside: false
+outline: false
+pageClass: statement-page
+comment: false
+contributors: false
+---
+
+# Privacy Policy
+
+We highly value your privacy. We **DO NOT collect any of your personal information**. However, please be aware that your IP address and other metadata might be collected by your ISP or intermediate network nodes beyond our control.
+
+## Privacy Policy
+
+- We DO NOT collect, store, process, or analyze any of your personal data.
+- We DO NOT use any tracking technologies (such as cookies, fingerprinting, web beacons, etc.) to gather your data.
+- We DO NOT share your information with any third parties.
+- Your actions within this service are NOT recorded by us.
+- HOWEVER, your IP address and visit time may be collected by your ISP or transit nodes as part of normal Internet infrastructure behavior, which is BEYOND our control.
+- If you have any privacy-related concerns, please feel free to contact us.
diff --git a/pages/en/seeds/background.md b/pages/en/seeds/background.md
new file mode 100644
index 000000000..e49bce51a
--- /dev/null
+++ b/pages/en/seeds/background.md
@@ -0,0 +1,45 @@
+---
+categories:
+ - seeds
+top: 990
+---
+
+# Background
+
+## Overview
+
+1. Users can generate a seed for one or more files — on local disk or on a drive — to share file information, or to re-upload after the files are lost.
+2. Users can share seeds to perform offline rapid upload, file sharing, backup, and space release across drives, users, and devices.
+3. Generic BT clients can download the files inside a seed through a server proxy over the drive; OSS-compatible clients can rapid-upload or download via the server proxy.
+
+## Glossary
+
+| Term | Meaning |
+| --------------- | ---------------------------------------------------------------------------------------------------- |
+| Transfer Seed | A portable file-metadata system built on three sidecar formats |
+| Sidecar | A companion file alongside the main file, e.g. `movie.mp4.torrent` |
+| Seed | An `openlist-sharing-seed` v1 document describing path, size, hashes, and sources for a set of files |
+| Hash Matrix | Specifies which hashes to compute per file (md5/sha1/sha256 × whole/pieces) |
+| Piece | A block produced by splitting a file at `piece_size`; each piece has its own hash |
+| Whole hash | A single hash computed over the entire file |
+| Piece hashes | An array of hashes, one per piece |
+| Rapid upload | Reusing known hashes so a drive completes instantly without re-sending content |
+| Relay / Transit | Save synchronously to an intermediate drive, then copy server-side to the final drive |
+| Channel | Where a seed is mounted on a drive (`driver` + `mount_path`) |
+
+## Format roles
+
+| Format | Suffix | Encoding | Completeness | Primary use |
+| --------------------- | ---------- | ----------- | --------------------------------------------------------- | -------------------------------------------- |
+| OpenList Sharing Seed | `.oss` | JSON | Highest, losslessly carries all fields | OpenList-internal share / edit / recalculate |
+| BitTorrent | `.torrent` | bencode | Medium, standard fields + `x-openlist` lossless extension | Generic BT clients / offline tools |
+| CAS | `.cas` | Base64 JSON | Low, only rapid-upload hashes | 189pc rapid upload |
+
+The three are projections of the same file metadata: `.oss` is the superset, while `.torrent` and `.cas` are its semantic projections (see [Design principles](/en/seeds/design)).
+
+## Typical scenarios
+
+1. **Cross-drive migration**: move files from Aliyundrive to 189pc. A seed carrying SHA1 + MD5 + piece hashes lets the destination hit the hash and rapid-upload without a full download-then-upload.
+2. **Sharing**: share a `.oss` or `.torrent` so a friend rapid-uploads or offline-downloads on their own drive without consuming the sharer's egress.
+3. **Backup and space release**: generate a seed, delete the original, and re-rapid-upload it later from the seed.
+4. **Integrity verification**: per-piece hashes verify whether a downloaded file is complete and locate damaged pieces.
diff --git a/pages/en/seeds/design.md b/pages/en/seeds/design.md
new file mode 100644
index 000000000..755a7bb1b
--- /dev/null
+++ b/pages/en/seeds/design.md
@@ -0,0 +1,287 @@
+---
+categories:
+ - seeds
+top: 980
+---
+
+# Design principles
+
+## Goals
+
+1. **Portable**: three convertible sidecar formats for sharing file information across drives, users, and devices.
+2. **Reuse hashes to avoid redundant downloads**: reuse drive-provided hashes or stream-hash files.
+3. **Third-party compatible**: `.torrent` follows BT v1, and the `.cas` single-file five fields are byte-compatible with the reference project.
+4. **Safe and bounded**: parsing is bounded by byte/file/depth/path-traversal limits, and seeds never serialize credentials.
+
+## Format relationships
+
+The three formats are different projections of the same file metadata. `.oss` is the most complete; `.torrent` and `.cas` are its semantic projections:
+
+- `.oss` ⊇ `.torrent`: `.oss` converts to `.torrent` when it has the required BT info (SHA-1 whole + pieces); `.torrent` always converts to `.oss`.
+- `.oss` ⊇ `.cas`: `.oss` converts to `.cas` when it has whole + piece MD5; `.cas` always converts to `.oss`.
+- Conversion diagnostics report exactly what is missing.
+
+```mermaid
+graph TD
+ OSS[.oss most complete] -->|has BT-required info| TORRENT[.torrent]
+ TORRENT -->|always convertible| OSS
+ OSS -->|has whole + piece MD5| CAS[.cas]
+ CAS -->|always convertible| OSS
+ TORRENT -.->|has x-cas extension| CAS
+ CAS -.->|missing SHA1 pieces, not directly convertible| TORRENT
+```
+
+## Seed design
+
+### `.oss` structure
+
+`.oss` is the most complete JSON container:
+
+| Field | Description |
+| --------------------------- | ----------------------------------------------------------------- |
+| `format` / `version` | fixed `openlist-sharing-seed` / `1` |
+| `name` | seed name (editable, auto-derived if empty) |
+| `comment` | overall comment |
+| `created_at` / `created_by` | creation time / creator |
+| `piece_size` | piece size (default 10 MiB) |
+| `trackers` | tracker list |
+| `channels` | channels (`driver` + optional `mount_path`), public metadata only |
+| `files` | file array |
+
+Each file (`files[]`) carries:
+
+| Field | Description |
+| ----------------------------------- | ----------------------------------------------- |
+| `path` / `size` / `modified` | path / size / mtime |
+| `comment` | per-file comment |
+| `hashes.md5` / `sha1` / `sha256` | whole-file hashes |
+| `hashes.pieces` | per-algorithm piece hashes |
+| `sources` | public direct (`/d/`) or share (`/sd/`) sources |
+| `cas_slice_md5` / `cas_create_time` | CAS aggregate slice MD5 / create time |
+| `missing_channels` | drives that failed rapid upload |
+
+### `.torrent` structure
+
+A standard BitTorrent v1 file whose info dict holds `piece length` and `pieces` (SHA-1), plus two extension keys:
+
+- `x-openlist`: the full OpenList seed (MD5/SHA256, comments, channels, shares, etc.).
+- `x-cas`: 189pc CAS info (`file_md5` / `slice_md5` / `slice_size`).
+
+### `.cas` structure
+
+A base64-encoded JSON, compatible with the reference five-field single-file payload and extended for multiple files:
+
+```json
+{
+ "name": "example",
+ "size": 12345,
+ "md5": "d41d8cd98f00b204e9800998ecf8427e",
+ "sliceMd5": "…",
+ "create_time": "1720000000",
+ "slice_md5s": ["…", "…"],
+ "slice_size": 10485760,
+ "files": [{ "name": "a.txt", "size": 100, "md5": "…", "sliceMd5": "…", "create_time": "…" }]
+}
+```
+
+- Single file uses the top-level five fields (byte-compatible with the reference project); multiple files use the `files` array.
+- `slice_md5s` / `slice_size` are optional extensions preserving the per-piece MD5 list for 189pc rapid upload.
+- Third-party CAS clients use standard JSON parsing and ignore extra fields, remaining backward compatible.
+
+## Field spec and safety bounds
+
+Every inbound seed (regardless of whether it comes from `.oss` / `.torrent` / `.cas` or arbitrary JSON) first passes through **normalization**, which enforces these hard limits at parse time:
+
+| Constraint | Value |
+| ------------------------- | ------------------------------------------------------------------ |
+| `piece_size` valid range | 16 KiB ~ 64 MiB (default 10 MiB) |
+| File count | 1 ~ 100,000 |
+| Max per-file path length | 4096 bytes |
+| Max path depth | 64 levels |
+| Piece hash count | must equal `ceil(size / piece_size)` (0 for empty files) |
+| Max bencode nesting depth | 32 |
+| Max bencode item count | 100,000 |
+| Path safety | reject `\0`, backslash `\`, leading `/`, empty segments, `.`, `..` |
+| Name safety | reject empty, `.`, `..`, or names containing `/` or `\` |
+| `sources` URL | must be absolute with a scheme |
+| `channels.mount_path` | reject `?`, `#`, `\0` |
+
+Seeds **never serialize credentials** (e.g. `cookie`, `access_token`); `channels` keeps only public metadata like `driver` and `mount_path`. Normalization also applies these fixes:
+
+- Hashes are lowercased; invalid hashes error (md5 32, sha1 40, sha256 64 hex chars).
+- Missing `name` falls back to the first segment of `files[0].path`.
+- Missing `format` / `version` default to `openlist-sharing-seed` / `1`.
+- Missing `created_at` / `created_by` default to now / `OpenList`.
+- Duplicate file paths error.
+
+## Hash matrix design
+
+The hash matrix is a 3×2 boolean selection specifying which hashes to compute per file:
+
+```json
+{
+ "md5": { "whole": true, "pieces": true },
+ "sha1": { "whole": true, "pieces": true },
+ "sha256": { "whole": true, "pieces": true }
+}
+```
+
+- **whole**: a single whole-file hash (`hashes.md5` / `sha1` / `sha256`).
+- **pieces**: per-piece hash arrays (`hashes.pieces.md5[]` / `sha1[]` / `sha256[]`).
+
+Normalization rules:
+
+1. **All-empty means all-on**: when all six flags are `false`, they are treated as all `true` ("compute as much as possible").
+2. **Format forcing**: selecting `.torrent` forces `sha1.whole = true` and `sha1.pieces = true`; selecting `.cas` forces `md5.whole = true` and `md5.pieces = true`. The UI disables these checkboxes with a "required by this format" hint.
+3. **Reuse drive hashes**: the generation wizard calls `capabilities` first and pre-selects the hashes the drive already exposes, avoiding redundant downloads.
+
+The matrix decides whether generation must download: piece hashes are generally not exposed by drive listings, so any `pieces` requirement forces a streaming download; a missing whole hash also forces a download.
+
+## Encoding and conversion details
+
+### bencode (the encoding underneath `.torrent`)
+
+`.torrent` uses bencode. Dictionary keys must be sorted by byte order. The encoder handles the four value types:
+
+- integer → `ie` (errors when out of safe-integer range)
+- byte string → `:`
+- list → `le`
+- dictionary → `de`
+
+The parser enforces depth ≤ 32, items ≤ 100,000, and rejects trailing data.
+
+### The `.torrent` info dictionary
+
+- Single file: `info` holds `name`, `piece length`, `pieces`, `length`, optional `md5sum`.
+- Multi-file: `info` holds `name`, `piece length`, `pieces`, `files` (each with `length`, `path`, optional `md5sum`).
+- `pieces` is the concatenation of all SHA-1 piece hashes in order (20 bytes each); parsing verifies the piece count equals `ceil(total_size / piece_size)`.
+- `info_hash` = SHA-1(bencode(info)), used for magnet links and BT identification.
+
+OpenList extension keys:
+
+- `x-openlist`: a lossless bencode-embedding of the full `.oss` seed (JSON values recursively mapped to bencode values), letting OpenList clients fully reconstruct the metadata.
+- `x-cas`: `{ cloud, file_md5, slice_md5, slice_md5s, slice_size }` for 189pc rapid upload; written only for a single file with MD5.
+- `announce` / `announce-list`: derived from `trackers` (first tracker becomes `announce`).
+- `creation date` / `comment` / `created by`: standard metadata.
+
+When `x-openlist` is present at parse time, its consistency with the info dict is validated (name, piece_size, file count, each file's path and size); any mismatch errors out to prevent forgery.
+
+### Multi-file `.torrent` boundary limit
+
+All files in a BT v1 torrent share one piece sequence, so when `files.length > 1`, every file except the last must have a size divisible by `piece_size`; otherwise a piece is split by a file boundary and cannot be legally divided. Conversion reports `a file boundary splits a piece`.
+
+### `.cas` `sliceMd5` rules
+
+- When the piece size equals 10 MiB (`DEFAULT_PIECE_SIZE`) and a per-piece MD5 list exists:
+ - one piece → `sliceMd5 = that piece MD5`.
+ - multiple pieces → `sliceMd5 = md5(per-piece MD5s uppercased and joined by newline)`.
+- When per-piece MD5 is absent:
+ - file ≤ 10 MiB → use the whole-file MD5 as `sliceMd5`.
+ - file > 10 MiB and no legacy `cas_slice_md5` → conversion errors (cannot derive safely).
+
+Encoding `.cas` emits base64-encoded JSON; decoding tries base64 first and falls back to plain JSON (for legacy files).
+
+### Format auto-detection
+
+The `parse` API detects the format by the first character: `{` → `.oss` (JSON), `d` → `.torrent` (bencode dict), otherwise → `.cas`. An explicit `format` hint can override this.
+
+## Architecture
+
+Seed capability is provided by two equivalent implementations, one per backend:
+
+| Backend | Language | Format library | API layer |
+| ----------------- | ---------- | ------------------------------------------------------------------------- | --------------------------- |
+| OpenList-Backends | Go | `pkg/torrent/` (bencode, hash writer, generate, parse, convert, diagnose) | `server/handles/torrent.go` |
+| OpenList-TSWorker | TypeScript | `internal/seed/` (`codec.ts`, `hash.ts`, `types.ts`) | `server/seed.ts` |
+
+Both share the same field spec and codec logic (bencode sorting, CAS `sliceMd5` derivation, hash-matrix normalization, consistency validation), so seeds produced by the Cloudflare Worker and Go versions interoperate.
+
+```mermaid
+graph LR
+ UI[HopeUI frontend] -->|POST /fs/seed/*| GO[Go backend]
+ UI -->|POST /fs/seed/*| TS[TS Worker backend]
+ GO --> FMT[pkg/torrent format library]
+ TS --> TSFMT[internal/seed codec]
+ GO --> DRV[drivers: 189pc / PutURL / offline]
+ TS --> TSDRV[drivers: rapid / session / stream]
+```
+
+Core components:
+
+- **`HashWriter` / `TorrentPieceHasher`**: streaming hashers that maintain whole-file hashes (md5/sha1/sha256) plus per-piece hashes in a single pass, avoiding a second read.
+- **Normalization layer**: `normalizeSeed` (and the Go equivalent) applies field defaults and safety validation.
+- **Conversion layer**: encode/decode between `.oss` ↔ `.torrent` ↔ `.cas`, with missing-information diagnostics.
+- **Capability preflight**: `capabilities` summarizes per file "hashes available / download needed / streamable", reused by the UI and generation logic.
+
+## Data model
+
+Both the Go and TS backends share one data model with identical field names, ensuring seeds from either backend interoperate. The core structures are:
+
+### `Seed`
+
+| Field | Type | Description |
+| ------------ | ------------------- | ----------------------------------- |
+| `format` | `string` | fixed `openlist-sharing-seed` |
+| `version` | `number` | fixed `1` |
+| `name` | `string` | seed name |
+| `comment` | `string` | overall comment |
+| `created_at` | `string` (ISO 8601) | creation time |
+| `created_by` | `string` | creator |
+| `piece_size` | `number` | piece size in bytes, default 10 MiB |
+| `trackers` | `string[]` | tracker list |
+| `channels` | `SeedChannel[]` | channels that saved successfully |
+| `files` | `SeedFile[]` | file array |
+
+### `SeedFile`
+
+| Field | Type | Description |
+| ------------------ | -------------- | -------------------------------- |
+| `path` | `string` | relative path |
+| `size` | `number` | size in bytes |
+| `modified` | `string` | mtime (ISO 8601) |
+| `comment` | `string` | per-file comment |
+| `hashes` | `SeedHashes` | hash collection |
+| `sources` | `SeedSource[]` | public direct / share sources |
+| `cas_slice_md5` | `string` | CAS aggregate slice MD5 (legacy) |
+| `cas_create_time` | `string` | CAS creation time (legacy) |
+| `missing_channels` | `string[]` | drives that failed rapid upload |
+
+### `SeedHashes`
+
+| Field | Type | Description |
+| -------- | -------- | ---------------------------------------------- |
+| `md5` | `string` | whole-file MD5 |
+| `sha1` | `string` | whole-file SHA-1 |
+| `sha256` | `string` | whole-file SHA-256 |
+| `pieces` | `object` | `{ md5[], sha1[], sha256[] }` per-piece arrays |
+
+### `SeedSource`
+
+| Field | Type | Description |
+| ------------ | -------- | --------------------------------------------------- |
+| `type` | `string` | `openlist-direct` or `openlist-share` |
+| `url` | `string` | absolute URL, restricted to the configured site URL |
+| `expires_at` | `string` | expiry time (optional) |
+| `share_id` | `string` | share ID (for `openlist-share`) |
+
+### `SeedChannel`
+
+| Field | Type | Description |
+| ------------ | -------- | --------------------- |
+| `driver` | `string` | driver name |
+| `mount_path` | `string` | mount path (optional) |
+
+### `CASPayload` (`.cas` payload)
+
+| Field | Type | Description |
+| ------------- | ----------- | -------------------------------------------------- |
+| `name` | `string` | file name |
+| `size` | `number` | file size |
+| `md5` | `string` | whole MD5 |
+| `sliceMd5` | `string` | aggregate slice MD5 |
+| `create_time` | `string` | creation time |
+| `slice_md5s` | `string[]` | per-piece MD5 (optional extension) |
+| `slice_size` | `number` | piece size (optional extension, default 10 MiB) |
+| `files` | `CASFile[]` | per-file array for multi-file (optional extension) |
+
+> Single file uses the top-level five fields (`name`/`size`/`md5`/`sliceMd5`/`create_time`), byte-compatible with the reference project; multiple files use the `files` array; `slice_md5s`/`slice_size` preserve per-piece MD5 for 189pc rapid upload.
diff --git a/pages/en/seeds/faq.md b/pages/en/seeds/faq.md
new file mode 100644
index 000000000..caf74d9c4
--- /dev/null
+++ b/pages/en/seeds/faq.md
@@ -0,0 +1,65 @@
+---
+categories:
+ - seeds
+top: 940
+---
+
+# FAQ
+
+## Notes
+
+- `.cas` per-piece MD5 and multi-file support rely on optional extension fields; the single-file five fields remain byte-compatible with the reference project.
+- Relayed transfer requires an intermediate storage with synchronous native reuse or PutURL.
+- Recalculation requires the source file to already exist on the server.
+- The generated `.torrent` is a valid BT file, but OpenList itself is not a BT peer.
+- All seed parsing is bounded by byte, file-count, depth, and path-traversal limits.
+
+## Common questions
+
+### Why is my generated `.cas` flagged as Legacy CAS?
+
+A legacy CAS only carries the five fields `name`, `size`, `md5`, aggregate `sliceMd5`, and creation time, with no per-piece MD5 list, so conversion is lossy. Newer generation writes `slice_md5s` / `slice_size` to preserve per-piece MD5, and the preview no longer shows the Legacy CAS warning when piece hashes are present.
+
+### Why can't a seed with only MD5 convert to `.torrent`?
+
+`.torrent` follows the BT v1 spec and requires SHA-1 whole + piece hashes. MD5 alone cannot produce a valid `pieces` field; conversion reports the missing SHA-1 pieces explicitly.
+
+### Why does multi-file `.torrent` conversion report "a file boundary splits a piece"?
+
+All files in a BT v1 torrent share one piece sequence. In multi-file mode, every file except the last must have a size divisible by `piece_size`; otherwise a piece is cut by a file boundary and cannot be legally divided. Adjust the piece size or use a single file so sizes align.
+
+### Why does rapid upload report `unavailable`?
+
+When the destination drive cannot reuse the hashes in the current seed, the operation reports `unavailable` instead of silently degrading to a normal upload. Make sure the seed contains the hashes the target drive requires (see the [rapid upload matrix](/en/seeds/rapid-upload)).
+
+### Why can't relayed transfer use asynchronous offline download?
+
+Asynchronous offline download cannot guarantee the intermediate storage has fully landed before the server-side copy to the final drive. Relaying therefore requires the intermediate storage to support synchronous native reuse or PutURL.
+
+### Can a generated `.torrent` be downloaded by a generic BT client?
+
+The generated `.torrent` is a valid BT v1 file and can be handed to an offline tool via magnet. However, OpenList itself is not a BT peer; whether generic BT clients can download depends on the tracker/webseed deployment.
+
+### Why does recalculation require the source file on the server?
+
+Recalculation re-reads an existing server-side file to recompute hashes; it never downloads from an external source. Upload or save the file to the server first if it is not already there.
+
+### How do I enable automatic sidecar generation on upload?
+
+The upload API is controlled by headers: set `X-Seed-Sidecars` (e.g. `oss,torrent,cas`) to specify formats directly, or combine `X-Generate-Seed: on` with the storage-level `seed_policy` and the global `seed_auto_generate_policy`. The global policy defaults to `off`, so nothing is generated by default.
+
+### Why can't asynchronous upload (`as_task=true`) generate sidecars?
+
+Sidecar generation must read the full upload stream and hash it in one pass. An async task cannot guarantee the complete stream is available in the same process and written synchronously, so the upload API returns 400 for the "sidecars + async upload" combination.
+
+### What does an all-empty hash matrix mean?
+
+When all six flags (md5/sha1/sha256 × whole/pieces) are `false`, the system treats it as "compute as much as possible", equivalent to selecting everything. To produce a minimal seed, explicitly select only the hashes you need.
+
+### What is `x-openlist` inside a `.torrent`?
+
+`x-openlist` is OpenList's lossless extension key that bencode-embeds the full `.oss` seed into a standard torrent. OpenList clients use it to fully reconstruct MD5/SHA256, comments, channels, and shares; parsing also validates its consistency with the info dictionary to prevent forgery.
+
+### Why are background seed-generation tasks lost on restart?
+
+Requests over 1 GiB are queued as background tasks, but those tasks are not persisted; an unfinished task is lost when the service restarts and must be re-triggered. Small files (≤ 1 GiB) are generated synchronously and are unaffected.
diff --git a/pages/en/seeds/generate.md b/pages/en/seeds/generate.md
new file mode 100644
index 000000000..20a9e7a0e
--- /dev/null
+++ b/pages/en/seeds/generate.md
@@ -0,0 +1,101 @@
+---
+categories:
+ - seeds
+top: 970
+---
+
+# Generating seeds
+
+## Generate on upload
+
+While uploading, you can enable `.oss` / `.torrent` / `.cas` sidecars (all off by default). The sidecars are produced alongside the streaming hash calculation without a second read.
+
+## Generate from the context menu
+
+Right-click one or more files and choose "Generate transfer seed" to open the wizard:
+
+1. **Seed name**: editable, auto-derived when empty (file name for single selection, common prefix or folder for multiple).
+2. **Formats**: enable `.oss` / `.torrent` / `.cas` (any combination).
+3. **Hash matrix**: choose MD5 / SHA-1 / SHA-256 whole and piece hashes, pre-selecting the hashes the drive already provides.
+4. **Piece size**: defaults to 10 MiB.
+5. **File list**: shows each file's size, drive-provided hashes, whether a download is needed, and the generation mode (direct/download); per-file comments and per-file share/direct toggles.
+6. **Trackers**: picked from the system-configured tracker list.
+
+## Seed naming
+
+The seed name is editable; when empty it is auto-derived in this priority:
+
+1. **Single file**: the file name with its extension removed.
+2. **Multiple files sharing a base name**: if all files share the same name after removing extensions (e.g. `a.mkv`, `a.srt`, `a.ass` in one folder), use that common name.
+3. **Otherwise**: the common parent directory name.
+4. **Fallback**: `OpenList Seed`.
+
+Naming is subject to the same safety checks (rejecting empty names, `.`, `..`, or names containing `/` or `\`).
+
+## Generation modes
+
+- **Direct**: the drive already provides all required hashes, no download needed.
+- **Download**: files are streamed and hashed on the fly, with estimated traffic shown.
+- If the drive cannot stream files, generation is blocked with a hint; requests over 1 GiB are queued as a background task.
+
+## Generate API
+
+Right-click generation calls `POST /fs/seed/generate` (compatible with the legacy `POST /fs/torrent/generate`). Request body:
+
+| Field | Type | Description |
+| --------------- | ---------------------- | ------------------------------------------------------- |
+| `paths` | `string[]` | source file/directory paths |
+| `formats` | `SeedFormat[]` | target formats: `oss` / `torrent` / `cas` |
+| `hash_matrix` | `SeedHashMatrix` | hash matrix (see [Design principles](/en/seeds/design)) |
+| `piece_size` | `number` | piece size in bytes, default 10 MiB |
+| `name` | `string` | seed name (optional, auto-derived) |
+| `comment` | `string` | overall comment (optional) |
+| `file_comments` | `Record` | per-file comments (optional) |
+| `trackers` | `string[]` | tracker list (optional) |
+| `share_files` | `string[]` | file paths to record share links (`/sd/`) |
+| `direct_files` | `string[]` | file paths to record public direct links (`/d/`) |
+| `output_path` | `string` | directory to save the generated sidecars |
+
+Returns `SeedGenerateResult`: on synchronous completion it carries the produced paths; a non-empty `task` or `async` field means the request was queued as a background task.
+
+## Upload sidecar mechanics
+
+The upload API (`POST /fs/put`) hashes **while streaming** and then writes the sidecars alongside the main file. Whether to generate is decided in this priority order:
+
+1. Header `X-Seed-Sidecars`: explicit formats (e.g. `oss,torrent,cas`); non-empty enables generation.
+2. Header `X-Generate-Seed`: `on` / `true` / `1` enables, `off` disables, `inherit` or empty falls through.
+3. Storage-level `seed_policy`: the target storage's `on` / `off` / `inherit`.
+4. Global setting `seed_auto_generate_policy`: defaults to `off`.
+
+Other sidecar headers:
+
+| Header | Purpose |
+| -------------------- | ------------------------------------------------------------ |
+| `X-Seed-Format` | Equivalent to `X-Seed-Sidecars`, specifies formats |
+| `X-Seed-Piece-Size` | Piece size in bytes; forced to 10 MiB when `cas` is included |
+| `X-Seed-Hash-Matrix` | JSON hash matrix controlling which hashes are written |
+
+Constraints and details:
+
+- Upload sidecars require **synchronous upload**; an async upload (`as_task=true`) returns 400 (sidecars need a complete streaming hash, which cannot be guaranteed in a background task).
+- Hashing reuses the upload stream via `io.TeeReader`, so one read both uploads and hashes — no second read.
+- After upload, the byte count read by the `HashWriter` is verified against the declared size; a mismatch errors out (keeping sidecar hashes consistent with the landed file).
+- Sidecars are written as `.` in the same directory (e.g. `movie.mp4.torrent`, `movie.mp4.cas`, `movie.mp4.oss`).
+- When no format is given, enabled formats are resolved from the global `seed_format_policies`.
+
+## Background tasks
+
+When the total size of a generation request exceeds 1 GiB, it is queued as a background task so the request thread is not blocked. On completion the sidecars are written to `output_path`, and progress/result can be checked in the task center.
+
+Requests over the 1 GiB threshold go background automatically; everything else returns the produced paths synchronously.
+
+## Previewing seeds
+
+Opening a `.oss` / `.torrent` / `.cas` file shows a unified preview with:
+
+- file list and sizes
+- per-file hashes (whole + pieces, copyable with a per-piece popup)
+- file comments, timestamps, multi-line overall comment
+- trackers, channels, and share/direct sources
+- conversion feasibility (✓/✗, hover or click for missing reasons)
+- available operations (rapid upload, offline download, transfer, convert, edit, recalculate, preview/remove a single file)
diff --git a/pages/en/seeds/index.md b/pages/en/seeds/index.md
new file mode 100644
index 000000000..e281156b0
--- /dev/null
+++ b/pages/en/seeds/index.md
@@ -0,0 +1,26 @@
+---
+categories:
+ - seeds
+top: 1000
+---
+
+# Transfer Seeds
+
+## What are Transfer Seeds
+
+Transfer Seeds are a portable file-metadata system built on three sidecar formats for sharing file information, offline rapid-upload, backup, and space release across drives, users, and devices.
+
+- **`.oss`** (`openlist-sharing-seed` v1): the most complete JSON format; every field is optional.
+- **`.torrent`**: a standard BitTorrent v1 file with OpenList extensions.
+- **`.cas`**: a content-addressable payload compatible with the reference project [OpenList-CAS](https://github.com/GitYuA/OpenList-CAS), used for 189pc rapid upload.
+
+The three formats convert between each other (when enough information is present) and support generation, preview, rapid upload, offline download, relayed save, editing, and recalculation.
+
+## Sections
+
+- [Background](/en/seeds/background) — why transfer seeds exist and current capability boundaries
+- [Design principles](/en/seeds/design) — design goals and the structure of the three formats
+- [Generating seeds](/en/seeds/generate) — generate on upload / from the context menu / preview
+- [Using seeds](/en/seeds/usage) — rapid upload, offline download, relay, convert, edit, recalculate
+- [Rapid upload matrix](/en/seeds/rapid-upload) — hashes each drive exposes and requires
+- [FAQ](/en/seeds/faq) — notes and common questions
diff --git a/pages/en/seeds/rapid-upload.md b/pages/en/seeds/rapid-upload.md
new file mode 100644
index 000000000..c34bbe56a
--- /dev/null
+++ b/pages/en/seeds/rapid-upload.md
@@ -0,0 +1,75 @@
+---
+categories:
+ - seeds
+top: 950
+---
+
+# Rapid upload matrix
+
+The seed system relies on drive-provided hashes to avoid redundant downloads. Different drives differ in the hashes they "provide in listing" and "require for rapid upload". The two dimensions are merged below into a single two-dimensional matrix: **rows = hashes provided by the source listing, columns = hashes required by the target for rapid upload**; each cell answers "can this source rapid-upload to this target".
+
+## Legend
+
+| Symbol | Meaning |
+| ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| ✅ | Direct rapid upload: the source listing already provides every hash the target needs, no content download |
+| 🔶 | Needs hashing: the source provides part of the required hashes but is missing piece hashes or another algorithm, so the file must be downloaded to compute the rest first |
+| ❌ | Cannot rapid upload: the source lacks the key hash the target requires |
+| ➖ | Not applicable: the target drive does not support rapid upload (normal upload only) |
+
+## Rapid upload matrix
+
+| Source provides \ Target needs | MD5 | MD5 + pieces | SHA1 | MD5 + SHA1 | SHA1 or MD5 | GCID | SHA256 | no rapid upload |
+| ------------------------------ | --- | ------------ | ---- | ---------- | ----------- | ---- | ------ | --------------- |
+| **MD5** | ✅ | 🔶 | ❌ | 🔶 | ✅ | ❌ | ❌ | ➖ |
+| **SHA1** | ❌ | ❌ | ✅ | 🔶 | ✅ | ❌ | ❌ | ➖ |
+| **MD5 + SHA1** | ✅ | 🔶 | ✅ | ✅ | ✅ | ❌ | ❌ | ➖ |
+| **MD5 + SHA1 + SHA256** | ✅ | 🔶 | ✅ | ✅ | ✅ | ❌ | ✅ | ➖ |
+| **GCID** (block SHA1) | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ➖ |
+| **none** | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ➖ |
+
+## Drive hash capability mapping
+
+The table maps each drive to the matrix's rows (listing provides) and columns (rapid upload needs), so any "source → target" pair can be located in the matrix.
+
+| Drive | Hashes provided (source / row) | Rapid upload requires (target / column) |
+| ------------------ | -------------------------------- | --------------------------------------- |
+| 189pc | MD5 | MD5 + piece MD5 (`slice_md5`) |
+| 189 (legacy) | MD5 | MD5 + piece MD5 |
+| 189tv | MD5 | MD5 |
+| Aliyundrive | SHA1 | SHA1 (`pre_hash` + `content_hash`) |
+| Aliyundrive Open | SHA1 | SHA1 (`pre_hash`) |
+| Baidu | none (returned MD5 is untrusted) | MD5 (`content-md5` + `slice-md5`) |
+| PikPak | GCID (block SHA1) | GCID |
+| 115 | SHA1 | SHA1 |
+| 115 Open | SHA1 | SHA1 |
+| Thunder | GCID | GCID |
+| Thunder X | GCID | GCID |
+| Thunder Browser | GCID | GCID |
+| Quark Open | SHA1 | MD5 + SHA1 |
+| Quark UC | none | MD5 + SHA1 |
+| febbox | GCID | GCID |
+| 139 (China Mobile) | none (`digest` not exposed) | SHA256 (rapid upload) |
+| 123 | MD5 (`etag`) | MD5 |
+| 123 Open | SHA1 / MD5 | SHA1 (`sha1_reuse`) or MD5 |
+| Google Drive | MD5 + SHA1 + SHA256 | no rapid upload (normal upload) |
+| OneDrive | none | no rapid upload (normal upload) |
+
+## How to read the matrix
+
+- **Aliyundrive → 115**: source provides SHA1, target needs SHA1 → matrix `SHA1 × SHA1` = ✅ direct rapid upload.
+- **123 → 189pc**: source provides MD5, target needs MD5 + pieces → matrix `MD5 × MD5+pieces` = 🔶 must download to compute piece MD5.
+- **PikPak → Aliyundrive**: source provides GCID, target needs SHA1 → matrix `GCID × SHA1` = ❌ cannot rapid upload.
+- **Any source → Google Drive / OneDrive**: target has no rapid upload → last column = ➖, normal upload only.
+
+## Relation to the hash matrix
+
+The hash matrix is preflighted against these capabilities: if the source drive already provides every hash the target needs, no download is required; otherwise files are streamed and hashed on the fly. Selecting `.torrent` forces SHA-1 whole + pieces; selecting `.cas` forces MD5 whole + pieces (fixed 10 MiB) for 189pc rapid upload.
+
+## Notes
+
+- **GCID** is a block SHA1 (40 hex chars), used by PikPak / Thunder family / febbox.
+- 189 and Baidu chunked uploads additionally need per-piece MD5 (`slice_md5`), so their column is `MD5 + pieces`; a source providing only MD5 is marked 🔶 (must download to compute pieces).
+- The Aliyundrive family uses `pre_hash` (SHA1 of the first 1024 bytes) to trigger rapid upload, then computes the full SHA1 on hit.
+- 139 rapid upload uses SHA256; 123 Open supports either SHA1 reuse (`sha1_reuse`) or MD5.
+- **Note**: the matrix reflects each drive's native rapid-upload capability. Currently only 189pc CAS rapid upload is wired into the seed "rapid save" flow; other drives' rapid upload takes effect in the normal upload path (`Put` / `PutRapid`).
diff --git a/pages/en/seeds/usage.md b/pages/en/seeds/usage.md
new file mode 100644
index 000000000..773aa5bdd
--- /dev/null
+++ b/pages/en/seeds/usage.md
@@ -0,0 +1,116 @@
+---
+categories:
+ - seeds
+top: 960
+---
+
+# Using seeds
+
+## Seed API overview
+
+Seed capability is exposed under `POST /fs/seed/*` (the legacy `/fs/torrent/*` routes remain compatible):
+
+| API | Purpose |
+| ------------------ | ------------------------------------------------------------------------------------------------------------------ |
+| `parse` | Parse a seed (auto-detects `.oss` / `.torrent` / `.cas`) |
+| `upload_parse` | Upload a seed file and parse it |
+| `generate` | Generate a seed (see [Generating seeds](/en/seeds/generate)) |
+| `convert` | Convert between formats |
+| `diagnose` | Diagnose missing information for conversion |
+| `capabilities` | Preflight: per-file hashes available / download needed / streamable; or probe a destination storage's save methods |
+| `rapid_upload` | Rapid-upload save |
+| `offline_download` | Offline download / relayed transfer |
+| `update` | Edit / recalculate / remove files |
+| `update_channels` | Update channels (write `channels` / `missing_channels` on success/failure) |
+| `quick_save` | Quick save (alias of `rapid_upload` / `offline_download`) |
+
+All seed payloads are base64-encoded in the request body. Common `SeedOperationRequest` fields:
+
+| Field | Description |
+| ---------------------- | ------------------------------------------------------------------------------- |
+| `seed_data` | base64 seed content (aliases `content` / `data` / `torrent_data` also accepted) |
+| `file_name` | original seed file name |
+| `path` / `target_path` | destination directory |
+| `selected_files` | indices into the seed's `files[]` |
+| `update_channel` | whether to update channels on success |
+| `remove_files` | file paths to remove |
+| `recalc_files` | files to recalculate (`path` + `source_path`) |
+| `hash_matrix` | hash matrix for recalculation |
+
+## Rapid upload
+
+Select files and choose a destination drive/path. The UI shows the destination drive's supported rapid-upload methods (e.g. 189pc CAS) and whether rapid upload is currently possible. Native rapid upload is preferred; if the drive cannot reuse hashes, the operation reports `unavailable` instead of silently degrading.
+
+Per-file save decision (`method` returned by `capabilities`):
+
+| Method | Meaning | Badge |
+| ------------------- | ------------------------------------------------------------------------------------------ | ------ |
+| `189pc_cas` | destination is 189pc and the seed has the MD5 + piece MD5 CAS needs, so rapid upload works | green |
+| `put_url` | the seed has a usable direct link, so PutURL pulls server-side | green |
+| `offline_download` | falls back to an offline download tool | blue |
+| `download_required` | hashes cannot be reused; the server streams and re-uploads | yellow |
+| `unavailable` | the destination drive supports no usable method | red |
+
+Only `189pc_cas` and `put_url` are true "rapid upload" (no content download).
+
+## Offline download
+
+When the seed contains usable direct/share sources, files can be downloaded into the destination drive (PutURL / offline tool / server streaming). Torrent seeds can be handed to an offline tool via magnet.
+
+- `.torrent`: converted to magnet as a whole (`announce` → `tr`, `name` → `dn`, `length` → `xl`) and handed to the offline tool.
+- Other seeds: downloaded per file from `sources` (`/d/` direct or `/sd/` share links).
+
+## Relayed transfer
+
+Save synchronously into an intermediate drive (native rapid upload or PutURL), then copy server-side to the final drive. Asynchronous offline downloads cannot be relayed.
+
+Set `transit_path` (the intermediate path) with `options: { mode: "transfer" }`; the system saves synchronously to the intermediate storage, then copies to the final `path`.
+
+## Update channel on success
+
+With "update channel on success" enabled, a successful save appends the current drive to the seed's `channels`, while a failure is recorded in `missing_channels`.
+
+- `channels`: an array of `{ driver, mount_path }` marking drives where the seed has landed successfully.
+- `missing_channels`: an array of drive names that failed rapid upload, avoiding repeat attempts.
+
+## Convert
+
+Convert between formats; missing information (e.g. no SHA-1 pieces) is reported before conversion.
+
+- The target format is given by `format` / `to_format` / `target_format`.
+- `diagnose` lists the hashes required but missing for each target format, driving the ✓/✗ UI and its reasons.
+- Feasibility mirrors generation: `.torrent` needs SHA-1 whole + pieces; `.cas` needs MD5 whole + pieces (or a whole-file MD5 for files ≤ 10 MiB).
+
+## Edit and recalculate
+
+- **Edit**: update overall comment, trackers, channels, per-file comments, and share sources; share validity is checked during editing (invalid shares report their IDs).
+- **Recalculate**: pick a source directory and recompute hashes (with a selectable hash matrix). The source path is the source directory plus the seed's relative path; recalculation only reads existing server-side files.
+- **Remove files**: drop specified files from the seed via `remove_files`.
+
+## File-operation sidecar follow
+
+When copying / moving / renaming / deleting a main file, enable "Follow transfer seed sidecars" to move the companion `.oss` / `.torrent` / `.cas` / `.cas.torrent` along, keeping the main file and sidecars consistent.
+
+| Operation | API | `follow_seed` behavior |
+| --------- | ----------------- | ---------------------------------------------- |
+| Copy | `POST /fs/copy` | synchronously copy sidecars to the destination |
+| Move | `POST /fs/move` | synchronously move sidecars to the destination |
+| Rename | `POST /fs/rename` | rename sidecars to `newName + original suffix` |
+| Remove | `POST /fs/remove` | synchronously delete sidecars |
+
+- Sidecar path rule: main path + `.oss` / `.torrent` / `.cas` / `.cas.torrent`.
+- Files only (directories are skipped); missing sidecars are silently ignored.
+
+## Settings
+
+| Setting | Description | Default |
+| ---------------------------- | ------------------------------------------- | -------------------------- |
+| `seed_site_url` | Public site URL for share/direct sources | empty |
+| `seed_default_matrix` | Default right-click hash matrix | md5/sha1/sha256 whole=true |
+| `seed_default_trackers` | Tracker list offered at generation | empty |
+| `seed_default_format` | Default seed format | oss |
+| `seed_format_policies` | Per-format auto-generation switches | all off |
+| `seed_auto_generate_policy` | Global auto-generation policy | off |
+| `seed_single_direct_preview` | Direct preview for single-file seeds | false |
+| `seed_cas_direct_access` | Rapid-upload and preview CAS on open | false |
+| per-storage `seed_policy` | Storage-level `inherit`/`on`/`off` override | inherit |
diff --git a/snippets/reverse-tip.md b/pages/en/snippets/reverse-tip.md
similarity index 54%
rename from snippets/reverse-tip.md
rename to pages/en/snippets/reverse-tip.md
index 3ca27c7a1..59b8d25a6 100644
--- a/snippets/reverse-tip.md
+++ b/pages/en/snippets/reverse-tip.md
@@ -1,12 +1,5 @@
-::: en
::: danger Please read the following notes carefully
This interface is a reverse-engineered interface based on legacy products. The project team will not actively maintain it. Please do not submit any issues regarding fixes or further reverse engineering requests for this driver.
:::
-::: zh-CN
-::: danger 请仔细阅读注意事项
-
-本接口是基于历史产物的逆向接口，项目组不会主动进行维护，请勿针对此驱动提出有关于任何修复或进行进一步逆向行为需求的issue。
-
-:::
diff --git a/snippets/tos-tip.md b/pages/en/snippets/tos-tip.md
similarity index 58%
rename from snippets/tos-tip.md
rename to pages/en/snippets/tos-tip.md
index 9575112a7..2d534cb2d 100644
--- a/snippets/tos-tip.md
+++ b/pages/en/snippets/tos-tip.md
@@ -1,12 +1,5 @@
-::: en
::: danger
Please use your account in a standardized manner. Do not use it for distribution services including but not limited to **`multi-person sharing`**, **`image hosting, software hosting`** and **`video external links to video websites for playback`**, as well as some other irregular uses not mentioned above. You will be responsible for the consequences of your account being blocked.
:::
-::: zh-CN
-::: danger
-
-请规范使用帐号，包含但不限于 **`多人共享使用`**、**`图床、软件床`** 和 **`视频外链到视频网站播放`** 等分发服务以及一些没有提到的不规范使用的方式导致帐号被封禁的，后果自负！
-
-:::
diff --git a/pages/en/terms.md b/pages/en/terms.md
new file mode 100644
index 000000000..d06434b7c
--- /dev/null
+++ b/pages/en/terms.md
@@ -0,0 +1,38 @@
+---
+sidebar: false
+aside: false
+outline: false
+pageClass: statement-page
+comment: false
+contributors: false
+---
+
+# Terms of Service
+
+## AGPL License Notice
+
+This software is licensed under the [GNU Affero General Public License v3.0 (AGPL-3.0)](https://www.gnu.org/licenses/agpl-3.0.html). You are free to use, modify, and distribute the software, but must comply with AGPL-3.0 terms, including disclosing source code when distributing or offering as a service. See the link above for details.
+
+## Terms of Use
+
+- This service is for lawful use only. Users must not engage in any illegal activity through this service.
+- Users assume all risks and responsibilities resulting from the use of this service.
+- We reserve the right to modify, suspend, or terminate the service at any time without prior notice.
+- The service is provided "as is" without any express or implied warranties of availability, accuracy, or fitness for a particular purpose.
+- All downstream projects based on OpenList must strictly comply with the full terms of the AGPL 3.0 license, including proper attribution, maintaining open-source status, and adopting the same license.
+- The OpenListTeam reserves the right to require downstream projects to be distributed under the same license and to pursue any violations of the license terms.
+- If you have any questions, please contact us.
+
+## DISCLAIMER
+
+- THE OPENLIST PROJECT IS FREE AND OPEN-SOURCE SOFTWARE, FORKED FROM THE UPSTREAM ALIST PROJECT AND MAINTAINED BY THE OPENLISTTEAM.
+- THIS SOFTWARE IS PROVIDED "AS IS" WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
+- THIS SOFTWARE IS LICENSED UNDER THE [GNU Affero General Public License v3.0 (AGPL-3.0)](https://www.gnu.org/licenses/agpl-3.0.html). YOU ARE FREE TO USE, MODIFY, AND DISTRIBUTE THE SOFTWARE, BUT MUST COMPLY WITH AGPL-3.0 TERMS, INCLUDING DISCLOSING SOURCE CODE WHEN DISTRIBUTING OR OFFERING AS A SERVICE. SEE THE LINK ABOVE FOR DETAILS.
+- PLEASE COMPLY WITH RELEVANT LAWS AND REGULATIONS WHEN USING THIS SOFTWARE, AND REFRAIN FROM ANY FORM OF ABUSE.
+- THIS SOFTWARE IS IMPLEMENTED BASED ON OFFICIAL SDKS OR APIS, WITHOUT MODIFYING, DAMAGING, OR INTERFERING WITH THEIR BEHAVIOR.
+- IT ONLY PERFORMS HTTP 302 REDIRECTS OR TRAFFIC FORWARDING, WITHOUT INTERCEPTING, STORING, OR TAMPERING WITH ANY USER DATA.
+- THIS PROJECT IS NOT AFFILIATED WITH ANY OFFICIAL PLATFORM OR SERVICE PROVIDER.
+- THE MAINTAINERS ARE NOT RESPONSIBLE FOR ANY DIRECT OR INDIRECT LOSSES RESULTING FROM THE USE OR INABILITY TO USE THIS SOFTWARE.
+- YOU ASSUME ALL RISKS ASSOCIATED WITH USING THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ACCOUNT BANS, DOWNLOAD SPEED LIMITS, ETC.
+- ANY FORKS, BRANCHES, OR DERIVATIVE PROJECTS BASED ON OPENLIST ARE INDEPENDENT PROJECTS WITH THEIR OWN CREATORS, MAINTAINERS, AND FEEDBACK CHANNELS. THE OPENLISTTEAM DOES NOT PROVIDE ANY SUPPORT FOR THEM.
+- ANY ACTIONS, CONTENT, AND CONSEQUENCES ARISING FROM SUCH FORKS, BRANCHES, OR DERIVATIVE PROJECTS ARE THE SOLE RESPONSIBILITY OF THEIR RESPECTIVE MAINTAINERS, AND THE OPENLISTTEAM IS NOT LIABLE FOR ANY SUCH ISSUES.
diff --git a/pages/faq/error.md b/pages/faq/error.md
index 68cb4b679..c0cca19cc 100644
--- a/pages/faq/error.md
+++ b/pages/faq/error.md
@@ -1,181 +1,79 @@
---
-# This is the title of the article
-title:
- en: OpenList Error-Code
- zh-CN: OpenList 错误码
-# This is the icon of the page
-icon: iconfont icon-state
-# This control sidebar order
top: 1
-# A page can have multiple categories
categories:
- faq
-# A page can have multiple tags
---
-::: en
-This article will collect some error codes that may occur during the use of OpenList and provide corresponding solutions (including network issues, changes in cloud storage APIs, and other cases that may require manual intervention).
-:::
-::: zh-CN
+# OpenList 错误码
+
本文将收集在使用 OpenList 过程中出现的一些错误码，并提供相应的解决方案（包括网络问题、网盘 API 更改及其他可能需要人工干预的情况）。
-:::
---
-::: en
-**Q**：Ali cloud disk open appears **TooManyRequests** 、**Too Many Requests**
-
-**A**：[**Click me to view detailed description**](../guide/drivers/aliyundrive_open.md)
-:::
-::: zh-CN
**Q**：阿里云盘open出现 **TooManyRequests** 、**Too Many Requests**
**A**：[**点我查看详细说明**](../guide/drivers/aliyundrive_open.md)
-:::
---
-::: en
-**Q**：Ali cloud disk open appears **ExceedCapacityForbidden**
-
-**A**：[**Click me to view detailed description**](../guide/drivers/aliyundrive_open.md#4-other-instructions)
-:::
-::: zh-CN
**Q**：阿里云盘open出现 **ExceedCapacityForbidden**
**A**：[**点我查看详细说明**](../guide/drivers/aliyundrive_open.md#4-其他说明)
-:::
---
-::: en
-**Q**：Token is expired（**Appears when logging in to the OpenList account**）
-
-**A**：It means that your `OpenList` login is valid for `48` hours by default, you can modify the configuration file `config.json`
-
-- If you are prompted to log in successfully when you log in and then this prompt is displayed again, check whether you have used CDN acceleration to cache the OpenList.
-
-:::
-::: zh-CN
**Q**：Token is expired（**出现在登录OpenList账号时**）
**A**：是指你`OpenList`登录有效期到了默认是`48`小时，可以在修改`config.json`配置文件中
- 如果你登录的时候提示登录成功然后又显示这个提示，检查你是否使用了CDN加速等给OpenList进行了缓存导致的
-:::
-
---
-::: en
-**Q**：Failed init storage but storage is already created: failed init storage: failed to refresh token: The input parameter refresh_token is missing. Please refer to document.
-
-**A**：Generally, the refresh token (token) is wrong when adding `driver`, and it can be solved by replacing it with the correct one.
-:::
-::: zh-CN
**Q**：Failed init storage but storage is already created: failed init storage: failed to refresh token: The input parameter refresh_token is missing. Please refer to document.
**A**：一般是在添加`驱动`的时候刷新令牌(token)不对，更换正确的替换了即可解决。
-:::
---
-::: en
-**Q**：failed get objs: failed to list objs: ForbiddenDriveNotValid:not valid driveld
-
-**A**：Generally, it means that `driver` has been deprecated. For example, Aliyun disk can be replaced with [**Alibaba cloud disk open**](../guide/drivers/aliyundrive_open.md). Others are temporarily unknown.
-:::
-::: zh-CN
**Q**：failed get objs: failed to list objs: ForbiddenDriveNotValid:not valid driveld
**A**：一般指的是`驱动`已经弃用，例如阿里云盘，更换成[**阿里云盘open**](../guide/drivers/aliyundrive_open.md)即可，其他的暂时未知。
-:::
---
-::: en
-**Q**：no such host、TLS handshake timeout、read: connection reset by peer、dns lookup failed、connect: connection refused、Client.Timeout exceeded while awaiting headers、network is unreachable
-
-**A**：These problems are generally caused by network problems, and you can troubleshoot and solve them yourself.
-
-- If you encounter it when you add `Aliyun disk open`：TLS handshake timeout （[Click me to see how to solve](./why.md#prompt-when-adding-aliyun-drive-shared-prompt-post-https-auth-aliyundrive-com-v2-account-token-net-http-tls-handshake-timeout)）
-
-:::
-::: zh-CN
**Q**：no such host、TLS handshake timeout、read: connection reset by peer、dns lookup failed、connect: connection refused、Client.Timeout exceeded while awaiting headers、network is unreachable
**A**：遇到这些问题一般都是网络问题导致的，自行排查然后解决。
- 如果是添加`阿里云盘open`时候遇到：TLS handshake timeout （[点击我查看如何解决](./why.md#添加阿里云盘-分享-时提示-提示post-https-auth-aliyundrive-com-v2-account-token-net-http-tls-handshake-timeout)）
-:::
-
---
-::: en
-**Q**：Failed create storage in database: UNIQUE constraint failed: x_storages.mount_path (**appears when mounting the driver**)
-
-**A**：The path to mount to, it is unique and cannot be repeated
-:::
-::: zh-CN
**Q**：Failed create storage in database: UNIQUE constraint failed: x_storages.mount_path （**出现在挂载驱动时**）
**A**：要挂载到的路径，它是唯一的，不能重复
-:::
---
-::: en
-**Q**：Key: 'Storage.MountPath' Error:Field validation for 'MountPath' failed on the 'required' tag (**appears when mounting the driver**)
-
-**A**：The mount path is a required option, please fill in it
-:::
-::: zh-CN
**Q**：Key: 'Storage.MountPath' Error:Field validation for 'MountPath' failed on the 'required' tag（**出现在挂载驱动时**）
**A**：挂载路径是必填选项，填写一下
-:::
---
-::: en
-**Q**：UNIQUE constraint failed: x_meta.path (appears when adding meta information)
-
-**A**：When adding meta information, there can only be one path, and it cannot be repeated
-:::
-::: zh-CN
**Q**：UNIQUE constraint failed: x_meta.path（**出现在添加元信息时**）
**A**：添加元信息时路径只能有一个，不可以重复
-:::
---
-::: en
-**Q**：Key: 'Meta.Path' Error:Field validation for 'Path' failed on the 'required' tag (appears when adding meta information)
-
-**A**：When adding metadata, the path must be filled in
-:::
-::: zh-CN
**Q**：Key: 'Meta.Path' Error:Field validation for 'Path' failed on the 'required' tag（**出现在添加元信息时**）
**A**：添加元信息时，路径是必须要填写的
-:::
---
-::: en
-**Q**：failed get objs: failed to list objs: Sorry, sharing is not available in the current region（**PikPak/share**）
-
-**Q**：failed get objs: failed to list objs: terabox is not yet available in this are（**Terabox**）
-
-**A**：Domestic access is not supported, if you build it locally, you can check this [**Reference Solution**](https://anwen-anyi.github.io/index/07-wenti.html#_41-alist如何-使用-吃到-代理-proxy)
-
-- For example, Google, Mega, Terabox, etc. that require a proxy to access can be used in this way
-
-:::
-
-::: zh-CN
**Q**：failed get objs: failed to list objs: Sorry, sharing is not available in the current region（**PikPak/分享**）
**Q**：failed get objs: failed to list objs: terabox is not yet available in this are（**Terabox**）
@@ -184,141 +82,68 @@ This article will collect some error codes that may occur during the use of Open
- 例如 Google、Mega、Terabox 等这些需要代理才能访问的都可以通过这样的方法使用
-:::
-
---
-::: en
-**Q**：Search not available（**appears when indexing**）
-
-**A**：The `Search Index` option is not selected, and cannot be built and used. I don’t know which search index to choose? [**Click me to view**](../guide/advanced/search.md#difference-between-different-search-indexes)
-:::
-::: zh-CN
**Q**：Search not available（**出现在构建索引时**）
**A**：`搜索索引`选项没有选择，无法构建使用，不知道选择哪个搜索索引好?[**点我查看**](../guide/advanced/search.md#不同搜索索引之间的差异)
-:::
---
-::: en
-**Q**：only chinese and english, numbers and underscores are supported, and the length is no more than 50 (**Appears when the baidu.photo folder is renamed**)
-
-**A**：When renaming the baidu.photo folder, the maximum length is 50
-:::
-::: zh-CN
**Q**：only chinese and english, numbers and underscores are supported, and the length is no more than 50（**出现在一刻相册文件改名时**）
**A**：一刻相册文件夹改名时最大50长度
-:::
---
-::: en
-**Q**：failed get objs: failed to list objs: NotFound.FileId:The resource file_id cannot be found. file_id:634e704cefa78f92fefd4c779f7422d820082d041（**Add Alibaba cloud disk open**）
-
-**A**：When adding the open storage of Alibaba Cloud disk, `root folder ID` is wrong, which of the last ID above is the wrong ID, just get the correct replacement.
-:::
-::: zh-CN
**Q**：failed get objs: failed to list objs: NotFound.FileId:The resource file_id cannot be found. file_id:634e704cefa78f92fefd4c779f7422d820082d041（**添加阿里云盘open**）
**A**：添加阿里云盘open存储时，`根文件夹ID`错误上述最后哪个ID就是错误的ID去获取正确的替换即可
-:::
---
-::: en
-**Q**：System error: SyntaxError: Invalid regular expression: /?/: Nothing to repeat
-
-**A**：Your Tampermonkey answering plug-in conflicts, just close it [**For details, click to view**](https://github.com/alist-org/alist/discussions/2399)
-:::
-::: zh-CN
**Q**：System error: SyntaxError: Invalid regular expression: /?/: Nothing to repeat
**A**：你的油猴答题插件冲突了，关闭了即可[**详情查看点击查看**](https://github.com/alist-org/alist/discussions/2399)
-:::
---
-::: en
-**Q**：Too many unsuccessful sign-in attempts have been made using an incorrect username or password, Try again later.
-
-**A**：If you enter the wrong password for 6 consecutive logins, it will be locked, and you can reset it by restarting OpenList.
-:::
-::: zh-CN
**Q**：Too many unsuccessful sign-in attempts have been made using an incorrect username or password, Try again later.
**A**：连续登录输入6次密码错误就会锁定，重启OpenList即可重置。
-:::
---
-::: en
-**Q**：Failed get storage: please add a storage first. （**When adding offline download files**）
-
-**A**：When adding an offline download file, you need to enter which cloud disk you want to download the offline download file to and then click on the `folder` instead of adding it on the home page [**Complete Instructions**](../guide/advanced/offline-download.md)
-:::
-::: zh-CN
**Q**：Failed get storage: please add a storage first. （**添加离线下载内容时**）
**A**：添加离线下载文件时，你需要进入你想把离线下载的文件下载到哪个云盘然后就进入哪个`文件夹`，而不是在首页添加 [**完整使用说明**](../guide/advanced/offline-download.md)
-:::
---
-::: en
-**Q**：failed get objs: failed to list objs: Unable to retrieve user's mysite URL（**When adding onedrive_app**）
-
-**A**：The newly created `OneDrive` user account does not take effect in real time, Delay takes effect, wait for a few hours and try again [**Case**](https://github.com/alist-org/docs/discussions/189#discussioncomment-5928892)
-:::
-::: zh-CN
**Q**：failed get objs: failed to list objs: Unable to retrieve user's mysite URL（**添加onedrive_app时**）
**A**：新建的 `OneDrive`用户账号不是实时生效，会延时生效等待几小时后试试看 [**案例**](https://github.com/alist-org/docs/discussions/189#discussioncomment-5928892)
-:::
---
-::: en
-**Q**：failed to start: listen tcp 0.0.0.0:5244: bind: address already in use （**When starting the OpenList program**）
-
-**A**：Port number 5244 is already in use, check whether it is occupied (generally you have started an OpenList with port 5244), or modify the port number started by OpenList, [**How to modify**](../configuration/configuration.md#scheme)
-:::
-::: zh-CN
**Q**：failed to start: listen tcp 0.0.0.0:5244: bind: address already in use （**启动OpenList程序时**）
**A**：5244端口号已经被使用，排查是否被占用(一般来说你已经启动了一个5244端口的OpenList导致的)，或者修改OpenList启动的端口号,[**如何修改**](../configuration/configuration.md#scheme)
-:::
---
-::: en
-**Q**：**[When OpenList upload file](why.md#why-do-i-get-413-http-code-when-i-upload-a-file)**：Request failed with status code 413
-
-**A**：Limit the size of the files configured nginx, modify the nginx's `client_max_body_size`,If you are a pagoda to go to the pagoda page to modify [Example](https://blog.csdn.net/u012514495/article/details/127981183)
-:::
-::: zh-CN
**Q**：**[OpenList上传文件时提示](why.md#为什么我在上传文件时得到-http-413-错误)**：Request failed with status code 413
**A**：Nginx配置的文件大小所限制，修改Nginx的`client_max_body_size`就可以，如果你是宝塔搭建的去宝塔页面修改[示例](https://blog.csdn.net/u012514495/article/details/127981183)
-:::
---
-::: en
-**Q**：**failed get objs: failed to list objs: query fail [61008]**
-
-**A**：It may be because some drivers do not support modifying the file sorting. Try to cancel the file sorting.
-:::
-::: zh-CN
**Q**：**failed get objs: failed to list objs: query fail [61008]**
**A**：可能是因为某些驱动不支持修改文件排序导致的，取消文件排序试试看
-:::
---
-::: zh-CN
**Q**：Docker 运行时查看日志，出现: FATA[2025-08-12 02:48:46] failed to create config file: open /opt/openlist/data/config.json: permission denied 。
**A**：挂载的目录与运行 Docker 的用户权限不一致导致的。解决方法:
@@ -339,28 +164,3 @@ docker run -d --name openlist --user 1000:1000 -v ${yourDataDir}:/opt/openlist/d
sudo chown -R 1001:1001 ${yourDataDir}
docker run -d --name openlist -v ${yourDataDir}:/opt/openlist/data -p 5244:5244 openlistteam/openlist
```
-
-:::
-::: en
-**Q**：When running `docker logs openlist`, the error appears: FATA[2025-08-12 02:48:46] failed to create config file: open /opt/openlist/data/config.json: permission denied 。
-
-**A**：This is caused by the directory mounted not matching the user permissions running the docker. The solution:
-
-1. Use the `--user` parameter to specify the user running the container, assuming the user is `1000:1000`.
-
- First, ensure that the `${yourDataDir}` directory has permissions of `1000:1000`. If not, use `sudo chown -R 1000:1000 ${yourDataDir}` to change the directory permissions.
-
- Then run the Docker with the following command:
-
-```bash
-docker run -d --name openlist --user 1000:1000 -v ${yourDataDir}:/opt/openlist/data -p 5244:5244 openlistteam/openlist
-```
-
-2. Change the owner of the `${yourDataDir}` directory to `1001:1001`, and then run the Docker:
-
-```bash
-sudo chown -R 1001:1001 ${yourDataDir}
-docker run -d --name openlist -v ${yourDataDir}:/opt/openlist/data -p 5244:5244 openlistteam/openlist
-```
-
-:::
diff --git a/pages/faq/howto.md b/pages/faq/howto.md
index 569aae1ee..d64705eb9 100644
--- a/pages/faq/howto.md
+++ b/pages/faq/howto.md
@@ -1,57 +1,17 @@
---
-# This is the title of the article
-title:
- en: How to
- zh-CN: 怎么做
-# This is the icon of the page
-icon: iconfont icon-state
-# This control sidebar order
top: 1
-# A page can have multiple categories
categories:
- faq
-# A page can have multiple tags
---
-## How to add password for a file/folder? { lang="en" }
+# 怎么做
-## 如何为文件/文件夹添加密码？ { lang="zh-CN" }
+## 如何为文件/文件夹添加密码？
-:::en
-Add a [meta](../guide/advanced/meta.md) record.
-:::
-:::zh-CN
添加[元信息](../guide/advanced/meta.md)
-:::
-
-## How to reverse proxy with sub directory? { lang="en" }
-## 如何对子目录进行反向代理？ { lang="zh-CN" }
+## 如何对子目录进行反向代理？
-:::en
-An example of using nginx to reverse proxy to https://example.com/openlist:
-
-- Normal installation
-- Set [site_url](../configuration/configuration.md#site-url) to `https://example.com/openlist` or just `/openlist` then restart openlist
-- Add a reverse proxy record in nginx
-
-```nginx
-location /openlist/ {
- proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
- proxy_set_header X-Forwarded-Proto $scheme;
- proxy_set_header Host $http_host;
- proxy_set_header X-Real-IP $remote_addr;
- proxy_set_header Range $http_range;
- proxy_set_header If-Range $http_if_range;
- proxy_redirect off;
- proxy_pass http://127.0.0.1:5244/openlist/;
- # the max size of file to upload
- client_max_body_size 20000m;
-}
-```
-
-:::
-:::zh-CN
使用 nginx 反向代理到 https://example.com/openlist 的示例：
- 正常安装
@@ -73,24 +33,8 @@ location /openlist/ {
}
```
-:::
-
-## How to get password if i forget it? { lang="en" }
-
-## 忘记密码怎么办？ { lang="zh-CN" }
-
-:::en
-If the password is forgotten, it can only be re-**`randomly generated`** or **`manually set`**
+## 忘记密码怎么办？
-```bash
-# Randomly generate a password
-./openlist admin random
-# Manually set a password, `NEW_PASSWORD` refers to the password you need to set
-./openlist admin set NEW_PASSWORD
-```
-
-:::
-:::zh-CN
如果忘记了密码只能通过重新 **`随机生成`** 或者 **`手动设置`**
```bash
@@ -100,122 +44,42 @@ If the password is forgotten, it can only be re-**`randomly generated`** or **`m
./openlist admin set NEW_PASSWORD
```
-:::
-
-## How to modify the listening port { lang="en" }
+## 如何修改监听端口
-## 如何修改监听端口 { lang="zh-CN" }
-
-:::en
-Refer to [config](../configuration/configuration.md#scheme)
-:::
-:::zh-CN
参考[config](../configuration/configuration.md#scheme)
-:::
-
-## How to upgrade { lang="en" }
-
-## 如何更新 { lang="zh-CN" }
-:::en
-Except for the incompatible version marked in the changelog, you can directly replace the binary file to upgrade.
+## 如何更新
-For Docker user, just remove the old container and pull the new image then run it.
-:::
-:::zh-CN
除了 Changelog 中标注的不兼容版本，通常可以直接替换二进制文件进行更新。
对于 Docker 用户，只需删除旧的容器并拉取新的 Docker 镜像，然后运行它即可。
-:::
-
-## How to allow guest to upload files { lang="en" }
-## 如何允许访客上传文件 { lang="zh-CN" }
+## 如何允许访客上传文件
-:::en
-Add a [meta](../guide/advanced/meta.md) record, and open `write` field.
-:::
-:::zh-CN
添加[元信息](../guide/advanced/meta.md)，并启用 `写入`。
-:::
-## How to remove "Powered by OpenList" at the bottom? { lang="en" }
+## 如何去掉底部的"由 OpenList 驱动"？
-## 如何去掉底部的"由 OpenList 驱动"？ { lang="zh-CN" }
-
-:::en
-According to our open source license:
-Permissions of this strongest copyleft license are conditioned on making available complete source code of licensed works and modifications, which include larger works using a licensed work, under the same license. **Copyright and license notices must be preserved.** Contributors provide an express grant of patent rights. When a modified version is used to provide a service over a network, the complete source code of the modified version must be made available.
-:::
-:::zh-CN
根据我们的开源许可:
此最强copyleft许可的权限以在同一许可下提供许可作品和修改的完整源代码为条件，其中包括使用许可作品的较大作品。**版权和许可声明必须保留** 贡献者明确授予专利权。当使用修改后的版本通过网络提供服务时，必须提供修改后版本的完整源代码。
-:::
-## When adding a 189 Cloud storage: the device ID does not exist, and a secondary device verification is required { lang="en" }
+## 添加 天翼云盘 云存储时：设备 ID 不存在，需要二次设备验证
-## 添加 天翼云盘 云存储时：设备 ID 不存在，需要二次设备验证 { lang="zh-CN" }
-
-:::en
-Open the Tianyi Account website at , log in, and then disable the Device Lock..
-:::
-:::zh-CN
打开天翼账号网站 ，登陆后关掉设备锁即可。
-:::
-## When adding 189 Cloud PC storage: prompt need img validate code: verification code { lang="en" }
-
-## 添加 天翼云盘客户端 存储时：提示 need img validate code: 验证码 { lang="zh-CN" }
-
-:::en
-
-- Click Edit, write the verification code you just saw into the configuration and click Save
-- Click Edit and turn on the Do not use OCR button
-- Or build it yourself [**Ocr interface**](../configuration/global.md#ocr-api)
-- **189 Cloud** Driver has been replaced with sliding verification code because web login has been replaced.**No longer supports OCR and manual input**, if the verification code needs to be used, please use the addition of `Cookie to log in` or use the `189 Cloud PC` Driver. Note: The 189 Cloud Driver is different from the 189 Cloud PC Driver.
-
-:::
-:::zh-CN
+## 添加 天翼云盘客户端 存储时：提示 need img validate code: 验证码
- 点击编辑，将刚才看到的验证码输入配置中，并点击保存。
- 点击编辑并开启“不使用 OCR”按钮。
- 或者自行搭建 [**OCR 接口**](../configuration/global.md#ocr-接口)。
- **天翼云盘** 驱动已被滑动验证码取代，因为网页登录方式已更改。**不再支持 OCR 和手动输入**，如果需要使用验证码，请使用 `Cookie 登录` 或者使用 `天翼云盘客户端` 驱动。注意：天翼云盘 驱动与 天翼云盘客户端 驱动不同。
-:::
-
-## TLS handshake timeout? / read: connection reset by peer? / dns lookup failed? / connect: connection refused / Client.Timeout exceeded while awaiting headers? / no such host? { lang="en" }
-
-## TLS handshake timeout? / read: connection reset by peer? / dns lookup failed? / connect: connection refused / Client.Timeout exceeded while awaiting headers? / no such host? { lang="zh-CN" }
+## TLS handshake timeout? / read: connection reset by peer? / dns lookup failed? / connect: connection refused / Client.Timeout exceeded while awaiting headers? / no such host?
-:::en
-For network problems such as these, please troubleshoot and solve them yourself.Don't create any issues for this.
-:::
-:::zh-CN
诸如此类的网络问题，请自行排查解决。不要为此提出任何的issue
-:::
-## How to add epub reading { lang="en" }
-
-## 怎么添加epub阅读器 { lang="zh-CN" }
-
-:::en
-Background --> Settings --> Preview --> Iframe preview, written behind the PDF
-
-```html{2-5}
- /*The comma below is also oh, don’t copy this comment, start copying from the second line*/
-,
- "epub": {
- "EPUB.js":"/static/epub.js/viewer.html?url=$e_url"
- }
-```
+## 怎么添加epub阅读器
-Version 3.7.x and higher already support ".epub" reading
-But you need to add it manually (because the database has already been created, it is not good to overwrite it for you, and you will make mistakes)
-If it is the first installation and startup (version 3.7.x and higher), no need to add it manually
-If the secondary directory reverse generation is set, please add the corresponding prefix in [site_url](../configuration/configuration.md#site-url), and then restart OpenList to take effect
-:::
-:::zh-CN
后台 ——>设置——>预览——>Iframe 预览，写在PDF后面
```html{2-5}
@@ -230,49 +94,20 @@ If the secondary directory reverse generation is set, please add the correspondi
但是需要自己手动添加(因为已经创建过数据库了 不好给你覆盖会出错)
如果是第一次安装启动（3.7.x版本及更高的版本）不用手动添加
如果设置了二级目录反代，请在[site_url](../configuration/configuration.md#site-url)中自行添加相应前缀，然后重启OpenList才会生效
-:::
-### How to quickly locate bugs { lang="en" }
-
-### 如何快速定位Bug { lang="zh-CN" }
-
-:::en
-If you find a bug, but the `log.log` log is not detailed, you can try to add the `--debug` parameter to start
-
-It is recommended to clear the log file `/log/log.log` in the **OpenList directory before starting with the `--debug` parameter**, so that developers can quickly locate problems later
-
-:::
-:::zh-CN
+### 如何快速定位Bug
如果发现Bug，但是`log.log`的日志不详细，可以尝试在 启动时候添加 `--debug` 参数启动
建议在使用`--debug` 参数启动之前将 **OpenList目录下的日志文件`/log/log.log` 清空**，这样方便开发者们后续快速定位问题
-:::
-:::en
-::: danger
-When using the `--debug` parameter to start, there will be some sensitive data such as **`account password, refresh token`**, etc., so if you need to desensitize before sending it to others
-:::
-:::zh-CN
::: danger
使用`--debug`参数启动时，会有一些敏感数据 例如 **`账号密码，刷新令牌`** 等，所以如果在你发给别人之前需要先处理一下脱敏
:::
-:::en
-
-- **Windows**：`openlist.exe server --debug`
-- **Linux**：`./openlist server --debug`
-- **Mac**: `./openlist server --debug`
-- **Docker**：`docker exec -it openlist ./openlist server --debug` (to be modified, because this command runs OpenList in an already started container, so it will not start a second OpenList)
-
-How to stop the relevant logs after startup? `Ctrl+C` can stop the program (or simply close the program directly)
-:::
-:::zh-CN
-
- **Windows**：`openlist.exe server --debug`
- **Linux**：`./openlist server --debug`
- **Mac**：`./openlist server --debug`
- **Docker**：`docker exec -it openlist ./openlist server --debug` (待修改，因为该命令是在已经启动的容器内运行OpenList，所以不会启动第二个OpenList)
启动后拿到相关日志，如何停止? `Ctrl+C` 可以使程序停止运行（或者简单粗暴直接关闭程序）
-:::
diff --git a/pages/faq/index.md b/pages/faq/index.md
index 087b8bac8..2e7933f58 100644
--- a/pages/faq/index.md
+++ b/pages/faq/index.md
@@ -1,5 +1,3 @@
----
-title: FAQ
----
+# FAQ
`
- 2. `-`
- 3. `:`
- 4. `-::`
-
- All port numbers must be between 1024 and 65535 (inclusive), and the starting port number of a range must be less than the ending port number.
-
- For cases where this field is left blank, the server will choose any port between 1024 and 65535 for passive transfer and will not perform any mapping.
- - Each "mapping group type 1" specifies a single port to be used for passive transfer, and no mapping will be performed for that port.
- - Each "mapping group type 2" specifies a range of ports, and all ports in that range will be used for passive transfer without any mapping.
- - Each "mapping group type 3" specifies a listening port to be used for passive transfer, and when the server selects this port, it will return the "response port number" to the client.
- - "Mapping group type 4" requires that the two ranges before and after the colon `:` have equal lengths. Each "mapping group type 4" forms a one-to-one pairing of port numbers, where each pair is treated as a "mapping group type 3."
-
- The following are legal formats:
- - `1024`
- - `4001-5000,5001-6000:50001-510004000:65535`
-
- The following are illegal formats:
- - `1023` (less than 1024)
- - `65536` (greater than 65535)
- - `4000, 5000` (space after the comma)
- - `2000 - 3000 : 4000 - 5000` (spaces are illegal)
- - `2000-2001:3000-3002` (unequal length of ranges)
-
- If the field is invalid, the server will choose any port between 1024 and 65535 for passive transfer without performing any mapping.
-
- The design of port mapping is intended to address the complexity of external port mapping. For example, if the server is running inside a Docker container and uses port 2000 for passive transfer, but Docker maps port 2000 inside the container to port 12000 on the host machine, you can achieve this mapping using the configuration `12000:2000`.
-
-```mermaid
-sequenceDiagram
- participant Client
- participant Port Mapping
- participant Server
- Client->>Server: Send EPSV command
- Server-->>Client: Return 12000
- Client->>Port Mapping: Connect to port 12000
- Port Mapping->>Server: Forward to port 2000
-```
-
-If there are multiple layers of port mapping between the server and the client, only the port number closest to the client needs to be specified before the `:` symbol, and only the port number closest to the server needs to be specified after the `:` symbol. For example, in the following scenario, you can fill in `2000:5000`:
-
-```mermaid
-sequenceDiagram
- participant Client
- participant NAT Traversal Service
- participant Soft Router Port Forwarding
- participant Docker Container Port Mapping
- participant OpenList Process
- Client->>NAT Traversal Service: 2000
- NAT Traversal Service->>Soft Router Port Forwarding: 3000
- Soft Router Port Forwarding->>Docker Container Port Mapping: 4000
- Docker Container Port Mapping->>OpenList Process: 5000
-```
-
-:::
-
-::: zh-CN
-
- FTP 被动传输端口映射
该字段由一系列以英文逗号`,`或换行符隔开的“映射组”构成，“映射组”的合法形式有以下四种：
@@ -284,46 +126,6 @@ sequenceDiagram
Docker 容器端口映射->>OpenList 进程: 5000
```
-:::
-
-::: en
-
-- FTP Proxy User-Agent Request Header
-
- Some storage drivers require a User-Agent request header when accessing the FTP server. You can simply use any fake value for this header.
-
-- Force FTP Connection to Use Explicit TLS
-
- Forces the use of the FTPS protocol, which only encrypts the data stream and not the control stream.
- If the "Enable FTP Implicit TLS" option is enabled, this option will be ignored.
-
- If no valid TLS private key and certificate are provided, and this option is not enabled, the server will only accept the FTP protocol.
-
- If valid TLS private key and certificate are provided, but this option is not enabled, the server will accept both the FTP and FTPS protocols.
-
- If no valid TLS private key and certificate are provided, but this option is enabled, the FTP server will fail to start.
-
-- Enable FTP Implicit TLS
-
- Uses the FTPS protocol, which encrypts both the data stream and the control stream. This makes it incompatible with FTP and FTPS (explicit) protocols.
-
- When this option is enabled, the "Force FTP Connection to Use Explicit TLS" option will be ignored.
- If no valid TLS private key and certificate are provided but this option is enabled, the FTP server will fail to start.
-
-- FTP TLS Private Key Path
-
- The path to the TLS private key file. Leaving it empty or providing an invalid path means TLS will not be enabled.
-
- Enabling TLS may require the client to access the server using a domain name, though the "FTP Server Public Address" can still be an IP address.
-
-- FTP TLS Certificate Path
-
- The path to the TLS certificate file. Leaving it empty or providing an invalid path means TLS will not be enabled.
-
-:::
-
-::: zh-CN
-
- FTP 代理 User-Agent 请求头
某些存储驱动在访问时需要用到 User-Agent 请求头，随便写一个假的就行。
@@ -358,26 +160,9 @@ sequenceDiagram
TLS 证书文件路径，留空或无效表示不启用 TLS。
-:::
-
-## SFTP Configurations { lang="en" }
-
-## SFTP 配置文件\* { lang="zh-CN" }
-
-::: en
-
-| Field | Meaning | Example Value |
-| ------ | ------------------------------ | --------------------------------------------------------- |
-| enable | Whether enabled | `true` / `false` |
-| listen | (Allowed access IP mask)\:port | `":5222"` (default) / `"0.0.0.0:22"` / `"127.0.0.1:2222"` |
-
-:::
-
-::: zh-CN
+## SFTP 配置文件\*
| 字段 | 含义 | 示例值 |
| ------ | ----------------------- | ------------------------------------------------------- |
| enable | 是否启用 | `true` / `false` |
| listen | (允许访问的IP掩码):端口 | `":5222"`（默认） / `"0.0.0.0:22"` / `"127.0.0.1:2222"` |
-
-:::
diff --git a/pages/guide/advanced/ipa.md b/pages/guide/advanced/ipa.md
index cfc30b3ec..bb8a44b6f 100644
--- a/pages/guide/advanced/ipa.md
+++ b/pages/guide/advanced/ipa.md
@@ -1,28 +1,14 @@
---
-title:
- en: IPA install
- zh-CN: IPA 安装
categories:
- guide
- advanced
top: 70
---
-## 1. IPA native installation { lang="en" }
+# IPA 安装
-## 1. IPA原生安装 { lang="zh-CN" }
+## 1. IPA原生安装
-::: en
-You can directly upload the ipa file.
-But for **ios>=16**, you need to name the ipa file: `original file name@bundle-identifier.ipa`, that is, you need to add `@bundle-identifier` on the original basis, in which `bundle-identifier` is the `CFBundleIdentifier` of Info.plist in the IPA package. Such as:
-
-- aszs@rn.notes.best.ipa
- Recommended to use [ipa-renamer](https://github.com/Xhofe/ipa-renamer) to rename your ipa files automatically and quickly.
-- If you are a mobile phone user, you can also rename the IPA file, but you must know the format mentioned above, but there is no mobile phone renaming software, please solve it yourself...
-
-:::
-
-::: zh-CN
直接上传 ipa 文件即可。
但是对于 **iOS 16 以上的** 设备，你需要将 ipa 文件命名为：`原文件名@bundle-identifier.ipa`，即需要在原来的基础上加入`@bundle-identifier`，其中的 `bundle-identifier` 即 IPA 包中 `Info.plist` 的 `CFBundleIdentifier`。如：
@@ -30,31 +16,7 @@ But for **ios>=16**, you need to name the ipa file: `original file name@bundle-i
推荐你使用 [ipa-renamer](https://github.com/Xhofe/ipa-renamer) 自动快速地重命名你的 IPA 文件。
- 如果你是手机用户也可以给IPA文件改名，但是你要会上述提到的格式才行，但是不提供手机改名软件请你自己解决...
-:::
-
-### Tips { lang="en" }
-
-### Tips { lang="zh-CN" }
-
-::: en
-
-- **.ipa installation requires https and a valid certificate** , not just a package can be installed without a signature
- - How to change the name of the computer version
-
- `
-3. Is there any benefit to this installation?
- - See the flow chart below for explanation
-
-```mermaid
----
-title: Is there any benefit to this installation?
----
-flowchart TB
- A-->B
- subgraph A[original process]
- C[First download the application from OpenList]-->D[find the downloaded software]
- D-->E[click on the software and select share in the upper right corner]
- E-->F[find the troll icon]
- F-->G[jump into the troll software to install]
- G-->H[install and delete the software]
- end
- subgraph B[troll process]
- I[Click the OpenList troll install button and click the pop-up window prompt]-->J[enter the troll app and wait for download]
- J-->K[after downloading, click the install button]
- end
-```
-
-:::
-::: zh-CN
+### 其他说明
1. 如果你点击 **TrollStore(巨魔)** 按钮后打开的是 Apple的放大镜是因为如下原因
- 你的 `TrollStore` 版本号小于1.3+版本，建议直接更新到最新版
@@ -223,5 +100,3 @@ flowchart TB
G==>J
H===|使用巨魔不用手动删除|K
```
-
-:::
diff --git a/pages/guide/advanced/mcp.md b/pages/guide/advanced/mcp.md
index 7e3850c31..453ac66b7 100644
--- a/pages/guide/advanced/mcp.md
+++ b/pages/guide/advanced/mcp.md
@@ -1,25 +1,12 @@
---
-title:
- en: MCP
- zh-CN: MCP
categories:
- guide
- advanced
top: 20
---
-::: en
-[MCP (Model Context Protocol)](https://modelcontextprotocol.io) is an open protocol that standardizes how applications provide context and tools to Large Language Models (LLMs). OpenList implements MCP as a **Streamable HTTP** transport endpoint, enabling AI agents and MCP clients to interact with file storage.
+# MCP
-With the OpenList MCP endpoint, you can:
-
-- List files and directories
-- Get file or directory details
-- Obtain download links
-
-:::
-
-::: zh-CN
[MCP (Model Context Protocol)](https://modelcontextprotocol.io) 是一种开放协议，它标准化了应用程序向大型语言模型（LLM）提供上下文和工具的方式。OpenList 将 MCP 作为 **Streamable HTTP** 传输端点实现，使 AI 智能体和 MCP 客户端能够与文件存储进行交互。
通过 OpenList MCP 端点，您可以：
@@ -28,29 +15,7 @@ With the OpenList MCP endpoint, you can:
- 获取文件或目录详情
- 获取下载链接
-:::
-
-## How to Enable { lang="en" }
-
-## 如何启用 { lang="zh-CN" }
-
-::: en
-
-1. Open the [Configuration File](../../configuration/configuration.md#mcp)
-2. Set `mcp.enable` to `true`:
-
-```json{2}
- "mcp": {
- "enable": true
- }
-```
-
-3. Restart OpenList for the change to take effect
-4. The MCP endpoint is now available at `http[s]://your-domain:port/mcp`
-
-:::
-
-::: zh-CN
+## 如何启用
1. 打开 [配置文件](../../configuration/configuration.md#mcp)
2. 将 `mcp.enable` 设置为 `true`：
@@ -64,32 +29,8 @@ With the OpenList MCP endpoint, you can:
3. 重启 OpenList 使配置生效
4. MCP 端点现在可以通过 `http[s]://your-domain:port/mcp` 访问
-:::
-
-## MCP Client Configuration { lang="en" }
-
-## MCP 客户端配置 { lang="zh-CN" }
-
-::: en
-To connect an MCP client (such as an AI coding agent that supports MCP) to OpenList, use the following configuration:
-
-**Transport type**: Streamable HTTP
-
-**URL**: `http[s]://your-domain:port/mcp`
-
-**Authentication**: Token Authentication. The token is your OpenList login token — include it directly in the `Authorization` header of each request (e.g. `Authorization: `). Do **NOT** add a `Bearer` prefix. Obtain the token from your OpenList account settings page or via the API.
-
-::: warning
-OpenList's authentication middleware reads the `Authorization` header value as-is. Adding a `Bearer ` prefix will result in authentication failure. Use `Authorization: ` only.
-:::
-
-::: en
-**Protocol version**: `2025-11-25` (also compatible with `2025-06-18`)
+## MCP 客户端配置
-**Session handling**: A session is created on `initialize` and identified via the `MCP-Session-Id` response header. You must include this header in subsequent requests.
-:::
-
-::: zh-CN
要将 MCP 客户端（例如支持 MCP 的 AI 编码助手）连接到 OpenList，请使用以下配置：
**传输类型**：Streamable HTTP
@@ -102,36 +43,14 @@ OpenList's authentication middleware reads the `Authorization` header value as-i
OpenList 的认证中间件直接对比 `Authorization` 头的原始值。如果添加 `Bearer ` 前缀会导致认证失败，请仅使用 `Authorization: `。
:::
-::: zh-CN
-
**协议版本**：`2025-11-25`（同时兼容 `2025-06-18`）
**会话管理**：在 `initialize` 时创建会话，并通过 `MCP-Session-Id` 响应头标识。后续请求必须包含此标头。
-:::
-## Available Tools { lang="en" }
-
-## 可用工具 { lang="zh-CN" }
+## 可用工具
### `openlist.fs.list`
-::: en
-List files and directories under a mount path that the current user can access.
-
-**Parameters**:
-
-| Parameter | Type | Required | Description |
-| ---------- | --------- | -------- | ---------------------------------------------- |
-| `path` | `string` | Yes | Mount path to list, e.g. `"/"` or `"/movies"` |
-| `refresh` | `boolean` | No | Refresh the directory listing before returning |
-| `password` | `string` | No | Optional password for protected paths |
-| `page` | `integer` | No | 1-based page number (default: 1) |
-| `per_page` | `integer` | No | Page size (default: all items) |
-
-**Response**: Returns file list with name, size, type, modification time, thumbnail, hash info, and storage details.
-:::
-
-::: zh-CN
列出当前用户可访问的挂载路径下的文件和目录。
**参数**：
@@ -145,24 +64,9 @@ List files and directories under a mount path that the current user can access.
| `per_page` | `integer` | 否 | 每页大小（默认：全部） |
**响应**：返回文件列表，包含名称、大小、类型、修改时间、缩略图、哈希信息和存储详情。
-:::
### `openlist.fs.get`
-::: en
-Get file or directory details for a mount path that the current user can access.
-
-**Parameters**:
-
-| Parameter | Type | Required | Description |
-| ---------- | -------- | -------- | ------------------------------------------------ |
-| `path` | `string` | Yes | Mount path to inspect, e.g. `"/movies/demo.mp4"` |
-| `password` | `string` | No | Optional password for protected paths |
-
-**Response**: Returns file details including name, size, type, modification time, raw URL, readme, header, provider, and related files at the same level.
-:::
-
-::: zh-CN
获取当前用户可访问的挂载路径下的文件或目录详情。
**参数**：
@@ -173,25 +77,9 @@ Get file or directory details for a mount path that the current user can access.
| `password` | `string` | 否 | 受保护路径的密码 |
**响应**：返回文件详情，包括名称、大小、类型、修改时间、原始 URL、README、Header、提供商及同级相关文件。
-:::
### `openlist.fs.link`
-::: en
-Return usable link information for a file path that the current user can access.
-
-**Parameters**:
-
-| Parameter | Type | Required | Description |
-| ---------- | -------- | -------- | ----------------------------------------------- |
-| `path` | `string` | Yes | File mount path, e.g. `"/movies/demo.mp4"` |
-| `password` | `string` | No | Optional password for protected paths |
-| `type` | `string` | No | Optional link type forwarded to storage drivers |
-
-**Response**: Returns link information including direct URL, proxy URL, download URL, HTTP headers, content length, concurrency, and part size (for multi-part downloads).
-:::
-
-::: zh-CN
返回当前用户可访问的文件路径的可用的链接信息。
**参数**：
@@ -203,26 +91,10 @@ Return usable link information for a file path that the current user can access.
| `type` | `string` | 否 | 传递给存储驱动的可选链接类型 |
**响应**：返回链接信息，包括直链 URL、代理 URL、下载 URL、HTTP 头、内容长度、并发数和分片大小（用于多部分下载）。
-:::
-
-## Protocol Details { lang="en" }
-
-## 协议细节 { lang="zh-CN" }
-
-### Transport { lang="en" }
-### 传输方式 { lang="zh-CN" }
+## 协议细节
-::: en
-OpenList implements the MCP **Streamable HTTP** transport. The endpoint accepts:
-
-- `POST /mcp` — Main endpoint for all MCP JSON-RPC requests
-- `GET /mcp` — Returns `405 Method Not Allowed` with `Allow: POST, DELETE` (used for CORS preflight validation)
-- `DELETE /mcp` — Terminates an active session (requires `MCP-Session-Id` header)
-
-:::
-
-::: zh-CN
+### 传输方式
OpenList 实现了 MCP **Streamable HTTP** 传输。端点接受：
@@ -230,39 +102,11 @@ OpenList 实现了 MCP **Streamable HTTP** 传输。端点接受：
- `GET /mcp` — 返回 `405 Method Not Allowed` 及 `Allow: POST, DELETE`（用于 CORS 预检验证）
- `DELETE /mcp` — 终止活跃会话（需要 `MCP-Session-Id` 头）
-:::
-
-### Authentication {{ lang="en" }}
-
-### 认证 {{ lang="zh-CN" }}
-
-::: en
-
-The MCP endpoint reuses OpenList's authentication middleware. Requests must include a valid `Authorization` header with a valid user token. The session is bound to the authenticated user — a user cannot use sessions belonging to other users.
-
-:::
-
-::: zh-CN
+### 认证
MCP 端点复用 OpenList 的认证中间件。请求必须在 `Authorization` 头中包含有效的用户令牌。会话与认证用户绑定——用户不能使用属于其他用户的会话。
-:::
-
-### Session Lifecycle {{ lang="en" }}
-
-### 会话生命周期 {{ lang="zh-CN" }}
-
-::: en
-
-1. **Initialize**: Client sends `initialize` request. Server returns a `MCP-Session-Id` response header.
-2. **Notify Initialized**: Client sends `notifications/initialized` to mark the session as ready.
-3. **Tool Calls**: Client sends `tools/list` and `tools/call` requests with the `MCP-Session-Id` header.
-4. **Ping**: Client may send `ping` to keep the session alive.
-5. **Cleanup**: Sessions expire after 30 minutes of inactivity. Global maximum: 128 sessions per server, 16 sessions per user. The least recently used sessions are evicted first.
-
-:::
-
-::: zh-CN
+### 会话生命周期
1. **初始化**：客户端发送 `initialize` 请求。服务器返回 `MCP-Session-Id` 响应头。
2. **通知已初始化**：客户端发送 `notifications/initialized` 将会话标记为就绪。
@@ -270,49 +114,13 @@ MCP 端点复用 OpenList 的认证中间件。请求必须在 `Authorization`
4. **心跳**：客户端可发送 `ping` 保持会话活跃。
5. **清理**：会话在 30 分钟无活动后过期。全局上限：每台服务器 128 个会话，每个用户 16 个会话。最近最少使用的会话会被优先淘汰。
-:::
-
-### Protocol Version {{ lang="en" }}
-
-### 协议版本 {{ lang="zh-CN" }}
-
-::: en
-
-Supported protocol versions: `2025-11-25` (default), `2025-06-18`.
-
-The server returns its protocol version during `initialize` negotiation. Subsequent requests must carry a compatible `MCP-Protocol-Version` header matching the negotiated version.
-
-:::
-
-::: zh-CN
+### 协议版本
支持的协议版本：`2025-11-25`（默认）、`2025-06-18`。
服务器在 `initialize` 协商期间返回其协议版本。后续请求必须携带与协商版本匹配的 `MCP-Protocol-Version` 头。
-:::
-
-### Error Codes {{ lang="en" }}
-
-### 错误码 {{ lang="zh-CN" }}
-
-::: en
-
-| Code | Meaning |
-| ------ | ---------------------------------- |
-| -32700 | Parse error |
-| -32600 | Invalid request |
-| -32601 | Method not found |
-| -32602 | Invalid params |
-| -32603 | Internal error |
-| -32000 | Bad request (missing headers, etc) |
-| -32001 | Session/user not found |
-| -32002 | Session not initialized |
-| -32003 | Permission error |
-
-:::
-
-::: zh-CN
+### 错误码
| 错误码 | 含义 |
| ------ | -------------------- |
@@ -326,36 +134,8 @@ The server returns its protocol version during `initialize` negotiation. Subsequ
| -32002 | 会话未初始化 |
| -32003 | 权限错误 |
-:::
-
-## Example: Using with AI Coding Agents { lang="en" }
-
-## 示例：与 AI 编码助手一起使用 { lang="zh-CN" }
+## 示例：与 AI 编码助手一起使用
-::: en
-Many AI coding assistants support the MCP protocol and can be configured to use OpenList as a file system tool. Below is an example configuration (e.g., for VS Code or Claude Desktop):
-
-```json
-{
- "mcpServers": {
- "openlist": {
- "type": "http",
- "url": "https://your-domain:port/mcp",
- "headers": {
- "Authorization": "YOUR_OPENLIST_TOKEN"
- }
- }
- }
-}
-```
-
-Replace `YOUR_OPENLIST_TOKEN` with your actual OpenList authentication token, which can be obtained from the OpenList management panel.
-
-> **Warning**: Do **NOT** prefix the token with `Bearer `. The `Authorization` header value must be the token itself, nothing else.
-
-:::
-
-::: zh-CN
许多 AI 编码助手支持 MCP 协议，可以配置为使用 OpenList 作为文件系统工具。以下是一个示例配置（例如用于 VS Code 或 Claude Desktop）：
```json
@@ -375,5 +155,3 @@ Replace `YOUR_OPENLIST_TOKEN` with your actual OpenList authentication token, wh
将 `YOUR_OPENLIST_TOKEN` 替换为你的 OpenList 认证令牌，可从 OpenList 管理面板获取。
> **Warning**：**不要**在令牌前加 `Bearer ` 前缀。`Authorization` 头的值必须直接是令牌本身，不要加任何前缀。
-
-:::
diff --git a/pages/guide/advanced/meta.md b/pages/guide/advanced/meta.md
index 989c85f4d..5c1909e4f 100644
--- a/pages/guide/advanced/meta.md
+++ b/pages/guide/advanced/meta.md
@@ -1,52 +1,20 @@
---
-title:
- en: Meta
- zh-CN: 元信息
categories:
- guide
- advanced
top: 80
---
-::: en
-Most settings in meta information apply to `All Roles`. The `Read Users` and `Write Users` fields are exceptions — they allow you to restrict access to specific users.
-:::
-::: zh-CN
-元信息中的大多数设置对`所有角色`生效。`可读用户`和`可写用户`字段是例外——它们允许你将访问权限限制到特定用户。
-:::
+# 元信息
-## Path { lang="en" }
+元信息中的大多数设置对`所有角色`生效。`可读用户`和`可写用户`字段是例外——它们允许你将访问权限限制到特定用户。
-## 路径 { lang="zh-CN" }
+## 路径
-::: en
-The path for this meta to take effect.
-:::
-::: zh-CN
此元信息生效的路径。
-:::
-
-## Password { lang="en" }
-
-## 密码 { lang="zh-CN" }
-::: en
-Password required to access this path.
+## 密码
-- Meta information password will not take effect when accessed using `WebDav`
-
-::: danger Notes
-If you want the password to be effective in subfolders, please check `Apply to sub folder` after the password. Do not check `Write` and then check `Apply to sub folder`
-
-The correct check example is shown below. If you configure the options correctly, if you check the wrong option `Write` and then check `Apply to sub folder`, it will cause anyone to have permission to write dangerous operations
-
-
-
-
-
-:::
-
-::: zh-CN
访问此路径需要密码
- 元信息密码在使用`WebDav`访问时不会生效
@@ -62,106 +30,39 @@ The correct check example is shown below. If you configure the options correctly
:::
-## Read Users { lang="en" }
-
-## 可读用户 { lang="zh-CN" }
-
-::: en
-A whitelist of users allowed to read this path. If the list is non-empty, only the selected users can access the path; all other users will be denied access.
-
-- Users are selected by name in the management interface
-- Check `Apply to sub folder` to also restrict sub-directories
+## 可读用户
-:::
-::: zh-CN
允许读取此路径的用户白名单。如果列表非空，则只有选中的用户才能访问该路径，其他所有用户将被拒绝访问。
- 在管理界面中通过用户名选择用户
- 勾选`应用到子文件夹`可同时限制子目录
-:::
-
-## Write Users { lang="en" }
-
-## 可写用户 { lang="zh-CN" }
+## 可写用户
-::: en
-A whitelist of users allowed to write to this path. If the list is non-empty, only the selected users can perform write operations (upload, create, rename, move, delete) on this path.
-
-- Users are selected by name in the management interface
-- Check `Apply to sub folder` to also restrict sub-directories
-
-:::
-::: zh-CN
允许写入此路径的用户白名单。如果列表非空，则只有选中的用户才能对该路径执行写入操作（上传、新建、重命名、移动、删除）。
- 在管理界面中通过用户名选择用户
- 勾选`应用到子文件夹`可同时限制子目录
-:::
+## 开放写入
-## Write Content Bypass { lang="en" }
-
-## 开放写入 { lang="zh-CN" }
-
-::: en
-Allow any user to make directory, create new file and upload files, bypassing user-level write permission checks.
-:::
-::: zh-CN
允许任何用户新建目录、新文件和上传文件，绕过用户级别的写入权限检查。
-:::
-
-## Hide { lang="en" }
-
-## 隐藏 { lang="zh-CN" }
-
-::: en
-The objects to hide of this path, One regular expression (in `Golang`) per line
-- Meta information hiding can take effect when accessed using `WebDav`
+## 隐藏
-:::
-::: zh-CN
此路径要隐藏的对象，每行一个正则表达式（在 `Golang` 中）
- 元信息隐藏在使用`WebDav`访问时可以生效
-:::
-
-## Readme { lang="en" }
-
-## 说明 { lang="zh-CN" }
+## 说明
-::: en
-The Readme to render while enter this path, support markdown content or markdown link.
-
-- Show at bottom of list
-- The automatically rendered file name is: **`readme.md`**
-
-:::
-::: zh-CN
进入该路径时渲染的自述文件，支持 Markdown 内容或 Markdown 链接。
- 在列表底部显示
- 自动渲染的文件名为：**`readme.md`**
-:::
-
-## Header { lang="en" }
-
-## 顶部说明 { lang="zh-CN" }
-
-::: en
-The Readme to render while enter this path, support markdown content or markdown link.
+## 顶部说明
-- Show at top of list
-- The automatically rendered file name is: **`top.md`**
- - Files can not be displayed in the list, for example `readme.md` is not displayed in the list
- - Backstage --> Settings --> Global --> Hidden files --> Add newline `/\/top.md/i`
-
-:::
-
-::: zh-CN
进入该路径时渲染的自述文件，支持 Markdown 内容或 Markdown 链接。
- 在列表顶部显示
@@ -169,36 +70,14 @@ The Readme to render while enter this path, support markdown content or markdown
- 可以在列表中不显示文件，例如`readme.md`不在列表显示
- 后台 --> 设置 --> 全局 --> 隐藏文件 --> 换行添加 `/\/top.md/i`
-:::
-
-## Apply to sub folder { lang="en" }
-
-## 应用到子文件夹 { lang="zh-CN" }
+## 应用到子文件夹
-::: en
-Apply this meta to sub folder of specific path
-:::
-::: zh-CN
将此元信息应用于特定路径的子文件夹
-:::
-## :warning: Tips { lang="en" }
+## :warning: Tips
-## :warning: Tips { lang="zh-CN" }
-
-::: en
-
-Regarding hidden, users without permissions can search for hidden folders/files, solutions:
-
-:white_check_mark: If you want to hide the folder in a folder, create a new Yuan information alone, and select the folder we want to hide,，Hidden if you want to hide everything, write directly`.*`
-
-:x: You cannot directly fill in the meta information of the root directory `/`, and then fill in the folder we want to hide, the error case [View details](https://github.com/alist-org/alist/issues/4494) > 
-:::
-
-::: zh-CN
关于隐藏，没有权限的用户可以搜索到隐藏的文件夹/文件，解决方案：
:white_check_mark:如果你要隐藏某个文件夹內的文件夹，要单独新建一条元信息，路径选择我们要隐藏的文件夹，隐藏如果你要隐藏所有直接写 `.*`即可
:x: 不可以直接在选择根目录`/`的元信息內填写，然后隐藏位置填写我们要隐藏的文件夹，错误案例[查看详情](https://github.com/alist-org/alist/issues/4494) > 
-:::
diff --git a/pages/guide/advanced/offline-download.md b/pages/guide/advanced/offline-download.md
index bdc6c1c9e..a395691ab 100644
--- a/pages/guide/advanced/offline-download.md
+++ b/pages/guide/advanced/offline-download.md
@@ -1,34 +1,14 @@
---
-title:
- en: Offline download
- zh-CN: 离线下载
categories:
- guide
- advanced
top: 50
---
-## Please read this tip before use { lang="en" }
+# 离线下载
-## 使用前请阅读此提示 { lang="zh-CN" }
+## 使用前请阅读此提示
-::: en
-::: warning Please read the following tips carefully
-There are two kinds of software with offline download function
-
-The two usages are the same, and the software configuration is set in advance (see the following instructions for specific configuration),
-
-Then go back to the front-end interface, **find the folder you want to upload offline files to, and you can manually enter the folder**
-
-Then find the offline download button in the lower right corner, and choose to use Aria2 download or qBittorrent download (>v 3.11.0)
-
-If you use **docker**, please map the following two default paths by yourself. (mapped to the same directory on the host machine)
-
-- **/opt/openlist/data/temp/aria2**
-- **/opt/openlist/data/temp/qBittorrent**
-
-:::
-::: zh-CN
::: warning 请仔细阅读以下提示
有两款离线下载功能软件
@@ -45,22 +25,6 @@ If you use **docker**, please map the following two default paths by yourself. (
:::
-::: en
-::: danger OpenList ≥ 3.42.0
-OpenList Version ≥ 3.42.0 View [Allow all cloud disks to call other cloud disks' offline download tools](../../configuration/other.md)
-
-- ≥ 3.42.0 If you want to use offline download, you need to configure a temporary folder in the background before you can use it (otherwise it will only show **SimpleHttp**)
-- manage ==> settings ==> other （ **https://example.com/@manage/settings/other** ）
- - If you want to [use/configure] PikPak for offline downloading
- 1. Mount PikPak storage
- 2. Set Pikpak temp dir in the background
- 3. Select any folder of this account as a temporary directory
- - If multiple PikPaks are mounted and you want to use that account for offline downloading, then select the directory of that account as the temporary directory.
-
-**The following applies only to configuration instructions**
-
-:::
-::: zh-CN
::: danger OpenList ≥ 3.42.0
OpenList版本 ≥ 3.42.0 的查看 [允许所有云盘调用其他云盘的离线下载工具](../../configuration/other.md)
@@ -78,15 +42,8 @@ OpenList版本 ≥ 3.42.0 的查看 [允许所有云盘调用其他云盘的离
### Aria2
-::: en
-[**Click to view instructions for use**](../../configuration/other.md)
-
-:::
-::: zh-CN
[**点击查看使用说明**](../../configuration/other.md)
-:::
-
### qBittorrent
#### Docker Compose
@@ -134,34 +91,6 @@ networks:
#### Windows
-::: en
-(Here we take the Windows side as an example, I don’t know if there is one on the Linux side)
-First of all, we need to configure the default values on the client side of **`qBittorrent`**
-According to [source code](https://github.com/alist-org/alist/blob/main/internal/bootstrap/data/setting.go#L159-L162), we know that the default values are admin:adminadmin@localhost:8080/
-
-- **ip**: localhost
-- **port**: 8080
-- **user**: admin
-- **password**: adminadmin
-
-1. We fill in the above parameters into the **`qBittorrent`** client, after configuration, we go to the OpenList front end to download offline (**method refer to the description at the beginning**)
- - If you are prompted after submitting the offline link: **Qbittorrent not ready**, try restarting both OpenList and qBittorrent
-2. Default value configuration view address: (The link may also change position based on subsequent optimization)
- - **https://github.com/OpenListGo/alist/blob/main/internal/offline_download/qbit/qbit.go#L28**
- - `{ *** Value: "http://admin:adminadmin@localhost:8080/", Type: conf.TypeString, *** } `
-
-3. Use **`qBittorrent`** to offline `.torrent` type files
- - Although you cannot directly add offline `.torrent` type files, you can save the country with a curve Reference: [View method](https://github.com/alist-org/alist/issues/2459#issuecomment-1354870010)
-
-4. You can configure it yourself not to delete after the download is complete, but to do seeding, the default is `0`, and it will be deleted immediately after uploading
- - Modification location: **OpenList background** --> **Settings** --> **Qbittorrent seedtime** option, set the time you need to configure, the unit is `minute`, after the set seeding time is reached, it will automatically delete
-
-5. **We can also customize, instead of using the default presets**
- - Modification location: **OpenList Manage** --> **Settings** --> **Qbittorrent url** option, just follow the modification
- 
-
-:::
-::: zh-CN
（这里以Windows端举例，Linux端不清楚有没有）
首先我们先要在 **`qBittorrent`** 客户端配置好预设值
根据[源码](https://github.com/OpenListTeam/OpenList/blob/main/internal/bootstrap/data/setting.go#L159-L162)我们知道预设值分别是 admin:adminadmin@localhost:8080/
@@ -187,32 +116,7 @@ According to [source code](https://github.com/alist-org/alist/blob/main/internal
- 修改位置：**OpenList后台** --> **设置** --> **Qbittorrent url** 选项，照着修改即可
-:::
-
-#### Precautions { lang="en" }
-
-#### 注意事项 { lang="zh-CN" }
-
-::: en
-
-1. Appeared in the background qBittorrent task: **`torrent parse timeout`**, parsing timed out
-2. The torrent can be parsed, but **`The system cannot find the path specified.`** appears when uploading.
-
- The above two methods are most likely caused by the qBittorrent software itself, probably because of the green version and the modified version that have undergone some functional castration modifications. It is recommended to go to the official website to download and install it to restore it (the conclusion drawn by myself after stepping on the pit)
- - **qBittorrent** official website: **https://www.qbittorrent.org/**
- - **qBittorrent-Enhanced-Edition** GitHub: **https://github.com/c0re100/qBittorrent-Enhanced-Edition**
-
-3. Because the `v2.8.3` API is used, the minimum version of qBittorrent should be `4.4.0beta2` or `4.3.8` official version
-4. If **qBittorrent** sets the ip where alist is located to be exempt from authentication, you can directly omit the user name and password before `@` (configured on the **qBittorrent** client side)
- - 3 and 4 are not mentioned in the video.
- **qBittorrent** Video Tutorials
-
- 
-:::
diff --git a/pages/guide/advanced/s3.md b/pages/guide/advanced/s3.md
index bf6e8196f..1366f4a3f 100644
--- a/pages/guide/advanced/s3.md
+++ b/pages/guide/advanced/s3.md
@@ -1,56 +1,26 @@
---
-title:
- en: S3
- zh-CN: 对象存储
categories:
- guide
- advanced
top: 40
---
-::: en
-This function is to map OpenList as the S3 protocol. You can use the [S3 client](#s3-client-recommendation-fill-in-sample), just as OpenList can be mapped to WebDAV.
+# 对象存储
-- It can be the entire OpenList (root directory) or a separate folder
-
-:::
-::: zh-CN
此功能是将 OpenList 映射为 S3 协议，可以使用 [S3客户端](#s3-客户端推荐-填写示例) 使用和查看，就像 OpenList 可以映射为 WebDAV 一样
- 可以是整个OpenList（根目录），也可以是单独某个文件夹
-:::
-
-## 1. How to use { lang="en" }
-
-## 1. 使用方式 { lang="zh-CN" }
-
-::: en
-1.1 If it is for the first time, first open OpenList Manage to generate `S3 access key id` and `S3 secret access key` to save, then stop OpenList, open the configuration file to enable the `S3` service
-
-- If you update ID and secrets in the future, update and save, and then restart OpenList to take effect
-
-:::
+## 1. 使用方式
-::: zh-CN
1.1 如果是第一次使用，先打开OpenList后台生成一下 `访问客户端ID` 和 `访问秘钥` 保存，然后停止 OpenList，打开配置文件启用 `S3` 服务
- 如果你后续更新访问ID和秘钥，更新保存，再重启OpenList才可以生效
-:::
-
-::: en
-1.2 Open the [Configuration File](../../configuration/configuration.md#s3), change the `enable` field to` true` to enable S3 service
-
-:::
-
-::: zh-CN
1.2 打开 [配置文件](../../configuration/configuration.md#s3)，将`enable`字段改成`true`启用S3服务
-:::
-
```json{2}
"s3": {
"enable": true,
@@ -59,39 +29,13 @@ This function is to map OpenList as the S3 protocol. You can use the [S3 client]
}
```
-::: en
-1.3 After the first two steps are completed, Start OpenList, open the Manage `s3` configuration page, and choose to store a certain path as an object to store the barrel
-
-- On the left is the name of the storage bucket displayed outside, and the right is the existing list directory path of OpenList. If you want to map the entire root directory, you can choose the `root` path in the list
- - There may be errors in manual filling. It is recommended to use the `Choose` button on the right side for selection
- 
-
-:::
-
-::: zh-CN
1.3 前两步操作完成后启动 OpenList，继续进入后台`S3`配置页面，选择自己想将某路径映射为对象存储存储桶
- 左侧是对外显示的存储桶名字，右侧是 OpenList 已有的列表目录路径，如果想将整个根目录全部映射出去可以可以选择列表中的 `root` 路径
- 手动填写可能会出现错误，建议使用右侧 `选择` 按钮进行选择
-:::
-
-## 2. Use instructions { lang="en" }
-
-## 2. 使用说明 { lang="zh-CN" }
-
-::: en
-
-1. For ordinary object downloads, the transfer mode depends on the storage and proxy settings:
- - If proxying is not required and the storage provides a direct download URL, OpenList may return an HTTP 302 redirect to the storage provider.
- - If **Web Proxy** is enabled for the target storage, or another driver or proxy rule requires proxying, OpenList serves the response body through the local server.
-2. A direct redirect saves OpenList bandwidth, but the S3 client must follow a cross-host redirect and accept the provider URL's access requirements. Server relay uses OpenList bandwidth and is a safer starting point for clients that cannot use the direct provider redirect. For repository tools such as restic or rustic, enable **Web Proxy** unless direct mode has been verified.
-3. Currently only supports the use of client operations `List`, `get`, `put`, `del`, other operations are not supported yet
-4. Currently only supports the use of the `S3 Client` to operate, Mount S3 to the `OpenList Object Storage` temporarily unavailable
-
-:::
-::: zh-CN
+## 2. 使用说明
1. 对于普通对象下载，传输方式取决于存储和代理设置：
- 如果不需要代理，并且存储提供了直链下载地址，OpenList 可能返回 HTTP 302，将客户端重定向到存储提供商。
@@ -100,11 +44,7 @@ This function is to map OpenList as the S3 protocol. You can use the [S3 client]
3. 目前仅支持使用客户端 `获取列表`、`下载`、`上传`、`删除` 操作，其它操作暂未支持
4. 目前仅支持使用`S3客户端`来进行操作，挂载到OpenList对象存储暂时无法使用
-:::
-
-## 3. S3 client recommendation/fill in sample { lang="en" }
-
-## 3. S3 客户端推荐/填写示例 { lang="zh-CN" }
+## 3. S3 客户端推荐/填写示例
### 3.1. S3 Browser
diff --git a/pages/guide/advanced/search.md b/pages/guide/advanced/search.md
index 167231e0b..589d208b4 100644
--- a/pages/guide/advanced/search.md
+++ b/pages/guide/advanced/search.md
@@ -1,28 +1,14 @@
---
-title:
- en: Search
- zh-CN: 搜索/索引
categories:
- guide
- advanced
top: 100
---
-### how to use { lang="en" }
+# 搜索/索引
-### 如何使用 { lang="zh-CN" }
+### 如何使用
-::: en
-::: danger Follow the steps below to enable search:
-
-1. Go to the `indexes` page to select a **Search index** and click `Save`.
-2. After the index is saved, click `Build indexes` to build the index.
-3. Now you can search for files by click the search block on the top right corner of the page or by using the shortcut `Ctrl + K`.
-
-:exclamation: If you do not follow the above prompts, the prompt will be opened: **Search Not available**
-:::
-
-::: zh-CN
::: danger 按照以下步骤开启搜索:
1. 转到`索引`页，选择一个**搜索索引**，并单击`保存`;
@@ -32,48 +18,7 @@ top: 100
:exclamation: 若不按照上述提示开启会提示：**Search not available**
:::
-## Difference between different search indexes { lang="en" }
-
-## 不同搜索索引之间的差异 { lang="zh-CN" }
-
-::: en
-
-- `database`: Search by database, which is using the existing data.db. It will create a new table, record the parent directory, name, and size of every object, but the search does not split words which means that match whether the keywords you enter appear in the name of object. In general, if you don't have a specific search requirement, we recommend you choose it.
-
-- `database (non-full-text search)`: The full-text search mode is used above, but full-text search will have some strange problems when using **MySQL database** as an OpenList database, which has not been resolved yet, so if your OpenList database Change to **MySQL**, and your OpenList version **`≥3.9.1`** It is recommended that you use this to build an index, although it is slower than full-text search and the gap is not very big, but it will not search for strange files , it’s more secure. After the future version is repaired, we will inform you to use the new full-text search to build the index. If you are using **sqlite3**, you can use whichever you like.
-
-- `bleve`: An open source full-text search engine. It will split the words in the name of object and search for the keywords you enter. But its search results may be so strange that you can't get the results you want, and it will take up more resources.
-
-- **sqlite3** is easy to trigger `database is locked` lock library cannot write files
- - Solution to `database is locked`:
- - It's because the database is building the index. If you are still in the building process, please wait patiently.
- - If the index has been completed, it is caused by turning on [Automatically update the index](#automatically-update-the-index). Please turn off [Automatically update the index](#automatically-update-the-index). If the problem still occurs, please close and restart OpenList.
- - Or switch the database to MySQL
-
-- `meilisearch`: A feature-rich, multilingual, blazing-fast search engine written in Rust. More accurate compared to `bleve`.
- Requires [self-hosting](https://www.meilisearch.com/docs/learn/self_hosted/getting_started_with_self_hosted_meilisearch) or using a cloud service.
- `OpenList` uses "http://localhost:7700" as the default meilisearch host,
- if you host `meilisearch` and `OpenList` together locally with `meilisearch` authentication disabled, `OpenList` will automatically connect it,
- otherwise you need to modify the **meilisearch** field in the configuration file (host, index UID, API key).
- When `meilisearch` instance is protected by `api key`, the minimal actions of `api key` required by `OpenList` are `["search","indexes.get","settings.*","documents.*","tasks.*"]`.
- Storage Space Usage: ~800MiB per 100,000 files (including folders), which may be larger or smaller depending on filename length and folder depth. Please note that the storage space occupied by `meilisearch` will increase as files are continuously added/updated, and space will not be released even if you delete some or all documents from the index, unless you create a refresh instance. Generally, you don't need to worry too much about this situation, as the storage space usage will stabilize at a certain value with use, and will only have a significant impact on space usage when large numbers of files are added.
- - Download：https://github.com/meilisearch/meilisearch/releases
- - `meilisearch` Docs：https://www.meilisearch.com/docs/
- - Reference：https://github.com/AlistGo/alist/discussions/6830
-
-The following table could help you understand the difference between these search indexes quickly:
-
-| | database(full text search) | Database (non-full-text search) | bleve | meilisearch |
-| ----------------------- | ----------------------------------------------- | ------------------------------------------------------------------------ | ----------- | ----------------------------------------- |
-| Search results | Can't search in Chinese | More accurate than full-text search, you can search Chinese | Fuzzy match | Support CJK tokenizers & Chinese variants |
-| Search speed | Fast,see above for advantages and disadvantages | Slower than full-text search, see above for advantages and disadvantages | Fast | Blazing fast |
-| Specify folder search | Yes | Yes | No | Yes |
-| Disk usage | Low | Low | High | High |
-| Auto incremental update | Yes | Yes | No | Yes |
-
-:::
-
-::: zh-CN
+## 不同搜索索引之间的差异
- `数据库`：按数据库搜索，它使用现有的 data.db。它将创建一个新表，记录父目录、名称和每个对象的大小，但搜索不拆分单词，这意味着匹配您输入的关键字是否出现在对象的名称中。一般来说，如果您没有特定的搜索要求，我们建议您选择它。
@@ -107,19 +52,6 @@ The following table could help you understand the difference between these searc
| 硬盘占用 | 低 | 低 | 高 | 高 |
| 自动增量更新 | 支持 | 支持 | 不支持 | 支持 |
-:::
-
-::: en
-::: warning
-If you are using _MySQL_ as the database, it is recommended to use **`non-full-text search`** (strongly recommended)
-
-**`Non-full-text search`** Although it is not as fast as full-text search, it is not much slower. If you insist on using full-text search, you may have to sacrifice the inability to search Chinese
-
-If you use sqlite as the database, there is no full-text search, you can choose any database~
-
-Full-text search: It will not search in the text of all files, don't get it wrong.
-:::
-::: zh-CN
::: warning
若你使用的是 **MySQL** 作为数据库，建议使用 **`非全文搜索`** （强烈推荐）
@@ -130,66 +62,9 @@ Full-text search: It will not search in the text of all files, don't get it wron
全文搜索：不是在所有文件里面进行文件的文字里面进行搜索，别理解错了。
:::
-### Deploy MeiliSearch for indexing using Docker Compose { lang="en" }
-
-### 使用docker compose部署meilisearch进行索引 { lang="zh-CN" }
-
-#### Deploy MeiliSearch using Docker Compose { lang="en" }
-
-#### 使用docker compose部署meilisearch { lang="zh-CN" }
-
-::: en
-
-Feeling confused?
-
-Here's a Compose example to add `meilisearch` to your Openlist Compose. Follow the steps to set up indexing with `meilisearch`.
-
-```yaml
-version: '3.3'
-services:
- openlist:
- image: 'openlistteam/openlist:beta-aio'
- container_name: openlist
- volumes:
- - '/tmp/data/Docker/OpenList:/opt/openlist/data'
- ports:
- - '5244:5244'
- environment:
- - UMASK=022
- networks:
- - openlist
- restart: unless-stopped
-
- meilisearch:
- image: getmeili/meilisearch:v1.16
- container_name: meilisearch
- ports:
- - '7700:7700'
- volumes:
- - /tmp/data/Docker/meilisearch/meili_data:/meili_data
- command: meilisearch --schedule-snapshot --snapshot-dir /meili_data/snapshots
- environment:
- - MEILI_MASTER_KEY=your_master_key_here
- tty: true
- stdin_open: true
- networks:
- - openlist
- restart: unless-stopped
-
-networks:
- openlist:
- driver: bridge
-```
-
-Configuration Explanation:
-
-- `UMASK`: Sets file permissions
-- `getmeili/meilisearch:v1.16`: Official recommendation to use a fixed version number (latest version at time of writing is `v1.16`). You may check the latest version yourself via the [official local deployment docs](https://www.meilisearch.com/docs/learn/self_hosted/install_meilisearch_locally).
-- Additional parameters for meilisearch can be modified via the [official local deployment docs](https://www.meilisearch.com/docs/learn/self_hosted/install_meilisearch_locally) or deployed using alternative methods.
+### 使用docker compose部署meilisearch进行索引
-:::
-
-::: zh-CN
+#### 使用docker compose部署meilisearch
感到一头雾水？
@@ -238,18 +113,6 @@ networks:
- `getmeili/meilisearch:v1.16`: 官方建议使用固定的版本编号(本文撰写时最新版本为`v1.16`),您可以自行从[官网本地部署docs](https://www.meilisearch.com/docs/learn/self_hosted/install_meilisearch_locally)查询最新版本。
- 有关meilisearch的其他参数可以通过[官网本地部署docs](https://www.meilisearch.com/docs/learn/self_hosted/install_meilisearch_locally)自行修改或采用其他方式部署。
-:::
-
-::: en
-::: warning
-The `/tmp/data/Docker` directory here is merely an example; please store your data in an appropriate location.
-
-Additionally, the `MEILI_MASTER_KEY` here should be replaced with a key you generate yourself. You should substitute it with any alphanumeric string of 16 bytes or more. In most cases, one character corresponds to one byte.
-
-PS: This provides only a basic example. Please modify it according to your needs and add other configurations as required.
-:::
-
-::: zh-CN
::: warning
这里的`/tmp/data/Docker`仅是一个示例，请将你的数据存储在合适的位置。
@@ -258,32 +121,8 @@ PS: This provides only a basic example. Please modify it according to your needs
PS：这里仅仅提供一个基础示例，请根据你的需求进行修改和添加其他配置。
:::
-#### Setting up meilisearch in openlist { lang="en" }
-
-#### 在openlist中设置使用meilisearch { lang="zh-CN" }
-
-::: en
-How to configure MeiliSearch in OpenList
+#### 在openlist中设置使用meilisearch
-First, you need to modify config.json. In this example, it should be located at `/tmp/data/Docker/OpenList/config.json`.
-
-Edit the section below, filling in the IP address and port of your MeiliSearch instance, along with the key you set in `MEILI_MASTER_KEY`.
-
-```json
- "meilisearch": {
- "host": "http://meilisearch:7700",
- "api_key": "your_master_key_here",
- "index": "openlist"
- },
-```
-
-Next, open the management panel, click `Indexes`, select `meilisearch`, and click `Refresh` to rebuild the index.
-
-{width=600px}
-
-:::
-
-::: zh-CN
如何在openlist设置meilisearch
首先你需要修改config.json,在这个示例中，它应该位于`/tmp/data/Docker/OpenList/config.json`。
@@ -302,45 +141,15 @@ Next, open the management panel, click `Indexes`, select `meilisearch`, and clic
{width=600px}
-:::
-
-## Search tips { lang="en" }
-
-## 搜索提示 { lang="zh-CN" }
-
-::: en
-
-- If you want to search for a specific folder, you must choose `database` as the search index;
-- If you choose `database` as the search index and the type of your database is `sqlite3`, we suggest that you don't make any changes in the admin page while building the index, as sqlite3 does not support concurrent writes and can cause `database-lock` issues;
-- If you choose `bleve` as the search index, and if you want to search for new files or if you don't want to search for deleted files, the index needs to be completely rebuilt to take effect because `bleve` does not support incremental updates;
-- But for `database`, it supports incremental updates, so you can search for new files or deleted files just by access the modified folder (and click `refresh` icon if cached) without rebuilding the index, which is much more convenient than `bleve`.
-
-:::
-::: zh-CN
+## 搜索提示
- 如果你想搜索特定的文件夹内的文件，你可以选择`数据库`或`meilisearch`作为搜索索引;
- 如果你选择`数据库`作为搜索索引，你的数据库类型是`sqlite3`，我们建议你在创建索引时不要在管理页面做任何更改，因为 `sqlite3` 不支持并发写，可能导致`数据库锁定`问题;
- 如果你选择`bleve`作为搜索索引，如果你想搜索新文件或不想搜索已删除的文件，索引需要完全重建才能生效，因为`bleve`不支持增量更新;
- 但对于`数据库`/`meilisearch`，它支持增量更新，所以你可以搜索新的文件或删除的文件，只需访问修改的文件夹(并单击'刷新'图标，如果缓存)，无需重建索引，这比`bleve`方便得多。
-:::
-
-### Ignore paths { lang="en" }
-
-### 忽略路径 { lang="zh-CN" }
-
-::: en
-Paths to be skipped during index building, one path per line, multiple lines can be filled
+### 忽略路径
-- Example:
- - `/aaa network disk`
- - `/bbb network disk/ccc folder`
-
-If you don't want to configure this, you can turn on the `disable index` option in each driver
-
-:::
-
-::: zh-CN
构建索引期间跳过填写的路径，一行一个路径，可多行填写
- 例子：
@@ -349,21 +158,7 @@ If you don't want to configure this, you can turn on the `disable index` option
如果不想(不会)配置这里，可以去每个驱动中将`禁用索引`选项打开
-:::
-
-## Update index { lang="en" }
-
-## 更新索引 { lang="zh-CN" }
-
-::: en
-
-- (formerly: the path to update the index)
- After building all the indexes, or a file has a large number of file updates, but it is inconvenient to rebuild, you can use this to update the index
-- Example: - /aaa network disk - /bbb network disk/ccc folder
-
-:::
-
-::: zh-CN
+## 更新索引
- (原：要更新索引的路径)
构建完所有索引后，或者某文件有大批量文件更新，但是又不方便点重新构建就可以使用这个来更新一下索引
@@ -371,37 +166,8 @@ If you don't want to configure this, you can turn on the `disable index` option
- `/aaa网盘`
- `/bbb网盘/ccc文件夹`
-:::
-
-### Automatically update the index { lang="en" }
-
-### 自动更新索引 { lang="zh-CN" }
-
-::: en
-:warning: **`The default is off, and the index will not be built automatically`**.
-
-For example, you have already built the index, but added a **network disk mount** or **folder update** later.
-
-But you have already built a lot of indexes. According to the previous words, there are two methods.
-
-1. Go in folder by folder before building
-
-2. Or it is cumbersome to refactor all
-
- But this time, just turn on the **`Automatically build index`** button and enter the **Newly mounted network disk** or **Updated folder**, the indexed files in this directory and The folder automatically builds the index without entering a folder by folder to let him build it automatically
+### 自动更新索引
-- Advantages: Don't worry, all the indexes in this folder can be automatically built if there is an update into the root directory of the updated folder
-- Cons: always on call ready to build
-
----
-
-Someone will find out that [**Path to update index**](#Path to update index) can also be updated? Can be updated but the two do not conflict.
-
-- [**Automatically update index**](#automatically-update-the-index): suitable for users who build indexes for all files
-- [**Update Index**](#update-index): Suitable for **not** to build indexes for all files, but there are files that need to be built, manually build indexes to avoid all being indexed
-
-:::
-::: zh-CN
:warning: **`默认是关闭状态，不自动构建索引`**。
例如你已经构建完毕索引，但是后面又添加一个 **网盘挂载** 或者 **文件夹更新**。
@@ -424,40 +190,13 @@ Someone will find out that [**Path to update index**](#Path to update index) can
- [**自动更新索引**](#自动更新索引)：适合将所有文件都构建索引的用户
- [**更新索引**](#更新索引)：适合 **不** 将所有文件都构建索引，但是有文件需要构建，自己手动去构建索引避免所有的都被构建索引
-:::
-
-### Maximum index depth { lang="en" }
-
-### 最大索引深度 { lang="zh-CN" }
+### 最大索引深度
-::: en
-default 20.
-The one shown outside is built manually, and the update index option selects the depth in the update index button.
-Explanation: The directory can enter up to several layers. For example, if you have a folder with a depth of 30 layers, set it to 20, and only build the first 20 layers, and the remaining 10 layers will not be built.
-:::
-::: zh-CN
默认为20。
外面显示的是手动构建的，更新索引选项在更新索引按钮里面选择深度。
说明：目录最多进几层，例如你有一个文件夹深度多达30层文件夹，设置为20，只构建前20层，剩下的10层不进行构建。
-:::
-## :warning: Precautions for use { lang="en" }
-
-## :warning: 使用注意事项 { lang="zh-CN" }
-
-::: en
-
-- OpenList **V2** and **v3** types of mounts cannot be built by default
-- If you are using **MySQL** as the database, it is recommended that you use **database (non-full-text search)**, [**Click to view details to see the second item**](#difference-between-different-search-indexes)
-- In the future version (**≥3.9.0 version**), V3 users can choose whether to allow others to mount your network disk and then index it :no_entry:**`Use with caution`**:no_entry:
- - View details: [allow-indexing](/configuration/site#allow-indexing)
- - Don't ask why V2 is not supported, because the V2 version is no longer maintained, so there is no follow-up
-- Why not directly open V2 V3 index construction: **https://github.com/alist-org/alist/discussions/2529**
-- After building an index, users without permissions can search for hidden file/folder solutions [click to view](meta.md#tips)
-
-:::
-
-::: zh-CN
+## :warning: 使用注意事项
- OpenList **V2** 和 **v3** 类型的挂载默认不能构建
- 如果你使用的是 **MySQL** 作为数据库，推荐你使用 **数据库(非全文搜索)**, [**点击查看详情看第二条**](#不同搜索索引之间的差异)
@@ -467,44 +206,8 @@ Explanation: The directory can enter up to several layers. For example, if you h
- 为什么不直接开放V2 V3索引构建： **https://github.com/alist-org/alist/discussions/2529**
- 构建索引后，没有权限的用户可以搜索到隐藏的文件/文件夹解决方案[点击查看](meta.md#tips)
-:::
-
-## The database file is very large, what should I do if it is still the same after clearing the index? { lang="en" }
-
-## 数据库文件很大，清空索引后还是一样大怎么办? { lang="zh-CN" }
-
-::: en
-Normal users do not modify the database options. They use the `sqlite` database to build indexes, which will cause the database file to be particularly large
+## 数据库文件很大，清空索引后还是一样大怎么办?
-- Data files, `Data` folders in the same directory in OpenList program,`data.db，data.db-shm，data.db-wal`
-
-After turning on the constructive index, the more the number you build, the larger the files. Finally, you accidentally occupy the machine's hard disk, and then click the clear index button. What should I do if the file is still as big?
-
-- This is caused by the cache of `sqlite`, there are two solutions:
- 1. We use commands or tools to connect to `sqlite` database, input：**`VACUUM;`**
-
- ```sql
- VACUUM;
- ```
-
- 2. After using the command to clean up, we replace it with `mysql` database before constructing indexes
- - Sqlite replaced with mysql database tutorial：**[BV1iV4y1T7kh](https://www.bilibili.com/video/BV1iV4y1T7kh)**
-
- Comparison after cleaning the command: The picture above shows before cleaning up, and the following figure shows that after cleaning, you can execute several commands several times if there is no effect.
-
- 
-
----
-
-`data.db, data.db-shm, data.db-wal` when backup, when backup，`data.db-shm，data.db-wal` Do these two files need backup？
-
-- In the backup, stop the program first, and then backup. You only need to backup the `data.db` database file. The other two do not need to backup
-
-- It may be after you stop the program`data.db-shm，data.db-wal`will automatically disappear, don't worry
-
-:::
-
-::: zh-CN
正常用户都是没有修改数据库选项使用的是 `sqlite` 数据库来构建索引的，就会导致数据库文件特别大
- 数据库文件在OpenList同级目录下的`data`文件夹，`data.db，data.db-shm，data.db-wal`
@@ -531,5 +234,3 @@ After turning on the constructive index, the more the number you build, the larg
- 建议在备份时，先将程序停止，再进行备份，到时候可以只单独备份`data.db`数据库文件，另外两个可以不进行备份
- 有可能在你停止程序后`data.db-shm，data.db-wal`这两个文件会自动消失，也不用担心
-
-:::
diff --git a/pages/guide/advanced/sso.md b/pages/guide/advanced/sso.md
index b9abd65e3..eda2c4021 100644
--- a/pages/guide/advanced/sso.md
+++ b/pages/guide/advanced/sso.md
@@ -1,40 +1,18 @@
---
-title:
- en: Third-party single sign-on
- zh-CN: 单点登录
categories:
- guide
- advanced
top: 60
---
-## 1. Single sign-on client id { lang="en" }
+# 单点登录
-## 1. 单点登录客户端ID { lang="zh-CN" }
+## 1. 单点登录客户端ID
-::: en
-client ID.
-:::
-::: zh-CN
客户端ID。
-:::
-
-## 2. Single sign-on client secrets { lang="en" }
-
-## 2. 单点登录客户端秘钥 { lang="zh-CN" }
-::: en
-client secrets.
-::: warning matters needing attention
-
-1. Remember to write and save the background parameters of OpenList. After writing and saving, you have to go back to the bottom of the personal data and there will be a button that needs to be bound, otherwise it cannot be used
-2. Only one of the four types of single sign-on can be enabled temporarily. If you used other single sign-on methods before and then changed to a new single Unbind (just one click) and then bind the single sign-on method you want to use now.
-3. If you use **`GitHub,Microsoft,Google,DingTalk`**, you only need to fill in the client ID and secret key, and select the corresponding platform in the options.
- - If you use **`Casdoor`** the following parameters need to be filled in, just follow the tutorial to fill in
-
-:::
+## 2. 单点登录客户端秘钥
-::: zh-CN
客户端秘钥
::: warning 注意事项
@@ -48,9 +26,7 @@ client secrets.
:::
-## 3. Registration binding single sign-on { lang="en" }
-
-## 3. 注册绑定单点登录 { lang="zh-CN" }
+## 3. 注册绑定单点登录
##
@@ -66,20 +42,7 @@ client secrets.
##
-## 4. SSO automatically registers as an OpenList account { lang="en" }
-
-## 4. 单点登录自动注册为OpenList帐号 { lang="zh-CN" }
-
-::: en
-
-- **OpenList Version > **v3.22.1** New Features**
- Before using single sign-on to register as an OpenList account, we need to bind the single sign-on of OpenList first, the binding method is explained above
-- Supports the `five` single sign-on methods mentioned above
-- Do not use the default organization (**app-built-in**) directly, because all users in this organization are global administrator accounts
-- Except `CASDOOR`, you only need to fill in the` Client id` and the `Client secrets`and the newly added single login account registered as OpenList account configuration
-
-:::
-::: zh-CN
+## 4. 单点登录自动注册为OpenList帐号
- **OpenList 版本 > **v3.22.1** 新增功能**
在使用单点登录注册为OpenList帐号前，我们需要先将OpenList的单点登录进行绑定，绑定方法在上面有说明
@@ -87,77 +50,25 @@ client secrets.
- 如果使用`Casdoor`,请勿直接使用默认组织(**app-built-in**),因为这个组织内的用户都是全局管理员帐号
- 除了`Casdoor`其它的只需要填写`客户端ID`和`客户端秘钥`以及下面新增的单点登录帐号注册为OpenList帐号的配置
-:::
+### 4.1. SSO完整填写示例
-### 4.1. SSO Full Fill Demo { lang="en" }
-
-### 4.1. SSO完整填写示例 { lang="zh-CN" }
-
-::: en
-Please refer to the detailed description below for how to fill in, the schematic diagram is just a reference for filling in and not suitable for everyone’s user habits
-
-
-:::
-
-::: zh-CN
分别如何填写看下面的详细说明，示意图只是一个填写参考并不适合每个人的用户习惯
-:::
-### 4.2. SSO auto register { lang="en" }
+### 4.2. SSO自动注册
-### 4.2. SSO自动注册 { lang="zh-CN" }
-
-::: en
-If we want SSO single sign-on to be registered as an OpenList account, we need to enable this option before it can be used
-:::
-::: zh-CN
如果我们想让SSO单点登录注册为OpenList帐号我们需要打开这个选项才可以使用
-:::
-
-### 4.3. SSO default dir { lang="en" }
-
-### 4.3. SSO默认路径 { lang="zh-CN" }
-
-::: en
-That is to say, the default path used by the registered account is equivalent to the `Base path` in the OpenList user settings.
-It can be the root directory `/`, or the path `/path/test/Demo` specified by the user
+### 4.3. SSO默认路径
-
-:::
-::: zh-CN
也就是说注册的帐号默认使用的路径，相当于OpenList用户设置里面的`基本路径`
可以是根目录`/`，也可以是用户指定的路径`/path/test/Demo`
-:::
-
-### 4.4. SSO default permission { lang="en" }
-
-### 4.4. SSO默认权限 { lang="zh-CN" }
-
-::: en
-It is equivalent to which permissions are enabled by default for registered users, as shown below
-
-
-
-
-
-The default is 0, no permission is enabled
-
-If we need to enable some permissions during registration, we only need the sum of the numbers of different permissions.
-
-For example：
-1. We need to open the user's `WebDav reading` and `WebDav manage ` by default, that is 256+512=768, we just fill in `768` in the options
-2. If we need to open the three permissions of `Make dir or upload`, `Rename` and `Delete` by default when registering, then it is 8+16+128=152, we can fill in `152` in the background
- I won’t say much about the examples, just add the permissions you need
-
-:::
-::: zh-CN
+### 4.4. SSO默认权限
相当于注册的用户默认开通哪些权限，就如下面所示的
@@ -170,55 +81,8 @@ For example：
2. 如果我们需要注册时默认开通`创建目录或上传`和`重命名`和`删除`这三个权限 那就是8+16+128=152，我们在后台填写`152`即可
例子就不多说了，需要那个权限自己相加就可以
-:::
-
-### 4.5. Precautions and instructions { lang="en" }
-
-### 4.5. 注意事项以及说明 { lang="zh-CN" }
-
-::: en
-**4.1-There is already this user in the OpenList user database**
-
-| username | password | base\*path | role | permission | opt_secret | github_id | disabled | sso_id |
-| ------------------ | -------- | ---------- | ---- | ---------- | ---------- | --------- | -------- | ----------- |
-| anyi | FzdDfkmU | /test1 | 0 | 3 | | | 0 | |
-| anyi**\*dc188911** | RUCtgqCw | /test1 | 0 | 3 | | | 0 | **dc18891** |
-
-As shown in the above table, a string of redundant ids is added after the newly registered single sign-on user name
-
-This is because the same user already exists in the OpenList user database, so the sso_id is also added after the user name
-
-If your newly registered single sign-on user name does not exist in the OpenList user database, it will not add the sso_id after the name
-
-**4.2-What should I do if I don’t want the SSO account to be registered as an OpenList account?**
-
-Just turn `SSO auto register` off,This will not affect the use of accounts that have been registered using Sso
-
-**4.3-If I turn off the single sign-on option, what should I do with the account registered with Sso?**
+### 4.5. 注意事项以及说明
-Don't worry, after using single sign-on to register and log in to OpenList, log in in the background, and find `personal information` after logging in
-
-- You can modify **`username`** and **`password`** by yourself, save it after modification, so that you can log in with the OpenList account normally
-- At this time, you can click `Unbind Single Sign-On Platform`, you can unbind or not unbind, and the subsequent [**default path**](#sso-default-dir) and [**default permissions**](#sso-default-permission) of this user can only be modified by the administrator in the OpenList background user
-
-**4.4-Why is this error code displayed when using sso?**
-
-```json{3}
-{
- "code": 400,
- "message": "The single sign on platform is not bound to any users: record not found",
- "data": null
-}
-```
-
-This is because [Single Sign-On Automatic Registration](#sso-auto-register) is not enabled for the OpenList account, and the single sign-on cannot be registered as an OpenList account
-
-- If you are an administrator, you can turn it on
-
-- If you are a user, you can contact the administrator to enable
-
-:::
-::: zh-CN
**4.1-OpenList用户数据库已存在同名的帐号**
| username | password | base_path | role | permission | opt_secret | github_id | disabled | sso_id |
@@ -258,23 +122,8 @@ This is because [Single Sign-On Automatic Registration](#sso-auto-register) is n
- 如果你是管理员，你可以开启一下
- 如果你是用户，你可以去联系管理员开启
-:::
-
-## 5. Sso compatibility mode { lang="en" }
-
-## 5. SSO兼容模式 { lang="zh-CN" }
-
-::: en
-OpenList single -point login is bound to Dingtalk, and then opens OpenList in the **`Dingtalk`** application, When you log in, choose Dingtalk login and jump to your computer browser. After authorization, you find that there is no response, because the browser cannot jump to the Dingtalk application inner browser page
-
-At this time, you need to open the **`sso compatability mode`** again to click on the login to log in successfully
-
-**OpenList applied in Dingtalk and opened as shown in the figure：**
+## 5. SSO兼容模式
-
-
-:::
-::: zh-CN
OpenList单点登录绑定了钉钉，然后在 **`钉钉`** 应用内打开OpenList，登录时选择钉钉登录会跳到自己电脑浏览器，授权后你会发现没有后续反应了，因为浏览器无法跳回钉钉应用內浏览器页面
这时候就需要打开 **`SSO兼容模式`** 再去点击登录就可以登录成功了
@@ -283,66 +132,22 @@ OpenList单点登录绑定了钉钉，然后在 **`钉钉`** 应用内打开Open
-:::
-
-## 6. How to create the application in Dingtalk workbench { lang="en" }
-
-## 6. 如何创建钉钉工作台內应用 { lang="zh-CN" }
+## 6. 如何创建钉钉工作台內应用
-::: en
-A picture teaches you to create a new application and add it
-
-- LOGO is not modified when the newly -built newly built, you can wait for the newly built and then modify See_Figure_2
-- If you just browse OpenList in the Dingtalk application, you do n’t need a single -point login management, you do n’t need to set up a single -point login configuration, you can just add an application
- 
-
-:::
-::: zh-CN
一张图教你新建一个应用并且添加
- LOGO是默认的新建时不可修改，可以等新建好后再修改 (看图二)
- 如果你只是在钉钉应用內浏览OpenList，不使用单点登录后台管理，可以不用设置单点登录配置只添加应用就可以
-:::
-
-### 6.1. Modify the application logo { lang="en" }
-
-### 6.1. 修改应用LOGO { lang="zh-CN" }
+### 6.1. 修改应用LOGO
-::: en
-Open [**DingTalk open platform management**](https://open-dev.dingtalk.com/fe/app#/corp/app) Find your newly built app to modify the logo.
-
-
-
-:::
-::: zh-CN
打开 [**钉钉开放平台后台**](https://open-dev.dingtalk.com/fe/app#/corp/app) 找到你新建的应用进去修改LOGO就可以
-:::
-
-## 7. redirect url { lang="en" }
+## 7. 回调参数(重定向链接)
-## 7. 回调参数(重定向链接) { lang="zh-CN" }
-
-::: en
-After turning on **`Sso compatibility mode`** Then you need to log in to the corresponding software to modify the redirect url to change it to the two redirect url below
-
-- `GitHub` only needs to add one：`http(s)://You_Url/api/auth/sso_get_token`
-- `Microsoft` and` Google` both need to be added, you can add multiple Redirect urls, so you only need to add two Redirect URLs.
-
-```
-http(s)://You_Url/api/auth/get_sso_id
-http(s)://You_Url/api/auth/sso_get_token
-```
-
-If you enable the **Sso compatibility mode** if you do not modify it, you will prompt `Invalid Redirect URL` Error
-
-:::
-
-::: zh-CN
开启 **`SSO兼容模式`** 后需要将单点登录对应的软件内修改一下回调参数链接改成下面的两个回调参数
- `GitHub` 只需要添加一条：`http(s)://You_Url/api/auth/sso_get_token`
@@ -354,5 +159,3 @@ http(s)://You_Url/api/auth/sso_get_token
```
如果启用 SSO兼容模式 不修改则会提示 `invalid redirect url` 错误
-
-:::
diff --git a/pages/guide/advanced/sso/01-GitHub.md b/pages/guide/advanced/sso/01-GitHub.md
index bb5b8e6f9..aa22614d1 100644
--- a/pages/guide/advanced/sso/01-GitHub.md
+++ b/pages/guide/advanced/sso/01-GitHub.md
@@ -1,45 +1,12 @@
-### 3.1. Github { lang="en" }
+### 3.1. GitHub
-::: en
-::: warning
-If you want to use GitHub to log in, you first need the machine you built OpenList to be able to connect to GitHub before you can call and use it, otherwise you cannot use it if the link is not connected
-:::
-::: en
-Open **https://github.com/settings/developers** Click **`New OAuth App`**
-:::
-
-### 3.1. GitHub { lang="zh-CN" }
-
-::: zh-CN
::: warning
若想使用GitHub登录，首选需要你搭建OpenList的机器能连接访问GitHub才可以调用使用，不然连接不上无法使用
:::
-::: zh-CN
-打开 **https://github.com/settings/developers** 点击 **`New OAuth App`**
-:::
-
-#### 3.1.1. Register OAuth Instructions { lang="en" }
-
-#### 3.1.1. Register OAuth 填写说明 { lang="zh-CN" }
-
-::: en
-
-- Application name
- - Write whatever you want to call it
-- **Homepage URL**
- - home URL address
- - Both **http** and **https** can be used
-- Application description
- - write whatever you want
-- **Authorization callback URL**
- - Callback URL address
- - **https://your_domain/api/auth/sso_callback** - Both **http** and **https** can be used
- Remember to get **Client secrets** after filling it out, and then fill it in the OpenList background.
- Remember to write and save the background parameters of OpenList. After writing and saving, you have to go back to the bottom of the personal data and there will be a button that needs to be bound, otherwise it cannot be used
-:::
+打开 **https://github.com/settings/developers** 点击 **`New OAuth App`**
-::: zh-CN
+#### 3.1.1. Register OAuth 填写说明
- Application name
- 随便写想叫什么叫什么
@@ -53,21 +20,10 @@ Open **https://github.com/settings/developers** Click **`New OAuth App`**
- **https://你的域名/api/auth/sso_callback** - 可以使用http https都可以
填写完毕后记得获取一下 **Client secrets**，然后填写到OpenList后台。
-:::
-
-#### 3.1.2. Completely fill in the reference schematic { lang="en" }
-
-#### 3.1.2. 完整填写参考示意图 { lang="zh-CN" }
+#### 3.1.2. 完整填写参考示意图
-::: en
-
-:::
-::: zh-CN
-:::
-
-#### 3.1.3. GitHub login Video Tutorials { lang="en" }
-#### 3.1.3. GitHub视频教程 { lang="zh-CN" }
+#### 3.1.3. GitHub视频教程
`https://your.openlist.domain/api/auth/sso_callback?method=sso_get_token`
`https://your.openlist.domain/api/auth/sso_get_token`
`https://your.openlist.domain/api/auth/get_sso_id` - Valid post logout redirect URIs|留空 - Web origins |留空 - ::: - ::: en - ::: details see the details - |Name|Value| - -|---- - Root URL |Leave blank - Home URL |Enter your OpenList access address, e.g.: https://your.openlist.domain - Valid redirect URIs|`https://your.openlist.domain/api/auth/sso_callback?method=get_sso_id`
`https://your.openlist.domain/api/auth/sso_callback?method=sso_get_token`
`https://your.openlist.domain/api/auth/sso_get_token`
`https://your.openlist.domain/api/auth/get_sso_id` - Valid post logout redirect URIs|Leave blank - Web origins |Leave blank + | 配置名 | 配置值 | + | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | + | Root URL | 留空 | + | Home URL | 填入你OpenList的访问地址，如：https://your.openlist.domain | + | Valid redirect URIs | `https://your.openlist.domain/api/auth/sso_callback?method=get_sso_id`
`https://your.openlist.domain/api/auth/sso_callback?method=sso_get_token`
`https://your.openlist.domain/api/auth/sso_get_token`
`https://your.openlist.domain/api/auth/get_sso_id` | + | Valid post logout redirect URIs | 留空 | + | Web origins | 留空 | ::: -##### 3.7.1.3. 获取JWT公钥 { lang="zh-CN" } - -##### 3.7.1.3. Retrieve JWT public key { lang="en" } - -::: zh-CN +##### 3.7.1.3. 获取JWT公钥 - 在左侧找到 `Clients`，选择刚创建的 Client 进入设置页面。 - 在 Client 设置页面，切换到 `Keys` 选项卡。 - 在 `Public Key` 字段中复制公钥内容，稍后在 OpenList 配置中使用。 - 如果没有看到公钥，可以点击 `Generate RSA Keys` 生成 -::: -::: en - -- In the left menu, find `Clients`, select the newly created Client to enter the settings page. -- In the Client settings page, switch to the `Keys` tab. -- Copy the content in the `Public Key` field for later use in OpenList configuration. -- If the public key is not visible, click `Generate RSA Keys` to generate it. - -::: - -##### 3.7.1.4. 获取Client Secret { lang="zh-CN" } - -##### 3.7.1.4. Retrieve Client Secret { lang="en" } - -::: zh-CN +##### 3.7.1.4. 获取Client Secret - 在 Client 设置页面，切换到 `Credentials` 选项卡。 - 在 `Client Secret` 字段中复制客户端密钥内容，稍后在 OpenList 配置中使用。 -::: -::: en - -- In the Client settings page, switch to the `Credentials` tab. -- Copy the content in the `Client Secret` field for later use in OpenList configuration. - -::: +#### 3.7.2. OpenList 设置 -#### 3.7.2. OpenList 设置 { lang="zh-CN" } - -#### 3.7.2. OpenList Setup { lang="en" } - -::: zh-CN 在 OpenList 的单点登录配置填写如下参数： - **启用 SSO 登录**：`是` @@ -176,24 +89,3 @@ After selecting the realm, click `Clients` → `Create Client`. 如有特殊需求，根据实际 Keycloak 部署调整 claims 和端点。 详细操作请参考 [Keycloak 官方 OIDC 文档](https://www.keycloak.org/documentation)。 - -::: - -::: en -Fill in the following parameters in OpenList's SSO configuration: - -- **SSO login enabled:** `yes` -- **SSO login platform:** `OIDC` -- **SSO client id:** Keycloak Client ID (from [Create Client](#_3-7-1-2-create-client) above) -- **SSO client secret:** Keycloak Client Secret (from [Retrieve Client Secret](#_3-7-1-4-retrieve-client-secret) above) -- **SSO oidc username key:** `preferred_username` or as per your Mapper settings -- **SSO organization name:** `master` (from [Create Realm](#_3-7-1-1-create-realm) above) -- **SSO application name:** `OpenList` (from [Create Client](#_3-7-1-2-create-client) above) -- **SSO endpoint name:** `https://your.keycloak.domain/realms/{realm-name}` (where realm-name matches the organization name) -- **SSO jwt public key:** from [Retrieve JWT public key](#_3-7-1-3-retrieve-jwt-public-key) above -- **SSO auto register as OpenList account:** Enable as needed -- **SSO compatibility mode:** `no` (enable if compatibility is required) - -Adjust claims and endpoints based on your specific Keycloak deployment if needed. -For detailed operations, refer to the [Keycloak official OIDC documentation](https://www.keycloak.org/documentation). -::: diff --git a/pages/guide/advanced/strm.md b/pages/guide/advanced/strm.md index 582af8c29..ac54765d9 100644 --- a/pages/guide/advanced/strm.md +++ b/pages/guide/advanced/strm.md @@ -1,11 +1,10 @@ --- -title: - en: Generate Strm - zh-CN: 生成 strm categories: - guide - advanced top: 10 --- +# 生成 strm + diff --git a/pages/guide/advanced/user.md b/pages/guide/advanced/user.md index f4093073b..9b3a99595 100644 --- a/pages/guide/advanced/user.md +++ b/pages/guide/advanced/user.md @@ -1,53 +1,24 @@ --- -title: - en: User - zh-CN: 用户 categories: - guide - advanced top: 140 --- -## Add user { lang="en" } +# 用户 -## 添加用户 { lang="zh-CN" } +## 添加用户 -::: en -::: warning Security Notice -Adding a user may expose files and server-side capabilities to another account. Use a strong, unique password, grant only the minimum required permissions, and create accounts only for trusted users. Security incidents resulting from improper user or permission management are the administrator's responsibility. -::: -::: zh-CN ::: warning 安全提醒 添加用户可能会使其他账户获得文件和服务器侧功能的访问能力。请使用强且唯一的密码，仅授予必要的最小权限，并仅为可信用户创建账户。因用户或权限管理不当而导致的安全事件，由管理员用户承担责任。 ::: -## Username { lang="en" } - -## 用户名 { lang="zh-CN" } +## 用户名 -::: en -Username for login. -::: -::: zh-CN 登录用户名。 -::: - -## Password { lang="en" } - -## 密码 { lang="zh-CN" } - -::: en -Password for login. -:::tip -Password is invalid for guest user. - -If you enter an incorrect password 6 times in a row, the current IP will be blocked for 30 minutes and you will not be able to enter your account and password to log in. However, it will not affect other IPs. It will only target IPs that entered 6 incorrect passwords. -- Restarting will immediately remove the 30-minute ban time +## 密码 -::: - -::: zh-CN 登录密码。 :::tip 密码对游客是无效的。 @@ -58,53 +29,15 @@ If you enter an incorrect password 6 times in a row, the current IP will be bloc ::: -## Base path { lang="en" } - -## 基本路径 { lang="zh-CN" } - -::: en -The root path that users see when he/she log in. +## 基本路径 -Q: **How to allow a user to see multiple folder paths?** - -A: You can create a new [alias](alias.md) storage, add all the paths you need to show the user to the alias, and then point to the newly created alias storage in the user path -::: -::: zh-CN 用户登录时看到的根路径。 Q：**如何否允许一个用户可以看到多个文件夹路径?** A：可以新建一个[别名](alias.md)存储,将你需要给用户展示的路径都添加到别名，然后在用户路径这里指向新建的别名存储。 -::: - -## Permission { lang="en" } - -## 权限 { lang="zh-CN" } - -::: en - -- Can see hides: Can see the hides files and folders -- Access without password: Can access without password -- Add offline download tasks: Add offline download tasks - - ⚠️ Granting a user remote file read/write permissions also grants them the ability to access resources from the server's network context, including internal network addresses. Only grant this permission to fully trusted users. Internal network access resulting from improper permission assignment is not considered a security vulnerability. -- Mkdir or upload: Can make directory or upload files -- Rename: Can rename files and folders -- Move: Can move files and folders -- Copy: Can copy files and folders -- Delete: Can delete files and folders -- Webdav read: Can read files and folders with webdav -- Webdav manage: Can manage files and folders with webdav -- FTP read: Can read files and folders with FTP -- FTP manage: Can manage files and folders with FTP -- Read archives: Read the contents of the file in the compressed package - - After turning on this option, compressed package format files will be previewed by default (as shown in the figure below), which will consume some server traffic, but will not download them all. - - If you want to turn off the preferred preview of the compressed format, **Manage => Setting => Preview by default when opening archives**, this option is turned off, and the preference is the download mode -- Decompress: Decompress compressed package files online -  -  -::: -::: zh-CN +## 权限 - 可以看到隐藏：可以看到隐藏的文件和文件夹 - 无密码访问：无需密码即可访问 @@ -126,37 +59,11 @@ A：可以新建一个[别名](alias.md)存储,将你需要给用户展示的路   -::: - -## Disabled { lang="en" } +## 停用 -## 停用 { lang="zh-CN" } - -::: en -After checking, this user will stop using it and cannot log in. The guest account is disabled by default. If you want to enable the guest account, please close it manually. -::: -::: zh-CN 勾选后将停止使用此用户，无法登陆，游客账户默认停用，如果要启用游客账户请手动关闭停用。 -::: - -## Tips { lang="en" } -## Tips { lang="zh-CN" } - -::: en - -1. Are you worried that visitors can see all files? [**Click to see how to set it up here**](../../faq/why.md#how-do-i-set-it-so-that-visitors-can-only-see-the-content-after-logging-in) -2. **`Guest user is disabled, login please`**: In order to protect your OpenList security, the guest access permission is closed, if you need guest access, open it yourself - - OpenList Manage --> users --> `guest` --> **Disable** uncheck -3. Question about **`Copy/Upload`** - - If you upload (including offline download and upload) large files, or upload a lot of files (hundreds or thousands), it is not recommended to use OpenList to operate, please go to the corresponding network disk official website to operate directly -4. Non-admin users can manage offline download, copy, upload and other operations in the background - - OpenList needs to be upgraded to
@@ -324,8 +143,6 @@ The interfaces of different software vary, but the key is to correctly fill in t
-### Synology NAS (Add via File Station) { lang="en"}
-
-### 群晖 NAS (通过 File Station 添加) { lang="zh-CN" }
+### 群晖 NAS (通过 File Station 添加)
diff --git a/pages/guide/drivers/115.md b/pages/guide/drivers/115.md
index a62ab9c67..eaf61a63f 100644
--- a/pages/guide/drivers/115.md
+++ b/pages/guide/drivers/115.md
@@ -1,35 +1,22 @@
---
-title:
- en: 115 Cloud / Share
- zh-CN: 115 网盘 / 分享
-# This is the icon of the page
-icon: iconfont icon-state
-# This control sidebar order
top: 697
-# A page can have multiple categories
categories:
- guide
- drivers
---
+# 115 网盘 / 分享
+
-::: zh-CN
::: tip
[**115 官方 Open API**](115_open.md)
:::
-::: en
-::: tip
-[**115 Official Open API**](115_open.md)
-:::
-## 115 Cloud { lang="en" }
+## 115 个人网盘
-## 115 个人网盘 { lang="zh-CN" }
+### 视频教程(优先选择文字教程)
-### 视频教程(优先选择文字教程) { lang="zh-CN" }
-
-::: zh-CN
视频教程有可能因为时间关系导致部分视频内功能不可用或产生变化
所以推荐优先选择文字教程，当然如果你看不懂文字教程或者嫌麻烦也可以观看视频教程
@@ -38,48 +25,16 @@ categories:
-:::
-
-### Root folder ID { lang="en" }
-
-### 根文件夹 ID { lang="zh-CN" }
+### 根文件夹 ID
-::: en
-Open the official website of 115 Cloud and click the string behind the url when you click into the folder you want to set,
-such as ,
-which is `249163533602609229`
-:::
-
-::: zh-CN
打开 115 网盘官网，点击进入要设置的文件夹时点击 URL 中 `cid`后面的数字
如
这个文件夹的 `根文件夹ID` 即为 `249163533602609229`
-:::
-
-### Cookie获取方式 { lang="zh-CN" }
-
-### Cookie acquisition method { lang="en" }
-
-::: en
-The following message is displayed when mounting a 115 cloud. This is because 115 has removed the three client applications of `Windows, Mac, and Linux`.
-
-```json
-{
- "state": 0,
- "error": "登录失败，系统已下架！如果你有电脑端的使用需求，我们诚挚邀请你下载体验115产品专属客户端“115浏览器”或在线使用“115网页端(115.com)”，畅享智能高效云生活。",
- "errno": 0,
- "message": "登录失败，系统已下架！如果你有电脑端的使用需求，我们诚挚邀请你下载体验115产品专属客户端“115浏览器”或在线使用“115网页端(115.com)”，畅享智能高效云生活。",
- "code": 0
-}
-```
-
-The cookies you have obtained from these three devices cannot be used. Please obtain the cookies from other devices again to mount them.
-:::
+### Cookie获取方式
-::: zh-CN
挂载115云盘提示如下信息，是因为 115已经下架了 `Windows、Mac、Linux` 这三个客户端的应用
```json
@@ -94,64 +49,31 @@ The cookies you have obtained from these three devices cannot be used. Please ob
你获取的是这三个设备的Cookie自然就无法使用，请重新获取其它设备的Cookie进行挂载
-:::
-
-#### 1. QRCode scanning method login { lang="en" }
+#### 1. QRCode 扫码方式登录
-#### 1. QRCode 扫码方式登录 { lang="zh-CN" }
-
-::: en
-::: tip
-Still under active development, please stay tuned!
-:::
-
-::: zh-CN
::: tip
开发中, 教程暂未更新, 敬请期待!
:::
-#### 2. 手动抓取 Cookie 方式登录 { lang="zh-CN" }
-
-#### 2. Log in by manually grabbing Cookies { lang="en" }
+#### 2. 手动抓取 Cookie 方式登录
-::: en
-The `cookie` can be obtained from the browser with your 115 account logined, or packet capture.
-:::
-::: en
-::: tip
-Please note that cookies should not end with `;`.
-:::
-
-::: zh-CN
Cookie 可以在浏览器登录账号时从浏览器获取，如 Chrome 浏览器可以使用 [115ToAlist插件](https://github.com/yenkn/115-to-alist) 自动同步 Cookie：
也可通过抓包 115 应用获取，有效期比较长。
-:::
-::: zh-CN
::: tip
注意 Cookie 最后不要有`;`。
:::
-#### 3. 使用 Python 脚本获取 Cookie { lang="zh-CN" } - -#### 3. Get Cookies Using Python Script { lang="en" } +#### 3. 使用 Python 脚本获取 Cookie -::: en -Expand the detailed description to view the tutorial and script source code - -Source code from：[**https://gist.github.com/ChenyangGao/d26a592a0aeb13465511c885d5c7ad61**](https://gist.github.com/ChenyangGao/d26a592a0aeb13465511c885d5c7ad61) -::: - -::: zh-CN 展开详细说明进行查看教程和脚本源码 源码来自：[**https://gist.github.com/ChenyangGao/d26a592a0aeb13465511c885d5c7ad61**](https://gist.github.com/ChenyangGao/d26a592a0aeb13465511c885d5c7ad61) -::: ::: details View source @@ -318,32 +240,6 @@ if __name__ == "__main__": ::: -::: en - -1. You need to install [**Python 3.11.x**](https://www.python.org/downloads/) or above -2. If the QR code cannot be displayed properly in the `CMD` and `powershell` terminals, you can use the `-o` parameter to generate an image to scan the code, or you need to install an additional terminal - 1. Use the `-o` parameter to generate the image method and scan the QR code to confirm - - ````python - python main.py wechatmini -o - ``` - The devices that can be obtained are as follows. If you do not fill in the device, the default device on the `Web` side will be used - `Web`，`android`，`ios`，~~`linux`，`mac`，`windows`~~，`tv`，`alipaymini`，`wechatmini`，`qandroid` - ```` - - `alipaymini` and `wechatmini` They are Alipay Mini Program and WeChat Mini Program. - - **Windows、Mac、Linux should not be able to use it anymore. The official client was recently removed from the shelves.** - - It is recommended to use some devices that you do not commonly use, otherwise logging in will crowd out the previous ones. - *** - 2. Additional installation terminal - - Windows Store：**https://apps.microsoft.com/detail/9n0dx20hk701?rtc=1&hl=zh-cn&gl=CN** - - GitHub Download：**https://github.com/microsoft/terminal/releases** - 3. Other ways, solve it yourself - ---- - -Execute the command and obtain the QR code. Scan the QR code on the APP to obtain `Cookie` - -::: zh-CN - 1. 需要安装 [**Python 3.11.x**](https://www.python.org/downloads/) 以上版本 2. 如果二维码在 `CMD` 和 `powershell` 两个终端无法显示正常，可以使用`-o`参数生成图片的方式来扫码，或者需要额外安装一个终端 1. 使用 `-o` 参数，生成图片方式然后扫码确认 @@ -365,11 +261,8 @@ Execute the command and obtain the QR code. Scan the QR code on the APP to obtai --- 执行命令，获取二维码 APP扫码获取 `Cookie` -::: - -##### 3.1. Direct Execution { lang="en" } -##### 3.1.直接执行 { lang="zh-CN" } +##### 3.1.直接执行 ```shell PS C:\Users\233\Desktop\115> python --version @@ -391,16 +284,9 @@ PS C:\Users\233\Desktop\115> python main.py wechatmini ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ ``` -::: en -Execute the command directly. The QR code will appear in the terminal for display. -::: -::: zh-CN 直接执行 二维码会出现在终端中进行显示 -::: - -##### 3.2. Using the -o parameter { lang="en" } -##### 3.2. 使用-o参数 { lang="zh-CN" } +##### 3.2. 使用-o参数 ```bash PS C:\Users\233\Desktop\115> python --version @@ -408,29 +294,9 @@ Python 3.12.2 PS C:\Users\233\Desktop\115> python main.py wechatmini -o ``` -::: en -After using the `-o` parameter, a QR code image will pop up automatically -::: - -::: zh-CN 使用 `-o` 参数后会自动弹出一张二维码图片 -::: - -### 秒传 { lang="zh-CN" } - -### Rapid upload { lang="en" } - -::: en -- **v.3.27.0** version Enhanced Rapid upload: You can directly upload files with `Alibaba Cloud Disk Open` by copying - - The premise is to upload the file from 115 Rapid upload to Alibaba Cloud Disk Open, the file already exists in Alibaba Cloud Disk Open, otherwise it is a normal copy task. - - If you want to transfer 115 cloud disk files to Alibaba Cloud Disk in seconds, you need to turn on the Rapid upload option of Alibaba Cloud Disk, otherwise it will be uploaded in normal mode. - If you want to upload files using Miaochuan, it is recommended to build an OpenList locally on your home computer and add a `local storage` and `115 cloud disk` to copy Miaochuan to save resources. -
- -::: - -::: zh-CN +### 秒传 - **v.3.27.0** 版本 增强秒传：可以直接通过复制方式来和`阿里云盘Open`进行相互秒传文件 - 前提是要从115秒传到阿里云盘Open的文件，阿里云盘Open已经存在，否则就是正常复制任务。 @@ -438,29 +304,8 @@ After using the `-o` parameter, a QR code image will pop up automatically 如果要使用秒传来上传文件建议在自己家用电脑本地搭建一个OpenList添加一个`本地存储`和`115云盘`进行复制秒传这样节省资源。
-::: +### 离线下载 -### 离线下载 { lang="zh-CN" } - -### Offline Download { lang="en" } - -::: en -**v3.37.0** and above versions support calling `115 Cloud` offline download function in OpenList -Select in the lower right corner and select `115 Cloud` for offline download options - -- Support: `magnet`, `http`, `ed2k` links - Only 115 Cloud is supported for offline download. If it is not 115 Cloud, the following error message will be displayed, Although the offline download prompt was successfully added, an error will be prompted in the background. -- unsupported storage driver for offline download, only 115 Cloud is supported -  -- Some tips for using 115 offline downloads: - 1. Out of sync problems may occur (manual refresh in the lower right corner ) - 2. Currently, when the download is successful, completed tasks in the offline list are deleted. - 3. 115 Task URLs that are already in the offline list cannot be added again. -
- -::: - -::: zh-CN **v3.37.0** 及以上版本支持在OpenList调用115离线下载功能 右下角选择 离线下载选项选择`115 Cloud` @@ -474,35 +319,7 @@ Select -::: - -### 默认使用的下载方式 { lang="zh-CN" } - -### The default download method used { lang="en" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -523,86 +340,32 @@ flowchart TB click c1 "../drivers/common.html#webdav-策略" ``` -::: +## 115网盘分享 -## 115 Share { lang="en" } - -## 115网盘分享 { lang="zh-CN" } - -::: zh-CN  `分享链接ID`1 和 `分享链接提取码`2 分别如何获取一目了然 -::: -::: en - - -`Sharing link ID`1 and `Sharing link extraction code`2 How to obtain them respectively is clear at a glance. -::: - -### Root folder ID { lang="en" } - -### 根文件夹ID { lang="zh-CN" } - -::: en -The default is empty and the entire directory file is mounted. - -The folder IDs are the root folder ID and the subfolder ID respectively. The following demonstrates how to obtain the `shared root folder directory ID`1 and `other subfolder directory ID`2 respectively. -::: - -#### 1. shared root folder directory ID { lang="en" } - -#### 1. 分享根文件夹目录ID {lang="zh-CN"} +### 根文件夹ID -::: en -Open developer mode (F12) and clear all requests first. Before we enter the folder, clear all requests first. +#### 1. 分享根文件夹目录ID -Let's click on the root folder to enter. There will be a new request on the right, and then select `Load` to see the ID (cid) of our folder. - - -::: -::: zh-CN 打开开发者模式(F12)先将请求全部清空，我们进入文件夹，先将全部请求清空， 我们再点击根文件夹进入，右侧会有一个新的请求，然后选择`载荷`就能看到我们的这个文件夹的ID (cid)  -::: - -#### 2. other subfolder directory ID { lang="en" } -#### 2. 其它子文件夹目录ID { lang="zh-CN" } +#### 2. 其它子文件夹目录ID -::: zh-CN 打开开发者模式(F12)先将请求全部清空，我们进入文件夹，先将全部请求清空， 右侧会有一个新的请求，然后选择`预览` 然后进行展开查看，就可以看到其它子文件夹的ID (cid)  -::: -::: en -Open developer mode (F12) and clear all requests first. Before we enter the folder, clear all requests first. - -There will be a new request on the right, then select `Preview` and expand it to see the IDs (cid) of other subfolders. - - -::: -### 错误提示 { lang="zh-CN" } +### 错误提示 -### Error Tips { lang="en" } - -::: en -For example, the 115 sharing link shown in the picture below has expired, but the sharing link can still be opened. - - - -But when adding and saving, the following error code will appear: - -`Failed init storage but storage is already created: failed init storage: failed to get share snap: json: cannot unmarshal number into Go struct field .data.shareinfo.share_state of type string ` -::: -::: zh-CN 例如下图所示的115分享链接分享过期，但是分享链接还能打开  @@ -610,36 +373,8 @@ But when adding and saving, the following error code will appear: 但是在添加保存时候会出现如下错误码： `Failed init storage but storage is already created: failed init storage: failed to get share snap: json: cannot unmarshal number into Go struct field .data.shareinfo.share_state of type string ` -::: - -### 默认使用的下载方式 { lang="zh-CN" } -### The default download method used { lang="en" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: - -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -659,5 +394,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/115_open.md b/pages/guide/drivers/115_open.md index b92320c94..bb8a531e7 100644 --- a/pages/guide/drivers/115_open.md +++ b/pages/guide/drivers/115_open.md @@ -1,122 +1,37 @@ --- -title: - en: 115 Open - zh-CN: 115 开放平台 -# This is the icon of the page -icon: iconfont icon-state -# This control sidebar order top: 698 -# A page can have multiple categories categories: - guide - drivers --- -::: en -::: tip -Developed with the official [**115 Open Platform API**](https://open.115.com) -::: -::: zh-CN +# 115 开放平台 + ::: tip 使用官方 [**115开放平台 API**](https://open.115.com) 开发 ::: -## 1. Necessary Conditions { lang="en" } - -## 1. 必要条件 { lang="zh-CN" } +## 1. 必要条件 -::: en -An **115** account is required. -::: -::: en -::: warning Note -The speed and stability are related to the local network environment, the network environment of the 115 server, and the performance of the machine running OpenList. -::: - -::: zh-CN 必须有 **115** 的帐号 -::: -::: zh-CN + ::: warning 注意事项 速度与稳定性与本地网络环境，115 服务器的网络环境以及 OpenList 的运行机器的性能有关 ::: -## 2. Preparation for Access { lang="en" } - -## 2. 准备接入 { lang="zh-CN" } +## 2. 准备接入 -### 2.1. Register an Application on the Open Platform (optional; no need to create if using the built-in key pair of OpenList/public welfare server/self-built server) { lang="en" } +### 2.1. 开放平台注册应用（可选，如果使用OpenList/公益服务器/自建服务器内置的密钥对，则不用创建） -### 2.1. 开放平台注册应用（可选，如果使用OpenList/公益服务器/自建服务器内置的密钥对，则不用创建） { lang="zh-CN" } - -::: en -::: tip -Please register the application according to the requirements of the 115 Open Platform. -::: -::: en -Open Platform address: [115 Open Platform: https://open.115.com](https://open.115.com) -::: -::: zh-CN ::: tip 请根据115 开放平台的要求注册应用 ::: -::: zh-CN -开放平台地址: [115 开放平台:https://open.115.com ](https://open.115.com) -::: - -### 2.2. Obtain Tokens { lang="en" } - -### 2.2. 获取令牌 { lang="zh-CN" } - -::: en - -1. Visit [api.oplist.org](https://api.oplist.org) **⚠️ If using a public welfare server/self-built server, visit the address of the public welfare server/self-built server**. - -2. Select **115 Network Disk Verification** from the drop-down box. - -  - -  - -3. If you are using the built-in key pair of `OpenList (or public welfare server/self-built server)` (i.e., you do not have application information from the 115 Open Platform), please configure according to `3.1`, `3.2`, and `3.3`: - - 3.1. Check `Use parameters provided by OpenList`. - - 3.2. Leave both `Client ID (ClientID/AppID)` and `Application Secret (AppKey/Secret)` blank. - - 3.3. Click the `Get Token` button. - -  -  - -4. If you are using your own created OAuth client ID and secret, please configure according to `4.1`, `4.2`, and `4.3`: - - 4.1. Do not check `Use parameters provided by OpenList`. - - 4.2. Enter your `AppId` in `Client ID` and your `AppSecret` in `Application Secret`. - - 4.3. Click the `Get Token` button. - -  - -  - -5. In the pop-up window, log in to your 115 account and authorize OpenList to access your 115 network disk. - -  - -6. After successful authorization, the page will display your `Access Token` and `Refresh Token`. Please copy and save these two tokens. - -  - -  - -::: +开放平台地址: [115 开放平台:https://open.115.com ](https://open.115.com) -::: zh-CN +### 2.2. 获取令牌 1. 访问[api.oplist.org](https://api.oplist.org) **⚠️如果使用公益服务器/自建服务器，请访问公益服务器/自建服务器的地址** @@ -160,30 +75,12 @@ Open Platform address: [115 Open Platform: https://open.115.com](https://open.11  -::: - -## 3. Adding 115 Network Disk to OpenList { lang="en" } - -## 3. 在OpenList中添加115网盘 { lang="zh-CN" } +## 3. 在OpenList中添加115网盘 -### 3.1. Configuration Instructions { lang="en" } +### 3.1. 配置说明 -### 3.1. 配置说明 { lang="zh-CN" } +#### 3.1.1. 根文件夹 ID -#### 3.1.1. Root Folder ID { lang="en" } - -#### 3.1.1. 根文件夹 ID { lang="zh-CN" } - -::: en -The default root directory ID is: `0` - -Open the 115 network disk official website, and when clicking to enter the folder to be set, click the number after `cid` in the URL. - -For example,
-
-The `root folder ID` of this folder is `249163533602609229`.
-:::
-::: zh-CN
默认根目录ID为：`0`
打开 115 网盘官网，点击进入要设置的文件夹时点击 URL 中 `cid`后面的数字
@@ -191,35 +88,8 @@ The `root folder ID` of this folder is `249163533602609229`.
如
这个文件夹的 `根文件夹ID` 即为 `249163533602609229`
-::: -### 3.2. Start Adding { lang="en" } - -### 3.2. 开始添加 { lang="zh-CN" } - -::: en - -1. Open the management interface of OpenList and click `Storage` in the left menu. - -2. On the storage list page, click the `Add Storage` button in the upper right corner. - -3. Select the driver as `115 Open Platform`. - -  - -  - -4. Enter the mounting path, such as: `115`. - -5. Enter the root folder ID obtained above in `Root Folder ID` (please refer to [3.1.1. Root Folder ID](#_3-1-1-root-folder-id)). - -6. Enter the obtained `Refresh Token` and `Access Token` in the refresh token (if not obtained, please refer to [2. Preparation for Access](#_2-preparation-for-access)). - - 115's token refresh mechanism does not require AppKey and has IP-based rate limiting, so it is implemented using [local logic](https://github.com/OpenListTeam/115-sdk-go). - -7. Click the `Add` button to complete adding the 115 network disk. - -::: -::: zh-CN +### 3.2. 开始添加 1. 打开 OpenList 的管理界面，点击左侧菜单中的`存储`。 @@ -240,24 +110,7 @@ The `root folder ID` of this folder is `249163533602609229`. 7. 点击`添加`按钮，完成115网盘的添加。 -::: - -### 3.3. Method for Refreshing Access Token { lang="en" } - -### 3.3. 当前AccessToken刷新的方式 { lang="zh-CN" } - -::: en - -```mermaid -sequenceDiagram - participant OpenList - participant 115 - OpenList->>115: Post refresh_token - 115->>OpenList: Get new access_token and refresh_token -``` - -::: -::: zh-CN +### 3.3. 当前AccessToken刷新的方式 ```mermaid sequenceDiagram @@ -267,26 +120,8 @@ sequenceDiagram 115服务器->>OpenList: 返回新的访问令牌+刷新令牌 ``` -## 4. Notes { lang="en" } - -## 4. 注意事项 { lang="zh-CN" } - -::: en -::: warning Handling Method for Token Leakage -If the Token is accidentally leaked, you can go to the 115 device login management to解除应用授权 (revoke application authorization). +## 4. 注意事项 -- 115 APP: [iOS, Android] versions need to be ≥ 35.11.0 -- 115 Web端: [https://115.com/?mode=device_manage](https://115.com/?mode=device_manage) - - When it expires, the following content will be prompted: - - ```json - failed get objs: failed to list objs: code: 40140116, message: no auth - ``` - -An account can obtain two `Refresh tokens` in the same application. After the third acquisition, the first obtained `Refresh token` will expire. Using the first `Refresh token` will prompt the above error. -::: -::: zh-CN ::: warning Token 泄漏后处理方法 如果不小心泄漏了 Token，可以前往115设备登录管理解除应用授权 @@ -302,61 +137,19 @@ An account can obtain two `Refresh tokens` in the same application. After the th 一个帐号可以在同一个应用获取两次`Refresh token`，第三次获取后第一次获取到的`Refresh token`就会失效，使用第一个`Refresh token`会提示上面的错误 ::: -## 5. Using Other APP IDs to Obtain Refresh Tokens (Not Yet Implemented) { lang="en" } - -## 5. 使用其他 APP ID 获取刷新令牌（尚未实现） { lang="zh-CN" } - -::: en -::: tip -Under development, the tutorial has not been updated yet. Stay tuned! -::: +## 5. 使用其他 APP ID 获取刷新令牌（尚未实现） -::: zh-CN ::: tip 开发中, 教程暂未更新, 敬请期待! ::: -## 6. Mobile QR Code Authorization PKCE Mode (Not Yet Implemented) { lang="en" } +## 6. 手机扫码授权PKCE模式（尚未实现） -## 6. 手机扫码授权PKCE模式（尚未实现） { lang="zh-CN" } - -::: en -::: tip -Under development, the tutorial has not been updated yet. Stay tuned! -::: - -::: zh-CN ::: tip 开发中, 教程暂未更新, 敬请期待! ::: -## 7. Default Download Method Used { lang="en" } - -## 7. 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +## 7. 默认使用的下载方式 ```mermaid --- @@ -376,5 +169,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/123.md b/pages/guide/drivers/123.md index 8d1a897ab..fe3e8f247 100644 --- a/pages/guide/drivers/123.md +++ b/pages/guide/drivers/123.md @@ -1,27 +1,14 @@ --- -title: - en: 123 Pan / Share / Link - zh-CN: 123 网盘 / 分享 / 直链 -# This is the icon of the page -icon: iconfont icon-state -# This control sidebar order top: 695 -# A page can have multiple categories categories: - guide - drivers --- - - -::: en -::: warning -123 Cloud Disk has implemented anti-leech measures for this **reverse-engineered driver**. To avoid unnecessary disputes, it is recommended that users choose the more standard 123 Open Platform driver. If you continue to use this driver, you need to enable a **local proxy** to prevent anti-leech detection. +# 123 网盘 / 分享 / 直链 -- [123 Open Platform](./123_open.md) + -::: -::: zh-CN ::: warning 123云盘对于该**逆向驱动**已经采取防盗链措施，为了避免不必要的纠纷，建议用户选用更为规范的123开放平台驱动。如果继续使用该驱动，需要开启**本地代理**以防止反盗链检测 @@ -29,32 +16,10 @@ categories: ::: -## Personal { lang="en" } - -## 个人 { lang="zh-CN" } - -::: en -Free user 1G traffic download, unlimited upload, multi-IP sharing is prohibited -::: +## 个人 -::: zh-CN 免费用户 1G 流量下载，上传不限制，禁止多IP共享使用 -::: -::: en -::: warning - -```json -failed get objs: failed to list objs:当前账号存在安全风险，请使用短信验证码或者微信进行登录。 -``` - -solution: - -- This is because the 123 cloud disk officially prohibits the mounting on strange devices, If you are mounted locally, `or` Windows Server server mount `to open the 123 cloud disk web page to log in or modify a password once - -::: - -::: zh-CN ::: warning 挂载提示： @@ -68,113 +33,39 @@ failed get objs: failed to list objs:当前账号存在安全风险，请使用 ::: -::: en -https://www.123pan.com/ - -Just fill in the account password. -::: - -::: zh-CN https://www.123pan.com/ 只需填写账户密码即可。 -::: - -### 用户名 { lang="zh-CN" } - -### Username { lang="en" } +### 用户名 -::: en -The mobile phone number used to log in -::: -::: zh-CN 用于登录的手机号码 -::: - -### 密码 { lang="zh-CN" } -### Password { lang="en" } +### 密码 -::: en -The password used to log in -::: -::: zh-CN 用于登录的密码 -::: -### 根文件夹 ID { lang="zh-CN" } +### 根文件夹 ID -### Root folder file_id { lang="en" } - -::: en -Enter the folder you want to mount, the last string of the official website URL, such as: -::: -::: zh-CN 输入要挂载的文件夹，官网 URL 的最后一串，如： -:::  -### 使用建议 { lang="zh-CN" } - -### Recommendations { lang="en" } - -::: en - -- It seems that the 123 API has a limited number of loads each time, so if you load hundreds of files in a folder at one time, an error may be reported -- It is recommended to A useful approach is not to put too many sub-items in the same folder. - -::: - -::: zh-CN +### 使用建议 - 貌似 123 的 API 每次加载的数量有限，故如果你一个文件夹内一次性加载几百个文件，可能会报错 - 建议不用在每个文件夹内放置太多子文件/文件夹 -::: - -## 直链 { lang="zh-CN" } - -## Link { lang="en" } +## 直链 -::: en -only adapted to the authentication function, the link also needs to be filled in by yourself, like [UrlTree](/guide/drivers/url_tree), fill in the direct link copied in 123 direct link. -::: -::: zh-CN 仅适配了鉴权功能，链接也需要自己填写，像[地址树一样](/guide/drivers/url_tree.md)，把在 123 直链复制的直链填写进去即可 -::: - -::: en -::: danger Please read this reminder carefully -Since 123 Cloud Disk Direct Link is a paid service with a storage quota, if you decide to add more storage, please ensure you set up passwords, metadata, and other protective measures to prevent malicious traffic. - -After configuring these settings, test them in incognito mode to confirm everything is working correctly. If you fail to implement adequate anti-theft measures and experience malicious traffic overload, you will be held responsible for the consequences. -::: - -::: zh-CN ::: danger 请仔细阅读此提醒 由于123云盘直链是付费服务并有限制额度，如果您添加123直链存储，请及时设置密码、元信息等安全措施，以防止恶意刷流量。 设置完成后，请先在无痕模式下进行测试，确保防盗措施已正确设置。如未设置妥当，导致被恶意刷流量，后果自负。 ::: -::: en -First open **`123 Cloud Disk Direct Link Management`**: **https://www.123pan.com/DirectLink** Set an authentication key in the lower right corner, and then turn on the authentication status switch - - - -- Open Settings 123 Cloud Disk Settings: **https://www.123pan.com/Setting** and find the account ID [`1` label in the picture below] -- How to activate direct link? (You need to activate membership to use it) - - Find the folder you want to open, right-click on `Enable Direct Link Space`, and after opening it, you will see a link icon in the folder [Tag `2` in the picture below] -- How to get a direct link to a file? [Tag `3` in the picture below] - - Enter the folder that has 'enabled direct link space', find the file you need to obtain, right-click 'Get direct link', and fill in the OpenList configuration after obtaining it. -  - -::: - -::: zh-CN 首先打开 **`123云盘直链管理`**: **https://www.123pan.com/DirectLink** 右下角自己设置一个鉴权秘钥，然后打开鉴权状态开关  @@ -186,42 +77,7 @@ First open **`123 Cloud Disk Direct Link Management`**: **https://www.123pan.com - 进入已经`启用直链空间`的文件夹，找到需要获取的文件右键`获取直链链接`，获取到后填写到OpenList配置內  -::: - -### 填写示例 { lang="zh-CN" } - -### Fill in example { lang="en" } - -::: en - -- **Origin urls**：Fill in the direct link to the files we copied one by one - - It supports creating different folders like [UrlTree](/guide/drivers/url_tree), and supports filling in the file size and modification time (four options are provided for use, like the UrlTree filling, refer to the second example of the picture below) - - File size unit: `B` bytes. For example, if you want to write a 1MB file, it is 1048567 bytes. You can search for the specific byte conversion in your browser (you can leave it blank). - - File modification time: It is `Unix timestamp`. You can search in the browser for the specific conversion (you can leave it blank). - - Fill in the format: - - ```txt - [FileSize:][Modified:]URL - 127451136:1694101621:https://vip.123pan.cn/1812xxx499/123-link-Test/linuxqq_3.2.0-16736_mips64el.deb - [FileSize:]URL - 134847488:https://vip.123pan.cn/1812xxx499/123-link-Test/linuxqq_3.2.0-16736_loong64.deb - [Modified:]URL - 1694101621:https://vip.123pan.cn/1812xxx499/123-link-Test/linuxqq_3.2.0-16736_arm64.AppImage - URL - https://vip.123pan.cn/1812xxx499/123-link-Test/linuxqq_3.2.0-16736_x86_64.AppImage - ``` - -- **Private key**： - - You can set up the direct link management page yourself and turn it on. Please turn it on. -- **Uid**： - - Account ID in the account settings page -- **Valid duration**： - - The file direct link validity period, in minutes, is filled in by default to 30 minutes - -::: - -::: zh-CN +### 填写示例 - **来源链接**：填写我们一条一条复制的文件直链 - 支持像[地址数](/guide/drivers/url_tree)那样新建不同文件夹，支持填写文件大小和修改时间（提供四种方案可以使用，像地址树填写参考下方图片的图二示例） @@ -248,62 +104,24 @@ First open **`123 Cloud Disk Direct Link Management`**: **https://www.123pan.com - **有效期**： - 文件直链有效期，单位为分钟，默认填充为30分钟 -::: -   -## 分享 { lang="zh-CN" } - -## Share { lang="en" } +## 分享 -::: en -Fill in the driver's **`share key`** and optional **`share password`** (if there is a password, you need to fill in), the root folder ID defaults to `0` to display all files -::: -::: zh-CN 填写驱动的 **`分享key`** 和选填 **`分享密码`** (如果有密码需要填写)，根文件夹ID默认为`0`显示全部文件 -::: - -### 填写示例 { lang="zh-CN" } -### Fill in the example { lang="en" } +### 填写示例 -::: en  -::: -::: zh-CN - -::: - -### Share Password { lang="en" } -### 分享密码 { lang="zh-CN" } +### 分享密码 -::: en -Fill in if you have it, don't if you don't -::: -::: zh-CN 有就填写，没有就不用 -::: - -### Root folder file_id { lang="en" } -### 根文件夹 ID { lang="zh-CN" } +### 根文件夹 ID -::: en -The ID of the root directory of the shared link is `0`, displaying all files - -If you only want to display a certain folder, open the developer mode (F12) to clear all requests (maybe 123 prohibits debug debugging, you need to close this by yourself to continue) - -Find the request on the right side of the picture in the upper-level directory request of the directory you want to display, then click `Response`, find the format button `{}` below and format it, and you can see the relevant directory ID. - -If you are not sure whether the directory ID is correct or not, there is a directory name under the directory ID - - - -::: -::: zh-CN 分享链接根目录ID是`0`，展示全部文件 如果只想展示某个文件夹，打开开发者模式(F12)清空全部请求（可能123禁止debug调试需要自己关闭这个才能继续） @@ -314,36 +132,7 @@ If you are not sure whether the directory ID is correct or not, there is a direc  -::: - -## The default download method used { lang="en" } - -## 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: - -::: zh-CN +## 默认使用的下载方式 ```mermaid --- @@ -363,5 +152,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/123_open.md b/pages/guide/drivers/123_open.md index 68ed98c2e..d94ff33f9 100644 --- a/pages/guide/drivers/123_open.md +++ b/pages/guide/drivers/123_open.md @@ -1,33 +1,18 @@ --- -title: - en: 123 Open - zh-CN: 123 开放平台 -# This is the icon of the page -icon: iconfont icon-state -# This control sidebar order top: 696 -# A page can have multiple categories categories: - guide - drivers --- +# 123 开放平台 + https://www.123pan.com/developer -## 1. Developer Application { lang="en" } - -## 1. 申请开发者 { lang="zh-CN" } - -::: en -::: warning -This driver uses the [developer authorization mode](https://123yunpan.yuque.com/org-wiki-123yunpan-muaork/cr6ced/hpengmyg32blkbg8), which grants direct management access to the cloud drive associated with the provided public/private key pair, , so you **must use your client id and client secret**. - -The acquired token counts as a login device +## 1. 申请开发者 -::: -::: zh-CN ::: warning 该驱动使用的是[开发者授权模式](https://123yunpan.yuque.com/org-wiki-123yunpan-muaork/cr6ced/hpengmyg32blkbg8),将会直接获得该密钥对应网盘的管理权限，所以**必须使用自己的密钥**。 @@ -35,21 +20,6 @@ The acquired token counts as a login device ::: -::: en - -**Application Method**: Visit the [123 Open Platform Official Website](https://www.123pan.com/developer), read the Developer Agreement, fill in the required fields marked with `*`, and apply for the `client_id` and `client_secret`.Typically, after your application is approved the keys will be sent to your email **remember to check your spam folder, and please keep the keys sent by email safe**. - -1. Sign the Developer Agreement - -2. Fill out the application materials - -3. Wait for the review notification - -**Reference Tutorial**: [OpenListTeam/discussions#55](https://github.com/orgs/OpenListTeam/discussions/55) - -::: -::: zh-CN - **申请方式**：访问[123开放平台官网](https://www.123pan.com/developer)，阅读开发者协议，填写对应必填项`*`信息，申请`client_id`和`client_secret`，一般来说申请通过后会发送至邮箱，记得检查邮件的垃圾箱，**请保管好通过邮件发送回来的密钥**。 1. 签署开发者协议 @@ -60,31 +30,7 @@ The acquired token counts as a login device **参考教程**：[OpenListTeam/discussions#55](https://github.com/orgs/OpenListTeam/discussions/55) -::: - -### 2. Get UID { lang="en" } - -### 2. 获取 UID { lang="zh-CN" } - -::: en - -The method to obtain the "Cloud Drive UID" required during the application process is as follows: - -1. **Log in to the 123 Cloud Drive web platform** - - Visit the 123 Cloud Drive official website and log in with your account (phone number). - -2. **Go to the "Settings" page** - - After logging in, click on the profile picture or username at the top right, and select "Settings" (or directly visit: ).
-
-3. **Find the "Account ID"**
-
- In the "Account Settings" or "Security Settings" section, locate the "Account ID," which is your "Cloud Drive UID." Copy it and paste it into the application form.
-
-:::
-
-::: zh-CN
+### 2. 获取 UID
填写申请过程中需要填入的“云盘UID”一项获取方式如下：
@@ -100,61 +46,22 @@ The method to obtain the "Cloud Drive UID" required during the application proce
在「账号设置」或「安全设置」栏目中，找到“个人账号ID”，该ID即为您的“云盘UID”，复制并填入即可。
-:::
-
-## 4. 在 OpenList 中添加 { lang="zh-CN" }
-
-## 4. Add in OpenList { lang="en" }
+## 4. 在 OpenList 中添加
-### 刷新令牌 { lang="zh-CN" }
+### 刷新令牌
-### RefreshToken { lang="en" }
-
-::: zh-CN
**留空**
-:::
-::: en
-**keep it empty**
-:::
-### 客户端ID { lang="zh-CN" }
+### 客户端ID
-### Client ID { lang="en" }
-
-::: zh-CN
填入你的客户端ID
-:::
-::: en
-Enter your client ID
-:::
-
-### 客户端密钥 { lang="zh-CN" }
-### Client Secret { lang="en" }
+### 客户端密钥
-::: zh-CN
填入你的客户端密钥
-:::
-::: en
-Enter your client secret
-:::
-
-### Root Folder ID { lang="en" }
-### 根文件夹 ID { lang="zh-CN" }
+### 根文件夹 ID
-::: en
-The default root directory ID is: `0`
-
-Open the official website of 123 Cloud Drive, navigate to the folder you want to set, and then click the number following `homeFilePath` in the URL.
-
-For example,
-
-API queries can also be used
-
-The `root folder ID` of this folder is `123456`.
-:::
-::: zh-CN
默认根目录ID为：`0`
打开 123 网盘官网，点击进入要设置的文件夹时点击 URL 中 `homeFilePath`后面的数字
@@ -167,39 +74,16 @@ The `root folder ID` of this folder is `123456`.
亦可右键文件夹，选择 `复制文件夹ID`
-:::
-
-### Direct Link { lang="en" }
-
-### 使用直链 { lang="zh-CN" }
+### 使用直链
-::: en
-Disabled by default; returns standard download links. When enabled, returns CDN direct links, which require VIP access and will consume direct link traffic quota.
-
-Users must manually enable direct link space: Go to the 123 Cloud Drive official website, right-click a folder under the **root directory**, and select `Enable Direct Link Space (VIP)`.
-:::
-::: zh-CN
默认禁用，返回普通下载链接。启用后，返回 CDN 直链，需要开通 VIP，会消耗直链流量包。
需要用户手动启用直链空间，方法：进入 123 网盘官网，右键**根目录**下的文件夹，选择 `启用直链空间（VIP）`。
-:::
-### Direct Link Private Key { lang="en" }
-
-### 直链鉴权密钥 { lang="zh-CN" }
-
-::: en
-Prerequisite: Enable `Direct Link`.
-
-Leave empty to disable direct link authentication and return permanent direct links.
-
-To prevent your site resources from being maliciously downloaded or stolen, you can configure an "Authentication Key" in 123 Cloud Drive's **Direct Link** → **Basic Function Configuration** → **URL Authentication**, and then set **Authentication Status** to **Enabled**.
+### 直链鉴权密钥
-After entering the key, the obtained direct links will automatically include authentication parameters.
-:::
-::: zh-CN
前置条件：开启 `使用直链`。
默认为空，代表不启用直链鉴权，返回永久直链。
@@ -207,53 +91,16 @@ After entering the key, the obtained direct links will automatically include aut
为防止站点资源被恶意下载盗用，您可以在 123 云盘的 **直链** -> **基础功能配置** -> **URL鉴权** 中配置 **鉴权密钥**，然后将 **鉴权状态** 设为 **启用**。
填写密钥后，获取到的直链会自动加上鉴权参数。
-:::
-### Direct Link Valid Duration { lang="en" }
-
-### 直链鉴权有效期 { lang="zh-CN" }
+### 直链鉴权有效期
-::: en
-Prerequisite: Enable `Direct Link` and configure the `Direct Link Private Key`.
-
-Used to generate the expiration timestamp in the direct link authentication parameters.
-:::
-::: zh-CN
前置条件：开启 `使用直链`，配置 `直链鉴权密钥`。
用于生成直链鉴权参数中的过期时间戳。
-:::
-
-## The default download method used { lang="en" }
-
-## 默认使用的下载方式 { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[local proxy]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[302]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-::: zh-CN
+## 默认使用的下载方式
```mermaid
---
@@ -273,5 +120,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/139.md b/pages/guide/drivers/139.md
index 2e6970327..7acb94f51 100644
--- a/pages/guide/drivers/139.md
+++ b/pages/guide/drivers/139.md
@@ -1,73 +1,26 @@
---
-title:
- en: 139Yun
- zh-CN: 中国移动云盘
-# This is the icon of the page
-icon: iconfont icon-state
-# This control sidebar order
top: 692
-# A page can have multiple categories
categories:
- guide
- drivers
---
-
+# 中国移动云盘
-::: en
-Cloud disk address: ****
-:::
-
-:::zh-CN
@@ -370,21 +152,7 @@ Although the video is for V2, the method for obtaining folder ID and Cloud ID is
****
:::
-### OpenList fill in examples { lang="en" }
-
-### OpenList 挂载填写示例 { lang="zh-CN" }
-
-::: en
-
-- `Authorization`: fill in only the content after `Basic `.
-- New personal folder ID: enter the target folder first, then use the current `currentCatalogID`.
-
-
-
-
-:::
-
-::: zh-CN
+### OpenList 挂载填写示例
- “授权”：只填写 `Basic ` 后面的内容。
- 新的个人盘文件夹 ID：先进入目标文件夹，再使用当前的 `currentCatalogID`。
@@ -392,83 +160,28 @@ Although the video is for V2, the method for obtaining folder ID and Cloud ID is
-:::
-
-## Share mount { lang="en" }
-## 分享挂载 { lang="zh-CN" }
-
-::: en
-The `share` type allows you to mount shared content from other 139Yun users. You need a valid authorization to access download APIs.
-:::
+## 分享挂载
-::: zh-CN
`share`（分享挂载）类型允许你挂载其他移动云盘用户分享的内容。访问下载接口仍需要有效的鉴权。
-:::
### LinkID format
### LinkID 格式
-::: en
-`LinkID` supports the following formats:
-
-- Single share: directly enter the share link ID
-- Password-protected share: `link_id#password`
-- Multiple shares: separate multiple entries with commas or new lines. For example: `share_a,share_b,share_c` or `share_a#pass1,share_b`
-
-:::
-
-::: zh-CN
`LinkID`（分享链接 ID）支持以下格式：
- 单个分享：直接填写分享链接 ID
- 加密分享：`link_id#password`（链接 ID 后加 `#` 和密码）
- 多个分享：多个分享用逗号或换行分隔，例如：`share_a,share_b,share_c` 或 `share_a#密码1,share_b`
-:::
-
-### Get share link ID { lang="en" }
-
-### 获取分享链接 ID { lang="zh-CN" }
-
-::: en
-
-1. Open the share link in your browser, e.g. `https://yun.139.com/w/#/share/xxxxx`
-2. The path segment after `/share/` is the share link ID (e.g. `xxxxx`)
-3. If the share is password-protected, append `#password` after the link ID
-
-:::
-
-::: zh-CN
+### 获取分享链接 ID
1. 在浏览器中打开分享链接，例如 `https://yun.139.com/w/#/share/xxxxx`
2. 链接中 `/share/` 后面的路径段就是分享链接 ID（如上例中的 `xxxxx`）
3. 如果分享有密码保护，在链接 ID 后加 `#密码`
-:::
-
-### Configuration { lang="en" }
-
-### 配置说明 { lang="zh-CN" }
-
-::: en
-
-- **Type**: `share`
-- **LinkID**: one or more share link IDs (see format above)
-- **Authorization** or **MailCookies + Username + Password**: required for authentication (same as other types)
-- **Root folder ID**: not used for share type. The share link ID in `LinkID` determines the mounted content.
-- **Cloud ID**: leave empty
-
-Notes:
-
-- Upload operations are not supported for the `share` type.
-- When mounting multiple shares, the root directory shows each share as a separate folder.
-- `${data_path}` resolves to the share root for path-based operations.
-
-:::
-
-::: zh-CN
+### 配置说明
- **类型**：`share`（分享挂载）
- **LinkID**：一个或多个分享链接 ID（格式见上方）
@@ -482,37 +195,8 @@ Notes:
- 挂载多个分享时，根目录会以文件夹形式展示每个分享的内容。
- path 相关操作会以分享根目录作为 `${data_path}`。
-:::
+## 下载方式
-## Download method { lang="en" }
-
-## 下载方式 { lang="zh-CN" }
-
-::: en
-The default download method is 302 redirection. If a player such as PotPlayer cannot play through 302, switch that mount to proxy mode or mount it through WebDAV with `WebDAV Native Proxy`.
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[302]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[local proxy]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-
-::: zh-CN
默认下载方式是 302 跳转。如果 PotPlayer 等播放器无法通过 302 播放，可以将该挂载切换为代理模式，或通过启用 `WebDAV 本地代理` 的 WebDAV 挂载播放。
```mermaid
@@ -533,5 +217,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/163music.md b/pages/guide/drivers/163music.md
index e55cc21d7..82f3e1b46 100644
--- a/pages/guide/drivers/163music.md
+++ b/pages/guide/drivers/163music.md
@@ -1,40 +1,18 @@
---
-title:
- en: 163 Music Drive
- zh-CN: 网易云音乐云盘
-icon: iconfont icon-state
-# This control sidebar order
top: 677
-# A page can have multiple categories
categories:
- guide
- drivers
---
+# 网易云音乐云盘
+
-::: en
-163 Music Drive can only upload music and other operations on the mobile phone, and the web page cannot operate
-:::
-::: zh-CN
网易云音乐云盘需要在手机端才可以进行上传音乐等操作，网页端无法操作
-:::
-
-## Cookie { lang="en" }
-
-## Cookie { lang="zh-CN" }
-
-::: en
-Open **https://music.163.com** and then open the F12 developer mode
-
-Open a request at will, just carry the `Cookie` to find the following two parameters and fill in the OpenList` Cookie`
-
-- **\_\_csrf** 、**MUSIC_U**
- 
-:::
+## Cookie
-::: zh-CN
进入 **https://music.163.com** 然后打开F12开发者模式
随意打开一个请求只要携带 `Cookie` 找到以下两个参数填写进OpenList的 `Cookie` 中就可以使用
@@ -42,64 +20,16 @@ Open a request at will, just carry the `Cookie` to find the following two parame
- **\_\_csrf** 、**MUSIC_U**
-:::
+## 歌曲获取上限
-## Song Limit { lang="en" }
-
-## 歌曲获取上限 { lang="zh-CN" }
-
-::: en
-You can only get 200 songs by default. If you exceed you, you can modify this option
-:::
-::: zh-CN
默认只能获取200首歌曲，如果你超出可以修改此选项
-:::
-
-### Precautions { lang="en" }
-
-### 注意事项 { lang="zh-CN" }
-::: en
-
-1. If there are many list files, it is recommended to open pagination loading, otherwise it will not be loaded
-2. Cloud space can only upload audio format files, and cannot upload other format files
-
-:::
-
-::: zh-CN
+### 注意事项
1. 如果列表文件很多，建议开启分页加载
2. 云空间只可以上传音频格式文件，无法上传其它格式文件
-:::
-
-### The default download method used { lang="en" }
-
-### 默认使用的下载方式 { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[302]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[local proxy]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-::: zh-CN
+### 默认使用的下载方式
```mermaid
---
@@ -119,5 +49,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/189.md b/pages/guide/drivers/189.md
index e84429d70..b400f0850 100644
--- a/pages/guide/drivers/189.md
+++ b/pages/guide/drivers/189.md
@@ -1,43 +1,22 @@
---
-title:
- en: 189Cloud
- zh-CN: 电信天翼云盘
-icon: iconfont icon-state
-# This control sidebar order
top: 694
-# A page can have multiple categories
categories:
- guide
- drivers
-# A page can have multiple tags
-tag:
- - Storage
- - Guide
- - '302'
-# this page is sticky in article list
-sticky: true
-# this page will appear in starred articles
-star: true
---
-
-
-::: en
-::: tip
-The web -side login has been replaced with sliding verification code, **no longer supports OCR or manual input**. If the verification code needs to be used, please use the add `Cookie` to log in
+# 电信天翼云盘
-If you encounter "Device ID does not exist, secondary device verification required",Open the 189 Account website at , log in, and then disable the Device Lock..
+
-::: zh-CN
::: tip
Web 端登录已更换为滑动验证码，**不再支持 OCR 与手动输入**，若需要验证码请使用 `添加 Cookie 进行登录` 或使用 `天翼云盘客户端` 驱动
如遇 **设备 ID 不存在，需要二次设备校验**，打开天翼账号网站 ，登陆后关掉设备锁即可
:::
-## 189CloudTV { lang="zh-CN" }
+## 189CloudTV
-::: zh-CN
使用天翼网盘的TV接口，挂载步骤最少。
(部分用户反馈存在限速问题,如果播放视频卡顿黑屏等无法加载的现象请改用天翼网盘客户端)
@@ -52,69 +31,18 @@ Web 端登录已更换为滑动验证码，**不再支持 OCR 与手动输入**
-:::
-
-## 189CloudTV { lang="en" }
-
-::: en
-Uses the TV interface of 189 Cloud Drive, with the fewest mounting steps.
-
-(Some users have reported throttling issues. If you experience video playback stuttering, black screens, or failure to load, please switch to the 189 Cloud PC client.)
-
-1. When mounting, select 189CloudTV. Leave the login parameters blank. If you are unsure, **just fill in the mount path**.
-
-2. After clicking save, simply return to the storage management page. You can choose to log in by scanning a QR code or click the link to log in (for link login, if you are unsure, it is recommended to **right-click the link and open it in a new window**).
+## 个人云
-
+### 用户名
-3. After entering, select SMS login. Once logged in, return to the storage management page. Disable and re-enable the storage to use it normally (you may need to refresh the page).
-
-
-
-:::
-
-## 个人云 { lang="zh-CN" }
-
-## Personal Cloud { lang="en" }
-
-### Username { lang="en" }
-
-### 用户名 { lang="zh-CN" }
-
-::: en
-the phone number used to log in
-:::
-::: zh-CN
用于登录的电话号码
-:::
-
-### 密码 { lang="zh-CN" }
-### Password { lang="en" }
+### 密码
-::: en
-password for login
-:::
-
-::: zh-CN
登录密码
-:::
-### 根文件夹ID { lang="zh-CN" }
-
-### Root folder ID { lang="en" }
-
-::: en
-The string at the end of the official website url, such as:
-
-- https://cloud.189.cn/web/main/file/folder/-11 -> `-11`
-- https://cloud.189.cn/web/main/file/folder/71398114617385472 -> `71398114617385472`
+### 根文件夹ID
- 
-
-:::
-
-::: zh-CN
官网 URL 末尾的字符串，如：
- https://cloud.189.cn/web/main/file/folder/-11 -> `-11`
@@ -122,113 +50,39 @@ The string at the end of the official website url, such as:
-:::
-
-### 家庭云中转 { lang="zh-CN" }
-
-### Family transfer { lang="en" }
-
-::: en
-Give 189 Cloud adds Personal's `Family Transfer option`, which is convenient for users without VIP, and a large number of family cloud spaces upload.
-
-- Note: The old upload interface family cloud will still limit the upload quantity, so `Rapid upload` and ` Old Upload` will not take effect
+### 家庭云中转
-:::
-::: zh-CN
为天翼云盘增加个人云使用`家庭云中转选项`，方便不开会员且家庭云空间小情况下大量上传。
- 注：旧的上传接口家庭云依然会限制上传量，所以`秒传选项`和`旧的上传方式`不生效
-:::
-
-## 家庭云 { lang="zh-CN" }
-
-## Family Cloud { lang="en" }
-
-::: en
-(189 Cloud PC Driver Only) Use a computer browser, open the developer tool (F12), switch the emulation device and select the mobile device
+## 家庭云
-Open https://h5.cloud.189.cn/main.html#/family, enter the folder you want to mount, you can see the request in the network, and then find the required parameters:
-:::
-
-::: zh-CN
（天翼云盘客户端驱动专用）使用电脑浏览器，打开开发者工具（F12），切换仿真设备选择手机设备
打开https://h5.cloud.189.cn/main.html#/family ，进入你想挂载的文件夹，可在网络中看到请求，然后找到所需参数：
-:::
-### OpenList挂载填写示例： { lang="zh-CN" }
-
-### OpenList fill in examples： { lang="en" }
-
-#### 天翼云盘 { lang="zh-CN" }
+### OpenList挂载填写示例：
-#### 189 Cloud { lang="en" }
+#### 天翼云盘
-::: en
-Fill in the account1and password2,Then click one request in the request, just bring `Cookies`3, click on one at will Then fill in,Cookie expires time is unknown
-:::
-
-::: zh-CN
填写帐号1和密码2，然后在请求中随便点击一个请求随意点击一个携带`Cookie`3的参数复制填写，Cookie有效期未知。
-:::
-#### 天翼云盘客户端 { lang="zh-CN" }
-
-#### 189 CloudPC { lang="en" }
+#### 天翼云盘客户端
-::: en
-Video reference: **https://www.bilibili.com/video/BV16A4y197De**
-:::
-::: zh-CN
视频参考：**https://www.bilibili.com/video/BV16A4y197De**
-:::
-
-## 建议 { lang="zh-CN" }
-## suggestion { lang="en" }
+## 建议
-::: en
-It is recommended to use the 189 Cloud PC first, [**Notes click to view.**](../../faq/howto.md#when-adding-a-189-cloud-storage-the-device-id-does-not-exist-and-a-secondary-device-verification-is-required)
-:::
-::: zh-CN
建议首选使用天翼云盘客户端，[**注意事项点击查看**](../../faq/howto.md#添加-天翼云盘-云存储时-设备-id-不存在-需要二次设备验证)
-:::
-### 默认使用的下载方式 { lang="zh-CN" }
-
-### The default download method used { lang="en" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[302]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[local proxy]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-
-::: zh-CN
+### 默认使用的下载方式
```mermaid
---
@@ -248,5 +102,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/alias.md b/pages/guide/drivers/alias.md
index 74f94447f..8378c126c 100644
--- a/pages/guide/drivers/alias.md
+++ b/pages/guide/drivers/alias.md
@@ -1,22 +1,10 @@
---
-title:
- en: Alias
- zh-CN: 别名（Alias）
-icon: iconfont icon-state
-# This control sidebar order
top: 997
-# A page can have multiple categories
categories:
- guide
- drivers
-# A page can have multiple tags
-tag:
- - Storage
- - Guide
-# this page is sticky in article list
-sticky: true
-# this page will appear in starred articles
-star: true
---
+# 别名（Alias）
+
diff --git a/pages/guide/drivers/alias_text.md b/pages/guide/drivers/alias_text.md
index 86c6c72da..5a6894cde 100644
--- a/pages/guide/drivers/alias_text.md
+++ b/pages/guide/drivers/alias_text.md
@@ -1,35 +1,3 @@
-::: en
-
-**Alias** is a feature that allows multiple different cloud drives or storage paths to be merged into a unified directory. By combining paths, content from different cloud drives or folders can be displayed in the same interface, simplifying access and management.
-
-For example: Cloud Drive Account 1 and Cloud Drive Account 2 both contain a folder named `Movies`, but the contents of these folders may not be identical.
-
-- **Previously (Virtual Path)**:
-
- You could only mount them to two different paths separately, like:
- - `CloudDrive1/Movies`, `CloudDrive2/Movies`
- - `Movies/CloudDrive1`, `Movies/CloudDrive2`
-
-- **Now (Alias)**:
-
- An aggregated folder (Movies) is provided, which can contain content from both Cloud Drive 1 and Cloud Drive 2 simultaneously.
-
-Folders with the same name will be automatically merged into one. The contents of the folder are the sum of the contents of all folders with the same name. Regarding how this driver handles files with the same name, please refer to the [Path conflict policies](/guide/drivers/alias#path-conflict-policies) section later.
-
-For Example:
-
-
-
-In the diagram, we can see that two different folders are merged into one. Files and folders with the same name are also combined, and unique ones are displayed separately.
-
-Example explanations:
-
-- **Example 1**: `riluo.jpg` is unique to Cloud Drive 1, so it is shown separately.
-- **Example 2**: Both folders contain a `video` folder, but the contents of these folders will be merged. Subfolders also follow the **same-name merging** display rule. Both folders contain two videos, but one of them has the same name. After merging according to the **same-name merging** rule, three video files will be displayed in total.
-
-:::
-::: zh-CN
-
**别名（Alias）** 是一种将多个不同云盘或存储路径合并为一个统一目录的功能。通过路径合并，来自不同云盘或文件夹的内容可以在同一界面中展示，从而简化访问和管理。
例如：云盘账号1和云盘账号2中都包含一个名为`电影`的文件夹，但两者的内容未必完全相同。
@@ -57,39 +25,8 @@ Example explanations:
- **例1**：`riluo.jpg` 仅存在于云盘1中，因此显示为独有文件。
- **例2**：两个文件夹都有一个名为`video`的子文件夹。合并后，两个`video`文件夹的内容会合并展示。若其中有同名文件（例如`movie.mp4`），合并后最终展示3个视频文件。
-:::
-
-## Paths filling method { lang="en" }
+## 路径填写方式
-## 路径填写方式 { lang="zh-CN" }
-
-::: en
-There are two ways to fill in:
-
-1. The first one is that you can only fill in the path of the subfolder and the folder with the same name must be used at the end. It is not recommended to use :x:
- - Paths filling example:
- ```
- /file1/locala
- /file2/localb
- ```
-2. The second is to directly mount the root folder path, using the `renaming` method, it is strongly recommended to use :heavy_check_mark:
- - Paths filling example:
-
- ```
- #Example 1 Directly write the root folder
- merge: /file1
- merge: /file2
-
- #Example 2 Mount different path folders for merging
- merge: /file1/localtest233
- merge: /file2/videos/TV series
- merge: /file3 2/TV/Domestic TV Series/Station XX
- ```
-
-According to the second method, we can `merge` and display different folders, which is convenient and quick.
-:::
-
-::: zh-CN
填写方式有两种：
1. 第一种是只可以填写子文件夹路径并且最后结尾时必须同名文件夹才可以，不推荐使用 :x:
@@ -113,91 +50,13 @@ According to the second method, we can `merge` and display different folders, wh
```
根据第二种这样我们可以将不同的文件夹进行合并显示，方便快捷。
-:::
-
-## Path conflict policies { lang="en" }
-## 路径冲突策略 { lang="zh-CN" }
+## 路径冲突策略
-::: en
-The three configuration items—**Reading conflict policy**, **Writing conflict policy**, and **Putting conflict policy**—determine how the Alias handles files or folders with the same name and identical paths in the backend drivers. Their values and corresponding behaviors are as follows:
-
-:::
-::: zh-CN
**读取冲突策略**、**写入冲突策略**和**上传冲突策略**三个配置项确定了别名驱动如何处理后端驱动中路径相同的同名文件或文件夹，其值与对应的行为如下：
-:::
-
-### Reading conflict policy { lang="en" }
-
-### 读取冲突策略 { lang="zh-CN" }
-
-::: en
-Determines the behavior for handling files with the same name when downloading, copying (as source files), and extracting (as source files) (excluding moving).
-
-- Get the file corresponding to the first conflict path: Select the file from the first available path (from top to bottom in the Paths) where the file exists.
-
-- Load balancing on a per-file basis: Randomly select one file from the available duplicates.
+### 读取冲突策略
-- Load balancing on a per-part basis:
- - During 302 downloads, copying, or extracting, it falls back to the **Load balancing on a per-file basis** strategy.
- - When using local proxy downloads, each transmitted chunk is randomly assigned to one of the duplicate files. This requires the backend driver to support Range requests. For details on setting the chunk size, refer to the section [Download concurrency, Download part size](/guide/drivers/alias#download-concurrency-download-part-size).
- - This policy achieves the actual effect as shown in the figure. It is important to note that this diagram is only intended to conveniently demonstrate the operation of this policy. The statement that "participating load-balanced files with the same name have different contents" is **not** a correct usage of this driver. OpenList does not guarantee stable or correct results under such circumstances, nor will it address any issues arising from this usage scenario. Furthermore, the actual minimum size for file splitting is 1 KiB, not 1 byte, so the effect depicted in the diagram will not occur in the stable version.
-
- 
-
-::: tip
-When a copy operation involves multiple source paths and target paths, the Alias will first attempt to pair source and target paths that belong to the same drive. Only for target paths that cannot be matched in this way will the method specified by the **Reading conflict policy** be used to select a source path.
-
-For example, when copying:
-
-- `DriverA/source/file.txt`
-- `DriverB/source/file.txt`
-
-to:
-
-- `DriverB/target/`
-- `DriverA/target/`
-- `DriverC/target/`
-
-The Alias driver will perform the following operations:
-
-1. Copy `DriverA/source/file.txt` to `DriverA/target/`, since both are located in Driver A.
-2. Copy `DriverB/source/file.txt` to `DriverB/target/`, since both are located in Driver B.
-3. For `DriverC/target/`, which has no matching source in the same driver, select `file.txt` from either Driver A or Driver B according to the **Reading conflict policy**, and copy it to `DriverC/target/` via an upload operation (creating a copy task).
-
-:::
-::: en
-::: tip
-The move operation involves a matching process similar to that of the copy operation. For target paths that cannot be matched with a source path from the same driver, the Alias will randomly select from the still-unmatched source paths to create a pairing (**one-to-one correspondence**). If the number of source paths exceeds the number of target paths, the unmatched source paths will be deleted. If the number of source paths is less than the number of target paths, the move operation will fail. The matching behavior for the move operation is not affected by the **Reading conflict policy**.
-
-For example, in the case described for the copy operation, since there is no source path corresponding to `DriverC/target/`, the move operation will fail.
-
-As another example, when moving:
-
-- `DriverA/source/file.txt`
-- `DriverB/source/file.txt`
-- `DriverD/source/file.txt`
-- `DriverE/source/file.txt`
-- `DriverG/source/file.txt`
-
-to:
-
-- `DriverA/target/`
-- `DriverB/target/`
-- `DriverC/target/`
-- `DriverF/target/`
-
-The Alias will perform the following operations:
-
-1. Move `DriverA/source/file.txt` to `DriverA/target/`.
-2. Move `DriverB/source/file.txt` to `DriverB/target/`.
-3. Randomly select one file from Driver D, E, or G, and move it to `DriverC/target/` (by creating a move task, which is essentially an upload followed by deletion). Let's assume E is selected.
-4. Randomly select one file from the remaining unmatched drivers (D or G), and move it to `DriverF/target/`. Let's assume G is selected.
-5. Delete `DriverD/source/file.txt`.
-
-:::
-::: zh-CN
影响下载、复制（作为源文件）、解压（作为源文件）（没有移动）同名文件的方式。
- 读取首个有效路径：选择填写的所有路径中从上到下第一个存在该文件的路径中的同名文件。
@@ -230,7 +89,7 @@ The Alias will perform the following operations:
3. 按照**读取冲突策略**给出的方案选择驱动 A 或 B 中的`file.txt`，通过上传的方式（创建复制任务）复制到`驱动C/target/`。
:::
-::: zh-CN
+
::: tip
移动操作存在与复制操作类似的匹配过程，对于未获得匹配的目标路径，随机选择同样未被匹配的源路径进行匹配（**一一对应**），源路径数量超过目标路径时，未得到匹配的源路径会被删除，源路径数量少于目标路径时，移动操作会失败。移动操作的匹配行为不会受到**读取冲突策略**的影响。
@@ -261,54 +120,8 @@ The Alias will perform the following operations:
:::
-### Writing conflict policy { lang="en" }
-
-### 写入冲突策略 { lang="zh-CN" }
-
-::: en
-Determines the behavior for renaming or deleting files/folders with the same name, as well as creating folders within identically named folders.
-
-- **Disable writing**: Prohibits rename, delete, and folder creation operations.
-- **Write into the first conflict path**: Operates on the driver containing the target path that appears first (top to bottom) in the configured path list.
-- **Allow unique path**: Executes the operation only if the target path is unique (exists in only one backend path). Otherwise, the operation is prohibited.
-- **Allow full conflict paths**: Executes the operation only if the target path exists in **all** configured backend paths, applying the operation across all of them. Otherwise, the operation is prohibited.
-- **Allow unique path and full conflict paths**: Allows the operation when the target path is either unique or exists in all configured backend paths.
-- **Write into all conflict paths**: Forwards the operation to all backend paths where the target path exists.
-
-::: tip
-If the above explanation is unclear, you can refer to the following example.
-
-- In Driver A, the file exists: `file1.txt`
-- In Driver B, the files exist: `file1.txt`, `file2.txt`, `file3.txt`
-- In Driver C, the files exist: `file1.txt`, `file3.txt`
-
-Configured backend paths:
-
-```
-test:DriverA
-test:DriverB
-test:DriverC
-```
-
-Then:
-
-- Since the sub-path `/file1.txt` is valid in all configured paths (`DriverA/`, `DriverB/`, `DriverC/`), `/file1.txt` is referred to as a **full conflict path**.
-- Since the sub-path `/file2.txt` is valid only under the single backend path `DriverB/`, `/file2.txt` is referred to as a **non-conflict path** or **unique path**.
-- Since the sub-path `/file3.txt` exists under both `DriverB/` and `DriverC/`, and the number of backend paths where it exists is neither 1 nor the maximum (3), `/file3.txt` is neither a non-conflict path nor a full conflict path.
+### 写入冲突策略
-When renaming any file to `file4.txt`, the corresponding files in the following drivers will be renamed:
-
-| Writing conflict policy | file1.txt | file2.txt | file3.txt |
-| ----------------------------------------- | ---------------------------- | --------- | ------------------ |
-| Disable writing | Fails | Fails | Fails |
-| Write into the first conflict path | Driver A | Driver B | Driver B |
-| Allow unique path | Fails | Driver B | Fails |
-| Allow full conflict paths | Driver A, Driver B, Driver C | Fails | Fails |
-| Allow unique path and full conflict paths | Driver A, Driver B, Driver C | Driver B | Fails |
-| Write into all conflict paths | Driver A, Driver B, Driver C | Driver B | Driver B, Driver C |
-
-:::
-::: zh-CN
影响重命名、删除同名文件或文件夹，在同名文件夹下创建文件夹的方式。
- 禁用：禁止重命名、删除和创建文件夹操作。
@@ -340,49 +153,20 @@ test:驱动C
- 由于子路径`/file3.txt`在`驱动B/`和`驱动C/`下存在，存在的后端路径数量既不为 1，也不为最大（3），因此`/file3.txt`既不是不冲突路径，也不是全冲突路径。
重命名任意文件为`file4.txt`时，以下驱动中的对应文件会被重命名：
-| 写入冲突策略 | file1.txt | file2.txt | file3.txt |
-| -- | -- | -- | -- |
-| 禁用 | 操作失败 | 操作失败 | 操作失败 |
-| 写入首个有效路径 | 驱动A | 驱动B | 驱动B |
-| 仅允许不冲突路径 | 操作失败 | 驱动B | 操作失败 |
-| 仅允许全冲突路径 | 驱动A、驱动B、驱动C | 操作失败 | 操作失败 |
-| 允许不冲突路径和全冲突路径 | 驱动A、驱动B、驱动C | 驱动B | 操作失败 |
-| 写入所有有效路径 | 驱动A、驱动B、驱动C | 驱动B | 驱动B、驱动C |
-
-:::
-
-### Putting conflict policy { lang="en" }
-
-### 上传冲突策略 { lang="zh-CN" }
-
-::: en
-Determines the behavior for uploading to, copying to, moving to, or extracting to folders with the same name.
-
-- **Disable putting**, **Put into the first conflict path**, **Allow unique path**, **Allow full conflict paths**, **Allow unique path and full conflict paths**, **Put into all conflict paths**: These options function identically to their counterparts in the **Writing conflict policy**.
-- **Random load balancing**: Randomly selects one valid path for the upload.
-- **Weighted random load balancing based on remaining space**: Retrieves the remaining free space of all valid paths, skips paths that fail to report free space or have insufficient space for the file being uploaded, and then randomly selects from the remaining valid paths, weighting the choice by their remaining capacity. If none of the valid paths that successfully reported free space have enough capacity for the file, **a random selection is made from among the valid paths that failed to report capacity**.
-- **Strict weighted random load balancing based on remaining space**: Retrieves the remaining free space of all valid paths, skips paths that fail to report free space or have insufficient space for the file being uploaded, and then randomly selects from the remaining valid paths, weighting the choice by their remaining capacity. If none of the valid paths that successfully reported free space have enough capacity for the file, **an error message is returned directly**.
-::: tip
-The load balancing mechanisms within the **Reading conflict policy** and the **Putting conflict policy** are two largely unrelated features. Informally speaking, the load balancing in the **Reading conflict policy** is analogous to RAID 1, while the load balancing in the **Putting conflict policy** is analogous to RAID 0. For specific use cases of each, please refer to [Advanced / Load balancing](/guide/advanced/balance).
-
-If you've understood the above, you'll realize that enabling both **Reading Load Balancing** and **Putting Load Balancing** won't make load balancing more balanced. In fact, this configuration produces effects that are hardly any different from enabling only **Putting Load Balancing**.
+| 写入冲突策略 | file1.txt | file2.txt | file3.txt |
+| -------------------------- | ------------------- | --------- | ------------ |
+| 禁用 | 操作失败 | 操作失败 | 操作失败 |
+| 写入首个有效路径 | 驱动A | 驱动B | 驱动B |
+| 仅允许不冲突路径 | 操作失败 | 驱动B | 操作失败 |
+| 仅允许全冲突路径 | 驱动A、驱动B、驱动C | 操作失败 | 操作失败 |
+| 允许不冲突路径和全冲突路径 | 驱动A、驱动B、驱动C | 驱动B | 操作失败 |
+| 写入所有有效路径 | 驱动A、驱动B、驱动C | 驱动B | 驱动B、驱动C |
:::
-::: en
-::: tip
-The legacy version of the Alias used three Boolean configuration items—**Writable**, **Protect same name**, and **Parallel write**—to implement path conflict policy functionality. The correspondence between the legacy configuration and the new configuration is as follows:
-- In the legacy configuration, the **Reading conflict policy** was always set to **Get the file corresponding to the first conflict path**.
-- In the legacy configuration, when **Writable** was disabled, both the **Writing conflict policy** and the **Putting conflict policy** were set to **Disabled**.
-- When **Writable** was enabled, the **Writing conflict policy** and the **Putting conflict policy** were both determined as follows:
- | | Parallel write disabled | Parallel write enabled |
- | -- | -- | -- |
- | Protect same name enabled | Allow unique path | Allow unique path and full conflict paths |
- | Protect same name disabled | Write/Put into the first conflict path | Write/Put into all conflict paths |
+### 上传冲突策略
-:::
-::: zh-CN
影响上传到、复制到、移动到、解压到同名文件夹的方式。
- 禁用、上传到首个有效路径、只允许不冲突路径、只允许全冲突路径、允许不冲突路径和全冲突路径、上传到所有有效路径：与**写入冲突策略**中的对应选项相同。
@@ -396,76 +180,37 @@ The legacy version of the Alias used three Boolean configuration items—**Writa
一旦理解了上述原理，你就会明白同时开启**读取负载均衡**和**上传负载均衡**并不能让你负载得均均又衡衡，这种配置产生的效果和仅开启**上传负载均衡**没有什么太大的区别。
:::
-::: zh-CN
+
::: tip
旧版别名驱动使用**可写**、**保护同名**和**并行写入**三个布尔配置项实现路径冲突策略功能，旧版配置与新版配置的对应关系如下：
- 在旧版配置中，**读取冲突策略**总为**读取首个有效路径**。
- 在旧版配置中，当**可写**关闭时，**写入冲突策略**与**上传冲突策略**均为**禁用**。
- 当**可写**开启时，**写入冲突策略**与**上传冲突策略**均为
- | | 关闭并行写入 | 开启并行写入 |
- | -- | -- | -- |
- | 开启保护同名 | 仅允许不冲突路径 | 允许不冲突路径和全冲突路径 |
- | 关闭保护同名 | 写入/上传到首个有效路径 | 写入/上传到所有有效路径 |
+ | | 关闭并行写入 | 开启并行写入 |
+ | ------------ | ----------------------- | -------------------------- |
+ | 开启保护同名 | 仅允许不冲突路径 | 允许不冲突路径和全冲突路径 |
+ | 关闭保护同名 | 写入/上传到首个有效路径 | 写入/上传到所有有效路径 |
:::
-## File consistency check { lang="en" }
-
-## 文件一致性校验 { lang="zh-CN" }
-
-::: en
-When enabled, the driver will filter out paths where the **size or hash value** differs from other copies during the process of collecting valid paths. This is a safety measure, and whether it is enabled has relatively minor impact. It is recommended to enable this option when using the **Load balancing on a per-part basis** reading policy.
-
-Regardless of whether this option is enabled, the Alias does not actively calculate file hashes. Instead, it performs a best-effort match using the hash values returned by the backend drivers.
-
-Different types of hash values returned by backend drivers will not lead to misjudgment. For example, if Driver 1 returns the MD5 of a file and Driver 2 returns the SHA1 of the file, even with this option enabled, the Alias will not consider either path from Driver 1 or Driver 2 invalid simply because the file's MD5 and SHA1 are not equal.
+## 文件一致性校验
-:::
-::: zh-CN
开启时，驱动在收集有效路径的过程中，会过滤掉那些**大小或哈希值**与其它副本不同的路径，是一种安全措施，开启与否影响不太大，推荐使用**按分片负载均衡**读取策略时打开。
无论是否启用该选项，别名都不会主动计算文件的哈希值，而是使用后端驱动返回的哈希值做尽力而为的匹配。
后端驱动返回不同种类的哈希值不会导致误判。例如驱动 1 返回了文件的 MD5，驱动 2 返回了文件的 SHA1，即便开启本选项，别名也不会因为文件的 MD5 与 SHA1 不相等而判定驱动 1 或 2 中的任何一个路径无效。
-:::
-
-## The download method to use { lang="en" }
-
-## 使用的下载方式 { lang="zh-CN" }
-
-::: en
-When adding **`alias`**, `Web Proxy` and `Webdav Policy` are not modified by default. The storage path filled in the Paths path can be `302`, `Local Proxy`, `Download Proxy URL`, three modes Mixed Playback Mixed Playback is possible.
+## 使用的下载方式
-If you checked `Web Proxy`, the storage filled in by the Paths path, if there is a 302 mode playback, it will be played in transit (local proxy mode) at that time, and it will become a proxy mode. If the Webdav policy is also changed, it will also change.
-
-Of course, it is up to you to choose whether to change the mode.
-:::
-::: zh-CN
添加 **`别名-alias`** 时 `Web代理` 和 `Webdav策略` 默认不修改的情况下 Paths路径填写的存储路径可以 `302`，`本地代理`，`下载代理URL`，三种模式混合播放可以进行混合播放。
如果你勾选了`Web代理` ，Paths路径填写的存储 如果有302模式播放的 到时候都会进行中转(本地代理模式)播放，变成代理模式，Webdav策略如果也进行了改动也会进行变化。
当然，是否选择更换模式您自己进选择。
-:::
-
-### What if you don’t know how the cloud disks you added are different? { lang="en" }
-### 如果你不知道你添加的云盘是什么方式怎么办? { lang="zh-CN" }
-
-::: en
-
-1. You can go to the bottom of the corresponding document to view the document, there is a flow chart description
- - If there is a 302, the 302 method is used by default. If there are only local proxy and download proxy URLs, the default is to use the local proxy, provided that you have not manually selected
-2. You can check when adding storage, select the corresponding storage to view, for example, let’s check the methods of Alibaba Cloud and 115 respectively
- - As you can see from the figure below, Alibaba Cloud Disk has the option of `web proxy`, and `webdav policy` defaults to 302. It can be judged that Alibaba Cloud Disk uses the 302 method by default
- - As you can see from the figure below, the 115 network disk does not have the option of `web proxy`, and the `webdav strategy` defaults to the local proxy. It can be judged that the 115 network disk uses the local proxy mode by default
- 
-
-:::
-
-::: zh-CN
+### 如果你不知道你添加的云盘是什么方式怎么办?
1. 可以前往文档的相对应的文档最底部查看，有一份流程图说明
- 如果有302的就是默认使用302方式，如果只有本地代理和下载代理URL默认的就是使用本地代理，前提是你没有进行手动选择
@@ -474,75 +219,16 @@ Of course, it is up to you to choose whether to change the mode.
- 从下图中看到，115网盘没有 `web代理`选择，`webdav策略`默认是本地代理，可以判断出115网盘默认使用的是本地代理方式
-:::
-
-## Proxy Range { lang="en" }
+## 代理 Range
-## 代理 Range { lang="zh-CN" }
-
-::: en
-You need to enable `Web Proxy` or` Webdav Native Proxy` to take effect. Currently only applicable to：`alias`、`139Yun`、`OpenList V3`.
-
-- The `139Yun` driver, when this option is enabled, can resolve issues that occur when a proxy is enabled but the download link does not return the correct HTTP status code, such as problems with video playback or lack of support for resume downloads.
-- The `Alias` driver is added to meet specific use cases, for example, when `139Yun` uses a 302 redirect. By enabling the `Alias` proxy, downloads can use `139Yun` with the 302 redirect, while video playback can use the proxy-enabled `Alias`, reducing unnecessary load.
-- The `OpenList` driver is added to support server-side OpenList mounting with `139Yun` using a 302 redirect. Locally, OpenList can be mounted via the proxy-enabled `OpenList` to access the server's OpenList for video playback, etc., to avoid consuming server bandwidth. This also allows for data-free video streaming on mobile networks.
-
-:::
-
-::: zh-CN
需要先启用 `Web代理` 或者 `Webdav本地代理` 才会生效。目前仅适用于：`别名`、`中国移动云盘`、`OpenList V3`。
- `139Yun` 驱动开启这个选项后，可解决即使开启代理但下载链接没有返回正确的http状态码导致的一些问题，例如视频无法播放、不支持断点续传等
- `Alias` 驱动添加是为了满足某些场景，例如 `139Yun` 走302， 然后通过 开启代理的 `Alias` 后，下载用 `139Yun` 走302，播放视频用 开启代理的 `Alias`，减少不必要的负载
- `OpenList` 驱动添加是为了 服务器的 OpenList 挂载 `139Yun` 走302，然后本地的 OpenList 通过 开启代理的 `OpenList` 挂载 服务器的 OpenList 播放视频等，达到不消化服务器流量的目的，移动卡还能免流
-:::
-
-## Download concurrency, Download part size { lang="en" }
-
-## 下载并发、下载分片大小 { lang="zh-CN" }
-
-::: en
-**Storage Settings:**
-
-- Alias (Alias) Drive
-- Local Proxy
-- Path: / Cloud Drive Mount Path
-- Download Concurrency: 10
-- Download Chunk Size: 1024
-
-**Effect:**
-
-- Client → OpenList Alias Drive: Uses 1 connection
-- OpenList Alias Drive → Cloud Drive: Supports 10 concurrent connections, with actual concurrency limited by the cloud drive.
-
-```mermaid
-graph LR
- A[Client] -->|Connection 1| B[OpenList Alias Drive]
- B -->|Concurrent Connection 1| C[Cloud Drive]
- B -->|Concurrent Connection 2| C
- B -->|Concurrent Connection 3| C
- B -->|Concurrent Connection 4| C
- B -->|Concurrent Connection 5| C
- B -->|Concurrent Connection 6| C
- B -->|Concurrent Connection 7| C
- B -->|Concurrent Connection 8| C
- B -->|Concurrent Connection 9| C
- B -->|Concurrent Connection 10| C
-```
-
-- Single-threaded speed is slower, but it supports concurrency: Using the alias drive allows concurrent downloads, significantly improving speed.
-- Video watching and download acceleration: The experience is enhanced by increasing concurrency.
-- Copying from alias drive to other drives: File transfer is also accelerated in this case.
+## 下载并发、下载分片大小
-**Friendly Reminder:** Please do not abuse this feature. Excessive use may cause abnormal activity on the cloud drive account, and you will bear the consequences.
-
-**Configuration Options:**
-
-- max_concurrency: Sets the maximum concurrency for the local proxy. The default is 64, and setting it to 0 means no limit on concurrency.
-
-:::
-::: zh-CN
**存储设置：**
- 别名 (Alias) 驱动
@@ -581,27 +267,8 @@ graph LR
- `max_concurrency`：设置本地代理的最大并发数，默认为 64，设置为 0 表示不限制并发数。
-:::
-
-## Other instructions { lang="en" }
-
-## 其他说明 { lang="zh-CN" }
-
-::: en
-
-If you are using `Windows`, the following situation will occur, and folders with different capitalization will also be regenerated.
+## 其他说明
-For example, Local 1 and Local 2 have a lowercase v for `video` respectively, and the folder OneDrive has an uppercase V `Video` folder.
-
-Then a lowercase video folder will be generated, which contains only `local 1, local 2` files merged by two folders.
-
-At the same time, the uppercase `Video` will gather the files of the three folders.
-
-This is because Windows is case-insensitive, video and Video will be considered as the same folder, you will not have this problem if you switch to Linux or Mac.
-
-:::
-
-::: zh-CN
如果你是使用的`Windows`，会出现如下情况，有大小写不同的文件夹也会进行二次生成。
例如本地1，本地2 分别有 `video` 小写的v ，文件夹 OneDrive 有一个大写的 V `Video` 文件夹。
@@ -611,5 +278,3 @@ This is because Windows is case-insensitive, video and Video will be considered
同时大写的 `Video` 里面 会集合三个文件夹的文件
这是因为 Windows 大小写不敏感，video和Video会被认为是同一个文件夹，你换成 Linux 或者 Mac 就不会有这个问题了
-
-:::
diff --git a/pages/guide/drivers/alidoc.md b/pages/guide/drivers/alidoc.md
index e7e10c989..e67bb28f6 100644
--- a/pages/guide/drivers/alidoc.md
+++ b/pages/guide/drivers/alidoc.md
@@ -1,34 +1,16 @@
---
-title:
- en: AliDoc
- zh-CN: 钉钉文档
top: 677
categories:
- guide
- drivers
---
-::: en
-::: danger Please read the notes carefully
-This driver is currently not officially maintained by the project team.
-:::
+# 钉钉文档
-::: zh-CN
::: danger 请仔细阅读注意事项
本接口目前非项目组官方维护
:::
-::: en
-Mount DingTalk Docs web storage in OpenList.
-
-Official website:
-
-- DingTalk Docs:
-:::
+### 2.1. 开放平台注册应用（可选，如果使用OpenList/公益服务器/自建服务器内置的密钥对，则不用创建）
-::: zh-CN
::: tip
请根据阿里云盘开放平台的要求注册应用
:::
-::: zh-CN
-开放平台地址：
-:::
-
-### 2.2. Obtain Tokens { lang="en" }
-
-### 2.2. 获取令牌 { lang="zh-CN" }
-
-::: en
-
-1. Visit [api.oplist.org](https://api.oplist.org) **⚠️ If using a public welfare server/self-hosted server, visit the address of the public welfare server/self-hosted server.**
-
-2. Select **AliYun Drive App Login** from the drop-down menu.
-
- 
-
- 
-
-3. If you are using the built-in key pair of `OpenList (or public welfare server/self-hosted server)` (i.e., you do not have application information from the AliYun Drive Open Platform), configure according to `3.1`, `3.2`, and `3.3`:
- 3.1. Check `Use parameters provided by OpenList`.
-
- 3.2. Leave both `Client ID (ClientID/AppID)` and `App Secret (AppKey/Secret)` blank.
-
- 3.3. Click the `Get Token` button.
-
- 
-
- 
-
-4. If you are using your own created OAuth client ID and secret, configure according to `4.1`, `4.2`, and `4.3`:
-
- 4.1. Do not check `Use parameters provided by OpenList`.
-
- 4.2. Enter your `AppId` in `Client ID` and your `AppSecret` in `App Secret`.
-
- 4.3. Click the `Get Token` button.
-
- 
-
- 
-
-5. In the pop-up window, scan the code to log in to your AliYun Drive.
-
- 
-
-6. After successful authorization, the page will display your `Access Token` and `Refresh Token`. Please copy and save these two tokens.
-
- 
-
- 
+开放平台地址：
-:::
-::: zh-CN
+### 2.2. 获取令牌
1. 访问[api.oplist.org](https://api.oplist.org) **⚠️如果使用公益服务器/自建服务器，请访问公益服务器/自建服务器的地址**
@@ -197,73 +87,9 @@ Open Platform URL:
-:::
-
-## 3. Add AliYun Drive to OpenList { lang="en" }
-
-## 3. 在 OpenList 中添加阿里云盘 { lang="zh-CN" }
+## 3. 在 OpenList 中添加阿里云盘
-### 3.1. Start Adding { lang="en" }
-
-### 3.1. 开始添加 { lang="zh-CN" }
-
-::: en
-
-1. Open the OpenList management interface and click `Storage` in the left menu.
-
-2. On the storage list page, click the `Add Storage` button in the upper right corner.
-
-3. Select the driver as `AliYun Drive (Oauth2)`.
-
-4. Enter the mount path, such as `aliyun-drive`.
-
-5. Enter the root folder ID obtained above in `Root Folder ID`. If using the root directory, enter `root`. See [Configuration Instructions/Root Folder ID](#_3-2-1-root-folder-id).
-
- 
-
- 
-
-6. Enter the refresh token obtained above in the refresh token field (if not obtained, refer to [Preparation for Access](#_2-preparation-for-access)).
-
-7. If you are using the OAuth client ID and secret provided by `OpenList (or public welfare server/self-hosted server)`, configure according to `6.1`, `6.2`, and `6.3`:
-
- 6.1. Check `Use online api`.
-
- 6.2. Leave both `Client ID (ClientID/AppID)` and `App Secret (AppKey/Secret)` blank.
-
- 6.3. Enter `https://api.oplist.org/alicloud/renewapi` in `Api url address`. If using a `public welfare server/self-hosted server`, enter the corresponding server address.
-
- 
-
- 
-
-8. If you are using your own created OAuth client ID and secret, configure according to `7.1`, `7.2`, and `7.3`:
-
- 7.1. Do not check `Use online api`.
-
- 7.2. Enter your `AppId` in `Client ID (ClientID/AppID)` and your `AppSecret` in `App Secret (AppKey/Secret)`. See [Configuration Instructions/Client ID, Secret](#_3-2-2-client-id-secret).
-
- 7.3. Leave `Api url address` blank.
-
- 
-
- 
-
-9. In the `Instant Upload` option, select whether to enable the instant upload function (optional). See [Configuration Instructions/Instant Upload](#_3-2-3-instant-upload).
-
-10. In `Removal Method`, select the way to delete files (optional), default is recycle bin. See [Configuration Instructions/Removal Method](#_3-2-4-removal-method).
-
-11. In `Cloud Drive Type`, select the cloud drive type (optional), default is `Default`. See [Configuration Instructions/Cloud Drive Type](#_3-2-5-cloud-drive-type).
-
-12. In `Livp Download Format`, select the format for downloading live photos (optional), default is `Jpeg`. See [Configuration Instructions/Livp Download Format](#_3-2-6-livp-download-format).
-
-13. In `Internal Upload`, select whether to enable internal upload (optional), default is off. See [Configuration Instructions/Internal Upload](#_3-2-7-internal-upload).
-
-14. Click the `Add` button to complete adding AliYun Drive.
-
-:::
-
-::: zh-CN
+### 3.1. 开始添加
1. 打开 OpenList 的管理界面，点击左侧菜单中的`存储`。
@@ -317,26 +143,10 @@ Open Platform URL:
14. 点击`添加`按钮，完成阿里云盘的添加。
-:::
-
-### 3.2. Configuration Instructions { lang="en" }
-
-### 3.2. 配置说明 { lang="zh-CN" }
-
-#### 3.2.1. Root Folder ID { lang="en" }
-
-#### 3.2.1. 根文件夹 ID { lang="zh-CN" }
+### 3.2. 配置说明
-::: en
-The default is `root`, displaying all cloud drive contents. If you only want to display contents within a certain folder, change it to `file_id`.
+#### 3.2.1. 根文件夹 ID
-Open the AliYun Drive official website, and when clicking into the folder to be set, click the string after the URL.
-
-For example, https://www.alipan.com/drive/folder/5fe01e1830601baf774e4827a9fb8fb2b5bf7940
-
-The file_id of this folder is `5fe01e1830601baf774e4827a9fb8fb2b5bf7940`.
-:::
-::: zh-CN
默认为`root`，展示全部云盘内容，若只想展示某文件夹內内容，可以改为`file_id`
打开阿里云盘官网，点击进入要设置的文件夹时点击 URL 后面的字符串
@@ -344,52 +154,16 @@ The file_id of this folder is `5fe01e1830601baf774e4827a9fb8fb2b5bf7940`.
如 https://www.alipan.com/drive/folder/5fe01e1830601baf774e4827a9fb8fb2b5bf7940
这个文件夹的 file_id 即为 `5fe01e1830601baf774e4827a9fb8fb2b5bf7940`
-:::
-#### 3.2.2. Client ID, Secret { lang="en" }
-
-#### 3.2.2. 客户端 ID，密钥 { lang="zh-CN" }
-
-::: en
-Normal users can leave it blank. If you have applied for official authorization, you can fill in your own. When blank, it defaults to using those provided by OpenList.
-
-- If using your own developer account, the Oauth token link must also be modified, and you must use your own developer account ID and secret to obtain the refresh token.
+#### 3.2.2. 客户端 ID，密钥
-:::
-
-::: zh-CN
正常用户不需要填写为空即可，如果自己申请了官方授权也可以使用自己的进行填写，为空时默认使用 OpenList 提供的。
- 如果使用自己的开发者帐号，Oauth令牌链接也要修改，同时也要使用自己开发者帐号ID和密钥获取刷新令牌
-:::
-
-#### 3.2.3. Instant Upload { lang="en" }
-
-#### 3.2.3. 秒传 { lang="zh-CN" }
-
-::: en
-
-- **Version v.3.22.1** new feature.
-
- Instant upload requires enabling `Instant Upload` when mounting. The prerequisite for instant upload is that the file already exists in AliYun Drive; otherwise, it will be a normal upload.
-
- Instant upload calculates the file's `sha1` value (should be correct) without requiring you to calculate it. You just need to upload, and it will automatically calculate after upload completion.
-
-- It uses the interface provided by AliYun Drive's official API. For details, see :point_right: [**Instant Upload Logic**](https://www.yuque.com/aliyundrive/zpfszx/ezlzok#y7lyH).
-
----
-
-- **Version v.3.27.0** enhances instant upload: files can be instantly transferred between `115 Network Disk` and AliYun Drive by direct copying.
- - Prerequisite: To instantly transfer a file from AliYun Drive to 115, the file must already exist in 115; otherwise, it will be a normal copy task.
- - If instantly transferring a file from 115 to AliYun Drive, enable the instant upload option for AliYun Drive; otherwise, it will be a normal upload.
- It is recommended to locally deploy an OpenList on your home computer, add a `local storage` and `AliYun Drive`, and use copy instant upload to save resources.
-
-:::
-
-::: zh-CN
+#### 3.2.3. 秒传
- **v.3.22.1** 版本 新增功能
@@ -407,24 +181,8 @@ Normal users can leave it blank. If you have applied for official authorization,
如果要使用秒传来上传文件建议在自己家用电脑本地搭建一个OpenList添加一个`本地存储`和`阿里云盘`进行复制秒传这样节省资源。
-:::
-
-#### 3.2.4. Removal Method { lang="en" }
-
-#### 3.2.4. 移除方式 { lang="zh-CN" }
-
-::: en
-If not set, it defaults to deleting to the recycle bin. If space is insufficient, you need to manually clean the recycle bin. If a file is deleted by mistake, please go to the AliYun Drive official website client to retrieve it.
+#### 3.2.4. 移除方式
-- **Recycle Bin**: Deleting in OpenList will move the file to the network disk recycle bin, occupying cloud drive space, but it can be retrieved later if deleted by mistake.
-- **Delete**: Direct deletion without staying in the recycle bin, not occupying cloud drive space, but cannot be retrieved later if deleted by mistake.
- - Note: Do not leak the Token obtained from AliYun Drive Open. If leaked by mistake, please immediately:
- - **Open AliYun Drive app → My → Settings gear icon in the upper right corner → Privacy Settings → Authorization Management → Click OpenList to view and revoke authorization**.
- - Then rescan the code to authorize for a new refresh token. Revoking authorization will invalidate all previously obtained tokens to protect your account security.
-
-:::
-
-::: zh-CN
不进行设置默认是删除到回收站內了，如果空间不够需要自己手动清理回收站/若删错文件请前往阿里云盘官网客户端进行找回恢复
- **回收站**：在OpenList删除后进入网盘回收站，会占用云盘空间，但是后期如果误删可以找回。
@@ -433,23 +191,8 @@ If not set, it defaults to deleting to the recycle bin. If space is insufficient
- **打开-阿里云盘-app-我的-右上角设置齿轮-隐私设置-授权管理-点击-openlist-进行查看和解除授权**
- 再重新扫码授权换新的刷新令牌，同时解除授权后之前获取的都会失效，以保护您账号的安全
-:::
-
-#### 3.2.5. Cloud Drive Type { lang="en" }
-
-#### 3.2.5. 云盘类型 { lang="zh-CN" }
-
-::: en
-You can select the cloud drive type according to your needs. When adding a driver using OpenList version v3.25.1 and above, the default selection is `Default`.
+#### 3.2.5. 云盘类型
-- **Default**: For users with a talent level, it defaults to displaying `non-backup file` content; for users without a talent level, it defaults to displaying `backup file` content.
-- **Resource Library**: Corresponding to the `non-backup file content` of the cloud drive.
-- **Backup Disk**: Corresponding to the `backup files` of the cloud drive.
- After AliYun Drive updated to version `6.0` in July 2024, the backup disk was changed to merge backup files and all files, but in terms of OpenAPI, it still distinguishes between `Resource Library` and `Backup Disk` types.
- 
-
-:::
-::: zh-CN
云盘类型可以选择，可以自己的需求选择不同类型，使用 v3.25.1及以上版本的OpenList添加驱动时进行设置，默认选择的是`默认`类型
- **默认**：有达人等级用户默认展示的是`非备份文件`内容，没有达人等级用户默认展示的是`备份文件`内容
@@ -458,67 +201,22 @@ You can select the cloud drive type according to your needs. When adding a drive
202407 --> 阿里云盘更新 `6.0` 版本后，备份盘变更为备份文件和全部文件合并在一起了，但是在OpenAPI方面还是区分 `资源库` 和 `备份盘` 类型
-:::
-
-#### 3.2.6. Livp Download Format { lang="en" }
-
-#### 3.2.6. Livp 下载格式 { lang="zh-CN" }
-
-::: en
-That is, iOS `live` photos cannot be parsed by non-iOS systems, so they cannot be downloaded. Now, you can choose `Jpeg` or `Mov` according to your needs.
-
-- Jpeg: The cover of the `live` photo.
-- Mov: The video frame of the `live` photo when long-pressed.
+#### 3.2.6. Livp 下载格式
-:::
-
-::: zh-CN
即 IOS`实况`照片因为非IOS系统无法解析，然后就无法下载，现根据自己的需求是需要`Jpeg`还是`Mov`
- Jpeg：就是`实况`照片所展示的封面
- Mov：长按`实况`照片的视频画面
-:::
-
-#### 3.2.7. Internal Upload { lang="en" }
-
-#### 3.2.7. 内部上传 { lang="zh-CN" }
-
-::: en
-If the server where OpenList is deployed is an AliYun ECS in the Beijing region, turning on this switch can improve file upload speed. Do not turn on this switch for servers that do not meet the requirements, otherwise, upload failures will occur.
-
-- Can `Internal Upload` be used on non-Beijing AliYun ECS? No, because AliYun Drive uses object storage in the Beijing region.
+#### 3.2.7. 内部上传
-:::
-
-::: zh-CN
如果你部署 OpenList 的服务器是阿里云北京地区ECS，打开此开关可以提升文件上传速度。不符合要求的服务器请不要打开此开关，否则会出现无法上传的问题。
- **内部上传**非北京地区的阿里云ECS可以使用吗？不能，因为阿里云盘在使用北京地区的对象存储
-:::
-
-## 4. Other Instructions { lang="en" }
-
-## 4. 其他说明 { lang="zh-CN" }
-
-### 4.1. Permission Scope { lang="en" }
-
-### 4.1. 权限范围 { lang="zh-CN" }
+## 4. 其他说明
-::: en
-
-OpenList only obtains cloud drive user (**name, avatar ¹**), (**file access permission ²**), and (**file write permission ³**), without obtaining phone number permission.
-
-Details can be viewed in the following two ways:
-
-1. The **prompt** when scanning the code to obtain the refresh token.
-2. Open **AliYun Drive app → My → Settings gear icon in the upper right corner → Privacy Settings → Authorization Management → Click OpenList** to view.
- - You can manually revoke permissions at any time if not in use.
-
-:::
-
-::: zh-CN
+### 4.1. 权限范围
OpenList 仅获取了 云盘用户 (**名称 头像 ¹**)，(**访问文件权限 ²**)和(**写入文件权限 ³**)，未获取手机号权限
@@ -529,25 +227,8 @@ OpenList 仅获取了 云盘用户 (**名称 头像 ¹**)，(**访问文件权
2. 打开 **阿里云盘 APP --> 我的 -->右上角设置齿轮 --> 隐私设置 --> 授权管理 --> 点击 OpenList** 进行查看
- 若不使用了可以随时手动解除权限
-:::
+### 4.2. 关于视频播放
-### 4.2. About Video Playback { lang="en" }
-
-### 4.2. 关于视频播放 { lang="zh-CN" }
-
-::: en
-
-The default player is AliYun Drive's built-in player - **Aliyun Video Previewer**.
-Videos uploaded to the cloud drive will be transcoded into H.264-encoded video streams through the transcoding service. (The benefit is that iOS can play them... Well, it should be like this.)
-
-- For newly uploaded videos, only the first 30s of the video is pre-transcoded by default. The first play will trigger full video transcoding. The transcoded video will be cached, and no retranscoding is needed for subsequent plays.
-- Videos shorter than 30s will not trigger pre-transcoding, and transcoding will only start when played for the first time.
-- Real-time transcoding takes some time.
-- Video qualities are: LD|SD|HD|FHD|QHD.
-
-:::
-
-::: zh-CN
默认使用的是阿里云盘自带播放器 - **Aliyun Video Previewer**
上传到云盘的视频，会经过转码服务转成 H.264 编码的视频流。（好处是 IOS 可以播放了...嗯 应该是这样）
@@ -557,43 +238,13 @@ Videos uploaded to the cloud drive will be transcoded into H.264-encoded video s
- 实时转码需要一定时间。
- 画质分别为：LD|SD|HD|FHD|QHD
-:::
-
-### 4.3. Inability to View Office Suite Files { lang="en" }
-
-### 4.3. Office 全家桶文件无法查看 { lang="zh-CN" }
-
-::: en
-
-> Q: Why can't Office suite files be viewed in AliYun Drive Open?
->
-> A: ~~Because AliYun Drive has not opened the relevant API, so it cannot be viewed temporarily~~ (Stay tuned.)
-
-:::
-
-::: zh-CN
+### 4.3. Office 全家桶文件无法查看
> Q：阿里云盘Open怎么看不了 Office 全家桶类型的文件
>
> A：~~因为阿里云盘未开放相关API故暂时无法查看~~（敬请期待）
-:::
-
-### 4.4. Subtitle Loading { lang="en" }
-
-### 4.4. 字幕加载 { lang="zh-CN" }
-
-::: en
-
-Q: How to load subtitles?
-
-A: AliYun Drive Open needs to use the **Aliyun Video Previewer** player, and currently only supports transcoding srt and vtt text format subtitles encapsulated in mkv.
-
-- Currently, only three languages are supported: eng, jpn, chi. Other languages will be lost.
-
-:::
-
-::: zh-CN
+### 4.4. 字幕加载
Q：如何加载字幕？
@@ -601,31 +252,7 @@ A：阿里云盘open 需要使用 **Aliyun Video Previewer**播放器，然后
- 目前只支持转码 eng、jpn、chi 三种语言，其他语言会丢失
-:::
-
-### 4.5. Common Issues { lang="en" }
-
-### 4.5. 常见问题 { lang="zh-CN" }
-
-::: en
-
-1. ExceedCapacityForbidden
-
- Q: When playing AliYun Drive videos online, it cannot play and prompts the error: **`ExceedCapacityForbidden`**.
-
- A: **The user's capacity is exceeded**, restricting playback. You need to expand the capacity or delete unnecessary files to free up space
- - In OpenList, it prompts: `ExceedCapacity Forbidden: Execeed Capactity Forbidden`.
- - In AliYun Drive, it prompts: `云盘可用空间不足` (Insufficient available space in cloud drive).
-
-2. Transcoding in progress, please try again later.
-
- Q: When viewing a video in AliYun Drive, it prompts `Transcoding in progress, please try again later`, and when mounting in OpenList, it prompts: `failed link: failed get link: UserNotAllowedAccessResource: user not allowed access resource for violation`.
-
- A: It means the account has been frozen (previously, it was directly unable to log in). For specific situations, please check the red content notes at the top.
-
-:::
-
-::: zh-CN
+### 4.5. 常见问题
1. ExceedCapacityForbidden
@@ -641,35 +268,7 @@ A：阿里云盘open 需要使用 **Aliyun Video Previewer**播放器，然后
A：代表帐号已经被冻结（以前都是直接无法登录），具体情况请查看顶部的红色内容注意事项
-:::
-
-## 5. The default download method used { lang="en" }
-
-## 5. 默认使用的下载方式 { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[302]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[local proxy]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-::: zh-CN
+## 5. 默认使用的下载方式
```mermaid
---
@@ -689,5 +288,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/autoindex.md b/pages/guide/drivers/autoindex.md
index a27866879..1b077a32e 100644
--- a/pages/guide/drivers/autoindex.md
+++ b/pages/guide/drivers/autoindex.md
@@ -1,46 +1,17 @@
---
-title:
- en: AutoIndex
- zh-CN: AutoIndex
-icon: iconfont icon-state
top: 350
categories:
- guide
- drivers
---
-::: en
-
-The AutoIndex driver is used to mount directory index pages built into HTTP servers, such as the [Nginx Source Index](https://nginx.org/download/) and [Redis Releases](https://download.redis.io/releases/).
-
-This driver essentially scrapes page information directly and requires manually specifying XPaths, making it suitable for scraping pages that are not directory index pages as well.
-
-:::
-
-::: zh-CN
+# AutoIndex
AutoIndex 驱动用于挂载 HTTP 服务器内置的目录索引页，如[Nginx Source Index](https://nginx.org/download/)、[Redis Releases](https://download.redis.io/releases/)。
该驱动本质上是直接爬取页面信息，需要手动填写 XPath，因此也可以用来爬取那些不是目录索引页的页面。
-:::
-
-## Setup Instructions { lang="en" }
-
-## 配置说明 { lang="zh-CN" }
-
-::: en
-
-- **URL:** The website address. If no scheme is included, `https://` will be automatically added. To mount a subpath, append it directly to the end of the URL. For example,
-:::
-
-### Web plugin { lang="en" }
-
-### 网页插件 { lang="zh-CN" }
-
-::: en
-
-The advantage of using a browser plug-in to modify is that it can be played directly online, of course, downloading is also possible.
-
-Example 1: If you really don’t know it, you can take a look at an example on the web page: **https://www.bilibili.com/video/BV1UA4y1X7J8**
-
-Example 2: Another plugin method covering 360, Chrome, Edge: **https://youtu.be/PP6b0WSzYMc**
-
-:::
-
-::: zh-CN
+### 网页插件
使用浏览器插件修改的好处是 可以直接在线播放，当然了下载也是可以的。
@@ -461,29 +202,9 @@ Example 2: Another plugin method covering 360, Chrome, Edge: **https://youtu.be/
例2：另一款插件方法涵盖360，Chrome，Edge： **https://youtu.be/PP6b0WSzYMc**
-:::
-
-### Aria2 { lang="en" }
-
-### Aria2 { lang="zh-CN" }
-
-::: en
-
-1. First follow the figure below to set the **`user-agent" `**, and then click the button option in the lower right corner, click ** gear ** (local settings) to configure the parameters well
-
- 
-
-2. Then open the third button option in the lower right corner (**Open the check box**), and then go to the list to select the file we want to download
-
-3. Select the files we need to download. After selecting, there will be a row of buttons. Select the second option on the right. One is sent to Aria2.
-
- If you use the webpage to modify the **`user-agent`**, you do not need to configure the `UA` of **Aria2**, and you can download it directly to Aria2
-
-:::
-
-::: zh-CN
+### Aria2
1. 先照着下图设置好 **`"User-Agent"`**，然后在**右下角**的按钮选项，点击**齿轮**(本地设置)，配置好参数
@@ -495,29 +216,7 @@ Example 2: Another plugin method covering 360, Chrome, Edge: **https://youtu.be/
如果你使用了网页修改 **`"User-Agent"`**，可以不配置 **Aria2** 的`UA`，直接推送到Aria2也能下载
-:::
-
-### Motrix { lang="en" }
-
-### Motrix { lang="zh-CN" }
-
-::: en
-
-1. First follow the figure below to set the **`user-agent" `**, and then click the button option in the lower right corner, click ** gear ** (local settings) to configure the parameters well
-
- 
-
-2. Then open the third button option in the lower right corner (**Open the check box**), and then go to the list to select the file we want to download
-
-3. Select the files we need to download. After selecting, there will be a row of buttons. Select the second option on the right. One is sent to Aria2.
-
- If you use the webpage to modify the **`user-agent`**, you do not need to configure the `UA` of **Motrix**, and you can download it directly to Aria2
-
-- Motrix Download link：[Motrix Official website](https://motrix.app/)，[Motrix-GitHub](https://github.com/agalwood/Motrix)
-
-:::
-
-::: zh-CN
+### Motrix
1. 先照着下图设置好 **`"User-Agent"`**，然后在**右下角**的按钮选项，点击**齿轮**(本地设置)，配置好参数
@@ -531,29 +230,8 @@ Example 2: Another plugin method covering 360, Chrome, Edge: **https://youtu.be/
- Motrix下载链接：[Motrix官网](https://motrix.app/)，[Motrix-GitHub](https://github.com/agalwood/Motrix)
-:::
-
-## Upload Config { lang="en" }
-
-## 上传配置 { lang="zh-CN" }
+## 上传配置
-::: en
-Official Documentation: [百度网盘开放平台 - 上传 - 能力说明](https://pan.baidu.com/union/doc/3ksg0s9ye)
-
-> ~~Baidu Netdisk requires that each slice be uploaded within 30 seconds, so excessively high concurrency during file uploads may result in a significant number of failures.~~
-> Currently (November 2025), Baidu Netdisk appears to have significantly relaxed the timeout limit for uploading slices.
-> Tests show that uploading single slice is now allowed to exceed 30 minutes.
-> Therefore, after extending the timeout duration, the failure rate for batch uploading large files should be greatly reduced (even if low upload bandwidth).
-
-- Upload Threads: The number of slices to upload concurrently.
-- Upload API: The domain endpoint used for uploading.
-- Use dynamic upload API: Dynamically fetch upload domain, generally can achieve maximum upload speed. When enabled, the `Upload API` setting will be used as a fallback if failed to get online. This is enabled by default.
-- Custom Upload Slice Size: Allows you to specify the size of each slice. Note that there are limitations, and this feature is available to VIPs only.
-- Low Bandwidth Upload Mode: Attempts to address the frequent `Client.Timeout exceeded while awaiting headers` errors encountered in low upload bandwidth scenarios (e.g., residential broadband). When enabled, it uses the smallest possible slice size.
-
-:::
-
-::: zh-CN
官方文档：[百度网盘开放平台 - 上传 - 能力说明](https://pan.baidu.com/union/doc/3ksg0s9ye)
> ~~百度网盘要求在 30s 内完成单个分片的上传，所以上传文件时并发过高可能会导致大量失败。~~
@@ -565,36 +243,7 @@ Official Documentation: [百度网盘开放平台 - 上传 - 能力说明](https
- 自定义上传分片大小：用于指定分片大小，有限制，仅会员可用
- 低带宽上传模式：尝试解决低上传带宽场景（如家宽）下，频繁出现 `Client.Timeout exceeded while awaiting headers` 的问题。开启后会使用尽可能小的分片大小。
-:::
-
-## The default download method used { lang="en" }
-
-## 默认使用的下载方式 { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[local proxy]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[302]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-
-::: zh-CN
+## 默认使用的下载方式
```mermaid
---
@@ -614,5 +263,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/baidu_photo.md b/pages/guide/drivers/baidu_photo.md
index 28723afcd..93fc7bb24 100644
--- a/pages/guide/drivers/baidu_photo.md
+++ b/pages/guide/drivers/baidu_photo.md
@@ -1,61 +1,22 @@
---
-title:
- en: Baidu Photo
- zh-CN: 一刻相册
-icon: iconfont icon-state
-# This control sidebar order
top: 689
-# A page can have multiple categories
categories:
- guide
- drivers
-# A page can have multiple tags
-tag:
- - Storage
- - Guide
- - '302'
-# this page is sticky in article list
-sticky: true
-# this page will appear in starred articles
-star: true
---
+# 一刻相册
+
## Cookie
-::: en
-Log in to [Baidu Photo](https://photo.baidu.com), open F12, and find any request containing the `Cookie` value. Copy it.
-:::
-
-::: zh-CN
登录 [一刻相册](https://photo.baidu.com) 打开F12随意找到一个携带 `Cookie` 值的请求进行复制就可以
-:::
-## Album ID { lang="en" }
-
-## 相薄ID { lang="zh-CN" }
-
-::: en
-
-**When left blank, all albums in the root directory are displayed by default.**
-
-If you want to mount a single album, fill in the following:
-
-- The **Album ID** should be: {album_id}|{tid}
- Example: `4021858707431029901|316519298447849660`
- - **{album_id}**: After entering the album you want to mount, check the top URL for the ID after `/album`. This is the **{album_id}**.
- - Example: [https://photo.baidu.com/photo/web/album/4021858707431029901](https://photo.baidu.com/photo/web/album/4021858707431029901)
- - **4021858707431029901** is the **{album_id}**
-
- - **{tid}**: Access [this link](https://photo.baidu.com/youai/album/v1/list?limit=1000) to obtain the **{tid}**
- - Once on the page, press `Ctrl+F` and search for the ID above. A few lines below you’ll find the corresponding **{tid}**.
+## 相薄ID
-:::
-
-::: zh-CN
**默认为空时,直接显示根目录全部相册.**
如果挂载单个相册时需填写如下内容
@@ -68,59 +29,15 @@ If you want to mount a single album, fill in the following:
- `{tid}`：访问 **https://photo.baidu.com/youai/album/v1/list?limit=1000** 获取
- 进入界面后`Ctrl+F`搜索上面的ID,在下面数几行就可以看到对应的 `{tid}`
-:::
-
-## Display Type { lang="en" }
-
-## 展示类型 { lang="zh-CN" }
-
-::: en
-Choose according to your needs.
-:::
+## 展示类型
-::: zh-CN
根据自己的需求选择
-:::
-## Delete Source Files { lang="en" }
+## 删除源文件
-## 删除源文件 { lang="zh-CN" }
-
-::: en
-By default, it only removes the album, not permanently deletes the files. If you enable this option, the files will be permanently deleted after removal. Be cautious when enabling this.
-:::
-
-::: zh-CN
默认只是移除相册，并非真正删除，如果开启此选项删除文件后将会彻底删除，谨慎开启
-:::
-
-## The default download method used { lang="en" }
-## 默认使用的下载方式 { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[302]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[local proxy]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-::: zh-CN
+## 默认使用的下载方式
```mermaid
---
@@ -140,5 +57,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/chaoxing.md b/pages/guide/drivers/chaoxing.md
index 51daf368c..c32bb1ea8 100644
--- a/pages/guide/drivers/chaoxing.md
+++ b/pages/guide/drivers/chaoxing.md
@@ -1,110 +1,37 @@
---
-title:
- en: ChaoxingxingGroupCloud
- zh-CN: 超星星小组盘
-icon: iconfont icon-state
-# This control sidebar order
top: 678
-# A page can have multiple categories
categories:
- guide
- drivers
-# A page can have multiple tags
-tag:
- - Storage
- - Guide
- - '本地代理'
-# this page is sticky in article list
-sticky: true
-# this page will appear in starred articles
-star: true
---
-
+# 超星星小组盘
-::: en
-chaoxingxing group cloud is also affiliated with chaoxingxing. After logging in to chaoxingxing, you can see a group under the left sidebar.
+
-Official website link：**https://i.chaoxing.com**
-:::
-::: zh-CN
超星星小组盘也是隶属于超星星，登录超星星后在左侧侧边栏下方能看到一个小组。
官网链接：**https://i.chaoxing.com**
-:::
-### Username Password { lang="en" }
+### 用户名 密码
-### 用户名 密码 { lang="zh-CN" }
-
-::: en
-chaoxingxing account and password
-:::
-::: zh-CN
超星星的帐号密码
-:::
-
-### Bbsid { lang="en" }
-### Bbsid { lang="zh-CN" }
+### Bbsid
-::: en
-Follow the example process below to obtain
-
-
-:::
-::: zh-CN
按照下面示例流程获取
-:::
-
-### Root Folder ID { lang="en" }
-### 根文件夹ID { lang="zh-CN" }
+### 根文件夹ID
-::: en
-The default is `-1`. For other subfolder ID acquisition methods, see the example below.
-
-- Search the keyword `getResourceList` in the request. For convenience, we can directly search `list` and see it. Then we enter the folder we need to mount. After entering the folder, we can find the `folder id by looking at the request.`
-
- 
-
-:::
-::: zh-CN
默认为`-1`，其它子文件夹ID获取方式看下图示例
- 在请求中搜索关键词`getResourceList`，为了方便我们可以直接搜索 `list`也可以看到，然后我们进入我们需要挂载的文件夹，进文件夹后再去看请求就可以找到`子文件夹ID`
-:::
-
-### The default download method used { lang="en" }
-
-### 默认使用的下载方式 { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- c1
- end
- c1[local proxy]:::someclass==default===>a2[user equipment]
- classDef someclass fill:#f96
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-::: zh-CN
+### 默认使用的下载方式
```mermaid
---
@@ -122,5 +49,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/chunk.md b/pages/guide/drivers/chunk.md
index 38059cc03..13de52d5b 100644
--- a/pages/guide/drivers/chunk.md
+++ b/pages/guide/drivers/chunk.md
@@ -1,72 +1,21 @@
---
-title:
- en: Chunk
- zh-CN: 分块（Chunk）
-icon: iconfont icon-state
top: 995
categories:
- guide
- drivers
-tag:
- - Storage
- - Guide
-sticky: true
-star: true
---
-::: en
-The Chunk is used to split large files into multiple file chunks. Each chunk is stored as an independent file on the backend driver.
+# 分块（Chunk）
-The size of each file chunk can be manually configured by the user. Except for the last chunk of each file—which is smaller than the configured size—all other chunks are always equal to the specified size.
-
-A chunked file is stored as a folder on the backend driver, containing all its chunks.
-
-:::
-
-::: zh-CN
分块驱动用于将大文件拆分为多个文件块，每个文件块以一个独立文件的形式存储在后端驱动上。
每个文件块的大小可由用户手动设定，除了每个文件的最后一个文件块的大小小于该设定值外，其余文件块的大小总是等于该设定值。
被分块的文件会以文件夹的形式存在于后端驱动上，文件夹内是该文件的所有分块。
-:::
-
-## Setup Instructions { lang="en" }
-
-## 配置说明 { lang="zh-CN" }
-
-::: en
-
-- **Remote path:** The real storage path of the chunked files. This path must be the root path or a subpath of another driver.
-- **Part size:** Maximum chunk size / Size of chunks except the last, in bytes.
-- **Chunk large file only:** Whether to only chunk files larger than Part size.
- - When disabled:
- 
- - When enabled:
- 
-- **Chunk prefix:** The prefix for the names of chunk folders stored on the backend driver, representing a chunked file. This is used to identify whether a folder is a regular folder or a chunked file storing folder, and therefore cannot be empty.
-- **Custom ext:** Custom suffix for chunk names, used to bypass limitations of certain drivers.
- - When left empty:
- - When setting to `.jpg`:
-
-::: warning TIP
-Once the driver is created, Custom ext should not be modified again, otherwise previously uploaded chunked files will become unrecognizable.
-
-If modification is necessary, you must manually change the suffix of all chunks on the backend driver afterward.
-:::
-
-::: en
-
-- **Store hash:** Whether to store the hashes of chunked files in the chunk folder as well.
- This feature does not actively compute hashes; it only stores the hashes that the file already carries when uploading.
-- **Num list workers:** When handling `List` requests, if a folder contains chunk folders, it is necessary to further list those chunk folders to retrieve information such as file size and hash value. Using multiple threads can speed up this process. A higher number of threads consumes more CPU and bandwidth resources but also increases speed. It is recommended to be disabled (set to 1) when the backend driver has API rate limiting.
-
-:::
-
-::: zh-CN
+## 配置说明
- **远程存储路径：** 分块后文件的真实存储路径，该路径必须是其它驱动的根路径或子路径。
- **分块大小：** 文件块的最大大小 / 除最后一个文件块外文件块的大小，单位：字节。
@@ -88,56 +37,12 @@ If modification is necessary, you must manually change the suffix of all chunks
如必须修改，修改后需要在后端驱动手动修改所有文件块的后缀名。
:::
-::: zh-CN
-
- **存储哈希值：** 是否在分块文件夹中同时存储完整文件的哈希值。
该功能不会主动计算文件的哈希值，只会存储文件在上传时就已经携带的哈希值。
- **列举分块文件夹线程数：** 处理`List`请求时，如果文件夹中有分块文件夹，需要继续列举分块文件夹以获取文件大小、哈希值等信息，此时使用多线程可以加速这一过程。线程数越大，消耗 CPU 和带宽资源越多，速度越快。后端驱动具有 API 限速时建议关闭（设为1）。
-:::
-
-## Use in combination with Crypt { lang="en" }
-
-## 与 Crypt 结合使用 { lang="zh-CN" }
-
-::: en
-If you need to both chunk and encrypt files, it is recommended to **encrypt first, then chunk**. Specifically, set Remote path of the [Crypt](/guide/drivers/crypt) driver to the mount path of the **Chunk** driver, and set Remote path of the **Chunk** driver to the actual storage path of the files.
-
-- Best practice:
-
-```mermaid
-graph LR
- File[Upload stream] --> Crypt
- Crypt --> Chunk
- Chunk -->|chunk1| Backend[Backend driver]
- Chunk -->|chunk2| Backend
- Chunk -->|chunk3| Backend
-```
-
-- Bad practice:
+## 与 Crypt 结合使用
-```mermaid
-graph LR
- File[Upload stream] --> Chunk
- Chunk -->|chunk1| Crypt1[Encryption algorithm]
- Chunk -->|chunk2| Crypt2[Encryption algorithm]
- Chunk -->|chunk3| Crypt3[Encryption algorithm]
- Crypt1 -->|encrypted chunk 1| Backend[Backend driver]
- Crypt2 -->|encrypted chunk 2| Backend
- Crypt3 -->|encrypted chunk 3| Backend
- subgraph Crypt
- Crypt1
- Crypt2
- Crypt3
- end
-```
-
-**Reason**: The bad practice involves storing a series of encryption metadata in each file chunk, which consumes more space. It also fails to guarantee that the chunks adhere to the user-specified maximum size, thereby undermining the purpose of file chunking.
-
-To perform emergency recovery on an encrypted file chunked according to the best practice, you simply need to concatenate all the chunks in order and then proceed with recovery.
-:::
-
-::: zh-CN
如果既需要对文件进行分块，又需要对文件进行加密，推荐**先加密后分块**，即将 [Crypt](/guide/drivers/crypt) 驱动的远程存储路径设为**分块**驱动的挂载路径，将**分块**驱动的远程存储路径设为文件真实存储路径。
- 正确实践：
@@ -172,49 +77,9 @@ graph LR
**原因**：错误实践的这种做法在每个文件块中都存储了一系列加密元信息，占用空间更多，也不能保证文件块具有用户给定的最大大小，失去了对文件分块的意义。
如果需要紧急恢复按推荐做法分块的加密文件，只需要按顺序直接拼接所有分块，再进行恢复即可。
-:::
-
-## Use in combination with Alias { lang="en" }
-
-## 与别名结合使用 { lang="zh-CN" }
-::: en
-If you need to store chunked files across multiple load-balanced drivers, you can combine this with the [Alias](/guide/drivers/alias) driver. For details, refer to [Load Balancing / Load balancing by file chunks](/guide/advanced/balance#load-balancing-by-file-chunks).
+## 与别名结合使用
-It's important to note that, unlike the approach used with Crypt, when combining with Alias, the process should be **chunk first, then load balance**. This means setting the Remote path of the **Chunk** driver to the mount path of the **Alias** driver, and setting the paths within the **Alias** driver to the actual file storage paths.
-
-- Best Practice:
-
-```mermaid
-graph LR
- File[Upload Stream] -->|File1| Chunk
- File -->|File2| Chunk
- Chunk -->|File1 Block1, File1 Block2, File1 Block3| Alias
- Chunk -->|File2 Block1, File2 Block2| Alias
- Alias -->|File1 Block3| D1[Backend Driver 1]
- Alias -->|File1 Block2| D2[Backend Driver 2]
- Alias -->|File1 Block1| D3[Backend Driver 3]
- Alias -->|File2 Block1| D1
- Alias -->|File2 Block2| D3
-```
-
-- Bad Practice:
-
-```mermaid
-graph LR
- File[Upload Stream] -->|File1| Alias
- File -->|File2| Alias
- Alias -->|File1| Chunk1[Chunk 1]
- Alias -->|File2| Chunk2[Chunk 2]
- Chunk1 -->|File1 Block1| D1[Backend Driver 1]
- Chunk1 -->|File1 Block2| D1
- Chunk1 -->|File1 Block3| D1
- Chunk2 -->|File2 Block1| D2[Backend Driver 2]
- Chunk2 -->|File2 Block2| D2
-```
-
-:::
-::: zh-CN
如果需要将分块后的文件在多个负载均衡驱动上存储，可以与[别名](/guide/drivers/alias)结合使用，详见[负载均衡 / 按文件块负载均衡](/guide/advanced/balance#按文件块负载均衡)。
需要注意的是，与结合 Crypt 使用的方案不同，与别名结合使用时，应**先分块后负载均衡**，即将**分块**驱动的远程存储路径设为**别名**驱动的挂载路径，将**别名**驱动的路径设为文件真实存储路径。
@@ -248,5 +113,3 @@ graph LR
Chunk2 -->|文件2块1| D2[后端驱动 2]
Chunk2 -->|文件2块2| D2
```
-
-:::
diff --git a/pages/guide/drivers/cloudflare-imgbed.md b/pages/guide/drivers/cloudflare-imgbed.md
index f85ace542..85cd90341 100644
--- a/pages/guide/drivers/cloudflare-imgbed.md
+++ b/pages/guide/drivers/cloudflare-imgbed.md
@@ -1,175 +1,67 @@
---
-title:
- en: CloudFlare-ImgBed
- zh-CN: CloudFlare 图床
-icon: iconfont icon-state
top: 700
categories:
- guide
- drivers
---
-
+# CloudFlare 图床
-## 免责声明 { lang="zh-CN" }
+
-## Disclaimer { lang="en" }
+## 免责声明
-::: zh-CN
::: warning
本驱动仅提供与 CloudFlare-ImgBed 后端交互的接口，不对该图床程序本身及其存储渠道的可用性、稳定性负责。
用户需自行决定并配置所使用的存储渠道（如 Cloudflare R2、HuggingFace、S3、Telegram 等），并应严格遵守相关平台及服务提供商的服务条款与使用政策。请勿利用此驱动进行任何违反法律法规、侵犯他人权益或滥用平台资源（如大量消耗免费额度、违规存储分发受版权保护的内容等）的行为。
因用户配置不当、违反平台政策或滥用服务而导致的一切后果（包括但不限于账号封禁、数据丢失、服务中断等），均由用户自行承担，与 OpenList 及其开发者无关。
:::
-::: en
-::: warning
-This driver only provides an interface to interact with the CloudFlare-ImgBed backend and is not responsible for the availability and stability of the image hosting program itself or its storage channels.
-Users are solely responsible for determining and configuring the storage channels used (e.g., Cloudflare R2, HuggingFace, S3, Telegram) and must strictly comply with the Terms of Service and acceptable use policies of the relevant platforms and service providers. Do not use this driver for any illegal activities, rights infringement, or abuse of platform resources (e.g., excessive consumption of free quotas, illegal storage/distribution of copyrighted content).
-All consequences arising from improper configuration, violation of platform policies, or service abuse (including but not limited to account suspension, data loss, service interruption, etc.) shall be borne by the user. OpenList and its developers shall not be held liable.
-:::
-## 1. 准备工作 { lang="zh-CN" }
+## 1. 准备工作
-## 1. Preparation { lang="en" }
-
-::: zh-CN
配置该驱动前，需要先部署你自己的 CloudFlare-ImgBed 后端。
项目地址：[MarSeventh/CloudFlare-ImgBed](https://github.com/MarSeventh/CloudFlare-ImgBed)
部署完成后，登录后端管理面板（`https://你的域名/dashboard`），并在系统设置中确保至少配置了一个存储渠道（如 HuggingFace、Cloudflare R2、S3、Telegram 等）。
-:::
-::: en
-Before configuring this driver, you need to deploy your own CloudFlare-ImgBed backend.
-Project address: [MarSeventh/CloudFlare-ImgBed](https://github.com/MarSeventh/CloudFlare-ImgBed)
-After deployment, log in to the backend dashboard (`https://your-domain/dashboard`), and ensure that at least one storage channel (e.g., HuggingFace, Cloudflare R2, S3, Telegram) is configured in the system settings.
-:::
-## 2. 在 OpenList 中添加 { lang="zh-CN" }
+## 2. 在 OpenList 中添加
-## 2. Add in OpenList { lang="en" }
+### 挂载路径
-### 挂载路径 { lang="zh-CN" }
-
-### Mount Path { lang="en" }
-
-::: zh-CN
填入你希望挂载到的路径，例如 `/imgbed`。
-:::
-::: en
-Enter the path you want to mount to, for example `/imgbed`.
-:::
-
-### 根目录路径 { lang="zh-CN" }
-### Root Folder Path { lang="en" }
+### 根目录路径
-::: zh-CN
默认为 `/`，留空即可。
-:::
-::: en
-Default is `/`, can be left empty.
-:::
-
-### 后端 API 地址 { lang="zh-CN" }
-### Address { lang="en" }
+### 后端 API 地址
-::: zh-CN
填入你部署的图床服务地址，例如 `https://img.example.com`。无需在末尾添加 `/`。
-:::
-::: en
-Enter the address of your deployed image hosting service, e.g., `https://img.example.com`. No need to add `/` at the end.
-:::
-
-### 认证令牌 { lang="zh-CN" }
-### Token { lang="en" }
+### 认证令牌
-::: zh-CN
填入图床后端系统设置中生成的 API Token。
-:::
-::: en
-Enter the API Token generated in the backend system settings.
-
-:::
-
-### 普通文件渠道名称 { lang="zh-CN" }
-### Small Channel Name { lang="en" }
+### 普通文件渠道名称
-::: zh-CN
通常用于上传小于 20MB 的文件。填入你在图床后端配置的渠道名称（如 `my cfr2`、`my telegram` 等）。
-:::
-::: en
-Typically used for uploading files smaller than 20MB. Enter the channel name configured in your backend (e.g., `my cfr2`, `my telegram`).
-:::
-
-### 大文件渠道名称 { lang="zh-CN" }
-### Large Channel Name { lang="en" }
+### 大文件渠道名称
-::: zh-CN
用于上传大于 20MB 的文件。建议配置支持大文件的渠道（如 `huggingface`）。留空则大文件会回退到普通渠道上传。
-:::
-::: en
-Used for uploading files larger than 20MB. It is recommended to configure a channel that supports large files (e.g., `huggingface`). If left blank, large files will fall back to the small channel for upload.
-:::
-
-### 大文件渠道类型 { lang="zh-CN" }
-
-### Large Channel Type { lang="en" }
+### 大文件渠道类型
-::: zh-CN
根据大文件渠道选择对应的类型：
- `huggingface`：使用 HuggingFace LFS 直传（支持秒传和分片）
- `telegram` / `cfr2` / `s3` / `discord`：使用图床后端的分片上传接口
- :::
- ::: en
- Select the corresponding type based on your large file channel:
-- `huggingface`: Uses HuggingFace LFS direct upload (supports instant upload and chunking)
-- `telegram` / `cfr2` / `s3` / `discord`: Uses the backend chunked upload API
- :::
-### 上传线程数 { lang="zh-CN" }
+### 上传线程数
-### Upload Thread { lang="en" }
-
-::: zh-CN
HuggingFace 分片直传的并发线程数，默认为 `3`，最大为 `32`。网络条件好时可适当增大。
-:::
-::: en
-Concurrent thread count for HuggingFace chunked direct upload, default is `3`, max is `32`. Can be increased if network conditions are good.
-:::
-## 默认使用的下载方式 { lang="zh-CN" }
-
-## The default download method used { lang="en" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[302]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[local proxy]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-::: zh-CN
+## 默认使用的下载方式
```mermaid
---
@@ -189,5 +81,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/cloudreve.md b/pages/guide/drivers/cloudreve.md
index 7f1595127..ead05ef3b 100644
--- a/pages/guide/drivers/cloudreve.md
+++ b/pages/guide/drivers/cloudreve.md
@@ -1,57 +1,20 @@
---
-title:
- en: Cloudreve V3
- zh-CN: Cloudreve V3
-icon: iconfont icon-state
-# This control sidebar order
top: 498
-# A page can have multiple categories
categories:
- guide
- drivers
-# A page can have multiple tags
-tag:
- - Storage
- - Guide
- - '本地代理'
- - '302'
-# this page is sticky in article list
-sticky: true
-# this page will appear in starred articles
-star: true
---
-## Parameters { lang="en" }
+# Cloudreve V3
-## 参数说明 { lang="zh-CN" }
+## 参数说明
-### Address { lang="en" }
+### 地址
-### 地址 { lang="zh-CN" }
-
-::: en
-The address of the Cloudreve V3 server, such as: `https://www.example.com`. It is better to remove the slash `/` after it.
-:::
-::: zh-CN
Cloudreve V3 服务器的地址，如：`https://www.example.com`，最好删掉后面的斜线`/`。
-:::
-
-### Authentication { lang="en" }
-
-### 鉴权 { lang="zh-CN" }
-
-::: en
-Cloudreve V3 supports authentication using Cookie. The mounting authentication methods are divided into:
-1. `Username` + `Password`: Automatically uses the login interface to obtain Cookie, there might be issues with CAPTCHA.
-2. `Cookie` Only: Can be temporarily used but will expire and cannot be renewed. Parameters can be found from browser requests or Local Storage.
-3. [Reference](../drivers/common.html#Reference): Fill in `ref:/{mount path}` in `Remark`: Reference authentication, tokens, etc., from "Mounted Storage".
+### 鉴权
-::: tip Steps to get cookie:
-Only the string following cloudreve-session= is required.
-:::
-
-::: zh-CN
Cloudreve V3 使用 Cookie 进行鉴权，这意味着挂载鉴权方式分为：
1. `用户名`+`密码`：会自动使用登录接口获取 Cookie，存在验证码问题
@@ -64,55 +27,20 @@ Cloudreve V3 使用 Cookie 进行鉴权，这意味着挂载鉴权方式分为
-### Root Folder Path { lang="en" }
-
-### 根文件夹路径 { lang="zh-CN" }
+### 根文件夹路径
-::: en
-Default is `/`, which can be obtained from the `?path=` in the web link. The obtained parameters may need to be [URL decoded](https://www.google.com/search?q=URL+decode).
-:::
-::: zh-CN
默认为：`/`，可从网页链接的 `?path=` 中获取。获取到的参数可能需要 [URL 解码](https://www.bing.com/search?q=URL+%E8%A7%A3%E7%A0%81)。
-:::
-### Enable Folder Size { lang="en" }
+### 启用缩略图和文件夹大小
-### 启用缩略图和文件夹大小 { lang="zh-CN" }
-
-::: en
-Enable Cloudreve V3 server to calculate the size of each folder and generate thumbnails for each file. Enabling this feature may cause server errors or slow performance, and it is `disabled` by default.
-:::
-::: zh-CN
让 Cloudreve V3 服务端统计每个文件夹的大小并为每个文件生成略缩图，启用可能会造成服务端报错、运行缓慢，默认禁用。
-:::
-### Custom UA { lang="en" }
+### 自定义 UA
-### 自定义 UA { lang="zh-CN" }
-
-::: en
-Used to customize the `User-Agent` header information used in requests. Leaving it blank will use OpenList default settings.
-:::
-::: zh-CN
用于自定义请求使用的 `User-Agent` 头部信息。留空为 OpenList 默认。
-:::
-## Upload { lang="en" }
-
-## 上传 { lang="zh-CN" }
-
-::: en
-The supported storage policies for uploading are as follows:
-
-- Local storage
-- Slave storage
-- OneDrive
-- S3
+## 上传
-Upload storage policies can be set within Cloudreve V4 web interface by entering the corresponding folder (requires the server to be Cloudreve Pro).
-:::
-
-::: zh-CN
支持上传到的存储策略如下：
- 本机存储
@@ -121,35 +49,8 @@ Upload storage policies can be set within Cloudreve V4 web interface by entering
- S3
上传的存储策略请在 Cloudreve V3 网页端进入相应文件夹中进行设置（需要服务端为 Cloudreve Pro）。
-:::
-## The default download method used { lang="en" }
-
-## 默认使用的下载方式 { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[302]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[local proxy]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-::: zh-CN
+## 默认使用的下载方式
```mermaid
---
@@ -169,5 +70,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/cloudreve_v4.md b/pages/guide/drivers/cloudreve_v4.md
index 3a3d87773..5c99c780e 100644
--- a/pages/guide/drivers/cloudreve_v4.md
+++ b/pages/guide/drivers/cloudreve_v4.md
@@ -1,48 +1,20 @@
---
-title:
- en: Cloudreve V4 / Share
- zh-CN: Cloudreve V4 / 分享
-icon: iconfont icon-state
-# This control sidebar order
top: 497
-# A page can have multiple categories
categories:
- guide
- drivers
-# A page can have multiple tags
---
-## Parameter Explanation { lang="en" }
+# Cloudreve V4 / 分享
-## 参数说明 { lang="zh-CN" }
+## 参数说明
-### Address { lang="en" }
+### 地址
-### 地址 { lang="zh-CN" }
-
-::: en
-The address of the Cloudreve V4 server, such as: `https://www.example.com`. It is better to remove the slash `/` after it.
-:::
-::: zh-CN
Cloudreve V4 服务器的地址，如：`https://www.example.com`，最好删掉后面的斜线`/`。
-:::
-
-### Authentication { lang="en" }
-
-### 鉴权 { lang="zh-CN" }
-
-::: en
-Cloudreve V4 supports authentication using Token. The mounting authentication methods are divided into:
-1. `Username` + `Password`: Automatically uses the login interface to obtain Access Token and Refresh Token, there might be issues with CAPTCHA.
-2. `Refresh Token` Only: Automatically uses the refresh interface to renew Access Token and Refresh Token, parameters can be found from browser requests or Local Storage.
-3. `Access Token` Only: Can be temporarily used but will expire and cannot be renewed.
-4. None: Anonymous user, suitable for public sharing.
-5. [Reference](../drivers/common.html#reference): Fill in `ref:/{mount path}` in `Remark`: Reference authentication, tokens, etc., from "Mounted Storage".
+### 鉴权
-:::
-
-::: zh-CN
Cloudreve V4 使用 Token 进行鉴权，这意味着挂载鉴权方式分为：
1. `用户名`+`密码`：会自动使用登录接口获取 Access Token 和 Refresh Token，存在验证码问题
@@ -51,179 +23,65 @@ Cloudreve V4 使用 Token 进行鉴权，这意味着挂载鉴权方式分为：
4. 无：匿名用户，适用于公开分享
5. [引用](../drivers/common.html#引用)：`备注`填写 `ref:/{挂载路径}`，从 `已挂载的存储` 中引用认证、令牌等
-:::
-
-### Steps to get tokens { lang="en" }
-
-### Token 获取方法 { lang="zh-CN" }
+### Token 获取方法
-#### From Local Storage { lang="en" }
+#### 本地存储
-#### 本地存储 { lang="zh-CN" }
-
-::: en
-::: tip
-There may be multiple sessions; please select the one you want to mount.
-:::
-::: zh-CN
::: tip
可能有多个会话，请选择要挂载的那个。
:::
-::: en
-
-:::
-
-::: zh-CN
-:::
-
-#### From Network { lang="en" }
-#### 浏览器请求 { lang="zh-CN" }
-
-::: en
-::: tip
-You may need to log in anew to see this request.
-:::
+#### 浏览器请求
-::: zh-CN
::: tip
可能需要全新登录才能看到这个请求。
:::
-::: en
-
-:::
-::: zh-CN
-
-:::
-### Root Folder Path { lang="en" }
+
-### 根文件夹路径 { lang="zh-CN" }
+### 根文件夹路径
-::: en
-Cloudreve V4 uses a custom URI as the path, which can be obtained from the `?path=` in the web link. The obtained parameters may need to be [URL decoded](https://www.google.com/search?q=URL+decode).
-:::
-::: zh-CN
Cloudreve V4 采用自定义 URI 作为路径。可从网页链接的 `?path=` 中获取。获取到的参数可能需要 [URL 解码](https://www.bing.com/search?q=URL+%E8%A7%A3%E7%A0%81)。
-:::
-
-#### Mounting My Files { lang="en" }
-#### 挂载「我的文件」 { lang="zh-CN" }
+#### 挂载「我的文件」
-::: en
-Default is `cloudreve://my/`, listing user files.
-:::
-::: zh-CN
默认为 `cloudreve://my/`，列出用户文件。
-:::
-#### Mounting Share { lang="en" }
+#### 挂载「分享」
-#### 挂载「分享」 { lang="zh-CN" }
-
-::: en
-Supports mounting folder-type shares, the path should be filled as: `cloudreve://{ShareID}@share/`.
-
-- ShareID is the parameter after `/s/` in the share link.
-- Currently, Cloudreve V4 does not support creating password-protected shares. However, if the data is migrated from V3, the previously created sharing password will be retained. The URI of the share link with the password (`/s/{shareID}/{sharePassword}`) is `cloudreve://{shareID}:{sharePassword}@share`.
-
-:::
-
-::: zh-CN
支持挂载文件夹类型的分享，路径填写为：`cloudreve://{分享ID}@share/`。
- 分享ID为分享链接 `/s/` 后面的参数。
- 目前 Cloudreve V4 不支持「创建带密码的分享」。但如果数据迁移自 V3，先前创建的分享密码会被保留。带密码的分享链接（`/s/{分享ID}/{分享密码}`），对应的 URI 为 `cloudreve://{分享ID}:{分享密码}@share`。
-:::
-
-### Enable Folder Size { lang="en" }
-
-### 启用文件夹大小 { lang="zh-CN" }
+### 启用文件夹大小
-::: en
-Enable Cloudreve V4 server to calculate the size of each folder. Enabling this feature may cause server errors or slow performance, and it is `disabled` by default.
-:::
-::: zh-CN
让 Cloudreve V4 服务端统计每个文件夹的大小，启用可能会造成服务端报错、运行缓慢，默认禁用。
-:::
-### Enable Thumbnails { lang="en" }
+### 启用缩略图
-### 启用缩略图 { lang="zh-CN" }
-
-::: en
-Enable Cloudreve V4 server to generate thumbnails for each file. Enabling this feature may cause server errors or slow performance, and it is `disabled` by default.
-:::
-::: zh-CN
让 Cloudreve V4 服务端为每个文件生成略缩图，启用可能会造成服务端报错、运行缓慢，默认禁用。
-:::
-### Enable Version Upload { lang="en" }
+### 启用版本上传
-### 启用版本上传 { lang="zh-CN" }
-
-::: en
-Enable overwrite upload and keep the previous version, which consumes extra space. Disabled by default, delete the existing file before overwriting upload.
-:::
-::: zh-CN
启用覆盖上传并保留之前的版本，需要消耗额外的空间。默认禁用，为覆盖上传前删除已有的文件。
-:::
-### Custom UA { lang="en" }
+### 自定义 UA
-### 自定义 UA { lang="zh-CN" }
-
-::: en
-Used to customize the `User-Agent` header information used in requests. Leaving it blank will use OpenList default settings.
-:::
-::: zh-CN
用于自定义请求使用的 `User-Agent` 头部信息。留空为 OpenList 默认。
-:::
-### Sorting { lang="en" }
+### 排序
-### 排序 { lang="zh-CN" }
-
-::: en
-Supports changing the sorting parameters when requesting lists.
-:::
-::: zh-CN
支持更改请求列表时排序的参数。
-:::
-
-### Hide files currently being uploaded { lang="en" }
-### 隐藏正在上传中的文件 { lang="zh-CN" }
+### 隐藏正在上传中的文件
-::: en
-Filter files with upload sessions (in progress) based on metadata information, size 0, unable to download
-:::
-::: zh-CN
根据 Metadata 信息进行过滤带有上传会话（上传中）的文件，大小为 0，无法下载
-:::
-
-## Upload { lang="en" }
-
-## 上传 { lang="zh-CN" }
-
-::: en
-The supported storage policies for uploading are as follows:
-
-- Local storage
-- Slave storage
-- OneDrive
-- S3
-- KS3
-Upload storage policies can be set within Cloudreve V4 web interface by entering the corresponding folder (requires the server to be Cloudreve Pro).
+## 上传
-If upload permissions are enabled for shares, uploads are supported. It requires the server to check "Enhance anonymous user permissions" for the user group (requires the server to be Cloudreve Pro).
-:::
-::: zh-CN
支持上传到的存储策略如下：
- 本机存储
@@ -235,35 +93,8 @@ If upload permissions are enabled for shares, uploads are supported. It requires
上传的存储策略请在 Cloudreve V4 网页端进入相应文件夹中进行设置（需要服务端为 Cloudreve Pro）。
如果分享开启了上传权限，支持上传。需要服务端为用户组勾选「提升匿名用户权限」（需要服务端为 Cloudreve Pro）。
-:::
-
-## The default download method used { lang="en" }
-
-## 默认使用的下载方式 { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[302]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[local proxy]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-:::
-::: zh-CN
+## 默认使用的下载方式
```mermaid
---
@@ -283,5 +114,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/cnb_releases.md b/pages/guide/drivers/cnb_releases.md
index b1ce2edde..33cc7c1e7 100644
--- a/pages/guide/drivers/cnb_releases.md
+++ b/pages/guide/drivers/cnb_releases.md
@@ -1,30 +1,16 @@
---
-title:
- en: CNB Releases
- zh-CN: CNB 发行版
categories:
- guide
- drivers
top: 397
---
-https://cnb.cool/
-
-## Known issues { lang="en" }
+# CNB 发行版
-## 已知问题 { lang="zh-CN" }
-
-::: en
-CNB releases are not a standard file system and have some unresolved issues. Please do not submit feedback for these.
+https://cnb.cool/
-1. An empty repository needs to be initialized first.
-2. Subdirectories are not supported under Tag / Release directories.
-3. The OpenAPI upload returns `expires_in_sec` as only 10 seconds. Uploading large files may time out; after time out, the upload continues but returns `invalid token`. Therefore, a local timeout mechanism is added to automatically stop uploading when the set time is reached, avoiding failed uploads and wasted bandwidth.
-4. `Move`, `Copy`, and `Rename` operations are not supported.
-5. Only when `UseTagName` is disabled, renaming can be done by modifying the Release name.
+## 已知问题
-:::
-::: zh-CN
CNB 发行版非正常文件系统，存在一些无法解决的问题，请勿反馈。
1. 空仓库需要先初始化
@@ -33,84 +19,27 @@ CNB 发行版非正常文件系统，存在一些无法解决的问题，请勿
4. 不支持 `移动`、`复制`、`重命名` 操作
5. 仅支持在关闭 `使用Tag名称` 时，通过修改 Release 的名称进行重命名
-:::
-
-## Parameters { lang="en" }
-
-## 参数 { lang="zh-CN" }
-
-### Repo { lang="en" }
+## 参数
-### 仓库 { lang="zh-CN" }
+### 仓库
-::: en
-Only one repository can be specified. To reuse a token, please use the [Reference](common.md#reference) feature.
-:::
-::: zh-CN
仅支持填写一个仓库。如需复用 Token，请使用 [引用](common.md#引用) 功能。
-:::
-### Token { lang="en" }
+### 访问令牌
-### 访问令牌 { lang="zh-CN" }
-
-::: en
-Access token. No need to include `Bearer`. Supports the [Reference](common.md#reference) feature.
-
-How to obtain: After logging in, go to `Personal Settings` - [Access Token](https://cnb.cool/profile/token) -> `Add Access Token`.
-
-For listing, grant the `repo-code:r` permission. For modifications, grant the `repo-code:rw` permission.
-:::
-::: zh-CN
访问令牌。无需填写 `Bearer`。支持 [引用](common.md#引用) 功能。
获取方法：登录后，进入 `个人设置` - [访问令牌](https://cnb.cool/profile/token) -> `添加访问令牌`。
对于获取列表，需授予 `repo-code:r` 权限。对于修改，需授予 `repo-code:rw` 权限。
-:::
-
-### UseTagName { lang="en" }
-### 使用Tag名称 { lang="zh-CN" }
+### 使用Tag名称
-::: en
-Use the original Tag name instead of the Release name.
-
-By default, this is disabled and the Release name is used, which supports renaming. Tag names cannot be changed once created. When creating a new folder for the first time, a Tag with the folder name will be published. Renaming an existing Release will modify the Release name.
-:::
-::: zh-CN
使用原始的 Tag 名称而不是 Release 名称。
默认关闭，使用 Release 名称，支持重命名。Tag 名称创建后无法更改。首次新建文件夹，会发布名为文件夹名称的 Tag，重命名已经存在的 Release，会修改 Release 的名称。
-:::
-
-## The default download method used { lang="en" }
-
-## 默认使用的下载方式 { lang="zh-CN" }
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[302]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[local proxy]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-::: zh-CN
+## 默认使用的下载方式
```mermaid
---
@@ -130,5 +59,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/common.md b/pages/guide/drivers/common.md
index 18e83d227..8c96ecac9 100644
--- a/pages/guide/drivers/common.md
+++ b/pages/guide/drivers/common.md
@@ -1,52 +1,20 @@
---
-title:
- en: Common
- zh-CN: 通用项
-icon: iconfont icon-state
-# This control sidebar order
top: 1000
-# A page can have multiple categories
categories:
- guide
- drivers
-# A page can have multiple tags
-tag:
- - Storage
- - Guide
-# this page is sticky in article list
-sticky: true
-# this page will appear in starred articles
-star: true
---
-## Mount Path { lang="en" }
+# 通用项
-## 挂载路径 { lang="zh-CN" }
+## 挂载路径
-::: en
-The unique identifier for the mount point, the name displayed externally, and the location where it should be mounted. If you want to mount it to the root directory, please enter `/`.
-:::
-
-::: zh-CN
挂载项的唯一标识，对外展示的名称，要挂载到的位置。如果要挂载到根目录，请填写 `/`。
-:::
-::: en
-::: danger
-You cannot use duplicate mount path names, otherwise, the following error will occur:
-
-```json
-Failed to create storage in database: UNIQUE constraint failed: x_storages.mount_path
-```
-
-Solution: Use [aliases](./alias.md) to aggregate multiple mount points.
-:::
-
-::: zh-CN
::: danger
不能使用重复的挂载路径名称，否则会报错：
@@ -57,18 +25,6 @@ Failed create storage in database: UNIQUE constraint failed: x_storages.mount_pa
解决方法：使用 [别名](./alias.md) 对多个挂载项目进行聚合。
:::
-::: en
-::: danger
-The mount path name is a required field and cannot be left empty, or the following error will occur:
-
-```json
-Key: 'Storage.MountPath' Error: Field validation for 'MountPath' failed on the 'required' tag
-```
-
-Solution: If you want to mount to the root directory, please enter `/`.
-:::
-
-::: zh-CN
::: danger
挂载路径名称是必填项，不能为空，否则会报错：
@@ -79,49 +35,16 @@ Key: 'Storage.MountPath' Error:Field validation for 'MountPath' failed on the 'r
解决方案：如果要挂载到根目录，请填写 `/`。
:::
-## Order { lang="en" }
+## 序号
-## 序号 { lang="zh-CN" }
-
-::: en
-When mounting multiple drives, this is used for sorting. The smaller the number, the further to the front. Negative numbers can also be used.
-:::
-::: zh-CN
当挂载多个驱动时，用于排序。越小越靠前。可以填写负数。
-:::
-
-## Remark { lang="en" }
-## 备注 { lang="zh-CN" }
+## 备注
-::: en
-You can add notes for easier management.
-:::
-::: zh-CN
您可以添加备注，以方便管理。
-:::
-
-### Reference { lang="en" }
-
-### 引用 { lang="zh-CN" }
-
-::: en
-Reference authentication, tokens, etc., from the **"Mounted Storage"** to enable sharing the same token between multiple cloud drives.
-
-Currently, the following cloud drives are supported:
-
-- 139Yun
-- AliyundriveOpen
-- 189CloudPC
-- 123PanShare（ref 123Pan）
-- Cloudreve V3 / V4
-
-**How to use**: In the storage settings, set the first line of **Remark** to: **ref:/mount_path**
-**Important**: `ref:/` should be in lowercase letters and symbols.
-:::
+### 引用
-::: zh-CN
从 `已挂载的存储` 中引用认证、令牌等，实现同一个 Token 多个网盘使用。
目前支持如下网盘：
@@ -135,91 +58,30 @@ Currently, the following cloud drives are supported:
**使用方法**：在存储设置中将`备注(Remark)`的第一行设置为：**ref:/挂载路径**
**注意事项**：`ref:/` 为小写英文和符号
-:::
-## Enable signing { lang="en" }
-
-## 启用签名 { lang="zh-CN" }
+## 启用签名
-::: en
-Sign and encrypt files (no password required), only valid for this driver, if other signatures are not enabled and `signature all` and `meta-information encryption` are not set, others will not be signed.
-
-Usage scenario: I don't want to enable all signatures, and I don't want to set metadata encryption. I just want to sign and encrypt a certain driver to prevent it from being scanned.
-
-Scope of influence: `Settings-->Global-->Signature All` > `Metainformation Directory Encryption` > `Single Driver Signature`.
-:::
-::: zh-CN
对文件进行签名加密(不会需要密码)，仅对本驱动生效，如果别的没启用签名也没设置`签名全部`和`元信息加密`其他的不会进行签名。
使用场景：不想开启全部签名，也不想设置元信息加密，只想对某驱动进行签名加密防止被扫。
影响范围：`设置-->全局-->签名所有` > `元信息目录加密` > `单驱动签名`
-:::
-## Disable index { lang="en" }
+## 禁用索引
-## 禁用索引 { lang="zh-CN" }
-
-::: en
-Allow users to disable storage indexing.
-
-- For example, if you enable `Ignore Index` in the index options, you no longer need to configure it after enabling `Disable Index`, which is more convenient.
-
-:::
-
-::: zh-CN
允许用户禁用存储索引。
- 例如索引选项中的`忽略索引`，启用`禁用索引`后不需要再去配置了，这样也更方便一些
-:::
-
-## Cache Expiration { lang="en" }
-
-## 缓存过期 { lang="zh-CN" }
+## 缓存过期
-::: en
-Cache time of directory structure.
-:::
-::: zh-CN
目录结构的缓存时间。
-:::
-## Custom Cache Policies { lang="en" }
-
-## 自定义缓存策略 { lang="zh-CN" }
-
-::: en
-
-Cache time for directory paths (in minutes).
-
-You can customize the cache time for specific file paths using pattern matching. The configuration supports wildcard patterns:
-
-- `*` matches a **single** directory level.
-- `**` matches **multiple** directory levels.
-
-Example configuration:
-
-```txt
-/Series/Completed/*:60
-/Series/Updating/*/**:10
-/Series/Archived/**:30
-```
+## 自定义缓存策略
-Explanation:
-
-- `*` matches only a single directory level. Items directly under `/Series/Completed` will be cached for 60 minutes. This does **not** include deeper subdirectories — for example, `/Series/Completed/A/B` will not match this rule.
-- `**` matches multiple directory levels. Therefore, the contents of subdirectories under `/Series/Updating` will be cached for 10 minutes. For example, `/Series/Updating/A/B` and `/Series/Updating/C/D` will match.
-- The pattern `/Series/Updating/*/**` enforces a “single level followed by multi-level” match. As a result, directories directly under `/Series/Updating` will **not** be matched by this rule.
-- All contents under `/Series/Archived` (including any depth of subdirectories) will be cached for 30 minutes.
-
-:::
-
-::: zh-CN
-
-目录路径缓存时间（单位：分钟）。
+目录路径缓存时间（单位：分钟）。
可以通过模式匹配来自定义某些文件路径的缓存时间。配置支持通配符：
@@ -240,31 +102,11 @@ Explanation:
- `**` 匹配多层目录，因此 `/剧集/更新中` 下级目录的内容会被缓存 10 分钟。例如 `/剧集/更新中/A/B` 和 `/剧集/更新中/C/D` 都会符合该规则。
- 由于 `/剧集/更新中/*/**` 严格设置了模糊匹配单层目录，所以直属于 `/剧集/更新中` 下都目录将不会命中规则。
- `/剧集/归档` 下的内容（包括任意层级的子目录）都会被缓存 30 分钟。
-:::
-
-## Web proxy { lang="en" }
-## Web 代理 { lang="zh-CN" }
+## Web 代理
-::: en
-Whether the web preview,download and the direct link go through the transfer. If you open this, recommended you set [site_url](../../configuration/configuration.md#site-url) so that OpenList can works fine.
-:::
-::: zh-CN
网页预览、下载和直接链接是否通过中转。如果你打开此项，建议你设置[site_url](../../configuration/configuration.md#site-url)，以帮助OpenList更好的工作。
-:::
-::: en
-::: tip
-
-- **Web proxy Strategies:** It is a strategy when using the webpage. The default is a local agent. If you fill in the proxy URL and enable the web agent to use the proxy URL
-- **Webdav policy Strategies:** It is an option to use the webdav function
- - If there are 302 options default to 302, if there is no 302 option default to the local agent, if you want to use the agent URL, please fill in and manually switch to the proxy URL strategy
-
-The two are different configurations.
-
-:::
-
-::: zh-CN
::: tip
- **Web代理**：是使用网页时候的策略，默认为本地代理，如果填写了代理URL并且启用了Web代理使用的是代理URL
@@ -275,22 +117,7 @@ The two are different configurations.
:::
-## Webdav policy { lang="en" }
-
-## WebDAV 策略 { lang="zh-CN" }
-
-::: en
-
-- **302 redirect:** redirect to the real link
- - Although it does not consume traffic, it is not recommended to share and use it.
-- **use proxy URL:** redirect to proxy URL
- - It will consume the traffic of the agent URL
-- **native proxy:** return data directly through local transit(best compatibility)
- - The traffic of the construction of OpenList device will consume
-
-:::
-
-::: zh-CN
+## WebDAV 策略
- **302 重定向**：重定向到真实链接
- 虽然不会消耗流量，但是不建议共享使用，有封禁账户的风险
@@ -299,33 +126,7 @@ The two are different configurations.
- **本机代理**：直接通过本地中转返回数据（最佳兼容性）
- 会消耗搭建OpenList设备的流量
-:::
-
-### Description of three modes { lang="en" }
-
-### 三种模式说明 { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: 302 redirect, use proxy URL, native proxy
----
-flowchart LR
- E(User operation OpenList calls API
triggers related API operations Cloud Drive
Cloud Drive receives command and begins execution) - A[(Cloud Drive)] - B(You) - C[Use proxy URL] - D{Native proxy} - E==>A==>E - A==>|Directly transferring from cloud drive to you without any loss
302 downloads as fast as possible|B - A-->|Send the cloud disk to the use proxy URL first|C-->|After being forwarded to you by the proxy URL, your download speed depends on the speed of downloading, forwarding, and forwarding on the other end of the proxy URL|B - A-->|Send the cloud drive to the device running OpenList first|D-->|After being forwarded to you by the device running OpenList, your download speed depends on the speed of downloading, uploading, and forwarding on the end where OpenList is built|B -``` - -::: - -::: zh-CN +### 三种模式说明 ```mermaid --- @@ -343,45 +144,12 @@ flowchart LR A-->|云盘先发送给搭建OpenList的设备|D-->|由搭建OpenList的设备转发给你
转发给你之后,你下载速度
取决于搭建OpenList那一端下载然后上传转发的速度|B ``` -::: - -## Download proxy URL { lang="en" } +## 下载代理 URL -## 下载代理 URL { lang="zh-CN" } - -::: en -When the proxy is turned on without filling in this field, the local machine will be used for transfer by default. -::: - -::: zh-CN 开启代理时不填写此字段，默认使用本机进行传输。 -::: - -### 1. Cloudflare Workers { lang="en" } - -### 1. Cloudflare Workers { lang="zh-CN" } - -::: en -Here’s the translation: - -You can use Cloudflare Workers as a proxy. Simply fill in your Cloudflare Workers address here. - -The code to set up Workers can be found at [https://github.com/OpenListTeam/OpenList-Proxy/blob/main/openlist-proxy.js](https://github.com/OpenListTeam/OpenList-Proxy/blob/main/openlist-proxy.js). When using it, you need to replace the following variables: -- `ADDRESS`: Your OpenList address, which must include the protocol header and should not end with a `/`. For example, `https://pan.example.com`. +### 1. Cloudflare Workers -- `TOKEN`: The [Token](../../configuration/other.md#token) of the admin account, which can be found in the “Other Settings” section of the OpenList admin page. - -- `WORKER_ADDRESS`: Your Worker address, which is usually the same as the **Download Proxy URL**. - - :warning: Cloudflare Workers free CDN support is only compatible with **http80** and **https443** ports (whether domestic or international), as tested by group members. - -When filling in the **Download Proxy URL** in the OpenList backend configuration, the link should not end with a `/`. - -Detailed text tutorial:
-:::
-
-::: zh-CN
可以使用 Cloudflare Workers 做代理，这里填写您的 Cloudflare Workers 地址即可。
搭建 Workers 代码可以在 https://github.com/OpenListTeam/OpenList-Proxy/blob/main/openlist-proxy.js 找到，实际使用时需要配置环境变量：
@@ -392,50 +160,15 @@ Detailed text tutorial:
来自安稳的详细文字教程：
-:::
-
-### 2. Universal Binary { lang="en" }
-
-### 2. 通用二进制 { lang="zh-CN" }
+### 2. 通用二进制
-::: en
-You can use another machine as a proxy. Download the program from https://github.com/OpenListTeam/OpenList-Proxy/releases and check the usage instructions with `./openlist-proxy -help`.
-
-Detailed text tutorial:
-:::
-
-::: zh-CN
您可以使用另一台机器进行代理，在 https://github.com/OpenListTeam/OpenList-Proxy/releases 下载程序并通过 `./openlist-proxy -help` 查看使用方法。
更多内容请参考[OpenList Proxy](../../ecosystem/official_proxy)
来自安稳的详细文字教程：
-:::
-
-### 3. Developing on your own { lang="en" }
-### 3. 自行开发 { lang="zh-CN" }
-
-::: en
-You can develop your own proxy program. The general steps are as follows:
-
-- When downloading, it will request `PROXY_URL/path?sign=sign_value`.
-- In the proxy program, validate the `sign`. The calculation method for `sign` is:
-
-```js
-const to_sign = `${path}:${expireTimeStamp}`
-const _sign = safeBase64(hmac_sha256(to_sign, TOKEN))
-const sign = `${_sign}:${expireTimeStamp}`
-```
-
-`TOKEN` is the [Token](../../configuration/other.md#token) of the administrator account, which can be obtained in the “Other Settings” section of the OpenList management page.
-
-- After validating the signature, request `HOST/api/fs/link` to obtain the file URL and the request headers to include.
-- Use the information to make the request and handle the response.
-
-:::
-
-::: zh-CN
+### 3. 自行开发
你可以开发自己的代理程序，一般步骤是：
@@ -453,48 +186,16 @@ const sign = `${_sign}:${expireTimeStamp}`
- 验证签名正确后，请求 `HOST/api/fs/link`，可以得到文件的 URL 和要携带的请求头
- 使用信息请求和返回
-:::
-
-## Sort related { lang="en" }
-
-## 排序相关 { lang="zh-CN" }
-
-::: en
-
-- **Sort by**: Sort by what
-- **Sort direction**: Whether the sort direction is ascending or descending
-
-:::
-
-::: zh-CN
+## 排序相关
- **排序方式**：按什么排序
- **排序方向**：排序方向是升序还是降序
-:::
-
-::: en
-::: info
-Some drives use their own sorting method, which may be different.
-:::
-::: zh-CN
::: info
有些驱动器使用自己的排序方法，可能会有所不同。
:::
-## Extract folder { lang="en" }
-
-## 提取文件夹 { lang="zh-CN" }
-
-::: en
-
-- **Extract to front**: put all folders to the front when sorting
-- **Extract to back**: put all folders to the back when sorting
-
-:::
-::: zh-CN
+## 提取文件夹
- **提取到前面**：排序时将所有文件夹放在前面
- **提取到后面**：排序时将所有文件夹放在后面
-
-:::
diff --git a/pages/guide/drivers/crypt.md b/pages/guide/drivers/crypt.md
index 7331e33e1..b69a0e095 100644
--- a/pages/guide/drivers/crypt.md
+++ b/pages/guide/drivers/crypt.md
@@ -1,32 +1,12 @@
---
-title:
- en: Crypt
- zh-CN: Crypt（加密）
-icon: iconfont icon-state
top: 996
categories:
- guide
- drivers
-tag:
- - Storage
- - Guide
-sticky: true
-star: true
---
-::: en
-The Crypt driver provides secure encryption for your files and folders, acting as a two-password-protected vault. Only users with the correct password and salt can access the encrypted content.
+# Crypt（加密）
-**Key Features:**
-
-- File and folder encryption with multiple security levels
-- Password and salt-based protection
-- Compatible with rclone crypt
-- Supports various encryption modes for filenames and directories
-
-:::
-
-::: zh-CN
Crypt 驱动为您的文件和文件夹提供安全加密，相当于一个双重密码保护的保险库。只有拥有正确密码和盐值的用户才能访问加密内容。
**主要特性：**
@@ -36,20 +16,6 @@ Crypt 驱动为您的文件和文件夹提供安全加密，相当于一个双
- 与 rclone crypt 完全兼容
- 支持多种文件名和目录加密模式
-:::
-
-::: en
-::: warning Important Security Notice
-
-1. Read this guide thoroughly before using the Crypt driver
-2. Test the configuration in a local environment before production deployment
-3. **Never modify the configuration after storing encrypted data** - this will make data lost
-4. Keep your password and salt values secure - losing them means losing access to your data
-
-Again, please read the documentation carefully; otherwise, any data loss will be at your own risk!
-:::
-
-::: zh-CN
::: warning 重要安全提醒
1. 使用 Crypt 驱动前请仔细阅读本指南
@@ -60,36 +26,7 @@ Again, please read the documentation carefully; otherwise, any data loss will be
**再次提醒请仔细阅读文档使用，否则数据丢失自行承担！**
:::
-## Setup Instructions { lang="en" }
-
-## 设置说明 { lang="zh-CN" }
-
-::: en
-
-1. **Create Storage Location**
-
- Create an **empty folder** in your existing mounted drive to store encrypted files.
-
-2. **Configure Remote Path**
-
- Enter the path of the empty folder in the `Remote path` field of your Crypt driver configuration.
-
- **Example Configuration:**
- - Original driver path: `/123`
- - New empty folder: `/123/encrypted_storage`
- - Remote path setting: `/123/encrypted_storage`
-
-3. **Upload Files**
-
- Upload files to the newly created Crypt driver mount point. Only files uploaded through the Crypt driver will be encrypted.
-
- **File Access:**
- - **Encrypted files**: Located in the remote path, appear scrambled and cannot be opened directly
- - **Decrypted access**: View and access files normally through the Crypt driver mount point
-
-:::
-
-::: zh-CN
+## 设置说明
1. **创建存储位置**
@@ -112,45 +49,12 @@ Again, please read the documentation carefully; otherwise, any data loss will be
- **加密文件**：位于远程路径中，显示为加密状态，无法直接打开
- **解密访问**：通过 Crypt 驱动挂载点正常查看和访问文件
-:::
-
-### Basic Configuration Example { lang="en" }
-
-### 基础配置示例 { lang="zh-CN" }
-
-::: en
-For users new to encryption, use the following default configuration:
+### 基础配置示例
-
-:::
-
-::: zh-CN
对于首次使用加密的新手用户，建议使用以下默认配置：
-:::
-
-::: en
-::: danger Please make sure to read the following important notes carefully to ensure understanding!
-
-**Important Declaration:**
-
-- **Do not modify the configuration! Do not modify the configuration! Do not modify the configuration!** Once the configuration is saved, do not modify it again!!! This is repeated for emphasis!
-- **Password** and **Salt** must be remembered! After clicking save, they will be encrypted and cannot be displayed in plain text (the plain text in the image shows the state before saving).
-
-> [**Password Configuration Instructions**](#password)
->
-> [**Salt Configuration Instructions**](#salt)
----
-
-- **If you have not yet uploaded files within the Crypt driver**, you can modify the password and configuration. **Otherwise, do not modify!**
-- After modifying the configuration, Crypt will attempt to filter illegal files/directories, but illegal data will not be automatically deleted.
- - **Illegal files/directories** refer to encrypted data generated with a different configuration.
-
-:::
-
-::: zh-CN
::: danger 请务必仔细阅读以下注意事项，确保理解！
**重要声明：**
@@ -170,22 +74,6 @@ For users new to encryption, use the following default configuration:
:::
-::: en
-::: warning
-Regarding encryption combinations, there are 5 options available (actually 6), but it’s important to note that if only folder encryption is enabled without encrypting the file names, the configuration will not take effect (as shown in the first example below).
-
-| Filename Encryption | Directory Encryption | Status |
-| ------------------- | -------------------- | ---------- |
-| `Off` | `Enabled` | ❌ Invalid |
-| `Off` | `Disabled` | ✅ Valid |
-| `Standard` | `Disabled` | ✅ Valid |
-| `Standard` | `Enabled` | ✅ Valid |
-| `Obfuscate` | `Disabled` | ✅ Valid |
-| `Obfuscate` | `Enabled` | ✅ Valid |
-
-:::
-
-::: zh-CN
::: warning
关于加密组合，共有5种方式可供选择（实际上是6种），但需要注意的是，如果只启用文件夹加密而不加密文件名的配置将不会生效（例如下面举例的第1种情况）。
@@ -200,36 +88,10 @@ Regarding encryption combinations, there are 5 options available (actually 6), b
:::
-## Configuration Options { lang="en" }
-
-## 配置选项 { lang="zh-CN" }
-
-### Filename Encryption { lang="en" }
-
-### 文件名加密 { lang="zh-CN" }
-
-::: en
-**Default:** `Disabled`
-
-**Available Options:**
-
-| Mode | Security Level | Description |
-| ----------- | -------------- | ----------------------------------------------------------------------------- |
-| `Off` | None | Files keep original names with encrypted suffix (e.g., `file.txt.bin`) |
-| `Standard` | High | **Recommended** - Strong encryption with good security |
-| `Obfuscate` | Low | Simple obfuscation, supports long filenames but may create special characters |
-
----
-
-In the image below, the left side shows file **name encryption** and folder **name encryption** enabled, while the right side shows the decrypted Crypt driver where files can be viewed.
+## 配置选项
-- **File name encryption not enabled**: Original name + encrypted suffix, as shown in the top left corner
-- **File name encryption enabled**: Fully encrypted file name, content cannot be recognized, as shown in the bottom left corner
+### 文件名加密
-
-:::
-
-::: zh-CN
**默认值：** `禁用`
**可用选项：**
@@ -248,31 +110,9 @@ In the image below, the left side shows file **name encryption** and folder **na
- **启用文件名加密**：完全加密的文件名，无法识别内容，如左下角
-:::
-
-### Directory Name Encryption { lang="en" }
-
-### 文件夹名称加密 { lang="zh-CN" }
-
-::: en
-**Default:** `Disabled`
-
-Directory encryption requires filename encryption to be enabled. When activated, folder names are also encrypted for enhanced security.
-**Configuration Combinations:**
+### 文件夹名称加密
-| Filename Encryption | Directory Encryption | Status |
-| ------------------- | -------------------- | ---------- |
-| `Off` | `Enabled` | ❌ Invalid |
-| `Off` | `Disabled` | ✅ Valid |
-| `Standard` | `Disabled` | ✅ Valid |
-| `Standard` | `Enabled` | ✅ Valid |
-| `Obfuscate` | `Disabled` | ✅ Valid |
-| `Obfuscate` | `Enabled` | ✅ Valid |
-
-:::
-
-::: zh-CN
**默认值：** `禁用`
目录加密需要先启用文件名加密。激活后，文件夹名称也会被加密以增强安全性。
@@ -288,142 +128,56 @@ Directory encryption requires filename encryption to be enabled. When activated,
| `Obfuscate（混淆）` | `禁用` | ✅ 有效 |
| `Obfuscate（混淆）` | `启用` | ✅ 有效 |
-:::
-
-### Remote Path { lang="en" }
-
-### 加密后文件存储路径 { lang="zh-CN" }
+### 加密后文件存储路径
-::: en
-The storage location for encrypted files. Can be any mountable drive supported by OpenList.
-:::
-::: zh-CN
加密文件的存储位置。可以是 OpenList 支持的任何可挂载驱动。
-:::
-### Security Parameters { lang="en" }
+### 安全参数
-### 安全参数 { lang="zh-CN" }
-
-::: en
-::: danger
-After saving the configuration, both password and salt values are encrypted and cannot be displayed in plain text. Store them securely in a separate location.
-:::
-::: zh-CN
::: danger
保存配置后，密码和盐值都会被加密，无法以明文显示。请在其他地方安全存储这些值。
:::
-#### Password { lang="en" }
+#### 密码
-#### 密码 { lang="zh-CN" }
-
-::: en
-::: warning
-Note that passwords exported using `rclone config` are obfuscated and cannot be used directly. Please prefix the password with `___Obfuscated___` before use.
-For example, if the exported password is `abc123xyz`, it should be entered as `___Obfuscated___abc123xyz` in the Crypt driver. -::: - -::: zh-CN ::: warning 请注意，使用rclone config导出的配置中，密码是混淆后的，无法直接使用，请在密码的前缀中添加 `___Obfuscated___` 后再使用。
例如导出的密码是 `abc123xyz`，则在 Crypt 驱动中应填写 `___Obfuscated___abc123xyz`。 ::: -::: en -Primary encryption key. **Must be remembered** - cannot be recovered if lost. -::: -::: zh-CN 主要加密密钥。**必须牢记** - 丢失后无法恢复。 -::: -#### Salt { lang="en" } +#### 盐值 -#### 盐值 { lang="zh-CN" } - -::: en -::: warning -Note that salts exported using `rclone config` are obfuscated and cannot be used directly. Please prefix the salt with `___Obfuscated___` before use.
-For example, if the exported salt is `abc123xyz`, it should be entered as `___Obfuscated___abc123xyz` in the Crypt driver. -::: - -::: zh-CN ::: warning 请注意，rclone config 导出的配置中，盐值(即password2)是混淆后的，无法直接使用，请在盐值的前缀中添加 `___Obfuscated___` 后再使用。
例如导出的盐值是 `abc123xyz`，则在 Crypt 驱动中应填写 `___Obfuscated___abc123xyz`。 ::: -::: en -Secondary encryption key, acts as an additional password layer. **Must be remembered** - cannot be recovered if lost. - -If you don't know what is salt, treat it as a second password. Optional but recommended - -::: -::: zh-CN 辅助加密密钥，相当于第二层密码保护。**必须牢记** - 丢失后无法恢复。 如果您不知道什么是加盐，可以视为第二个密码。可选，推荐。 -::: - -### Advanced Options { lang="en" } -### 高级选项 { lang="zh-CN" } +### 高级选项 -#### Encrypted Suffix { lang="en" } +#### 加密后缀 -#### 加密后缀 { lang="zh-CN" } - -::: en -**Default:** `.bin` - -Custom suffix for encrypted files (only used when filename encryption is disabled). Must start with a dot (e.g., `.abc`, `.encrypted`). -::: - -::: zh-CN **默认值：** `.bin` 加密文件的自定义后缀（仅在文件名加密禁用时使用）。必须以点开头（例如：`.abc`、`.encrypted`）。 -::: -#### Filename Encoding { lang="en" } +#### 文件名编码 -#### 文件名编码 { lang="zh-CN" } - -::: en -**Default:** `base64` - -**Warning:** Only modify if you understand the implications. Other encoding options are not thoroughly tested and may cause compatibility issues. - -For rclone compatibility, configure this setting in advanced options. -::: - -::: zh-CN **默认值：** `base64` **警告：** 仅在了解其影响时才修改此设置。其他编码选项未经充分测试，可能导致兼容性问题。 为了与 rclone 兼容，请在高级选项中配置此设置。 -::: - -## Advanced Usage { lang="en" } - -## 高级用法 { lang="zh-CN" } -### Rclone Compatibility { lang="en" } +## 高级用法 -### Rclone 兼容性 { lang="zh-CN" } +### Rclone 兼容性 -::: en -The Crypt driver is fully compatible with [rclone crypt](https://rclone.org/crypt). - -**Important Notes:** - -- OpenList Crypt uses `filename_encoding = base64` by default for better long filename support, configure this setting in advanced options when using with rclone -- Case-insensitive filesystems (e.g., Windows with local storage) may cause issues - -::: - -::: zh-CN Crypt 驱动与 [rclone crypt](https://rclone.org/crypt) 目前完全兼容。 **重要说明：** @@ -431,43 +185,16 @@ Crypt 驱动与 [rclone crypt](https://rclone.org/crypt) 目前完全兼容。 - OpenList Crypt 默认使用 `filename_encoding = base64` 以更好地支持长文件名，与 rclone 一起使用时请在高级选项中配置此设置 - 大小写不敏感的文件系统（如 Windows 本地存储）可能会出现问题 -::: - -## Troubleshooting { lang="en" } - -## 故障排除 { lang="zh-CN" } - -### Startup Errors { lang="en" } +## 故障排除 -### 启动错误 { lang="zh-CN" } +### 启动错误 -::: en -If Crypt shows errors during OpenList startup, it's likely because Crypt starts before its target path is available. - -**Solution:** Set a higher [order number](./common.md#order) for the Crypt driver to delay its initialization. -::: - -::: zh-CN 如果 Crypt 在 OpenList 启动时显示错误，可能是因为 Crypt 在其目标路径可用之前就启动了。 **解决方案：** 为 Crypt 驱动设置更高的[序号](./common.md#序号)以延迟其初始化。 -::: -### Data Access Issues { lang="en" } +### 数据访问问题 -### 数据访问问题 { lang="zh-CN" } - -::: en -If you cannot access previously encrypted data: - -1. Verify that the password and salt values are correct -2. Ensure the configuration hasn't been modified -3. Check that the remote path is accessible -4. Confirm the filename encoding setting matches your original configuration - -::: - -::: zh-CN 如果无法访问之前加密的数据： 1. 验证密码和盐值是否正确 @@ -475,33 +202,7 @@ If you cannot access previously encrypted data: 3. 检查远程路径是否可访问 4. 确认文件名编码设置与原始配置匹配 -::: - -## The default download method used { lang="en" } - -## 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - c1 - end - c1[local proxy]:::someclass==default===>a2[user equipment] - classDef someclass fill:#f96 - b1[Download proxy URL]-.alternative.->a2[user equipment] - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +## 默认使用的下载方式 ```mermaid --- @@ -519,5 +220,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/degoo.md b/pages/guide/drivers/degoo.md index 3bce42b64..4b03b83c3 100644 --- a/pages/guide/drivers/degoo.md +++ b/pages/guide/drivers/degoo.md @@ -1,25 +1,14 @@ --- -title: - en: Degoo - zh-CN: Degoo categories: - guide - drivers top: 587 --- -https://degoo.com/ - -::: en -**Authentication methods**: +# Degoo -1. Username + Password -2. Refresh Token -3. Access Token +https://degoo.com/ -In normal cases, you can log in with your username + password. If you encounter a 429 error, you can log in using tokens. You can obtain the token from the request body or header in your browser. -::: -::: zh-CN **鉴权方式**： 1. 用户名 + 密码 @@ -27,79 +16,24 @@ In normal cases, you can log in with your username + password. If you encounter 3. 访问令牌 正常情况下，可以使用用户名 + 密码进行登录。如果您遇到了429错误，可以使用令牌登录。您可以从浏览器的请求内容或头部中获取访问令牌。 -::: -## Username { lang="en" } +## 用户名 -## 用户名 { lang="zh-CN" } - -::: en -Your user's name. -::: -::: zh-CN 您的用户名。 -::: - -## Password { lang="en" } -## 密码 { lang="zh-CN" } +## 密码 -::: en -Your user's password. -::: -::: zh-CN 您用户的密码。 -::: - -## Refresh Token { lang="en" } -## 刷新令牌 { lang="zh-CN" } +## 刷新令牌 -::: en -Refresh token for automatic token renewal, obtained automatically. -::: -::: zh-CN 用于自动更新令牌的刷新令牌，自动获取。 -::: -## Access Token { lang="en" } +## 访问令牌 -## 访问令牌 { lang="zh-CN" } - -::: en -Access token for Degoo API, obtained automatically. -::: -::: zh-CN Degoo API 访问令牌，自动获取。 -::: - -## The default download method used { lang="en" } - -## 默认使用的下载方式 { lang="zh-CN" } -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +## 默认使用的下载方式 ```mermaid --- @@ -119,5 +53,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/develop.md b/pages/guide/drivers/develop.md index 9d920a5ff..0edceb634 100644 --- a/pages/guide/drivers/develop.md +++ b/pages/guide/drivers/develop.md @@ -1,30 +1,11 @@ --- -title: - en: Contribute new storage driver - zh-CN: 贡献新存储驱动 -icon: iconfont icon-code -# This control sidebar order top: 100 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - Develop -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- -::: en -Duplicate `drivers/template` to expand the new storage. Please read [CONTRIBUTING](https://github.com/OpenListTeam/OpenList/blob/main/CONTRIBUTING.md) for details. -The design of the driver part of OpenList is easy to expand, no need to modify other files, just create a new package under the back-end project drivers package and reference this package in the `all.go` file. -::: -::: zh-CN +# 贡献新存储驱动 + 复制 `drivers/template` 以扩展新存储。 请阅读 [CONTRIBUTING](https://github.com/OpenListTeam/OpenList/blob/main/CONTRIBUTING.md) 了解详情。 OpenList 的驱动部分的设计很容易扩展，不需要修改其他文件，只需在后端项目驱动包下新建一个包，在 `all.go` 文件中引用这个包即可。 -::: diff --git a/pages/guide/drivers/doubao.md b/pages/guide/drivers/doubao.md index 1d0e67431..f8fc67d4b 100644 --- a/pages/guide/drivers/doubao.md +++ b/pages/guide/drivers/doubao.md @@ -1,36 +1,16 @@ --- -title: - en: Doubao Drive - zh-CN: 豆包云盘 -icon: iconfont icon-state -# This control sidebar order top: 676 -# A page can have multiple categories categories: - guide - drivers --- - +# 豆包云盘 -::: en -Mount [Doubao Drive](https://www.doubao.com/chat/drive/) cloud storage. + -::: -::: zh-CN 挂载 [豆包云盘](https://www.doubao.com/chat/drive/) 云存储。 -::: - -::: en -::: danger Security Risk - -Do not use 302 if the storage is public accessible. -Otherwise, the download link may leak sensitive information such as access token or signature. -Others may use the leaked link to **access all your files**. - -::: -::: zh-CN ::: danger 安全风险 若存储可公开访问，则请勿使用302重定向。 @@ -39,41 +19,14 @@ Others may use the leaked link to **access all your files**. ::: -## Root folder ID { lang="en" } - -## 根文件夹ID { lang="zh-CN" } +## 根文件夹ID -::: en -The root folder ID is the parameter value displayed in the address bar when accessing Doubao Drive via a web page. For example, after accessing [Doubao Drive](https://www.doubao.com/chat/drive/), the address bar shows `https://www.doubao.com/chat/drive/AAAAAAAAAAAAAAAAAAAAAAAAAA?tab=myUpload`, where `AAAAAAAAAAAAAAAAAAAAAAAAAA` is the root folder ID. - - -::: - -::: zh-CN 根文件夹ID即为网页访问豆包云盘时地址栏中的参数值，例如访问[豆包云盘](https://www.doubao.com/chat/drive/)后，地址栏显示为`https://www.doubao.com/chat/drive/AAAAAAAAAAAAAAAAAAAAAAAAAA?tab=myUpload`，其中`AAAAAAAAAAAAAAAAAAAAAAAAAA`即为根文件夹ID。  -::: - -## Cookie { lang="zh-CN" } - -## Cookie { lang="en" } - -::: en -Required. Web cookie. Used to refresh token and extract Authorization/DPoP tokens. -Open browser developer tools, visit [Doubao Drive](https://www.doubao.com/drive/), log in to your account, check the `Network` tab, search for `biz_auth` and open it, find `Cookie` in the `Header`, copy the complete value and fill it in. - - - -OpenList will automatically extract other attributes from the Cookie. Please ensure that the Cookie contains the following key-value pairs: - -- `LARK_SUITE_DPOP` -- `LARK_SUITE_ACCESS_TOKEN` -- `feishu_dpop_keypair` (used for key generation, optional) +## Cookie -::: -::: zh-CN 必填，网页 Cookie。用于刷新 Token 和提取 Authorization/DPoP Token。 打开浏览器开发者工具，访问 [豆包云盘](https://www.doubao.com/drive/)，登录账号后，查看`Network`（网络）Tab，搜索 `biz_auth` 并打开它，在 `Header`（标头）中找到 `Cookie`，复制其完整值填入即可。 @@ -86,56 +39,20 @@ OpenList 会自动从 Cookie 中提取其他属性。请确保 Cookie 中包含 - `LARK_SUITE_ACCESS_TOKEN` - `feishu_dpop_keypair` （用于密钥生成，可选） -::: - -## App ID { lang="en" } - -## App ID { lang="zh-CN" } - -::: en -必填，Doubao's App ID. The App ID may vary for different clients, please refer to the actual value. -::: +## App ID -::: zh-CN 必填，豆包的App ID。不同客户端的App ID可能不相同，请以实际为准。 -::: - -## DPoP Key Secret, Auth Client ID, Auth Scope, Auth SDK Source, Auth SDK Version { lang="en" } -## DPoP 密钥、认证客户端ID、认证区域、认证SDK来源、认证SDK版本 { lang="zh-CN" } - -::: en -Optional, for Token refresh. Please obtain it yourself, and refer to the actual value. -::: +## DPoP 密钥、认证客户端ID、认证区域、认证SDK来源、认证SDK版本 -::: zh-CN 可选，用于刷新 Token。请自行获取，以实际为准。 -::: - -## Share Link { lang="en" } - -## 分享链接 { lang="zh-CN" } -::: en -Whether to use share link for download. If enabled, OpenList will create share and request with anonymous user's token to create download link. This can reduce authorization leak. - -Please ensure you have filled all authentication options above before enabling this function. -::: +## 分享链接 -::: zh-CN 是否使用分享链接下载。启用后，OpenList 将创建分享然后使用匿名用户Token请求创建下载链接以减少授权泄露。 请确保您在启用此功能前已经填写了上面的所有认证参数。 -::: - -## Ignore JWT Check { lang="en" } -## 忽略 JWT 检查 { lang="zh-CN" } +## 忽略 JWT 检查 -::: en -Whether to ignore JWT check to prevent time issue -::: - -::: zh-CN 是否忽略 JWT 检查以避免时间问题。 -::: diff --git a/pages/guide/drivers/dropbox.md b/pages/guide/drivers/dropbox.md index dca3db801..7b8adec66 100644 --- a/pages/guide/drivers/dropbox.md +++ b/pages/guide/drivers/dropbox.md @@ -1,77 +1,15 @@ --- -title: - en: Dropbox - zh-CN: Dropbox -icon: iconfont icon-state -# This control sidebar order top: 590 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - '302' -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- -::: en -Dropbox Official：https://www.dropbox.com/ -::: -::: zh-CN -Dropbox官网：https://www.dropbox.com/ -::: - -## Get refresh token { lang="en" } - -## 获取刷新令牌 { lang="zh-CN" } - -::: en - -- **This drive does not support the online API mode provided by OpenList.** - -- The following tutorial applies when the option is kept disabled as shown below. - -  - -- If you create your own `Client ID` and `Secret`, remember to authorize them. - -The steps are as follows: - -1. First, [click here](https://www.dropbox.com/developers/apps?_tk=pilot_lp&_ad=topbar4&_camp=myapps) to enter the Dropbox app management page and click "Create App". - -  - -2. After entering the app, configure the app type as shown below. - -  - -3. You can get the id and secret in the red box: the upper one is the id, the lower one is the secret. - -  - -4. Configure the callback URL. If you are strict about permissions and do not want to use an external callback address, you can set a local address here, or use the one outside the red box. - -  - -5. Finally, go to the permissions configuration page to set the app's permissions. - -  - -6. [Click here](https://api.oplist.org/) to enter the token acquisition tool. Select Dropbox, fill in your id and secret, and after authorization you can get the refresh token. - -7. In the OpenList configuration page, enter the refresh token, id, and secret to use. Note that the refresh token is about 40-50 characters long. +# Dropbox - - -::: +Dropbox官网：https://www.dropbox.com/ -::: zh-CN +## 获取刷新令牌 - **该驱动并不支持由 OpenList 提供的 online api 模式！** @@ -109,18 +47,6 @@ The steps are as follows:  -::: - -::: en -If you are highly privacy-conscious, Dropbox supports local callback. You can use the following script provided by GPT to quickly implement it, communicating only with Dropbox servers. - -::: warning -Since the callback address is local and you have not set up a real local callback server, please manually copy the authorization code from the browser address bar. - -**Please resolve Python environment issues yourself, or use the callback server provided above.** -::: - -::: zh-CN 如果你有强烈的隐私意识，dropbox支持本地回调，可以使用以下全程由GPT提供的脚本快速实现，只和dropbox的服务器进行通信。 ::: warning @@ -129,48 +55,6 @@ Since the callback address is local and you have not set up a real local callbac **请自行解决py运行的环境问题，或者使用上面搭建好的回调服务器** ::: -::: en - -```python -import requests -import webbrowser -# Please replace with your own Dropbox App information -CLIENT_ID = 'your_app_key' -CLIENT_SECRET = 'your_app_secret' -REDIRECT_URI = 'http://localhost:114514' -# Step 1: Get authorization code -auth_url = ( - f"https://www.dropbox.com/oauth2/authorize" - f"?client_id={CLIENT_ID}" - f"&redirect_uri={REDIRECT_URI}" - f"&response_type=code" - f"&token_access_type=offline" # Required: key parameter to get refresh_token -) -print("👉 Please visit the following link to authorize:\n") -print(auth_url) -webbrowser.open(auth_url) -auth_code = input("\n✅ After authorization, paste the code after ?code= in the redirected URL here:\n> ").strip() -# Step 2: Exchange for access_token + refresh_token -token_url = "https://api.dropboxapi.com/oauth2/token" -data = { - 'code': auth_code, - 'grant_type': 'authorization_code', - 'client_id': CLIENT_ID, - 'client_secret': CLIENT_SECRET, - 'redirect_uri': REDIRECT_URI -} -response = requests.post(token_url, data=data) -response.raise_for_status() -tokens = response.json() -# ✅ Only output the refresh token -print("\n🎉 Success! Your Dropbox refresh_token is:\n") -print(tokens.get("refresh_token")) -``` - -::: - -::: zh-CN - ```python import requests import webbrowser @@ -207,50 +91,13 @@ print("\n🎉 获取成功！你的 Dropbox refresh_token 是：\n") print(tokens.get("refresh_token")) ``` -::: - -## Root folder file_id { lang="en" } +## 根文件夹ID -## 根文件夹ID { lang="zh-CN" } - -::: en -**Empty is the root directory**：display all files -**Single folder ID**：Enter the folder you need to display, copy the top link to fill in `/home` behind - -::: -::: zh-CN 空为根目录：挂载全部文件 单文件夹ID：进入你需要挂载的文件夹复制顶部链接将`/home`后面的填写进去即可  -::: - -### The default download method used { lang="en" } - -### 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` -::: -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -270,5 +117,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/emby.md b/pages/guide/drivers/emby.md index 684ea3477..f29071a3d 100644 --- a/pages/guide/drivers/emby.md +++ b/pages/guide/drivers/emby.md @@ -1,136 +1,54 @@ --- -title: - en: Emby - zh-CN: Emby -icon: iconfont icon-state -# This control sidebar order top: 493 -# A page can have multiple categories categories: - guide - drivers --- -::: en -Mount media resources from an Emby server. -::: -::: zh-CN -挂载 Emby 服务器中的媒体资源。 -::: +# Emby -## URL { lang="en" } +挂载 Emby 服务器中的媒体资源。 -## URL 服务器地址 { lang="zh-CN" } +## URL 服务器地址 -::: en -Emby server address, for example: `http://127.0.0.1:8086`. -::: -::: zh-CN Emby 服务器地址，例如：`http://127.0.0.1:8086`。 -::: - -## ApiKey { lang="en" } -## ApiKey { lang="zh-CN" } +## ApiKey -::: en -Emby API Key. Use together with `UserID` for API authentication. -::: -::: zh-CN Emby API Key。与 `UserID` 搭配使用进行 API 认证。 -::: -## UserID { lang="en" } +## UserID -## UserID { lang="zh-CN" } - -::: en -Emby user ID. Used with `ApiKey`. -::: -::: zh-CN Emby 用户 ID。与 `ApiKey` 搭配使用。 -::: - -## Username { lang="en" } -## 用户名 { lang="zh-CN" } +## 用户名 -::: en -Emby account username. Used with `Password`. -::: -::: zh-CN Emby 账号用户名。与 `Password` 搭配使用。 -::: -## Password { lang="en" } +## 密码 -## 密码 { lang="zh-CN" } - -::: en -Emby account password. Used with `Username`. -::: -::: zh-CN Emby 账号密码。与 `Username` 搭配使用。 -::: - -## LinkMethod { lang="en" } - -## 链接方式 LinkMethod { lang="zh-CN" } -::: en -Choose link method: +## 链接方式 LinkMethod -- `stream`: Streaming link (recommended) -- `download`: Direct download link - -Some Emby servers do not grant download permission. In that case, please use `stream`. -::: -::: zh-CN 选择链接方式： - `stream`：串流链接（推荐） - `download`：下载链接 有些 Emby 服务器未开放下载权限，此时请使用 `stream`。 -::: - -## Authentication Method { lang="en" } -## 认证方式 { lang="zh-CN" } +## 认证方式 -::: en -Use **one** of the following login methods: - -1. `ApiKey + UserID` -2. `Username + Password` - -Do not mix both methods at the same time. -::: -::: zh-CN 登录方式二选一： 1. `ApiKey + UserID` 2. `Username + Password` 请不要同时混用两种方式。 -::: - -## Example Configuration { lang="en" } -## 配置示例 { lang="zh-CN" } - -::: en - -- URL: `http://127.0.0.1:8086` -- LinkMethod: `stream` -- Authentication: choose one method only - -::: - -::: zh-CN +## 配置示例 - URL：`http://127.0.0.1:8086` - LinkMethod：`stream` - 认证方式：仅选择其中一种 - -::: diff --git a/pages/guide/drivers/febbox.md b/pages/guide/drivers/febbox.md index f1b4994a5..8a8affa4a 100644 --- a/pages/guide/drivers/febbox.md +++ b/pages/guide/drivers/febbox.md @@ -1,54 +1,19 @@ --- -title: - en: FebBox - zh-CN: FebBox -icon: iconfont icon-state -# This control sidebar order top: 591 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - '302' -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- -::: en -FebBox：https://www.febbox.com - -- The upload function is currently unavailable. +# FebBox -::: -::: zh-CN FebBox：https://www.febbox.com - 需要代理，直连似乎无法访问？ - 目前上传功能不可用 -::: - -## Root folder ID { lang="en" } - -## 根文件夹ID { lang="zh-CN" } - -::: en -Root directory ID, default is `0`. +## 根文件夹ID -Other directory IDs can be viewed in the top link address bar after entering the folder. - -- **https://www.febbox.com/console#/files?parent_id=66889900** - - Then the directory ID is `66889900` - -::: -::: zh-CN 根目录ID，默认为`0`。 其它目录 ID 查看进入文件夹后看顶部链接地址栏。 @@ -57,74 +22,21 @@ Other directory IDs can be viewed in the top link address bar after entering the 那这个目录 ID 就是 `66889900` -::: - -## `Client_id`、`Client_secret` { lang="en" } +## 客户端 ID 和 秘钥 -## 客户端 ID 和 秘钥 { lang="zh-CN" } - -::: en -Generate address：**https://www.febbox.com/open/clients** - -- The generated client ID and secret key are filled in in the opposite order to the OpenList, so be careful not to fill them in incorrectly. - -  - -::: -::: zh-CN 生成地址：**https://www.febbox.com/open/clients** - 生成的客户端 ID 和秘钥和 OpenList 填写的顺序是相反的，注意别填错  -::: - -## User IP { lang="en" } - -## 用户 IP { lang="zh-CN" } - -::: en -**Optional**, the IP address of the user when downloading, quoting the official description - -> IP address, Optional parameter. Supports IPv6 format. After filling in, the best download server suitable for the IP location will be selected. If not filled in, the requested IP will be used. +## 用户 IP -::: - -::: zh-CN **可选** ，用户下载时的 IP，引用官方说明 > IP 地址，可选参数。支持 IPv6 格式。填写后，将选择适合 IP 位置的最佳下载服务器。如果未填写，将使用请求的 IP。 -::: - -## The default download method used { lang="en" } - -## 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +## 默认使用的下载方式 ```mermaid --- @@ -144,5 +56,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/feiji.md b/pages/guide/drivers/feiji.md index 317bd54df..646fdc622 100644 --- a/pages/guide/drivers/feiji.md +++ b/pages/guide/drivers/feiji.md @@ -1,101 +1,34 @@ --- -title: - en: FeiJi Cloud - zh-CN: 小飞机网盘 -icon: iconfont icon-state -# This control sidebar order top: 686 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - '302' -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- +# 小飞机网盘 + **https://feijipan.com/** -::: en -::: danger -Feiji Cloud imposes login restrictions on 3rd-party platforms. Attempting to access its service via OpenList may result in your account being banned. Please proceed with caution! -::: - -::: zh-CN ::: danger 小飞机网盘对第三方平台有登录限制，尝试登录极易封号，请谨慎使用！ ::: -## Root folder ID { lang="en" } +## 根文件夹ID -## 根文件夹ID { lang="zh-CN" } - -::: en -root folder ID the default is `0`，Other directory ID View the figure below obtaining method - -::: -::: zh-CN 根目录ID，默认为`0`，其它目录ID查看下图获取方式  -::: -## username、password { lang="en" } +## 账户、密码 -## 账户、密码 { lang="zh-CN" } - -::: en -Just fill in your own Feiji Cloud Account Password -::: -::: zh-CN 填写自己的小飞机网盘帐号密码 -::: - -## Known issues { lang="en" } -## 已知问题 { lang="zh-CN" } +## 已知问题 -::: en -The file size returned by iLanZou is in Kilo Bytes, not Bytes. Therefore, you cannot accurately determine if a file has been modified based on its size. Please pay attention to the configuration of your sync software. -::: -::: zh-CN 蓝奏云优享版返回的文件大小非 Bytes，而是 Kilo Bytes，因此无法使用文件大小准确判断一个文件是否被修改，需要注意同步软件的配置。 -::: - -## The default download method used { lang="en" } - -## 默认使用的下载方式 { lang="zh-CN" } -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +## 默认使用的下载方式 ```mermaid --- @@ -115,5 +48,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/ftp.md b/pages/guide/drivers/ftp.md index 3a12fb35f..f511964b9 100644 --- a/pages/guide/drivers/ftp.md +++ b/pages/guide/drivers/ftp.md @@ -1,106 +1,33 @@ --- -title: - en: FTP - zh-CN: FTP -icon: iconfont icon-state -# This control sidebar order top: 898 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - '本地代理' -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- -### Address { lang="en" } +# FTP -## 地址 { lang="zh-CN" } +## 地址 -::: en -FTP address, need contains port. -::: -::: zh-CN FTP 地址，需要包含端口。 -::: -### Username { lang="en" } +## 用户名 -## 用户名 { lang="zh-CN" } - -::: en -FTP username -::: -::: zh-CN FTP 用户名 -::: - -### Password { lang="en" } -## 密码 { lang="zh-CN" } +## 密码 -::: en -FTP password -::: -::: zh-CN FTP 密码 -::: - -### Root folder path { lang="en" } -## 根文件夹ID { lang="zh-CN" } +## 根文件夹ID -::: en -root folder , default `/`, same as local storage. -::: -::: zh-CN 根文件夹，默认 `/`，同本地存储。 -::: -## Enter directory before listing { lang="en" } +## 列出前先进入目录 -## 列出前先进入目录 { lang="zh-CN" } - -::: en -Whether to change into the target directory before listing files. Some FTP servers do not support listing files with a path argument directly. Enable this option to first `cd` into the directory and then `ls`, which can resolve such compatibility issues. Default: `false`. -::: - -::: zh-CN 是否在列出文件前先进入目标目录。部分 FTP 服务器不支持直接带路径参数列出文件，开启此选项后会先 `cd` 进入目录再 `ls`，可以解决此类兼容性问题。默认: `false`。 -::: - -### The default download method used { lang="en" } -### 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - c1 - end - c1[local proxy]:::someclass==default===>a2[user equipment] - classDef someclass fill:#f96 - b1[Download proxy URL]-.alternative.->a2[user equipment] - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -118,5 +45,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/github.md b/pages/guide/drivers/github.md index 99a78fedf..a2a38ac38 100644 --- a/pages/guide/drivers/github.md +++ b/pages/guide/drivers/github.md @@ -1,36 +1,12 @@ --- -title: - en: GitHub API - zh-CN: GitHub API -icon: iconfont icon-state -# This control sidebar order top: 399 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - '302' - - '官方' -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- -::: en -::: tip -GitHub API does not support operating files larger than 100MiB and folders containing more than 100,000 sub-items. - -All `.gitkeep` files will be managed by the driver and will be invisible to the user. - -Operations on submodules are currently not supported. -::: +# GitHub API -::: zh-CN ::: tip GitHub API 不支持操作 100M 或更大的文件，不支持操作含有超过 100,000 个子文件（夹）的文件夹。 @@ -39,28 +15,7 @@ GitHub API 不支持操作 100M 或更大的文件，不支持操作含有超过 本驱动暂不支持操作子模块。 ::: -## Token { lang="en" } - -## Token { lang="zh-CN" } - -::: en - -1. Log in GitHub and visit.
-
-2. Select `Generate new token (Classic)`
-
- 
-
-3. Fill the information. At least, select **repo**. And click `Generate token`.
-
- 
-
-4. Copy the token and paste it into the `Token` field.
-
- 
-
-:::
-::: zh-CN
+## Token
1. 登录 GitHub，访问：
@@ -76,58 +31,24 @@ GitHub API 不支持操作 100M 或更大的文件，不支持操作含有超过
-:::
-
-## Owner { lang="en" }
-
-## 所有者 { lang="zh-CN" }
+## 所有者
-::: en
-The owner of the repository. For example, if the URL of the repository is `github.com/AAA/BBB`, fill in `AAA` here.
-:::
-::: zh-CN
仓库的所有者，比如仓库链接是`github.com/AAA/BBB`，这里就填`AAA`。
-:::
-
-## Repo { lang="en" }
-## 仓库 { lang="zh-CN" }
+## 仓库
-::: en
-The name of the repository. For example, if the URL of the repository is `github.com/AAA/BBB`, fill in `BBB` here.
-:::
-::: zh-CN
仓库名，比如仓库链接是`github.com/AAA/BBB`，这里就填`BBB`。
-:::
-
-## Ref { lang="en" }
-## 引用 { lang="zh-CN" }
+## 引用
-::: en
-A branch, a tag or a commit SHA. Only when a branch name is filled in is the driver writable. It defaults to the default branch if not filled.
-:::
-::: zh-CN
分支名、tag或提交SHA，只有在填写分支名的情况下驱动才可写，不填会使用默认分支。
-:::
-
-## Gh Proxy { lang="en" }
-
-## Gh Proxy { lang="zh-CN" }
-
-::: en
-Used to speed up downloading
-- Download the content of `Raw` and `archive` and change it to `https://gh-proxy.com/raw.githubusercontent.com`
+## Gh Proxy
-:::
-::: zh-CN
用于加速下载
- 下载 `Raw`、`archive` 的内容要改成 `https://gh-proxy.com/raw.githubusercontent.com`
-:::
-
```
https://gh-proxy.com/raw.githubusercontent.com
```
@@ -140,104 +61,38 @@ https://ghfast.top/raw.githubusercontent.com
https://ghproxy.net/raw.githubusercontent.com
```
-## GPG private key { lang="en" }
-
-## GPG 私钥 { lang="zh-CN" }
-
-::: en
-GPG private key, used to provide commit verifications. Verified commits will be marked with a green "Verified" label on the GitHub webpage. Use the following command to obtain it. Leave blank if verifications are not needed.
+## GPG 私钥
-```bash
-gpg --export-secret-key -a
-```
-
-:::
-::: zh-CN
GPG 私钥，用于提供提交验证功能，经验证的提交会在 GitHub 网页上被标记为绿色的“Verified”，使用以下命令获取，不需要验证功能可以留空。
```bash
gpg --export-secret-key -a <密钥对ID>
```
-:::
+## GPG 私钥密码
-## GPG key passphrase { lang="en" }
-
-## GPG 私钥密码 { lang="zh-CN" }
-
-::: en
-Passphrase to the GPG private key. Leave blank if there is none.
-:::
-::: zh-CN
GPG 私钥的密码，没有则留空。
-:::
-
-## Committer name { lang="en" }
-## 提交者名称 { lang="zh-CN" }
+## 提交者名称
-::: en
-Custom committer name, defaulting to the owner's of the token when not filled.
-:::
-::: zh-CN
自定义提交者名称，不填会使用 Token 的所有者。
-:::
-
-## Committer email { lang="en" }
-## 提交者邮箱 { lang="zh-CN" }
+## 提交者邮箱
-::: en
-Custom committer name, defaulting to the owner's of the token when not filled.
-Required when "Committer name" is filled. Required to be empty when "Committer name" is empty.
-:::
-::: zh-CN
自定义提交者邮箱，不填会使用 Token 的所有者。
填写“提交者名称”时必填，未填写“提交者名称”时必不填。
-:::
-
-## Author name { lang="en" }
-## 作者名称 { lang="zh-CN" }
+## 作者名称
-::: en
-Custom author name, defaulting to the owner's of the token when not filled.
-:::
-::: zh-CN
自定义作者名称，不填会使用 Token 的所有者。
-:::
-
-## Author email { lang="en" }
-## 作者邮箱 { lang="zh-CN" }
+## 作者邮箱
-::: en
-Custom author name, defaulting to the owner's of the token when not filled.
-Required when "Author name" is filled. Required to be empty when "Author name" is empty.
-:::
-::: zh-CN
自定义作者邮箱，不填会使用 Token 的所有者。
填写“作者名称”时必填，未填写“作者名称”时必不填。
-:::
-## commit message { lang="en" }
-
-## 提交信息 { lang="zh-CN" }
-
-::: en
-Custom commit message, supporting the following template variables：
-
-- `UserName`: the user operating the file.
-- `ObjName`: the name of the file (or the folder) operated.
-- `ObjPath`: the path to the file (or the folder) operated.
-- `ParentName`: the name of the parent folder of the file (or the folder) operated.
-- `ParentPath`: the path to the parent folder of the file (or the folder) operated.
-- `TargetName`: (when renaming) new name. (when copying and moving) the target folder name.
-- `TargetPath`: (when renaming) new path. (when copying and moving) the target path.
-
-:::
+## 提交信息
-::: zh-CN
自定义提交信息，支持以下模板变量：
- `UserName`: 发起操作的用户
@@ -248,35 +103,7 @@ Custom commit message, supporting the following template variables：
- `TargetName`: （重命名时）新名称（复制、移动时）目标文件夹名称。
- `TargetPath`: （重命名时）新路径（复制、移动时）目标路径
-:::
-
-### The default download method used { lang="en" }
-
-### 默认使用的下载方式 { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[302]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[local proxy]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-::: zh-CN
+### 默认使用的下载方式
```mermaid
---
@@ -296,5 +123,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/github_releases.md b/pages/guide/drivers/github_releases.md
index 4a786a189..dd7ed25f5 100644
--- a/pages/guide/drivers/github_releases.md
+++ b/pages/guide/drivers/github_releases.md
@@ -1,47 +1,18 @@
---
-title:
- en: GitHub Releases
- zh-CN: GitHub 发行版
-icon: iconfont icon-state
top: 398
categories:
- guide
- drivers
-tag:
- - Storage
- - Guide
- - '302'
- - '官方'
-sticky: true
-star: true
---
-## Overview { lang="en" }
+# GitHub 发行版
-## 概述 { lang="zh-CN" }
+## 概述
-::: en
-GitHub Releases driver allows you to mount GitHub repository releases as a file system, enabling direct access to release assets through a familiar directory structure.
-:::
-
-::: zh-CN
GitHub Releases 驱动允许您将 GitHub 仓库的发布版本挂载为文件系统，通过熟悉的目录结构直接访问发布资源。
-:::
-
-## API Rate Limits { lang="en" }
-
-## API 速率限制 { lang="zh-CN" }
-::: en
-::: warning Rate Limits
+## API 速率限制
-- **Unauthenticated requests**: 60 requests per hour
-- **Authenticated requests** (with token): 5,000 requests per hour
-
-We recommend using a personal access token to avoid hitting rate limits.
-:::
-
-::: zh-CN
::: warning 速率限制
- **未认证请求**：每小时 60 次请求
@@ -50,32 +21,10 @@ We recommend using a personal access token to avoid hitting rate limits.
建议使用个人访问令牌以避免触及速率限制。
:::
-## Repository Configuration { lang="en" }
-
-## 仓库配置 { lang="zh-CN" }
-
-### Basic Usage { lang="en" }
+## 仓库配置
-### 基本用法 { lang="zh-CN" }
+### 基本用法
-::: en
-**Single Repository Mount**
-
-Mount a single repository to the root directory:
-
-```text
-OpenListTeam/OpenList
-```
-
-This is equivalent to:
-
-```text
-/:OpenListTeam/OpenList
-```
-
-:::
-
-::: zh-CN
**单个仓库挂载**
将单个仓库挂载到根目录：
@@ -90,32 +39,8 @@ OpenListTeam/OpenList
/:OpenListTeam/OpenList
```
-:::
-
-### Multiple Repositories { lang="en" }
-
-### 多个仓库 { lang="zh-CN" }
-
-::: en
-**Mount to Subdirectories**
-
-You can mount multiple repositories to different subdirectories:
-
-```text
-/openlist-gh:OpenListTeam/OpenList
-/openlist-frontend-gh:OpenListTeam/OpenList-Frontend
-```
-
-The leading `/` is optional:
-
-```text
-openlist-gh:OpenListTeam/OpenList
-openlist-frontend-gh:OpenListTeam/OpenList-Frontend
-```
-
-:::
+### 多个仓库
-::: zh-CN
**挂载到子目录**
您可以将多个仓库挂载到不同的子目录：
@@ -132,31 +57,10 @@ openlist-gh:OpenListTeam/OpenList
openlist-frontend-gh:OpenListTeam/OpenList-Frontend
```
-:::
-
-## Configuration Options { lang="en" }
-
-## 配置选项 { lang="zh-CN" }
-
-### Personal Access Token { lang="en" }
-
-### 个人访问令牌 { lang="zh-CN" }
-
-::: en
-**When to use:**
-
-- Required for accessing private repositories
-- Recommended to avoid rate limiting issues
-
-**How to get:**
+## 配置选项
-1. Log in to GitHub
-2. Visit: https://github.com/settings/tokens
-3. Generate a new token with appropriate permissions
+### 个人访问令牌
-:::
-
-::: zh-CN
**使用场景：**
- 访问私有仓库时必需
@@ -168,40 +72,8 @@ openlist-frontend-gh:OpenListTeam/OpenList-Frontend
2. 访问：https://github.com/settings/tokens
3. 生成具有适当权限的新令牌
-:::
-
-### Show All Versions { lang="en" }
-
-### 显示所有版本 { lang="zh-CN" }
+### 显示所有版本
-::: en
-**Disabled (default):**
-
-```
-openlist/
-├── openlist-linux-amd64.tar.gz
-└── openlist-windows-amd64.zip
-```
-
-**Enabled:**
-
-```
-openlist/
-├── v3.41.0/
-│ ├── openlist-linux-amd64.tar.gz
-│ └── openlist-windows-amd64.zip
-├── v3.40.0/
-│ ├── openlist-linux-amd64.tar.gz
-│ └── openlist-windows-amd64.zip
-└── v3.39.4/
- ├── openlist-linux-amd64.tar.gz
- └── openlist-windows-amd64.zip
-```
-
-When enabled, all available release versions are displayed in separate directories.
-:::
-
-::: zh-CN
**禁用（默认）：**
```
@@ -226,34 +98,9 @@ openlist/
```
启用后，所有可用的发布版本都会显示在单独的目录中。
-:::
-### Pagination Control (Show All Versions) { lang="en" }
+### 分页控制（显示所有版本）
-### 分页控制（显示所有版本） { lang="zh-CN" }
-
-::: en
-When "Show All Versions" is enabled, you can control the number of releases fetched via pagination:
-
-- **`per_page`**: Number of releases per page (default: `30`, max: `100`)
-- **`max_page`**: Maximum number of pages to fetch (`0` means unlimited)
-
-These settings help you avoid hitting API rate limits when repositories have a large number of releases.
-
-**Example:**
-
-To fetch at most 2 pages with 50 releases per page (up to 100 releases total):
-
-```text
-per_page = 50
-max_page = 2
-```
-
-::: tip
-A single unauthenticated request counts as 1 toward the 60 requests/hour limit. With `per_page=100` and `max_page=1`, fetching releases for a single repository costs only 1 request.
-:::
-
-::: zh-CN
当启用"显示所有版本"时，您可以通过分页控制获取的发布数量：
- **`per_page`**：每页 release 数量（默认：`30`，最大：`100`）
@@ -274,39 +121,8 @@ max_page = 2
单次未认证请求计为 1 次，占每小时 60 次限额。设 `per_page=100`、`max_page=1` 时，获取单个仓库的 release 仅消耗 1 次请求。
:::
-### Show README Files { lang="en" }
-
-### 显示 README 文件 { lang="zh-CN" }
-
-::: en
-**Disabled (default):**
-
-```
-openlist/
-├── openlist-linux-amd64.tar.gz
-└── openlist-windows-amd64.zip
-```
-
-**Enabled:**
-
-```
-openlist/
-├── v3.41.0/
-│ ├── openlist-linux-amd64.tar.gz
-│ └── openlist-windows-amd64.zip
-├── v3.40.0/
-│ ├── openlist-linux-amd64.tar.gz
-│ └── openlist-windows-amd64.zip
-├── LICENSE
-├── README.md
-└── README_cn.md
-```
-
-::: tip
-When enabled, README and LICENSE files from the repository are displayed alongside releases. However, folder size and modification time information will not be shown.
-:::
+### 显示 README 文件
-::: zh-CN
**禁用（默认）：**
```
@@ -334,40 +150,8 @@ openlist/
启用后，仓库的 README 和 LICENSE 文件会与发布版本一起显示。但是，不会显示文件夹大小和修改时间信息。
:::
-## GitHub Proxy Settings { lang="en" }
+## GitHub 代理设置
-## GitHub 代理设置 { lang="zh-CN" }
-
-::: en
-Use GitHub proxy services to accelerate downloads in regions with limited GitHub access.
-
-**Configuration:**
-Replace the GitHub domain with a proxy service URL:
-
-```text
-https://gh-proxy.com/https://github.com
-```
-
-**Available Proxy Services:**
-
-| Service | URL |
-| ----------- | ----------------------------------------- |
-| GH-Proxy | `https://gh-proxy.com/https://github.com` |
-| GHProxy.net | `https://ghproxy.net/https://github.com` |
-| GHFast | `https://ghfast.top/https://github.com` |
-
-Example:
-
-```
-Before: https://github.com/owner/repo/releases/download/v1.0/file.zip
-After: https://ghproxy.net/https://github.com/owner/repo/releases/download/v1.0/file.zip
-```
-
-::: warning
-Proxy services are third-party and may have varying availability and performance.
-:::
-
-::: zh-CN
使用 GitHub 代理服务来加速在 GitHub 访问受限地区的下载。
**配置方法：**
@@ -396,33 +180,7 @@ https://gh-proxy.com/https://github.com
代理服务为第三方提供，可用性和性能可能存在差异。
:::
-## The default download method used { lang="en" }
-
-## 默认使用的下载方式 { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[302]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[local proxy]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-::: zh-CN
+## 默认使用的下载方式
```mermaid
---
@@ -442,5 +200,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/google_drive.md b/pages/guide/drivers/google_drive.md
index 9d50e0dea..bca3b2cc4 100644
--- a/pages/guide/drivers/google_drive.md
+++ b/pages/guide/drivers/google_drive.md
@@ -1,46 +1,17 @@
---
-title:
- en: Google Drive
- zh-CN: 谷歌云盘
-icon: iconfont icon-state
-# This control sidebar order
top: 597
-# A page can have multiple categories
categories:
- guide
- drivers
---
-::: en
-
-Official website: https://drive.google.com/
-
-- Supports Team Drive (Enter the Team Drive directory ID for the Root Folder ID)
-
-:::
-
-::: zh-CN
+# 谷歌云盘
官网：https://drive.google.com/
- 支持团队盘（根目录ID填写团队盘的目录ID）
-:::
-
-## 1. Prerequisites { lang="en" }
-
-## 1. 必要条件 { lang="zh-CN" }
-
-::: en
-
-1. The machine on which the OpenList service is deployed must be able to connect to Google Drive.
-
-2. The Google Drive API service must be enabled. For details on how to enable it, please refer to [Enabling the Google Drive API](#_2-1-enable-google-drive-api).
-
- > For detailed steps, see [Google Workspace > Google Drive > Quick Start Guide](https://developers.google.com/workspace/drive/api/quickstart/js).
-
-:::
-::: zh-CN
+## 1. 必要条件
1. 搭建 OpenList 服务的机器必须能够连接到 Google 网盘。
@@ -48,26 +19,9 @@ Official website: https://drive.google.com/
> 详细步骤可参考 [Google Workspace > Google Drive > 快速入门指南](https://developers.google.com/workspace/drive/api/quickstart/js)
-:::
-
-## 2. Preparation { lang="en" }
-
-## 2. 准备接入 { lang="zh-CN" }
-
-### 2.1. Enable Google Drive API { lang="en" }
-
-### 2.1. 启用 Google Drive API 的 API { lang="zh-CN" }
-
-::: en
-
-1. On the [Guide Page](https://developers.google.com/workspace/drive/api/quickstart/js), locate the `Enable the API` button and click to proceed to the quick activation interface. Follow the instructions and confirm the settings to complete the activation process.
+## 2. 准备接入
-2. You can also visit the [Google Drive API Management Interface](https://console.cloud.google.com/apis/library/drive.googleapis.com). Find the `Enable` button at the top and click it; wait for the activation to complete.
-
-3. `Quotas and System Limits Management`(optional): Switch to the `Quotas and System Limits` tab and set appropriate quotas and limits based on your usage and requirements.
-
-:::
-::: zh-CN
+### 2.1. 启用 Google Drive API 的 API
1. 在[指南页面](https://developers.google.com/workspace/drive/api/quickstart/js)中找到`启用API`按钮，点击进入快捷开启界面，点击下一步以及确认后，即可完成开启。
@@ -75,33 +29,7 @@ Official website: https://drive.google.com/
3. `配额和系统限制管理`（可选）：切换到`配额和系统限制`选项卡，根据你的使用情况和需求，设置合适的配额和限制。
-:::
-
-### 2.2. Creating an OAuth Client (Optional; not required if using OpenList, a public welfare server, or a self-built server) { lang="en" }
-
-### 2.2. 创建 OAuth 客户端（可选，如果使用OpenList/公益服务器/自建服务器，则不用创建） { lang="zh-CN" }
-
-::: en
-
-1. On the [Credentials Page](https://console.cloud.google.com/apis/credentials?hl=en), click the `Create Credentials` dropdown menu and select and click `OAuth client ID`.
- > If prompted with `To create an OAuth client ID, you must first configure the consent screen`, click the `Configure consent screen` button, and complete the creation of the `Brand Information` on the subsequent page, selecting `External` for the `Audience`. After completion, return to the Credentials page to continue creating the OAuth client ID.
- > 
-2. In the pop-up window, select `Web Application` and enter the name of your application type.
-3. For the `Authorized redirect URIs`, enter `https://api.oplist.org/googleui/callback`. If you are using a self-built service or a non-profit organization, please enter the corresponding domain name, for example, `https://your-domain.com/googleui/callback`.
-4. Click the `Create` button to complete the creation of the OAuth client. Note: Make sure to copy and save the `Client ID` and `Client Secret`; you will need them later on.
-
- 
-
-5. Add yourself as a test user: On the left side, find the `Audience` menu and click to enter it. Then, locate `Test Users` and click the `+ Add users` button. Enter your Google account email address and click `Save`.
-
- 
-
-6. After completing the testing, you can publish your application: On the left side, find the `Audience` menu and click to enter it. Then, locate `Publication Status` and click the `Publish app` button. Confirm the publication to complete the application release process.
-
- 
-
-:::
-::: zh-CN
+### 2.2. 创建 OAuth 客户端（可选，如果使用OpenList/公益服务器/自建服务器，则不用创建）
1. 在[凭据界面](https://console.cloud.google.com/apis/credentials?hl=zh-cn)中，点击`创建凭据`下拉菜单，选择和点击`OAuth 客户端 ID`
@@ -125,50 +53,7 @@ Official website: https://drive.google.com/
-:::
-
-### 2.3. Get `Access Token` and `Refresh Token` { lang="en" }
-
-### 2.3. 获取`访问密钥`和`刷新密钥` { lang="zh-CN" }
-
-::: en
-
-1. Open the [OpenList Google Authorization Page](https://api.oplist.org/). **⚠️ If you are using a public or self-hosted server, please proceed with that server.**
-
-2. In the dropdown menu on the page, select `GoogleDrive Login`.
-
- 
- 
-
-3. If you created an OAuth Client ID in the previous steps, please enter the Client ID and Client Secrets in the input fields below.
-
- 
- 
-
- Otherwise, check the box ☑️ to use the API provided by OpenList. **⚠️ If you are using a public or self-hosted server, the built-in Client ID and Client Secrets of that server will be used.**
-
- 
- 
-
-4. Click the `Get Authorization` button. The system will redirect you to the Google Authorization page. Log in to your Google account and authorize OpenList to access your Google Drive.
-
- 
-
-5. If a message appears stating `This app has not been verified by Google`, click `Advanced` and then click `Go to oplist.org (insecure)` to continue. (If you are using a public or self-hosted server, the domain name here should match the actual domain name of the service; please verify this carefully.)
-
- 
-
-6. Pay attention to the permission information on the authorization page (within the red box in the image below). Make sure that the permission granted is only for accessing your Google Drive files. If you find that the permission includes access to something other than just your Google Drive files in the public service, please report an issue at [OpenListTeam/OpenList-Docs/issues](https://github.com/OpenListTeam/OpenList-Docs/issues).
-
- 
-
-7. After authorization is successful, the system will provide you with a `Refresh Token` and an `Access Token`. Please copy and save these tokens, as they will be used in subsequent configurations.
-
- 
- 
-
-:::
-::: zh-CN
+### 2.3. 获取`访问密钥`和`刷新密钥`
1. 打开[OpenList Google 授权页面](https://api.oplist.org/) **⚠️如果使用公益服务器/自建服务器，请访问公益服务器/自建服务器**
@@ -204,78 +89,17 @@ Official website: https://drive.google.com/
-:::
-
-## 3. Add Google Drive in OpenList { lang="en" }
+## 3. 在 OpenList 中添加谷歌云盘
-## 3. 在 OpenList 中添加谷歌云盘 { lang="zh-CN" }
-
-### 3.1. Configuration { lang="en" }
-
-### 3.1. 配置说明 { lang="zh-CN" }
-
-#### 3.1.1. Root Folder ID { lang="en" }
-
-#### 3.1.1. **根文件夹 ID** { lang="zh-CN" }
-
-::: en
-
-Similar to Aliyun Drive, it is the last string of the official website URL, such as:
-
-
+### 3.1. 配置说明
-:::
-::: zh-CN
+#### 3.1.1. **根文件夹 ID**
与阿里云盘类似，官网 URL 的最后一个字符串，如：
-:::
-
-### 3.2. Start Adding { lang="en" }
-
-### 3.2. 开始添加 { lang="zh-CN" }
-
-::: en
-
-1. Open the management interface of OpenList and click on `Storage` in the left menu.
-
-2. On the Storage List page, click the `Add Storage` button in the top right corner.
-
-3. Select `Google Drive` as the drive.
-
- 
- 
-
-4. Enter the mount path, for example: `google-drive`.
-
-5. In the `Root Folder ID` field, enter the root folder ID obtained earlier; if you are using the root directory, enter `root`.
-
-6. In the `Refresh Token` field, enter the refresh token obtained earlier (if not available, refer to [Preparing for Integration](#_2-preparation).
-
-7. If you are using the OAuth client ID and key provided by OpenList (or a public welfare server/self-built server), follow steps 7.1 and 7.2:
-
- 7.1. Check the `Use online API` option to indicate that you want to use the online API provided by OpenList.
-
- 7.2. Enter `https://api.oplist.org/googleui/renewapi` as the API URL; if it’s a public welfare server/self-built server, enter the corresponding server address.
-
- 
- 
-
-8. If you are using your own OAuth client ID and key, follow steps 8.1 and 8.2:
-
- 8.1. Uncheck the `Use online API` option to indicate that you are using your own OAuth client ID and key.
-
- 8.2. Enter your OAuth client ID in the `Client id` field and your OAuth Client secrets in the `Client secret` field.
-
- 
- 
-
-9. Click the `Add` button to complete the addition of Google Drive.
-
-:::
-::: zh-CN
+### 3.2. 开始添加
1. 打开 OpenList 的管理界面，点击左侧菜单中的`存储`。
@@ -312,28 +136,9 @@ Similar to Aliyun Drive, it is the last string of the official website URL, such
9. 点击`添加`按钮，完成谷歌云盘的添加。
-:::
+## 4. 关于`Use online api`选项的说明
-## 4. About `Use online api` option { lang="en" }
-
-## 4. 关于`Use online api`选项的说明 { lang="zh-CN" }
-
-### 4.1. AccessToken refresh method with own keys { lang="en" }
-
-### 4.1. 自身有密钥的情况下，AccessToken刷新的方式 { lang="zh-CN" }
-
-::: en
-
-```mermaid
-sequenceDiagram
- participant OpenList
- participant GoogleDrive
- OpenList->>GoogleDrive: Provide refresh token + built-in client ID and secret
- GoogleDrive->>OpenList: Return new access token + refresh token
-```
-
-:::
-::: zh-CN
+### 4.1. 自身有密钥的情况下，AccessToken刷新的方式
```mermaid
sequenceDiagram
@@ -344,30 +149,7 @@ sequenceDiagram
```
-:::
-
-### 4.2. AccessToken refresh method without own keys { lang="en" }
-
-### 4.2.自身没有密钥的情况下，AccessToken刷新的方式 { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: How to refresh AccessToken via OnlineAPI?
----
-sequenceDiagram
- participant OpenList
- participant OnlineAPI
- participant GoogleDrive
- OpenList->>OnlineAPI: Provide refresh token
- OnlineAPI->>GoogleDrive: Provide refresh token + built-in client ID and secret
- GoogleDrive->>OnlineAPI: Return new access token + refresh token
- OnlineAPI->>OpenList: Return new access token + refresh token
-```
-
-:::
-::: zh-CN
+### 4.2.自身没有密钥的情况下，AccessToken刷新的方式
```mermaid
---
@@ -383,33 +165,7 @@ sequenceDiagram
OnlineAPI->>OpenList: 返回新的访问令牌+刷新令牌
```
-:::
-
-## 5. The default download method used { lang="en" }
-
-## 5. 默认使用的哪种下载方式？ { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- c1
- end
- c1[Local Proxy]:::someclass==Default===>a2[User Device]
- classDef someclass fill:#f96
- b1[Proxy URL]-.Alternative.->a2[User Device]
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-::: zh-CN
+## 5. 默认使用的哪种下载方式？
```mermaid
---
@@ -427,5 +183,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/google_photos.md b/pages/guide/drivers/google_photos.md
index c3276d82e..acbf127df 100644
--- a/pages/guide/drivers/google_photos.md
+++ b/pages/guide/drivers/google_photos.md
@@ -1,73 +1,26 @@
---
-title:
- en: Google Photos
- zh-CN: 谷歌相册
-icon: iconfont icon-state
-# This control sidebar order
top: 596
-# A page can have multiple categories
categories:
- guide
- drivers
---
-::: zh-CN
+# 谷歌相册
+
::: tip
由于[谷歌相册官方于今年4月份对Library API做出的调整](https://developers.google.com/photos/support/updates?hl=zh-cn)，将谷歌相册成功挂载到openlist后，实际只能查看通过openlist上传的照片，而不能再像曾经一样查看用户通过谷歌相册官方app、网站上传的照片。
:::
-::: en
-::: tip
-Due to the adjustments made by Google Photos to its Library API in April this year (https://developers.google.com/photos/support/updates?hl=en), after successfully mounting Google Photos to openlist, you can actually only view the photos uploaded through openlist. You can no longer view the photos uploaded by users via the official Google Photos app or website as you could before.
-:::
-
-## 根文件夹 ID { lang="zh-CN" }
-## Root folder file_id { lang="en" }
+## 根文件夹 ID
-::: en
-The root directory is root, and other directory IDs are unknown (~~It seems that a separate album cannot be mounted~~ It has not been resolved yet [**Reference**](https://github.com/alist-org/alist/discussions/3264#discussioncomment-4874536))
-:::
-
-::: zh-CN
根目录root，其他目录ID未知( ~~貌似不能挂载单独的相册~~ 已解决下面有介绍)
-:::
-
-## 获取 client_id, client_secret { lang="zh-CN" }
-
-## Get client_id, client_secret { lang="en" }
-
-::: en
-
-Get the tool https://api.oplist.org
-
-How to get your own `client_id (client ID) client_secret (client secret key)` Go to [**Google Drive**](./google_drive.md) which article
-:::
-::: en
-::: tip
-
-Tip This app has not been verified by Google
-
-You have been authorized to use an app that is currently in beta. Do not proceed unless you know the developer who invited you.
-Let's click **Continue** on the left
+## 获取 client_id, client_secret
-Remember to check this option, otherwise an error will be reported, as explained in the following precautions
-:::
-::: en
-
-It is more convenient now. In fact, when obtaining Google cloud disk authorization, select the album permission at the same time, and the token obtained at that time can also be used to mount the album~ kill two birds with one stone
-
-Remember to enable **`Photos Library API`**
-
-- https://console.cloud.google.com/apis/library/photoslibrary.googleapis.com
-
-:::
-::: zh-CN
获取工具 https://api.oplist.org
如何获取自己的 `client_id(客户端ID) client_secret(客户端秘钥)` 去看[**谷歌网盘**](./google_drive.md)哪一篇
-:::
-::: zh-CN
+
::: tip
提示 此应用未经 Google 验证
@@ -82,32 +35,15 @@ Remember to enable **`Photos Library API`**
:::
-::: zh-CN
-
现在更加方便了，其实获取谷歌云盘的时候勾选了相册到时候获取到的token也可以拿来挂载相册~一举两得
记得打开 **`Photos Library API`** 哦~
- **https://console.cloud.google.com/apis/library/photoslibrary.googleapis.com?project=instant-shard-350513**
-:::
-
-## 挂载单个相册目录 { lang="zh-CN" }
-
-## Mount a single album directory { lang="zh-CN" }
+## 挂载单个相册目录
-::: en
-
-According to [above](https://api.oplist.org) obtained **client ID** and **secret key** and **refresh_token**
-
-We fill in **https://api.oplist.org** to get a single catalog ID for each of our Google Photos
-
-- Root file ID (that is, the album ID): default root, display all, if you only want to display a single album, you can fill in the album ID you want to display
-- After we fill in, there will also be an **`access_token`** below. This can also be filled in the OpenList background refresh token option and used. The refresh token obtained at the beginning can be used for both of them- [Explanation](https://github.com/alist-org/alist/discussions/3264#discussioncomment-5051171)
-
-:::
-
-::: zh-CN
+## Mount a single album directory
根据[上面](https://api.oplist.org)获取到的**客户端ID**和**秘钥**和**刷新令牌**
@@ -116,22 +52,7 @@ We fill in **https://api.oplist.org** to get a single catalog ID for each of our
- 根文件ID（就是相册ID）：默认root，展示全部，若只想展示单个相册，可以填写你想展示的相册ID
- 在我们填写后下方也会出现一个 **`access_token`** 这个也可以填写到刷新令牌里面前使用和之前获取到的，这两个都可以用 - [解释](https://github.com/alist-org/alist/discussions/3264#discussioncomment-5051171)
-:::
-
-## 两个注意事项： { lang="zh-CN" }
-
-## Two notes: { lang="en" }
-
-::: en
-
-1. failed get objs: failed to list objs: Request had insufficient authentication scopes.: []
- - It's because you didn't check the album permission (see the picture mentioned above) `view and organize the content in your Google Photos media library, and upload content to the media library when obtaining authorization. Learn more`
- - You get the `access_token` and the `refresh_token` without declearing the scope of `https://www.googleapis.com/auth/photoslibrary`
-2. failed get objs: failed to list objs: Photos Library API has not been used in project ... before or it is disabled. Enable it by visiting then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.: []
- - because **`Photos Library API`** is not enabled in your project, Google Photos API
-
-:::
-::: zh-CN
+## 两个注意事项：
1. failed get objs: failed to list objs: Request had insufficient authentication scopes.: []
- 是因为在获取授权的时候没有勾选 相册权限（查看上面提到的图片） `查看和整理您的Google相册媒体库中的内容,向媒体库上传内容。`
@@ -139,33 +60,7 @@ We fill in **https://api.oplist.org** to get a single catalog ID for each of our
2. failed get objs: failed to list objs: Photos Library API has not been used in project ... before or it is disabled. Enable it by visiting then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.: []
- 是因为对应的项目没有开启 **`Photos Library API`** 谷歌相册API
-:::
-
-### 默认使用的下载方式 { lang="zh-CN" }
-
-### The default download method used { lang="en" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- c1
- end
- c1[local proxy]:::someclass==default===>a2[user equipment]
- classDef someclass fill:#f96
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-::: zh-CN
+### 默认使用的下载方式
```mermaid
---
@@ -183,5 +78,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/guangyapan.md b/pages/guide/drivers/guangyapan.md
index 64f7d38ed..5fa12032d 100644
--- a/pages/guide/drivers/guangyapan.md
+++ b/pages/guide/drivers/guangyapan.md
@@ -1,209 +1,78 @@
---
-title:
- en: GuangYaPan
- zh-CN: 光鸭云盘
-icon: iconfont icon-state
-# This control sidebar order
top: 701
-# A page can have multiple categories
categories:
- guide
- drivers
-# A page can have multiple tags
-tag:
- - Storage
- - Guide
---
+# 光鸭云盘
+
-:::: en
-:::: warning
-This driver uses a **two-stage SMS login**. You need to provide a valid `client_id` before login. After completing the SMS login, `access_token` and `refresh_token` are saved automatically, and you can log in again with just `access_token` or `refresh_token`.
-::::
-:::: zh-CN
:::: warning
该驱动使用**两步短信登录**。登录前需要提供有效的 `client_id`。短信登录完成后会自动保存 `access_token` 与 `refresh_token`，之后只需凭 `access_token` 或 `refresh_token` 即可再次登录。
::::
-## 1. Add in OpenList { lang="en" }
-
-## 1. 在 OpenList 中添加 { lang="zh-CN" }
-
-### Client ID { lang="en" }
+## 1. 在 OpenList 中添加
-### 客户端 ID { lang="zh-CN" }
+### 客户端 ID
-:::: en
-**Required**. Fill in the `client_id` for the GuangYaPan API. This field must be provided, otherwise storage initialization will fail.
-::::
-:::: zh-CN
**必填**。填入光鸭云盘 API 的 `client_id`，此项必须填写，否则存储初始化会失败。
-::::
-### Phone Number { lang="en" }
+### 手机号
-### 手机号 { lang="zh-CN" }
-
-:::: en
-The phone number used for SMS login, e.g. `+86 13800000000`.
-::::
-:::: zh-CN
用于短信登录的手机号，例如 `+86 13800000000`。
-::::
-
-### Captcha Token { lang="en" }
-### 验证码令牌 { lang="zh-CN" }
+### 验证码令牌
-:::: en
-Captcha token required by `/v1/auth/verification`. Leave it empty if no captcha is triggered.
-::::
-:::: zh-CN
`/v1/auth/verification` 接口所需的验证码令牌。若未触发验证码可留空。
-::::
-### Send Code { lang="en" }
+### 发送验证码
-### 发送验证码 { lang="zh-CN" }
-
-:::: en
-Set it to `true` and save to send the SMS code. It auto-resets to `false` after sending.
-::::
-:::: zh-CN
设为 `true` 并保存即可发送短信验证码，发送后会自动重置为 `false`。
-::::
-
-### Verify Code { lang="en" }
-### 短信验证码 { lang="zh-CN" }
+### 短信验证码
-:::: en
-The SMS verification code you received. Fill it in and save to finish the login.
-::::
-:::: zh-CN
收到的短信验证码。填写后保存即可完成登录。
-::::
-### Verification ID { lang="en" }
+### 验证 ID
-### 验证 ID { lang="zh-CN" }
-
-:::: en
-Auto-generated after sending the SMS code. Do not edit it manually.
-::::
-:::: zh-CN
发送短信验证码后自动生成，请勿手动修改。
-::::
-
-### Access Token { lang="en" }
-### 访问令牌 { lang="zh-CN" }
+### 访问令牌
-:::: en
-Bearer access token. It is saved automatically after SMS login. If you already have a valid `access_token` or `refresh_token`, you can fill it directly instead of doing the SMS login.
-::::
-:::: zh-CN
Bearer 访问令牌。短信登录成功后会自动保存。如果已经持有有效的 `access_token` 或 `refresh_token`，可以直接填写而无需短信登录。
-::::
-### Refresh Token { lang="en" }
+### 刷新令牌
-### 刷新令牌 { lang="zh-CN" }
-
-:::: en
-Refresh token for auto-login and auto-refresh. Saved automatically after SMS login.
-::::
-:::: zh-CN
用于自动登录与自动刷新的刷新令牌，短信登录成功后会自动保存。
-::::
-
-### Root Folder Path { lang="en" }
-### 根文件夹路径 { lang="zh-CN" }
+### 根文件夹路径
-:::: en
-Full path in the GuangYaPan cloud drive, e.g. `/Movies/Anime`. Leave it empty to use the root directory.
-::::
-:::: zh-CN
光鸭云盘中的完整路径，例如 `/电影/动漫`。留空则使用根目录。
-::::
-### Device ID { lang="en" }
+### 设备 ID
-### 设备 ID { lang="zh-CN" }
-
-:::: en
-Optional custom device id (32 hex chars). Auto-generated when empty.
-::::
-:::: zh-CN
可选的自定义设备 ID（32 位十六进制字符），留空时自动生成。
-::::
-
-### Device Sign { lang="en" }
-### 设备签名 { lang="zh-CN" }
+### 设备签名
-:::: en
-Optional custom `X-Device-Sign` header. Generated from `device_id` when empty.
-::::
-:::: zh-CN
可选的自定义 `X-Device-Sign` 请求头，留空时根据 `device_id` 自动生成。
-::::
-
-### Page Size / Order By / Sort Type { lang="en" }
-
-### 分页大小 / 排序字段 / 排序方向 { lang="zh-CN" }
-
-:::: en
-
-- `Page Size`: file list page size, default `100`.
-- `Order By`: sort field used by the file list, options `0,1,2,3,4`, default `3`.
-- `Sort Type`: sort direction used by the file list, options `0,1`, default `1`.
-::::
-:::: zh-CN
+### 分页大小 / 排序字段 / 排序方向
- `分页大小`：文件列表每页数量，默认 `100`。
- `排序字段`：文件列表使用的排序字段，可选 `0,1,2,3,4`，默认 `3`。
- `排序方向`：文件列表使用的排序方向，可选 `0,1`，默认 `1`。
-::::
-
-## 2. SMS Login Steps { lang="en" }
-
-## 2. 短信登录步骤 { lang="zh-CN" }
-
-:::: en
-
-1. Fill in `client_id` and `phone_number` (and `captcha_token` if needed).
-2. Set `send_code` to `true`, then save. The storage will enter a "SMS sent" status and the `verification_id` is generated automatically.
-3. Fill in the received `verify_code`, then save again to finish the login. The `access_token` and `refresh_token` are saved automatically.
-
-::::
-:::: zh-CN
+## 2. 短信登录步骤
1. 填写 `client_id` 与 `phone_number`（如需要同时填写 `captcha_token`）。
2. 将 `send_code` 设为 `true` 并保存，存储会进入「短信已发送」状态，并自动生成 `verification_id`。
3. 填写收到的 `verify_code` 后再次保存，即可完成登录，`access_token` 与 `refresh_token` 会自动保存。
-::::
-
-## 3. Offline Download { lang="en" }
-
-## 3. 离线下载 { lang="zh-CN" }
-
-:::: en
-GuangYaPan supports calling its own offline download function from OpenList.
+## 3. 离线下载
-1. Mount a GuangYaPan storage.
-2. In the backend **Settings** → **Other**, set the GuangYaPan temporary directory (choose any folder of this account).
-3. Go back to the frontend, enter the target folder, and choose **GuangYaPan** in the offline download option at the lower right corner.
-
-- Supports adding offline tasks via URL (e.g. `http`, `magnet` links).
-
-::::
-:::: zh-CN
光鸭云盘支持在 OpenList 中调用其自身的离线下载功能。
1. 挂载光鸭云盘存储。
@@ -212,25 +81,9 @@ GuangYaPan supports calling its own offline download function from OpenList.
- 支持通过链接（如 `http`、`magnet`）添加离线任务。
-::::
-
-## 4. Precautions { lang="en" }
-
-## 4. 注意事项 { lang="zh-CN" }
-
-:::: en
-
-- `client_id` is required, otherwise storage initialization will fail.
-- The `verify_code` is one-time use and will be cleared after a successful login.
-- The driver does not support overwriting uploads (same-name files will not overwrite).
-- Login priority: `access_token` → `refresh_token` → SMS login.
-
-::::
-:::: zh-CN
+## 4. 注意事项
- `client_id` 为必填项，否则存储初始化会失败。
- `verify_code` 为一次性使用，登录成功后会被清空。
- 该驱动不支持覆盖上传（同名文件不会覆盖）。
- 登录优先级：`access_token` → `refresh_token` → 短信登录。
-
-::::
diff --git a/pages/guide/drivers/halalcloud.md b/pages/guide/drivers/halalcloud.md
index 9afe3d636..7e7042721 100644
--- a/pages/guide/drivers/halalcloud.md
+++ b/pages/guide/drivers/halalcloud.md
@@ -1,71 +1,22 @@
---
-title:
- en: halalcloud
- zh-CN: 6盘
-icon: iconfont icon-state
-# This control sidebar order
top: 679
-# A page can have multiple categories
categories:
- guide
- drivers
-# A page can have multiple tags
-tag:
- - Storage
- - Guide
- - '本地代理'
- - '官方'
-# this page is sticky in article list
-sticky: true
-# this page will appear in starred articles
-star: true
---
-::: en
-
-- `6盘（halalcloud）` Official website：[https://2dland.cn](https://2dland.cn/)
- - Cloud Login：https://drive.2dland.cn
-- Official announcement, document address：https://2dland.yuque.com/r/organizations/homepage
-
-:::
-
-::: zh-CN
+# 6盘
- `6盘（halalcloud）` 官方网站：[https://2dland.cn](https://2dland.cn/)
- 网盘登录：https://drive.2dland.cn
- 官方公告、文档地址：https://2dland.yuque.com/r/organizations/homepage
-:::
-
-## Root folder file_id { lang="en" }
-
-## 根文件夹 ID { lang="zh-CN" }
+## 根文件夹 ID
-::: en
-Top address bar path，Root folder file_id is:`/`
-Subfolder: `/A folder/C folder/C folder`
-:::
-::: zh-CN
顶部地址栏路径，根文件夹是：`/`
子文件夹：`/A文件夹/C文件夹/C文件夹`
-:::
-## Fill in the example { lang="en" }
-
-## 填写示例 { lang="zh-CN" }
-
-::: en
-
-On the HalalCloud (6 盘) website, go to `User Center` and navigate to `Authorization Management`. Enter your HalalCloud account password to verify your identity.
-
-Create a new authorization (you can name it anything you like). Click `Confirm`, then copy and save the `Client ID` and `Client Secret`.
-
-
-
-In the OpenList admin panel, go to `Storage` and add a new driver. Select `HalalCloudOpen`, and enter the `Client ID` and `Client Secret` obtained from the previous step.
-
-:::
-::: zh-CN
+## 填写示例
在 `6盘官网`内点击`用户中心`，进入`授权管理`页面，输入 6 盘账户密码验证身份。
@@ -75,22 +26,7 @@ In the OpenList admin panel, go to `Storage` and add a new driver. Select `Halal
在 OpenList 后台的存储页添加驱动，选择`HalalCloudOpen`，在下方填写`客户端 ID` 和`客户端密钥`，分别对应上方的值即可。
-:::
-
-## Other parameters { lang="en" }
-
-## 其它参数 { lang="zh-CN" }
-
-::: en
-
-- `Upload thread`: Upload threads (Default: 3, Range: 1-32)
-
-- `Host`: (Provided by default, no input required)
-
-- `WebDAV Policy`: Default is `302 Redirect`. Switch to `Local Proxy` if you encounter any issues.
-
-:::
-::: zh-CN
+## 其它参数
- `Upload thread`：上传线程（默认为 3，范围 1-32）
@@ -98,35 +34,7 @@ In the OpenList admin panel, go to `Storage` and add a new driver. Select `Halal
- `WebDav策略`：默认为`302重定向`，若有问题可以修改为`本地代理`
-:::
-
-### The default download method used { lang="en" }
-
-### 默认使用的下载方式 { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[302]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[local proxy]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-::: zh-CN
+### 默认使用的下载方式
```mermaid
---
@@ -146,5 +54,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/ilanzou.md b/pages/guide/drivers/ilanzou.md
index 2bec65511..857e1eb28 100644
--- a/pages/guide/drivers/ilanzou.md
+++ b/pages/guide/drivers/ilanzou.md
@@ -1,91 +1,30 @@
---
-title:
- en: iLanZou
- zh-CN: 蓝奏云优享版
-icon: iconfont icon-state
-# This control sidebar order
top: 687
-# A page can have multiple categories
categories:
- guide
- drivers
-# A page can have multiple tags
-tag:
- - Storage
- - Guide
- - '302'
-# this page is sticky in article list
-sticky: true
-# this page will appear in starred articles
-star: true
---
+# 蓝奏云优享版
+
**https://ilanzou.com**
-## Root folder ID { lang="en" }
-
-## 根文件夹ID { lang="zh-CN" }
+## 根文件夹ID
-::: en
-root folder ID the default is `0`，Other directory ID View the figure below obtaining method
-
-:::
-::: zh-CN
根目录ID，默认为`0`，其它目录ID查看下图获取方式
-:::
-## username、password { lang="en" }
+## 账户、密码
-## 账户、密码 { lang="zh-CN" }
-
-::: en
-Just fill in your own NewLanzou Cloud Account Password
-:::
-::: zh-CN
填写自己的蓝奏云优享版帐号密码
-:::
-
-## Known issues { lang="en" }
-## 已知问题 { lang="zh-CN" }
+## 已知问题
-::: en
-The file size returned by iLanZou is in Kilo Bytes, not Bytes. Therefore, you cannot accurately determine if a file has been modified based on its size. Please pay attention to the configuration of your sync software.
-:::
-::: zh-CN
蓝奏云优享版返回的文件大小非 Bytes，而是 Kilo Bytes，因此无法使用文件大小准确判断一个文件是否被修改，需要注意同步软件的配置。
-:::
-
-## The default download method used { lang="en" }
-## 默认使用的下载方式 { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[302]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[local proxy]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-::: zh-CN
+## 默认使用的下载方式
```mermaid
---
@@ -105,5 +44,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/kodbox.md b/pages/guide/drivers/kodbox.md
index e394df736..879c02ecd 100644
--- a/pages/guide/drivers/kodbox.md
+++ b/pages/guide/drivers/kodbox.md
@@ -1,46 +1,16 @@
---
-title:
- en: KodBox
- zh-CN: 可道云
-icon: iconfont icon-state
-# This control sidebar order
top: 496
-# A page can have multiple categories
categories:
- guide
- drivers
-# A page can have multiple tags
-tag:
- - Storage
- - Guide
- - '302'
-# this page is sticky in article list
-sticky: true
-# this page will appear in starred articles
-star: true
---
-::: en
-Use this driver to mount a KodBox netdisk space to OpenList.
-:::
-::: zh-CN
-使用本驱动可以挂载 KodBox 的网盘空间到 OpenList。
-:::
-
-## Root folder path { lang="en" }
-
-## 根文件夹ID { lang="zh-CN" }
-
-::: en
-Suppose you have a network disk space named `My Files`. If you remount the contents of the network disk space, you need to obtain the path corresponding to `My File`; if you re-display a name in the network disk space for For the directory of `abc`, you must obtain the path corresponding to `My File/abc`, and so on.
+# 可道云
-Example: How to get the path of KodBox network disk space `My File`, the result path is `{source:5}`
+使用本驱动可以挂载 KodBox 的网盘空间到 OpenList。
-Open the KodBox network disk space in the browser. In the console mode, you can see the path corresponding to the network disk space. Do not leave it blank.
-
-:::
+## 根文件夹ID
-::: zh-CN
假设你有一个网盘空间名为 `个人空间`，如果你只想挂载该网盘空间的内容，就要获取`个人空间`对应的 path；如果你只想展示该网盘空间内一个名为 `abc` 的目录，就要获取`个人空间/abc`对应的 path ，以此类推。
示例：如何获取 KodBox 网盘空间`个人空间`的path，得出path为`{source:5}`
@@ -48,76 +18,23 @@ Open the KodBox network disk space in the browser. In the console mode, you can
在浏览器中打开 KodBox 网盘空间，在控制台模式下即可看到网盘空间对应的 path，不可留空不填。
-:::
-
-## Address { lang="en" }
-## 地址 { lang="zh-CN" }
+## 地址
-::: en
-Your KodBox server address, e.g.
-
-- `https://kodcloud.cc`
-- `http://192.168.1.24:8000`
-
-:::
-::: zh-CN
你的 KodBox 服务器地址，形如：
- `https://kodcloud.cc`
- `http://192.168.1.24:8000`
-:::
-
-## Username { lang="en" }
-
-## 用户名 { lang="zh-CN" }
+## 用户名
-::: en
-The email or username used to log in to your KodBox server.
-:::
-::: zh-CN
用于登录你的 KodBox 服务器的邮箱或用户名。
-:::
-## Password { lang="en" }
+## 密码
-## 密码 { lang="zh-CN" }
-
-::: en
-The password for your email or username.
-:::
-::: zh-CN
邮箱或用户名对应的密码。
-:::
-
-### The default download method used { lang="en" }
-
-### 默认使用的下载方式 { lang="zh-CN" }
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[302]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[local proxy]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-::: zh-CN
+### 默认使用的下载方式
```mermaid
---
@@ -137,5 +54,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/lanzou.md b/pages/guide/drivers/lanzou.md
index 66ed5e745..63188662c 100644
--- a/pages/guide/drivers/lanzou.md
+++ b/pages/guide/drivers/lanzou.md
@@ -1,45 +1,14 @@
---
-title:
- en: LanZou Cloud
- zh-CN: 蓝奏云盘
-icon: iconfont icon-state
-# This control sidebar order
top: 688
-# A page can have multiple categories
categories:
- guide
- drivers
-# A page can have multiple tags
-tag:
- - Storage
- - Guide
- - '302'
-# this page is sticky in article list
-sticky: true
-# this page will appear in starred articles
-star: true
---
-
-
-::: en
-Lanzuo Network Disk has three types of **modes (types)**, which are **Accounts**, **Cookie** and **Url**
-
-- **Account**: You can display all the files of your own cloud disk, you only need to fill in the account password, which will automatically help you refresh the cookie
-
-- **Cookie**: All files in the network disk can be displayed, but the cookie of the network disk needs to be provided
-
-- **Url**: only display the content in the link (you can mount it without providing a cookie)
-
-::: tip
-
-It is recommended to use the **Account** method to mount
-
-- Cookie mode needs to manually update Cookie
+# 蓝奏云盘
-:::
+
-::: zh-CN
蓝奏网盘挂载有三种**模式（类型）**，分别是 **账户**，**Cookie** 和 **链接**
- **账户**：可以显示自己网盘所有文件，只需要填写帐号密码，会自动帮你刷新cookie
@@ -55,21 +24,8 @@ It is recommended to use the **Account** method to mount
:::
-## root folder ID { lang="en" }
-
-## 根文件夹 ID { lang="zh-CN" }
-
-::: en
-Lanzuo cloud disk root directory ID, the default is `-1`，If you use `Url`Type to mount the root folder ID, please see the third item of [Fill in instructions](#fill-in-instructions)
-
-- **Additional Folder ID**
- - Two ways to obtain (see the picture below)
-
- 
-
-:::
+## 根文件夹 ID
-::: zh-CN
蓝奏云盘根目录ID，默认为`-1`，如果使用`链接`类型挂载根文件夹ID请看[填写说明](#填写说明)的第三条
- **其他文件夹ID**
@@ -77,102 +33,34 @@ Lanzuo cloud disk root directory ID, the default is `-1`，If you use `Url`Type
-:::
-
-## Account { lang="en" }
-
-## 账户 { lang="zh-CN" }
+## 账户
-::: en
-Just fill in your own Lanzou Cloud Account Password
-:::
-::: zh-CN
只需要填写自己的蓝奏云帐号密码
-:::
-## Cookie { lang="en" }
+## Cookie
-## Cookie { lang="zh-CN" }
-
-::: en
-Log in to your [**Lanzuo Cloud Disk**](https://pc.woozooo.com/) account, then F12 to open the developer mode, you can find `Cookie`, there is no specific one, such as the left side of the picture Just click one and there will be `Cookie` in the blue part of the right picture.
-
-:::
-::: zh-CN
登录自己的 [**蓝奏云盘**](https://pc.woozooo.com/) 账号，然后F12打开开发者模式，就能找到 `Cookie`，没有具体的，例如图片中左侧的随便点一个然后有右图蓝色部分的 `Cookie` 即可.
-:::
-## Share link and share password { lang="en" }
-
-## 分享链接和分享密码 { lang="zh-CN" }
-
-::: en
-
-- **Share link**: Randomly generate a share link in the Lanzuo cloud disk
- - Small tip: **lanzouX** in the link, the last default **X** content sometimes cannot be opened in some areas, you can try to change it yourself, for example, change to i, x, u, t, etc. Anyway, try it out for yourself.
-- **Share password**: the password for the link
-
-:::
-::: zh-CN
+## 分享链接和分享密码
- **分享链接**：在蓝奏云盘内随便生成一个分享链接
- 小提示：链接里面的 **lanzouX**，最后这个默认的 **X**内容有时候有些地区打不开，可以自己更换一下试试看比如换成 i,x,u,t 等等等反正好多自己试试看就行.
- **分享密码**：链接的密码
-:::
-
-## Repair file info { lang="en" }
+## 修复文件信息
-## 修复文件信息 { lang="zh-CN" }
-
-::: en
-If you need **WebDav** service, you need to open it
-:::
-::: zh-CN
需要 **WebDav** 服务的，需要打开它
-:::
-
-## error message { lang="en" }
-
-## 错误信息 { lang="zh-CN" }
-::: en
-Use cookie type or account type to add prompt `not find file page param` error because lanzou changed the domain name
+## 错误信息
-- Solution: It is recommended to use account type to add
- - Change the sharing link to `https://wwop.lanzoul.com` and save it. If it still doesn't work, refresh the lower right corner.
- - lanzoul will also make changes in the future
-
-:::
-
-::: zh-CN
使用Cookie类型或者账户类型添加提示`not find file page param`错误是因为蓝奏云更换了域名
- 解决方案：建议使用账户类型添加
- 把分享链接改成 `https://wwop.lanzoul.com`保存即可，如果还是不可以，右下角刷新一下。
- 后续蓝奏可能还会更改。
-:::
-
-## Fill in instructions { lang="en" }
-
-## 填写说明 { lang="zh-CN" }
-
-::: en
-
-1. **Acount mode**: Type selects `account`, fill in` account` and `password` options, and the `root folder ID` (the default is all files of the root directory)
-2. **Cookie mode**: Type selects `Cookie`, fill in` Cookie`, and the `root folder ID` (the default is all files of the root directory)
-3. **URL mode**: Type selects `Url`, fill in` ShareUrl` and `root folder ID` and`Share Password (if there is a password)`
- - The sharing link is :point_right: https://xxx.lanzou.com/aaabbbccc :point_left: in this format
- - Fill in `ShareUrl`: https://xxx.lanzou.com
- - Fill in `root folder ID`: aaabbbccc
- - Share Password: if there is a password
- 
-
-:::
-
-::: zh-CN
+## 填写说明
1. **账户模式**：类型选择`账户`，填写`账户`和`密码`选项，以及`根文件夹ID`(选填,默认为根目录全部文件)
2. **Cookie模式**：类型选择`Cookie`，填写`Cookie`，以及`根文件夹ID`(选填,默认为根目录全部文件)
@@ -183,35 +71,7 @@ Use cookie type or account type to add prompt `not find file page param` error b
- 在`分享密码`填写：有密码就写没有就不用写
-:::
-
-## The default download method used { lang="en" }
-
-## 默认使用的下载方式 { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[302]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[local proxy]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-::: zh-CN
+## 默认使用的下载方式
```mermaid
---
@@ -231,5 +91,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/lenovo_nas_share.md b/pages/guide/drivers/lenovo_nas_share.md
index 026ea5447..b837257d2 100644
--- a/pages/guide/drivers/lenovo_nas_share.md
+++ b/pages/guide/drivers/lenovo_nas_share.md
@@ -1,130 +1,43 @@
---
-title:
- en: Lenovo Nas Share
- zh-CN: 联想家庭储存链接分享
-icon: iconfont icon-state
-# This control sidebar order
top: 494
-# A page can have multiple categories
categories:
- guide
- drivers
-# A page can have multiple tags
-tag:
- - Storage
- - Guide
- - '302'
-# this page is sticky in article list
-sticky: true
-# this page will appear in starred articles
-star: true
---
-
+# 联想家庭储存链接分享
-::: en
-Need to purchase Lenovo devices **https://pc.lenovo.com.cn**
-:::
+
-::: zh-CN
需要购买联想设备 **https://pc.lenovo.com.cn**
-:::
-
-## Root Folder ID { lang="en" }
-
-## 根文件夹ID { lang="zh-CN" }
-::: en
-Root Folder ID: Leave it blank
+## 根文件夹ID
-Subfolder ID: Get as shown in the picture
-:::
-
-::: zh-CN
根文件夹：留空
子文件夹：按图片所示获取
-:::
-## Share ID and Share Password { lang="en" }
-
-## 分享ID和分享密码 { lang="zh-CN" }
-
-::: en
-Example of share link: https://siot-share.lenovo.com.cn/s/#/eb.3N93ZbJsaAjerjdm4N Extraction code: `e5eu`
-
-- **Share ID**: Fill in the sharing link and automatically extract the string `eb.3N93ZbJsaAjerjdm4N` at the end of the sharing link
-- **Share Password**: The extraction code `e5eu`
+## 分享ID和分享密码
-:::
-
-::: zh-CN
分享链接链接示例：https://siot-share.lenovo.com.cn/s/#/eb.3N93ZbJsaAjerjdm4N 提取码：`e5eu`
- **分享ID**：填写分享链接，自动提取分享链接中末尾的字符串 `eb.3N93ZbJsaAjerjdm4N`
- **分享密码**：提取码 `e5eu`
-:::
-
-## Host Address { lang="en" }
-
-## 主机地址{ lang="zh-CN" }
-
-::: en
-The default uses the public network: **https://siot-share.lenovo.com.cn**
+## 主机地址
-(Not recommended) If you are using a local network, you can change it to the internal network address of the Lenovo device: **http://192.168.XX.XX**
-:::
-
-::: zh-CN
默认使用公网的：**https://siot-share.lenovo.com.cn**
（不推荐）如果你使用局域网的可以改成联想设备内网地址：**http://192.168.XX.XX**
-:::
-
-## Show Root Folder { lang="en" }
-## 显示根文件夹 { lang="zh-CN" }
+## 显示根文件夹
-::: en
-If unchecked and `Share ID` is empty, the folder ID of the first-level folder is automatically filled in.
-Taking the above picture as an example, the contents of the `OpenList` folder are directly displayed without displaying the `OpenList` folder.
-:::
-
-::: zh-CN
若取消勾选且 `分享ID` 为空，自动填入第一级文件夹的文件夹ID。
以上图为例，直接显示 `OpenList` 文件夹中的内容，不显示 `OpenList` 文件夹。
-:::
-
-## The default download method used { lang="en" }
-## 默认使用的下载方式 { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[302]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[local proxy]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-::: zh-CN
+## 默认使用的下载方式
```mermaid
---
@@ -144,5 +57,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/local.md b/pages/guide/drivers/local.md
index c807e0c7f..504347978 100644
--- a/pages/guide/drivers/local.md
+++ b/pages/guide/drivers/local.md
@@ -1,80 +1,27 @@
---
-title:
- en: Local storage
- zh-CN: 本机存储
-icon: iconfont icon-state
-# This control sidebar order
top: 999
-# A page can have multiple categories
categories:
- guide
- drivers
-# A page can have multiple tags
-tag:
- - Storage
- - Guide
- - '本地代理'
-# this page is sticky in article list
-sticky: true
-# this page will appear in starred articles
-star: true
---
-::: en
-Support mounting the directory of the local machine.
-:::
-::: zh-CN
-支持挂载本机的目录。
-:::
-
-## Root folder path { lang="en" }
-
-## 根文件夹ID { lang="zh-CN" }
+# 本机存储
-::: en
-The path of folder you wanted to mount. For example:
+支持挂载本机的目录。
-- Linux: `/root`
-- Windows: `C:`
+## 根文件夹ID
-:::
-::: zh-CN
您要挂载的文件夹的路径。 例如：
- Linux: `/root`
- Windows: `C:`
-:::
-
-## Local storage video thumbnail { lang="en" }
-
-## 本地存储视频封面 { lang="zh-CN" }
+## 本地存储视频封面
-::: en
-You need to use the `ffmpeg` tool to add.
-:::
-
-::: zh-CN
需要使用 `ffmpeg` 工具来添加.
-:::
-
-## Local storage PDF thumbnail on macOS { lang="en" }
-## macOS 本地存储 PDF 缩略图 { lang="zh-CN" }
+## macOS 本地存储 PDF 缩略图
-::: en
-On macOS, the Local storage driver can generate thumbnails from the first page of PDF files using the system Quick Look tool.
-
-To enable this feature:
-
-1. Enable `Thumbnail`.
-2. Enable `PDF thumbnail`.
-3. It is recommended to configure `Thumb cache folder` to avoid rendering the same PDF repeatedly.
-
-This feature is disabled by default and is only available when OpenList runs on macOS. Rendering is performed on cache misses and may consume additional CPU and memory.
-:::
-
-::: zh-CN
在 macOS 上，本机存储驱动可以调用系统 Quick Look 工具，为 PDF 文件生成首页缩略图。
启用方法：
@@ -84,27 +31,9 @@ This feature is disabled by default and is only available when OpenList runs on
3. 建议配置 `缩略图缓存目录（Thumb cache folder）`，避免重复渲染同一 PDF 文件。
该功能默认关闭，并且仅在 OpenList 运行于 macOS 时可用。缓存未命中时会执行渲染，可能额外消耗 CPU 和内存。
-:::
-
-## Recycle bin path { lang="en" }
-
-## 回收站路径 { lang="zh-CN" }
-
-::: en
-path to recycle bin, delete permanently if empty or keep 'delete permanently'
-
-If you fill in this path, you will move the file into the folder when deleting the local storage file, so that you have a chance to regret it.
-
-The method of filling in the above -mentioned mounting path is different from different system filling methods.
-
-If you don’t know if you fill in it correctly, you can test it yourself first and then use the production environment to use it yourself.
-- Linux: `/root`
-- Windows: `C:`
-
-:::
+## 回收站路径
-::: zh-CN
回收站的路径，如果为空则永久删除或保持“永久删除”
如果填写此路径在删除本地存储文件时会将文件移动到此文件夹內，让你有一次后悔的机会。
@@ -116,33 +45,7 @@ If you don’t know if you fill in it correctly, you can test it yourself first
- Linux: `/root`
- Windows: `C:`
-:::
-
-## The default download method used { lang="en" }
-
-## 默认使用的下载方式 { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- c1
- end
- c1[local proxy]:::someclass==default===>a2[user equipment]
- classDef someclass fill:#f96
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-::: zh-CN
+## 默认使用的下载方式
```mermaid
---
@@ -160,5 +63,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/mediafire.md b/pages/guide/drivers/mediafire.md
index 2d79a46a7..fb13e3395 100644
--- a/pages/guide/drivers/mediafire.md
+++ b/pages/guide/drivers/mediafire.md
@@ -1,75 +1,30 @@
---
-title:
- en: MediaFire
- zh-CN: Mediafire
-icon: iconfont icon-state
-# This control sidebar order
top: 520
-# A page can have multiple categories
categories:
- guide
- drivers
---
-::: en
-Mount [MediaFire](https://www.mediafire.com/) cloud storage.
+# Mediafire
-:::
-::: zh-CN
挂载 [MediaFire](https://www.mediafire.com/) 云存储。
-:::
+## 根文件夹ID
-## 根文件夹ID { lang="zh-CN" }
-
-## Root folder path { lang="en" }
-
-::: en
-The default root directory for the path to mount mediafire, default is `/`.
-
-:::
-::: zh-CN
要挂载的Mediafire路径，默认为 `/`。
-:::
-
-## Session Token { lang="zh-CN" }
+## Session Token
-## Session Token { lang="en" }
-
-::: en
-Session Token
-
-Open the browser developer tools, visit [mediafire.com](https://www.mediafire.com/), log in to your account, go to the `Network` tab, open `get_session_token.php`, find `session_token` in the `Response`, and copy its value to fill in.
-
-
-
-:::
-::: zh-CN
会话令牌
打开浏览器开发者工具，访问 [mediafire.com](https://www.mediafire.com/)，登录账号后，查看`Network`（网络）Tab，打开`get_session_token.php`，在`Response`（响应）中找到`session_token`，复制其值填入即可。
-:::
-
-## Cookie { lang="zh-CN" }
-
-## Cookie { lang="en" }
-
-::: en
-Web Cookie
-
-Open the browser developer tools, visit [mediafire.com](https://www.mediafire.com/), log in to your account, go to the `Network` tab, open `get_session_token.php`, find `Cookie` in the `Header`, and copy its value to fill in.
-
-
+## Cookie
-:::
-::: zh-CN
网页Cookie
打开浏览器开发者工具，访问 [mediafire.com](https://www.mediafire.com/)，登录账号后，查看`Network`（网络）Tab，打开`get_session_token.php`，在`Header`（标头）中找到`Cookie`，复制其值填入即可。
-:::
diff --git a/pages/guide/drivers/mediatrack.md b/pages/guide/drivers/mediatrack.md
index 350c5d9cb..3528eb7ce 100644
--- a/pages/guide/drivers/mediatrack.md
+++ b/pages/guide/drivers/mediatrack.md
@@ -1,98 +1,30 @@
---
-title:
- en: Mediatrack
- zh-CN: 分秒帧
-icon: fa-solid fa-x
-# This control sidebar order
top: 680
-# A page can have multiple categories
categories:
- guide
- drivers
-# A page can have multiple tags
-tag:
- - Storage
- - Guide
- - '302'
-# this page is sticky in article list
-sticky: true
-# this page will appear in starred articles
-star: true
---
-::: en
-**https://app.mediatrack.cn**
-:::
-::: zh-CN
-**https://app.mediatrack.cn**
-:::
+# 分秒帧
-### Access token { lang="en" }
+**https://app.mediatrack.cn**
-## 访问令牌 { lang="zh-CN" }
+## 访问令牌
-::: en
-You can get it in request header after logging in
-
-:::
-::: zh-CN
登录后可以在请求头中获取
-:::
-
-### Project id { lang="en" }
-## 项目编号 { lang="zh-CN" }
+## 项目编号
-::: en
-Get from official website url:
-
-:::
-::: zh-CN
从官网网址获取：
-:::
-### Root folder id { lang="en" }
+## 根文件夹 ID
-## 根文件夹 ID { lang="zh-CN" }
-
-::: en
-Get it from the request after logging in
-
-:::
-::: zh-CN
登录后从请求中获取
-:::
-
-### The default download method used { lang="en" }
-
-### 默认使用的下载方式 { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[302]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[local proxy]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-:::
-::: zh-CN
+### 默认使用的下载方式
```mermaid
---
@@ -112,5 +44,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/mega.md b/pages/guide/drivers/mega.md
index 9ea9f8783..c5e0dc837 100644
--- a/pages/guide/drivers/mega.md
+++ b/pages/guide/drivers/mega.md
@@ -1,147 +1,50 @@
---
-title:
- en: MEGA Disk
- zh-CN: MEGA Disk
-icon: iconfont icon-state
-# This control sidebar order
top: 592
-# A page can have multiple categories
categories:
- guide
- drivers
-# A page can have multiple tags
-tag:
- - Storage
- - Guide
- - '本地代理'
- - '官方'
-# this page is sticky in article list
-sticky: true
-# this page will appear in starred articles
-star: true
---
-::: en
-::: warning
-Due to MEGA requires decryption to be performed on the OpenList server backend, **using proxy URL** with this driver cannot avoid server traffic consumption.
-:::
-::: zh-CN
+# MEGA Disk
+
::: warning
由于MEGA需要在OpenList服务器后端实现解密，在该驱动**使用代理地址**不能避免服务器流量消耗。
:::
-::: en
-MEGA official website: **https://mega.nz/login**
-:::
-::: zh-CN
MEGA官网：**https://mega.nz/login**
-:::
-
-### Mail { lang="en" }
-### 邮箱 { lang="zh-CN" }
+### 邮箱
-::: en
-MEGA login account
-:::
-::: zh-CN
MEGA登录账号
-:::
-
-### password { lang="en" }
-### 密码 { lang="zh-CN" }
+### 密码
-::: en
-login password
-:::
-::: zh-CN
登录密码
-::: - -## 2FA { lang="en" } -## 两步验证 { lang="zh-CN" } +## 两步验证 -::: en -Non -filling options,If you open 2FA, you need to fill in it,If you don’t use 2FA, you don’t need to fill in it -::: -::: zh-CN 非必填选项，如果开启了需要填写，没开启的不需要填写 -::: - -### Two fa secret { lang="en" } -### 两步验证秘钥 { lang="zh-CN" } +### 两步验证秘钥 -::: en -**https://mega.nz/fm/account/security/two-factor-authentication** -Click to enable `Enable two-factor authentication (2FA)` and then see a QR code, there is a string of letters below the QR code, This is `Two fa secret`, please record before scanning the code and do not lose it, Should the `Two-factor authentication (2FA) secret` be lost, you can unbinding and then retrieve a new 2FA QR code for setup. - -::: -::: zh-CN **https://mega.nz/fm/account/security/two-factor-authentication** 点击启用 `启用双重验证（2FA）`然后会看到一个二维码，二维码下方有一串字母，这个就是`2FA验证秘钥`，请在扫码绑定前记录一下切勿丢失，`2FA验证秘钥`如果丢失可以解绑重新获取一个新的  -::: - -### Two fa code { lang="en" } -### 两步验证代码 { lang="zh-CN" } +### 两步验证代码 -::: en -To enable 2-factor authentication, you need to install a app that support 2FA (such as [Google Authenticator](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2), [Microsoft Authenticator](https://support.microsoft.com/en-us/account-billing/download-and-install-the-microsoft-authenticator-app-351498fc-850a-45da-b7b6-27e523b8702a)), on your phone. -Then login to OpenList manage and goto `Profile` page, click `Enable 2FA` button, scan the QR code with your 2FA app, and enter the code generated by your 2FA app. -Scan the QR appearing on the screen. At the same time, this QR code is also [two-fa-secret](#two-fa-secret) - -
-::: -::: zh-CN 要启用双因素身份验证，需要在手机上安装支持 TOTP 的验证器，例如 [Google Authenticator](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2)，[Microsoft Authenticator](https://support.microsoft.com/zh-cn/account-billing/%E4%B8%8B%E8%BD%BD%E5%B9%B6%E5%AE%89%E8%A3%85microsoft-authenticator%E5%BA%94%E7%94%A8-351498fc-850a-45da-b7b6-27e523b8702a) 扫描屏幕出现的二维码就可以，同时这个二维码也是[两步验证秘钥](#两步验证秘钥) 
-::: -## Fill in example: { lang="en" } +## 填写示例 -## 填写示例 { lang="zh-CN" } - -::: en - -
-::: -::: zh-CN 
-::: - -### The default download method used { lang="en" } -### 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - c1 - end - c1[local proxy]:::someclass==default===>a2[user equipment] - classDef someclass fill:#f96 - b1[Download proxy URL]-.alternative.->a2[user equipment] - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -159,5 +62,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/misskey.md b/pages/guide/drivers/misskey.md index 8b7d28775..2fa23981d 100644 --- a/pages/guide/drivers/misskey.md +++ b/pages/guide/drivers/misskey.md @@ -1,45 +1,17 @@ --- -title: - en: Misskey Drive - zh-CN: Misskey Drive -icon: iconfont icon-state -# This control sidebar order top: 588 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - '302' -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- -## Instance URL { lang="en" } +# Misskey Drive -## 实例地址 { lang="zh-CN" } +## 实例地址 -::: en -The URL of your Misskey instance, whether self-hosted or in use. -For example, the official instance at `https://misskey.io` -::: -::: zh-CN 自行部署的或正在使用的Misskey实例地址 例如官方实例`https://misskey.io` -::: -## Token { lang="en" } +## Token -## Token { lang="zh-CN" } - -::: en -Visit `https://{misskey-instance}/settings/api` to generate an access token. It requires the `read:drive` and `write:drive` permissions. -::: -::: zh-CN 前往`https://{misskey-instance}/settings/api`生成访问token，需要`read:drive`及`write:drive`权限。 -::: diff --git a/pages/guide/drivers/mopan.md b/pages/guide/drivers/mopan.md index 3814f25e8..00e006d12 100644 --- a/pages/guide/drivers/mopan.md +++ b/pages/guide/drivers/mopan.md @@ -1,114 +1,34 @@ --- -title: - en: MoPan - zh-CN: 四川电信魔盘 -icon: iconfont icon-state -# This control sidebar order top: 691 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - '302' -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- - - -::: en -MoPan address：**https://mopan.sc.189.cn/mopan/#/downloadPc** +# 四川电信魔盘 -- There is no web version, only `Android`, `iOS`, `PC-Win64bit`, `iPad`, and `TV`. - -::: + -::: zh-CN 四川电信魔盘官网链接：**https://mopan.sc.189.cn/mopan/#/downloadPc** - 没有网页端，只有`Android`,`IOS`,`PC-Win64位`,`iPad`,`TV` -::: +## Sms code -## Sms code { lang="en" } - -## Sms code { lang="zh-CN" } - -::: en -Enter the option of the mobile phone number and password when the first addition, and then enter the `SMS Code` input `send`, and then click Save to send it to you. -::: -::: zh-CN 第一次添加时先输入 手机号和密码的选项，然后在`Sms Code`输入 `send`，再点击保存会给你进行发短信，然后将验证码重新输入就可以添加 -::: - -## Root folder ID { lang="en" } - -## 根文件夹ID { lang="zh-CN" } -::: en -Do not fill in this option, it will automatically fill into the root directory +## 根文件夹ID -- Due to encrypted requests, an appropriate method for obtaining folder IDs has not yet been found - -::: -::: zh-CN 留空会自动填充为根目录 - 由于请求加密，暂时未想到合适的获取文件夹 ID 的方法 -::: - -### Tips { lang="en" } - -## 提示 { lang="zh-CN" } - -::: en - -1. `root folder ID`,`equipment information`does not need to be filled in, will automatically help you fill -2. If you enter the send in [SMS Code] (#SMS-Code), it is found that it has been saved,Please click Edit to enter the verification code received - -::: - -::: zh-CN +## 提示 1. `根文件夹ID`、`设备信息`不用填写,会自动帮你填充 2. 如果在[Sms Code](#sms-code)输入验证码后已经保存了，请进入编辑输入收到的验证码 -::: - -### The default download method used { lang="en" } - -### 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -128,5 +48,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/onedrive.md b/pages/guide/drivers/onedrive.md index 345279756..0dd38fa35 100644 --- a/pages/guide/drivers/onedrive.md +++ b/pages/guide/drivers/onedrive.md @@ -1,25 +1,12 @@ --- -title: - en: OneDrive / Share - zh-CN: OneDrive / 分享 -icon: iconfont icon-state -# This control sidebar order top: 599 -# A page can have multiple categories categories: - guide - drivers --- -:::en -:::tip - -- If you have global administrator permissions for a non-home edition, you can use the [OneDrive APP](onedrive_app.md) driver. -- If your account does not support the API, (for example, the school account has not verified the administrator, or the administrator has disabled the API), then you can also mount it through webdav. For details, see [webdav](webdav.md) - -::: +# OneDrive / 分享 -:::zh-CN :::tip - 如果你拥有非家庭版的全局管理员权限，可使用 [OneDrive APP](onedrive_app.md) 驱动 @@ -27,25 +14,8 @@ categories: ::: -## 1. Mounting using Online API's default application { lang="en" } - -## 1. 使用在线 API 的默认应用挂载 { lang="zh-CN" } - -::: en -You do not need to create an application yourself by mounting in this way. - -1. Open and select the corresponding OneDrive version according to your account.
+## 1. 使用在线 API 的默认应用挂载
-2. Check "Use parameters provided by OpenList", click "Get Token", then log in to the OneDrive account you want to mount. After authorization, return to the page to get the refresh token.
-
- 
-
-3. Go to the storage management interface of OpenList, select the OneDrive driver, check "Use online API", fill in the refresh token and you can mount it.
-
- 
-
-:::
-::: zh-CN
通过这种方式挂载，您无需自行创建应用。
1. 打开 ，根据自己的账户选择对应的 OneDrive 版本。
@@ -58,43 +28,7 @@ You do not need to create an application yourself by mounting in this way.
-:::
-
-## 2. Mounting by creating an application manually { lang="en" }
-
-## 2. 手动创建应用挂载 { lang="zh-CN" }
-
-::: en
-
-The application provided by OpenList API may experience issues such as request rate limits due to a high number of users. In this case, you can manually create an application.
-
-1. Navigate to the corresponding management page based on your account type.
- - OneDrive Global：https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade
- - OneDrive 21vianet：https://portal.azure.cn/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade
- - OneDrive Germany：https://portal.microsoftazure.de/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade
- - OneDrive US GOV：https://portal.azure.us/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade
-
-2. After logging in, select `Register Application`, enter `Name`, and select `Accounts and Individuals in Any Organization Directory` (note that you don't look at the location selection but the text here. Some people may be the middle option, don't select a single Tenant or other options, otherwise it will cause problems when logging in), enter the `Redirect URL` as `https://api.oplist.org/onedrive/callback`, click `Register`, and then you can get the `client_id`.
-
- 
-
-3. After registering the application, select `Certificate and Password`, click `New Client Password`, enter a string of passwords, select the one with the longest time, and click `Add`.
-
- (Note: The password entered after adding will disappear, please record the value of client_secret)
-
- 
-
-4. Select `API Permissions`, click `MicroSoft Graph`, enter file in the `Select Permissions`, and check `Files.read` (Note: `Files.read` is a read-only minimum permission. The permission in the figure is larger, and the same can be done), click `Update Permission`.
-
- 
-
-5. Fill in the `client_id` and `client_secret` obtained in the previous step into page, click `Get Token`.
-
-6. Go to OpenList's add storage page, uncheck "Use online API", and fill in the obtained `client_id`, `client_secret`, `Callback URL`, and `Refresh Token` in OpenList.
-
-:::
-
-::: zh-CN
+## 2. 手动创建应用挂载
OpenList 在线 API 提供的默认应用程序因为用户太多，可能存在请求速率限制等问题。此时您可以手动创建应用程序。
@@ -122,59 +56,22 @@ OpenList 在线 API 提供的默认应用程序因为用户太多，可能存在
6. 进入 OpenList 添加存储页面，取消勾选`使用在线API`，将获取到的 `client_id`、`client_secret`、`Callback URL`、`Refresh Token` 填入 OpenList 中
-:::
-
-## Parameters { lang="en"}
-
-## 参数 { lang="zh-CN"}
+## 参数
-### Sharepoint site_id { lang="en" }
+### SharePoint 站点 ID
-### SharePoint 站点 ID { lang="zh-CN" }
-
-::: en
-If you need to mount SharePoint, after completing the above steps, there will be an input field for the site address below the refresh token display. Enter the site address, click to get the `site_id`, and then fill the obtained information into the `site_id` field on the OpenList add storage page. Make sure `Is sharepoint` is enabled.
-:::
-::: zh-CN
如果需要挂载 SharePoint，完成上面的步骤后，在显示刷新令牌的界面的下面有输入站点地址，输入站点地址后点击获取 `site_id`，然后将获取到的信息填入 OpenList 添加存储页面的 `站点ID` 中，确保已启用 `是否Sharepoint`。
-:::
-
-### Root folder path { lang="en" }
-### 根文件夹路径 { lang="zh-CN" }
+### 根文件夹路径
-::: en
-The default is `/`, if you need to customize, just fill in the path, starting from the root path, the same as the local path, such as `/test`
-:::
-::: zh-CN
默认为 `/`，如果需要自定义，就填路径就行，从根路径开始，和本地路径一样，比如 `/test`
-:::
-
-### Chunk size { lang="en" }
-### 分片大小 { lang="zh-CN" }
+### 分片大小
-::: en
-Upload chunk size (MiB). The default is `5`, which means `5 * 1024 * 1024 = 5,242,880` bytes. Make sure to use a size that is a multiple of 320 KiB (`327,680` bytes).
-:::
-::: zh-CN
上传分片大小（MiB），默认值为 `5`，即 `5 * 1024 * 1024 = 5,242,880` 个字节，需要确保使用 320 KiB（`327,680` 个字节）倍数的字节大小。
-:::
-### Custom host { lang="en" }
+### 自定义HOST
-### 自定义HOST { lang="zh-CN" }
-
-::: en
-Custom accelerated download link. This is the domain name of your reverse-proxied OneDrive download API (for example, for personal accounts: `my.microsoftpersonalcontent.com`). Only domain replacement is supported here, not path replacement.
-
-::: warning
-
-- Only hostname replacement is supported, not path.
-- Be sure to properly isolate and only reverse proxy your own paths, otherwise your Cloudflare account may be banned!
-
-:::
-::: zh-CN
自定义加速下载链接。即反代你的 OneDrive 下载 API （如个人版：`my.microsoftpersonalcontent.com`）的域名。
::: warning
@@ -184,33 +81,7 @@ Custom accelerated download link. This is the domain name of your reverse-proxie
:::
-## The default download method used { lang="en" }
-
-## 默认使用的下载方式 { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[302]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[local proxy]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-::: zh-CN
+## 默认使用的下载方式
```mermaid
---
@@ -231,40 +102,14 @@ flowchart TB
click c1 "../drivers/common.html#webdav-策略"
```
-:::
-
-## 3. OneDrive Share Url { lang="en" }
-
-## 3. OneDrive 分享 { lang="zh-CN" }
+## 3. OneDrive 分享
-::: en
-
-:::
-::: zh-CN
-:::
-
-### Url { lang="en" }
-
-### 链接 { lang="zh-CN" }
-
-::: en
-The sharing link is the same as the example below and can be mounted. It can be obtained from E3, E5, A1, and A1P.
-
-```html
-https://connecthkuhk-my.sharepoint.com/:f:/g/personal/jhyang13_connect_hku_hk/EsEgHtGOWbJImxop6tF15FIBIH-ihrjuDclbrbmwWfY_RA?e=s6fitN
-```
-
-If it is OneDrive personal version, it will not work. The link is as follows
-```html
-https://onedrive.live.com/?cid=64EA5FCC7735E8C6&id=64EA5FCC7735E8C6%2117289
-```
+### 链接
-:::
-::: zh-CN
分享链接是这样的可以挂载，来自E3、E5、A1、A1P等
```html
@@ -277,44 +122,11 @@ https://connecthkuhk-my.sharepoint.com/:f:/g/personal/jhyang13_connect_hku_hk/Es
https://onedrive.live.com/?cid=64EA5FCC7735E8C6&id=64EA5FCC7735E8C6%2117289
```
-:::
-
-### Password { lang="en" }
-
-### 密码 { lang="zh-CN" }
+### 密码
-::: en
-It is the extraction code. If you have it, write it. If you don’t have it, don’t fill it in.
-:::
-::: zh-CN
就是提取码，如果有就写，如果没有就不用写
-:::
-
-### The default download method used { lang="en" }
-
-### 默认使用的下载方式 { lang="zh-CN" }
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- c1
- end
- c1[local proxy]:::someclass==default===>a2[user equipment]
- classDef someclass fill:#f96
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-::: zh-CN
+### 默认使用的下载方式
```mermaid
---
@@ -332,5 +144,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/onedrive_app.md b/pages/guide/drivers/onedrive_app.md
index 146e37f24..f3fda105b 100644
--- a/pages/guide/drivers/onedrive_app.md
+++ b/pages/guide/drivers/onedrive_app.md
@@ -1,39 +1,13 @@
---
-title:
- en: OneDrive APP
- zh-CN: OneDrive APP
-icon: iconfont icon-state
-# This control sidebar order
top: 598
-# A page can have multiple categories
categories:
- guide
- drivers
-# A page can have multiple tags
-tag:
- - Storage
- - Guide
- - '302'
-# this page is sticky in article list
-sticky: true
-# this page will appear in starred articles
-star: true
---
-## Benefits and Precautions { lang="en" }
+# OneDrive APP
-## 好处以及注意事项 { lang="zh-CN" }
-
-::: en
-
-1. The advantage is that the administrator is only authorized to log in once, and the same is used when adding parameters later. When adding, everything is the same except for the mailbox.
- - For example, E5 has 25 5T accounts. After you log in and initialize in advance, you can directly use the parameters before the CV. You don’t have to get the refresh token every time as before, and it will expire after a long time
- - A1, A1P, etc. can distribute more accounts (500 - **unlimited**)
-2. After the administrator authorizes in this way, he can view the account of each member in the organization at will, which will leak his own files
- - It is recommended to apply for OneDrive E5 to get better
-
-:::
-::: zh-CN
+## 好处以及注意事项
1. 好处是只授权一次管理员登录，后续添加参数时用一样的，在添加时除了邮箱哪里不同，别的都一样
- 例如E5 25个5T的账号，你提前登录初始化完毕后，直接CV之前的参数即可，不用像以前一样每次都得去获取刷新令牌时间一长还失效
@@ -41,29 +15,10 @@ star: true
2. 这样的方式管理员授权后，可以随意查看组织中每个成员的账号，泄露了自己的文件
- 建议自己申请 OneDrive E5 去好一些
-:::
-::: en
-::: tip
-It is not applicable to the home version. If you are in the configuration process, it does not match the options that appear in the tutorial. It may not be supported
-:::
-::: zh-CN
::: tip
不适用于家庭版，如果你在配置过程中，与教程中出现的选项不符可能是不支持
:::
-::: en
-First log in with your personal or organizational account
-
-
-Login to get our `tenant ID`
-
-
-
-To log in to OneDrive (Operated by 21Vianet), please use this link
-
-
-:::
-::: zh-CN
首先使用个人或者组织账号登录
@@ -75,73 +30,13 @@ To log in to OneDrive (Operated by 21Vianet), please use this link
世纪互联版本的 OneDrive 登录
-:::
-
-## Create process { lang="en" }
-## 新建过程 { lang="zh-CN" }
+## 新建过程
-::: en
-::: danger Read the precautions carefully
-Please read carefully the following **`serial numbers , view in sequence`** , if there is any error, please feedback in time
-:::
-::: zh-CN
::: danger 请仔细阅读注意事项
请仔细阅读下面的 **`序号，依次查看`** ，如有错误可及时反馈
:::
-::: en
-
-1. Register an application, choose the type yourself, it is recommended to choose the third
-2. Redirect URL (callback parameter), select Web as the type, and fill in the parameters **https://entra.microsoft.com/TokenAuthorize** ,Otherwise, it will not be able to authorize later. For OneDrive (Operated by 21Vianet), please use: **https://entra.microsoftonline.cn/TokenAuthorize**
-3. After filling out, click on the registration below and you can see it after jumping `client ID`
- 
-
-Let's get a client secret key, just get it as shown in the figure below, remember `secret key` save in time, it will only appear once
-
-
-Once you have obtained the client secret key, go to authorize the **`API`** to be used, and follow the picture below to get it
-
-
-After the API is authorized, we go to authorize the organization application
-
-- Left sidebar ---> Enterprise applications ---> All applications ---> **{choose which application name we started to create}** ---> Permissions ---> Click for `xxxx `Grant admin consent
- 
-
-matters needing attention
-
-- If you start to register the application, the callback parameters are not the same, you may get an error when you click Authorization, remember to write the same
-- How to check whether the authorization is successful. If it is not authorized, the page will prompt `The application has not been found to have the authorization of the administrator's permission`. After the authorization is successful, refresh the page and you will see three API permissions, as shown in the figure below
- - The above is what it looks like when it is not authorized, and the following is what it looks like after authorization (just refresh the page after authorization)
- 
-
-From the beginning to the present, we have obtained the following parameters: tenant ID1, registered application2, client ID/secret key3, authorization API/administrator API4
-Then open the browser and finally authorize it through the following format, which are `tenant ID` `client ID` `Callback URL` Change to your own final login to receive
-
-```html
-https://login.microsoftonline.com/{tenant ID or common}/adminConsent?client_id={client
-ID}&redirect_uri={Callback URL}
-```
-
-For OneDrive (Operated by 21Vianet), please use:
-
-```html
-https://login.partner.microsoftonline.cn/{tenant ID or common}/adminConsent?client_id={client
-ID}&redirect_uri={Callback URL}
-```
-
-
-If you log in according to the spelled link and find that you are redirected to a blank page, such as the sample code and picture below, the authorization is successful, don’t worry
-
-```
-https://entra.microsoft.com/TokenAuthorize?admin_consent=True&tenant={Tenant ID}#
-```
-
-
-:::
-
-::: zh-CN
-
1. 注册一个应用，类型自己选，建议选第三吧
2. 重定向URL(回调参数)，类型选择Web，参数填写： **https://entra.microsoft.com/TokenAuthorize** ，否则后面授权时无法授权。世纪互联版本的 OneDrive 请填写： **https://entra.microsoftonline.cn/TokenAuthorize**
3. 填好后点击下方的注册 跳转后就可以看到 `客户端ID`
@@ -187,111 +82,29 @@ https://entra.microsoft.com/TokenAuthorize?admin_consent=True&tenant={租户ID}#
```
-:::
-## Fill in the example { lang="en" }
+## 填写示例
-## 填写示例 { lang="zh-CN" }
-
-::: en
-Fill in the values obtained in the above process one by one. If you don’t know which email address it is, you can find it by [**view all users of the organization**](#view-all-users-of-the-organization)
-
-:::
-::: zh-CN
将上述过程中获取得到的值依次填入即可，如果那个邮箱你不知道是什么了，可以通过[**查看组织所有用户**](#查看组织所有用户)来查找
-:::
; )`).
-:::
-::: zh-CN
自定义 S3 请求的 User-Agent。留空默认为 AWS SDK for Go 自动生成（如：`aws-sdk-go/1.55.8 (go1.xx.x; ; )`）。
-:::
-
-## Add object storage examples and official documents { lang="en" }
-## 添加对象存储示例及官方文档 { lang="zh-CN" }
+## 添加对象存储示例及官方文档
-::: en
-`S3 Object Storage` includes but is not limited to these. There are many more, such as Microsoft and Google, which have not been added. There are no examples here because it is difficult to register and activate and cannot provide example tutorials. If you have an account, please contact us and provide an account and I will add it.
-:::
-::: zh-CN
`对象存储`包含但不限于只有这些，还有很多例如微软谷歌没有添加，这里没有示例是因为注册开通困难无法提供示例教程，如果您有帐号欢迎联系提供帐号我来添加
-:::
-### Alibaba { lang="en" }
-
-### 阿里云 { lang="zh-CN" }
-
-::: en
-[**Alibaba Cloud OSS Official Website**](https://oss.console.aliyun.com/)
-
-[**Comparison Table of Endpoints in Different Regions of OSS under Public Cloud**](https://help.aliyun.com/document_detail/31837.html)
-:::
-::: en
-::: tip
-OpenList needs to skip `referer` to mount **Alibaba Cloud Disk**. If you do not allow `referer` to be empty in anti-leech, it will not work, because Alibaba Cloud Disk uses Alibaba Cloud OSS (in Beijing area)
+### 阿里云
-In fact, the `Region|Region` option can be written as `Endpoint`, but for the sake of specification, let’s write it according to the comparison table.:::
-:::
-::: zh-CN
[**阿里云OSS官网**](https://oss.console.aliyun.com/)
[**公共云下OSS各地域Endpoint对照表**](https://help.aliyun.com/document_detail/31837.html)
-:::
-::: zh-CN
+
::: tip
OpenList 挂载**阿里云盘**需要跳过 `referer` ，若你在防盗链开启不允许 `referer` 为空的话会无法使用，因为阿里云盘用的就是阿里云OSS（北京地区的）
其实 `地区|Region` 选项写 `Endpoint` 一样的也可以用，但是为了规范还是照着对照表写吧。
:::
-::: en
-Fill in example:
-
-:::
-::: zh-CN
填写示例：
-:::
-### Tencent { lang="en" }
+### 腾讯云
-### 腾讯云 { lang="zh-CN" }
-
-::: zh-CN
[**腾讯云COS官网**](https://console.cloud.tencent.com/cos)
[**公共云下COS各地域Endpoint对照表**](https://cloud.tencent.com/document/product/436/6224)
@@ -273,22 +110,9 @@ Fill in example:
填写示例：
-:::
-::: en
-[**Tencent Cloud COS Official Website**](https://console.cloud.tencent.com/cos)
-[**Collection Table of Endpoints in Each Region of COS under the Public Cloud**](https://cloud.tencent.com/document/product/436/6224)
+### 火山引擎
-Fill in example:
-
-
-:::
-
-### VolcEngine { lang="en" }
-
-### 火山引擎 { lang="zh-CN" }
-
-::: zh-CN
[**火山引擎TOS官网**](https://console.volcengine.com/tos)
[**公共云下TOS各地域Endpoint对照表**](https://www.volcengine.com/docs/6349/107356)
@@ -296,22 +120,9 @@ Fill in example:
填写示例：
-:::
-::: en
-[**VolcEngine TOS Official Website**](https://console.volcengine.com/tos)
-
-[**Collection Table of Endpoints in Each Region of COS under the Public Cloud**](https://www.volcengine.com/docs/6349/107356)
-Fill in example:
+### 天翼云
-
-:::
-
-### Tianyi { lang="en" }
-
-### 天翼云 { lang="zh-CN" }
-
-::: zh-CN
[**天翼云OOS官网**](https://oos-cn.ctyun.cn/oos/ctyun/consoleBucket.html)
[**公共云下OOS各地域Endpoint对照表**](https://www.ctyun.cn/document/10026693/10027878)
@@ -319,22 +130,9 @@ Fill in example:
填写示例：
-:::
-::: en
-[**Tianyi Cloud OOS Official Website**](https://oos-cn.ctyun.cn/oos/ctyun/consoleBucket.html)
-
-[**Comparison Table of Endpoints of OOS Regions under Public Cloud**](https://www.ctyun.cn/document/10026693/10027878)
-
-Fill in example:
-
-
-:::
-
-### Baidu { lang="en" }
-### 百度云 { lang="zh-CN" }
+### 百度云
-::: zh-CN
[**百度云BOS官网**](https://console.bce.baidu.com/bos)
[**自行配置Bucket的Referer白名单权限**](https://cloud.baidu.com/doc/BOS/s/Bk6kqu8eq#设置referer白名单)
@@ -346,26 +144,9 @@ Fill in example:
填写示例：
-:::
-::: en
-[**Baidu Cloud BOS official website**](https://console.bce.baidu.com/bos)
-
-[**Self-configure Bucket’s Referer whitelist permissions**](https://cloud.baidu.com/doc/BOS/s/Bk6kqu8eq#Setrefererwhitelist)
-
-[**comparison table of Region and Endpoint of BOS under public cloud**](https://intl.cloud.baidu.com/doc/BOS/s/xjwvyq9l4-en)
-
-**Endpoint comparison table compatible with AWS S3**[**Click to view details**](https://cloud.baidu.com/doc/BOS/s/xjwvyq9l4)
-Fill in example:
+### 七牛云
-
-:::
-
-### Qiniu { lang="en" }
-
-### 七牛云 { lang="zh-CN" }
-
-::: zh-CN
[**七牛云Kodo官网**](https://portal.qiniu.com/kodo/bucket)
[**公共云下Kodo各地域Region和Endpoint对照表**](https://developer.qiniu.com/kodo/4088/s3-access-domainname)
@@ -373,22 +154,8 @@ Fill in example:
填写示例：
-:::
-::: en
-[**Qiniu Cloud Kodo official website**](https://portal.qiniu.com/kodo/bucket)
-
-[**Region and Endpoint comparison table of Kodo under the public cloud**](https://developer.qiniu.com/kodo/4088/s3-access-domainname)
-
-Fill in example:
-
-
-:::
-
-### Huawei { lang="en" }
-### 华为云 { lang="zh-CN" }
-
-::: zh-CN
+### 华为云
[**华为云OBS官网**](https://console.huaweicloud.com/console/#/obs/manager/buckets)
@@ -399,22 +166,9 @@ Fill in example:
填写示例：
-:::
-::: en
-[**HUAWEI CLOUD OBS Official Website**](https://www.huaweicloud.com/intl/en-us/)
-
-[**Check the Region and Endpoint comparison table of OBS under the public cloud**](https://developer.huaweicloud.com/intl/en-us/endpoint), the secret key AK/SK[acquire](https://console.huaweicloud.com/iam/?region=cn-north-4#/mine/accessKey) to set by yourself.
-
-Fill in example:
-
-
-:::
-
-### JD { lang="en" }
-### 京东云 { lang="zh-CN" }
+### 京东云
-::: zh-CN
[**京东云OSS官网**](https://www.jdcloud.com/cn/products/object-storage-service)
优点：[免费10G](https://www.jdcloud.com/cn/activity/oss)，支持IPV6
@@ -426,26 +180,9 @@ Fill in example:
填写示例：
-:::
-::: en
-[**JD CLOUD OBS Official Website**](https://www.jdcloud.com/cn/products/object-storage-service)
-
-Advantages: [free 10G](https://www.jdcloud.com/cn/activity/oss), support IPV6
-
-Disadvantages: need to precharge 100 to open，However, after the pre-deposit is completed, the object storage is activated, and the pre-deposited amount can still be used after withdrawal.
-
-[**Region and Endpoint comparison table of Kodo under the public cloud**](https://docs.jdcloud.com/cn/object-storage-service/oss-endpont-list)
-
-Fill in example:
-
-
-:::
-### Doge { lang="en" }
+### 多吉云
-### 多吉云 { lang="zh-CN" }
-
-::: zh-CN
[**多吉云OSS官网**](https://www.dogecloud.com/product/oss)，如果要添加多吉云，请使用单独的`多吉云`驱动添加，请勿使用`对象存储`驱动
地区代码：
@@ -455,24 +192,9 @@ Fill in example:
```
-:::
-::: en
-[**Doge Cloud OSS Official Website**](https://www.dogecloud.com/product/oss)，If you want to add Doge, use a separate `DogeCloud` driver to add, please do not use the `S3` the driver
-
-Region Code：
-
-```json
-// 0: 上海（华东），1: 北京（华北），2: 广州（华南），3: 成都（西南）
-```
-
-
-:::
-
-### 139 { lang="en" }
-### 移动云 { lang="zh-CN" }
+### 移动云
-::: zh-CN
[**移动云EOS官网**](https://console.ecloud.10086.cn/api/page/eos-console-web/CIDC-RP-00/eos/bucket?productType=os&v=new)
[**公共云下OSS各地域Region和Endpoint对照表**](https://ecloud.10086.cn/op-help-center/doc/article/48082)
@@ -480,33 +202,13 @@ Region Code：
填写示例：
-:::
-::: en
-[**139 CLOUD EOS Official Website**](https://console.ecloud.10086.cn/api/page/eos-console-web/CIDC-RP-00/eos/bucket?productType=os&v=new)
-
-[**Region and Endpoint comparison table of Kodo under the public cloud**](https://ecloud.10086.cn/op-help-center/doc/article/48082)
-Fill in example:
+### 又拍云
-
-:::
-
-### upyun { lang="en" }
-
-### 又拍云 { lang="zh-CN" }
-
-::: zh-CN
[**又拍云USS官网**](https://console.upyun.com/services/file/)：[点击这里进行配置USS](./uss.md)
-:::
-::: en
-[**Yupyun USS Official Website**](https://console.upyun.com/services/file/):[Click here to configure USS](./uss.md)
-:::
-
-### Amazon { lang="en" }
-### 亚马逊 { lang="zh-CN" }
+### 亚马逊
-::: zh-CN
[**亚马逊S3官网**](https://s3.console.aws.amazon.com/s3/)
端点 URL 包含存储桶所在的区域名称
@@ -531,40 +233,8 @@ Region (地区)参数：**`us-east-2`**
-:::
-
-::: en
-[**Amazon S3 Official Website**](https://s3.console.aws.amazon.com/s3/)
-
-The endpoint URL contains the name of the region where the bucket is located
-
-Example 1, if your bucket is in the US East (Ohio) region
-
-Then the format of the Endpoint URL is **`s3.us-east-2.amazonaws.com/your-bucket-name`**
-
-Region parameter: **`us-east-2`**
-
-Bucket name: **`your-bucket-name`** (your own bucket name)
-
-Example 2, my storage bucket is `Tokyo`, and the name of the storage bucket is `cdn-aw`, then the complete parameter filling is as follows
-
-1. **Endpoint**: s3.ap-northeast-1.amazonaws.com
-2. **Region**: ap-northeast-1
-3. **Bucket Name**: cdn-aw
-
-Let's take a look at the complete parameter filling example
-
-Fill in example:
-
-
-
-:::
-
-### Cloudflare R2 { lang="en" }
+### Cloudflare R2
-### Cloudflare R2 { lang="zh-CN" }
-
-::: zh-CN
[**Cloudflare R2官网**](https://dash.cloudflare.com/)
**Endpoint**：S3 端点可通过 **`https://.r2.cloudflarestorage.com`** 端点使用
@@ -574,24 +244,9 @@ Fill in example:
填写示例：
-:::
-::: en
-[**Cloudflare R2 Official Website**](https://dash.cloudflare.com/)
-
-**Endpoint**: The S3 endpoint is available via the **`https://.r2.cloudflarestorage.com`** endpoint.
-
-**`ACCOUNT_ID`**: This account ID can be seen everywhere, and the simplest is the position at the top of the browser. The string of IDs behind the website link is your account ID.
-
-填写示例：
-
-
-:::
-
-### Backblaze B2 { lang="en" }
-### Backblaze B2 { lang="zh-CN" }
+### Backblaze B2
-::: zh-CN
[**Backblaze官网**](https://secure.backblaze.com/b2_buckets.htm)
全称 **`Backblaze`**，不需要验证信息，说是前10G免费。
@@ -599,22 +254,9 @@ Fill in example:
填写示例：
-:::
-::: en
-[**B2 Official Website**](https://secure.backblaze.com/b2_buckets.htm)
-
-The full name is **`Backblaze`**, no verification information is required, and it is said that the first 10G is free.
-
-Fill in example:
-
-
-:::
-### Scaleway { lang="en" }
+### Scaleway
-### Scaleway { lang="zh-CN" }
-
-::: zh-CN
[**Scaleway官网**](https://console.scaleway.com/object-storage/buckets)
需要卡验证信息
@@ -624,24 +266,9 @@ Fill in example:
填写示例：
-:::
-::: en
-[**Scaleway Official Website**](https://console.scaleway.com/object-storage/buckets)
-
-Card required, verification information
-
-[**Region and Endpoint comparison table of Kodo under the public cloud**](https://www.scaleway.com/en/docs/storage/object/concepts/#object-storage)
-
-Fill in example:
-
-
-:::
-### Minio { lang="en" }
+### Minio
-### Minio { lang="zh-CN" }
-
-::: zh-CN
使用`Minio`自建对象存储的应该都知道，ID和秘钥如何获取，这里就不说了
只需要填写存储桶名称，访问秘钥ID，安全访问秘钥，Endpoint 这四个选项，地区空着即可
@@ -653,47 +280,9 @@ Fill in example:
填写示例：
-:::
-::: en
-Those who use `Minio` self-built object storage should know how to obtain the ID and secret key, so I won’t talk about it here.
-
-You only need to fill in the four options of bucket name, access key ID, security access key, and Endpoint, and leave the region empty.
-
-**Endpoint：`http(s)://your-server:9001/`**, You can use IP or domain name
-
-Finally, remember to enable **`Force Path Style`** to use, otherwise it cannot be used [Click to view details](https://github.com/alist-org/alist/discussions/4920#discussioncomment-6635452)
-
-Fill in example:
-
-
-:::
-
-### Google Cloud { lang="en" }
-
-::: en
-I assume you already have a Google Cloud account, so let’s go directly to the Google Cloud Storage settings page:
-
-Then you will enter the following page:
-
-
-
-You can see Endpoint and Access Key on this page, you need to select an account and create an Access Key
-
-
-
-Access Key/Secret will be displayed on the new page, They will only be displayed this time. Please save them properly.
-
-
-
-At this point, the EndPoint, access key Id, and security access key required by OpenList have been obtained. Please view the remaining buckets and regions in the corresponding buckets.
-
-
-
-:::
-### Google Cloud { lang="zh-CN" }
+### Google Cloud
-::: zh-CN
默认你已经有Google Cloud的账号了，那么我们直接进入 Google Cloud Storage的设置页面：
然后会进入下面这个页面
@@ -712,39 +301,8 @@ At this point, the EndPoint, access key Id, and security access key required by
-:::
-
-### Intranet access { lang="en" }
-
-### 内网接入 { lang="zh-CN" }
-
-::: en
-The server and object storage need to be in the same region, currently only supports `Alibaba Cloud OSS`. For example, if you are `Alibaba Cloud Hangzhou Server` and `Alibaba OSS in Hangzhou`, you can use it.
-
-- Previous behavior (taking Aliyun OSS as an example):
- - Download link without custom host (using internal endpoint):
-
- ```
- https://.oss-cn-beijing-internal.aliyuncs.com/?X-Amz-Algorithm=***&X-Amz-Credential=***...
- ```
-
- - Download link within custom host (using external endpoint, the following link is **invalid**):
-
- ```
- https://.oss-cn-beijing.aliyuncs.com/
- ```
-
-- Current behavior when `EnableCustomHostPresign` is `false`: Same as previous
-
-- Current behavior when `EnableCustomHostPresign` is `true` :
- - Download link within custom host (using external endpoint, the following link is **valid**):
+### 内网接入
- ```
- https://.oss-cn-beijing.aliyuncs.com/?X-Amz-Algorithm=***&X-Amz-Credential=***...
- ```
-
-:::
-::: zh-CN
服务器和对象存储需要同一地域，目前仅支持`阿里云OSS`。例如你是`阿里云杭州服务器` 和 `杭州地区的对象存储` 就可以使用。
- 之前的行为（以阿里云 OSS 为例）：
@@ -769,54 +327,14 @@ The server and object storage need to be in the same region, currently only supp
https://.oss-cn-beijing.aliyuncs.com/?X-Amz-Algorithm=***&X-Amz-Credential=***...
```
-:::
-
-### How to solve the problem of files with the same name as the folder { lang="en" }
-
-### 出现和文件夹同名文件如何解决 { lang="zh-CN" }
+### 出现和文件夹同名文件如何解决
-::: en
-After mounting the object storage and opening the folder, there is always a file with the same name as the folder that cannot be deleted or opened
-
-- The solution is to change the `List object version` in the configuration to V2, as shown in the following figure
- 
-
-:::
-::: zh-CN
挂载对象存储后打开文件夹后总是会出现一个和文件夹名一样的文件无法删除也无法打开
- 解决办法把配置里面的 `列出对象版本` 换成V2就可以，参考如下图所示
-:::
-
-### The default download method used { lang="en" }
-
-### 默认使用的下载方式 { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[302]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[local proxy]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-::: zh-CN
+### 默认使用的下载方式
```mermaid
---
@@ -836,5 +354,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/seafile.md b/pages/guide/drivers/seafile.md
index 8dc45658d..dbff68bea 100644
--- a/pages/guide/drivers/seafile.md
+++ b/pages/guide/drivers/seafile.md
@@ -1,142 +1,49 @@
---
-title:
- en: Seafile
- zh-CN: Seafile
-icon: iconfont icon-state
-# This control sidebar order
top: 495
-# A page can have multiple categories
categories:
- guide
- drivers
-# A page can have multiple tags
-tag:
- - Storage
- - Guide
- - '302'
-# this page is sticky in article list
-sticky: true
-# this page will appear in starred articles
-star: true
---
-::: en
-Seafile uses libraries as a unit for version control and synchronization.
+# Seafile
-Use this driver to mount a Seafile repository to OpenList, encrypted libraries are supported.
-:::
-::: zh-CN
Seafile 是以资料库为单位进行版本控制和同步的开源云盘。
使用本驱动可以挂载 Seafile 的资料库到 OpenList，已支持访问加密资料库。
-:::
-## Root folder path { lang="en" }
-
-## 根文件夹ID { lang="zh-CN" }
-
-::: en
-
-1. If the `RepoId` is not set, this configuration specifies the name and sub-path of the library to access, defaulting to the root path: `/`, indicating displaying all libraries. Suppose you have a library named `example`, if you only want to mount the contents of this library, you can set this item to `/example`; if you only want to display a directory named `abc` within this library, you can set this item to `/example/abc`, and so on.
-2. If the `RepoId` is set, this configuration is used to set the directory within the specified library, defaulting to the root directory: `/`.
-
-:::
-
-::: zh-CN
+## 根文件夹ID
1. 如果未设置资料库ID（RepoId），则该配置可指定要访问的资料库的名称与子路径，默认为根路径：`/`，表示展示所有资料库。假设你有一个资料库名为 `example`，如果你只想挂载该资料库的内容，可以将本项设为 `/example`；如果你只想展示该资料库内一个名为 `abc` 的目录，则可以将本项设置为 `/example/abc` ，以此类推。
2. 如果设置了资料库ID（RepoId），则该配置用来设置指定资料库内的目录，默认为根目录：`/`。
-:::
-
-## Address { lang="en" }
-
-## 地址 { lang="zh-CN" }
-
-::: en
-Your Seafile server address, e.g.
-
-- `https://seacloud.cc`
-- `http://192.168.1.24:8000`
+## 地址
-:::
-
-::: zh-CN
你的 Seafile 服务器地址，形如：
- `https://seacloud.cc`
- `http://192.168.1.24:8000`
-:::
-
-## Username { lang="en" }
-
-## 用户名 { lang="zh-CN" }
+## 用户名
-::: en
-The email or username used to log in to your Seafile server.
-:::
-::: zh-CN
用于登录你的 Seafile 服务器的邮箱或用户名。
-:::
-## Password { lang="en" }
+## 密码
-## 密码 { lang="zh-CN" }
-
-::: en
-The password for your email or username.
-:::
-::: zh-CN
邮箱或用户名对应的密码。
-:::
-
-## Token { lang="en" }
-## 令牌 { lang="zh-CN" }
+## 令牌
-::: en
-Applicable to certain Seafile cloud storage systems integrated with enterprise/school unified authentication. For such cloud storage systems, there is no need to enter the username and password; only the token information needs to be filled in. Taking Tsinghua Cloud Disk as an example, the following steps can be used to obtain the token: `cookie` → `seahub_auth` → `"student ID@tsinghua.edu.cn@random string"`, where the random string is the token.
-
-:::
-::: zh-CN
适用于某些接入了企业/学校统一认证的Seafile云盘。对于这类云盘，无需填写用户名和密码，只需要填写令牌信息即可。以清华云盘为例，可采用如下步骤获取令牌：`cookie`-->`seahub_auth`-->`"学号@tsinghua.edu.cn@随机字符串"`，这里的随机字符串即为令牌。
-:::
-
-## RepoId (Library ID) { lang="en" }
-
-## RepoId（资料库ID） { lang="zh-CN" }
-
-::: en
-Seafile library ID, such as: `86fc6316-3f2a-4c64-b6f5-d4d2b341bc9a`
-
-- Open the Seafile library in a browser, and you can see the library ID in the address bar.
-- Can be left empty, if left empty, all visible libraries for the specified account will be displayed.
+## RepoId（资料库ID）
-:::
-::: zh-CN
Seafile 资料库ID，形如：`86fc6316-3f2a-4c64-b6f5-d4d2b341bc9a`
- 在浏览器中打开Seafile资料库，即可在地址栏中看到资料库ID。
- 可留空不填，不填则展示指定账号所有可见的资料库。
-:::
+## RepoPwd（资料库密码）
-## RepoPwd (Library Password) { lang="en" }
-
-## RepoPwd（资料库密码） { lang="zh-CN" }
-
-::: en
-Set the password used to access encrypted libraries, leave blank if no encrypted libraries are present.
-
-After configuring this item, OpenList will use this password to access all encrypted libraries for the specified account, without affecting access to unencrypted libraries. If you have multiple encrypted libraries using the same password, they can all be accessed normally.
-
-Different passwords for different libraries within a storage are not currently supported. If you have such a requirement, you can add multiple Seafile storage to achieve this, allowing you to specify different passwords for accessing different encrypted libraries.
-
-If you still cannot access files within encrypted libraries after setting the library password, please check if the password and other configurations above are correct. It is recommended to restart OpenList after modifying this password configuration to avoid caching issues.
-:::
-::: zh-CN
设置用来访问加密资料库的密码，如果没有加密资料库请留空。
配置该项后 OpenList 将会用此密码访问指定账号所有已加密的资料库，不会影响未加密资料库的访问。如果你有多个加密资料库使用了相同的密码则均可以正常访问。
@@ -144,35 +51,8 @@ If you still cannot access files within encrypted libraries after setting the li
暂不支持在一个存储内对不同的资料库配置不同的密码进行访问，如果你有这种需求，可以添加多个 Seafile 存储来实现，这样就可以对不同的加密资料库指定不同的密码进行访问。
如果设置了资料库密码后仍无法访问加密资料库内的文件，请检查密码及上面的其他配置是否有误，建议修改此密码配置后重新启动 OpenList，避免缓存的影响。
-:::
-
-### The default download method used { lang="en" }
-### 默认使用的下载方式 { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[302]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[local proxy]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-::: zh-CN
+### 默认使用的下载方式
```mermaid
---
@@ -192,5 +72,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/sftp.md b/pages/guide/drivers/sftp.md
index e97548054..cd883b40d 100644
--- a/pages/guide/drivers/sftp.md
+++ b/pages/guide/drivers/sftp.md
@@ -1,25 +1,12 @@
---
-title:
- en: SFTP
- zh-CN: SFTP
-icon: iconfont icon-state
-# This control sidebar order
top: 897
-# A page can have multiple categories
categories:
- guide
- drivers
-# A page can have multiple tags
-tag:
- - Storage
- - Guide
- - '本地代理'
-# this page is sticky in article list
-sticky: true
-# this page will appear in starred articles
-star: true
---
+# SFTP
+
即通过 SSH 协议访问文件。
## 地址
diff --git a/pages/guide/drivers/smb.md b/pages/guide/drivers/smb.md
index 75c693bc9..73fa1e8a5 100644
--- a/pages/guide/drivers/smb.md
+++ b/pages/guide/drivers/smb.md
@@ -1,63 +1,18 @@
---
-title:
- en: SMB
- zh-CN: SMB
-icon: iconfont icon-state
-# This control sidebar order
top: 896
-# A page can have multiple categories
categories:
- guide
- drivers
-# A page can have multiple tags
-tag:
- - Storage
- - Guide
- - '本地代理'
-# this page is sticky in article list
-sticky: true
-# this page will appear in starred articles
-star: true
---
-::: en
-It is to mount smb to OpenList, instead of sharing OpenList through smb, instead of sharing smb like webdav.
-Because there are no related equipment and services, it is impossible to test. You can test it yourself according to the method provided in the **`GitHub Discussions`** discussion
-**https://github.com/alist-org/alist/discussions/2215#discussioncomment-4104018**
-Wait for the more detailed tutorials to be supplemented after the relevant equipment or services are available, or wait for the PR of the boss who has no problem with the test.
-:::
-::: zh-CN
+# SMB
+
是把smb挂载到OpenList，而不是OpenList通过smb共享出来，而不是smb能像webdav共享出来。
因无相关设备和服务，无法测试，可以根据 **GitHub Discussions** 讨论中提供的办法自行测试一下
**https://github.com/alist-org/alist/discussions/2215#discussioncomment-4104018**
等待有了相关设备或服务后更详情的教程再进行补充，或者等待测试没问题的大佬pr。
-:::
-
-## The default download method used { lang="en" }
-
-## 默认使用的下载方式 { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- c1
- end
- c1[local proxy]:::someclass==default===>a2[user equipment]
- classDef someclass fill:#f96
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-:::
-::: zh-CN
+## 默认使用的下载方式
```mermaid
---
@@ -75,5 +30,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/strm.md b/pages/guide/drivers/strm.md
index eab3bceda..3ba57d36c 100644
--- a/pages/guide/drivers/strm.md
+++ b/pages/guide/drivers/strm.md
@@ -1,22 +1,10 @@
---
-title:
- en: Strm
- zh-CN: Strm
-icon: iconfont icon-state
-# This control sidebar order
top: 990
-# A page can have multiple categories
categories:
- guide
- drivers
-# A page can have multiple tags
-tag:
- - Storage
- - Guide
-# this page is sticky in article list
-sticky: true
-# this page will appear in starred articles
-star: true
---
+# Strm
+
diff --git a/pages/guide/drivers/strm_text.md b/pages/guide/drivers/strm_text.md
index b66c54755..d9c7c6a56 100644
--- a/pages/guide/drivers/strm_text.md
+++ b/pages/guide/drivers/strm_text.md
@@ -1,17 +1,3 @@
-::: en
-**Strm** is a driver that allows you to convert supported files from multiple cloud drives into .strm files.
-
-::: warning Important Notes
-Please understand the function of strm files before use
-
-Only the **`Download Preview (Read-Only)`** operation is supported. Other operations such as **Copy, Delete, Rename,
-Offline Download, Upload** are **not supported**.
-
-Strm uses a local proxy method, and during the **`Download Preview (Read-Only)`** operation, it will consume traffic
-from the deployed machine (depending on the number of files; individual files typically consume less than 100KB).
-:::
-
-::: zh-CN
**Strm** 是一种可以将多个不同云盘中的支持的文件转换为strm文件的驱动。
::: warning 注意事项
@@ -22,25 +8,9 @@ from the deployed machine (depending on the number of files; individual files ty
Strm采用本地代理方式，在 **`下载预览（只读）`** 操作时会消耗一定部署机器的流量（取决于文件数量、单个文件一般不超过100KB）
:::
-### Parameter Descriptions { lang="en" }
-
-### 参数介绍 { lang="zh-CN" }
-
-#### Path { lang="en" }
-
-#### 路径 { lang="zh-CN" }
-
-::: en
-The full path in OpenList where .strm files should be generated.
-Examples:
-
-```
-/115_open/Video
-/kuake_open/Video
-```
+### 参数介绍
-:::
-::: zh-CN
+#### 路径
需要生成strm文件的`OpenList上的完整路径`。
@@ -51,25 +21,8 @@ Examples:
/kuake_open/Video
```
-:::
-
-#### Site URL { lang="en" }
-
-#### 站点URL { lang="zh-CN" }
+#### 站点URL
-::: en
-The URL prefix for the generated .strm files.
-
-For example, if the directory /115_open/Video contains the file:`/电影/再见，李可乐 (2023)/再见，李可乐 (2023) - 2160p.mkv`
-
-And you enter http://localhost:5244 as the Site URL, the generated .strm file will point to:
-`http://localhost:5244/d/115_open/Video/电影/再见，李可乐 (2023)/再见，李可乐 (2023) - 2160p.strm`
-
-This field is optional. If left blank, the current access URL will be used as the default prefix.
-
-:::
-
-::: zh-CN
Strm文件的URL前缀。
如在`/115_open/Video`目录下有`/电影/再见，李可乐 (2023)/再见，李可乐 (2023) - 2160p.mkv`
@@ -79,30 +32,8 @@ Strm文件的URL前缀。
此项可默认不填、不填时URL前缀会采用你当前访问的地址作为URL前缀
-:::
-
-#### File Type Filter { lang="en" }
-
-#### 过滤文件类型 { lang="zh-CN" }
-
-::: en
-Specify which file types should be included for .strm generation.
-
-The following types are built-in:
-
-```
-Video Type
-mp4,mkv,flv,avi,wmv,ts,rmv,web
-
-Audio Type
-mp3,flac,aac,wav,ogg,m4a,wma,alac
-```
+#### 过滤文件类型
-You can add more types as needed. Use **commas (,)** to separate multiple file types.
-
-:::
-
-::: zh-CN
过滤需要生成的strm的文件类型
目前内置了如下文件类型
@@ -117,30 +48,8 @@ mp3,flac,aac,wav,ogg,m4a,wma,alac
可以自行补充，多文件类型间采用 **,** 分割
-:::
-
-#### Encode Path { lang="en" }
-
-#### 编码路径 { lang="zh-CN" }
+#### 编码路径
-::: en
-Whether to enable URL path encoding.
-
-If disabled, the .strm URL will be:
-
-```
-http://localhost:5244/d/Video/电影/再见，李可乐 (2023)/再见，李可乐 (2023) - 2160p.strm
-```
-
-If enabled, it will be:
-
-```
-http://localhost:5244/d/Video/%E7%94%B5%E5%BD%B1/%E5%86%8D%E8%A7%81%EF%BC%8C%E6%9D%8E%E5%8F%AF%E4%B9%90%20(2023)/%E5%86%8D%E8%A7%81%EF%BC%8C%E6%9D%8E%E5%8F%AF%E4%B9%90%20(2023)%20-%202160p.mkv
-```
-
-:::
-
-::: zh-CN
是否启用路径编码
不启用时生成的strm文件为:
@@ -155,79 +64,25 @@ http://localhost:5244/d/Video/电影/再见，李可乐 (2023)/再见，李可
http://localhost:5244/d/Video/%E7%94%B5%E5%BD%B1/%E5%86%8D%E8%A7%81%EF%BC%8C%E6%9D%8E%E5%8F%AF%E4%B9%90%20(2023)/%E5%86%8D%E8%A7%81%EF%BC%8C%E6%9D%8E%E5%8F%AF%E4%B9%90%20(2023)%20-%202160p.mkv
```
-:::
-
-#### Without Url { lang="en" }
-
-#### 不包含URL前缀 { lang="zh-CN" }
-
-::: en
-The generated strm file will not contain URL prefixes
+#### 不包含URL前缀
-:::
-
-::: zh-CN
开启后生成的strm文件将不包含URL前缀
-:::
-
-#### SaveStrmToLocal { lang="en" }
-
-#### 保存Strm文件至本地 { lang="zh-CN" }
-
-::: en
-When enabled, accessing a directory within or mounted by the Strm driver will save the Strm files locally
+#### 保存Strm文件至本地
-:::
-
-::: zh-CN
开启后访问 strm 驱动中目录或被 strm 驱动挂载的目录时会将 strm 文件保存至本地
-:::
-
-#### SaveStrmLocalPath { lang="en" }
-
-#### 保存Strm文件本地路径 { lang="zh-CN" }
+#### 保存Strm文件本地路径
-::: en
-The local directory path where Strm files are stored.
-
-:::
-
-::: zh-CN
strm文件保存的本地路径
-:::
-
-#### KeepLocalDownloadFile { lang="en" }
-
-#### 保留本地下载文件 { lang="zh-CN" }
+#### 保留本地下载文件
-::: en
-::: warning
-Warning: Deprecated parameter, removed in version 4.1.9 and will be removed in future versions
-:::
-::: zh-CN
::: warning
警告：已废弃参数，4.1.9版本移除，后续版本将彻底移除
:::
-#### Local Save Mode { lang="en" }
-
-#### 本地保存模式 { lang="zh-CN" }
-
-::: en
-
-- `Insert Mode`: Only generate files that do not exist locally; existing local files will not be modified.
-- `Update Mode`: Generate files that do not exist locally and update the content of existing local files to the latest
- version.
-- `Sync Mode`: Based on Update Mode, additionally delete local files that no longer exist on the cloud drive.
-
-> if you need scraper software to read local strm files and generate metadata files, please choose `Update Mode` to ensure that the content of local strm files is up to date and metadata files are not deleted
-
-:::
-
-::: zh-CN
+#### 本地保存模式
- `新增模式`: 仅对本地没有的文件进行生成，对本地文件不进行任何操作
- `更新模式`: 对本地没有的文件进行生成同时更新本地文件内容至最新
@@ -235,23 +90,9 @@ Warning: Deprecated parameter, removed in version 4.1.9 and will be removed in f
> 如果您需要刮削器等软件需要读取本地strm文件且生成元数据文件，请选择`更新模式`，以确保本地strm文件内容是最新的且不会删除元数据文件
-:::
-
-### Actively generate local files { lang="en" }
-
-### 主动生成本地文件 { lang="zh-CN" }
-
-::: en
-The local file generation feature only takes effect when users access the corresponding directory. To recursively generate files for all paths, you can use the **Manually Scan** function, located under `Manage Page / Indices / Manually Scan`. In the **Path to scan** field, enter the **mount path of the Strm driver**, and in the **Rate limit** field, specify the API rate limit for the scanning process. Click start and wait for completion.
-
-Enabling the [Global Settings / Handle hook after writing](/configuration/global#handle-hook-after-writing) allows local files to be automatically generated after performing upload, rename, delete, move, copy, or extraction operations either under the original driver.
-Scheduled or automatic local file generation by listening for driver changes is not currently supported.
-:::
-
-::: zh-CN
+### 主动生成本地文件
生成本地文件功能仅会在用户访问相应目录时生效，为了递归生成所有路径，可以使用**手动扫描**功能，其位于`管理界面 / 索引 / 手动扫描`下，**扫描路径**填写**Strm驱动的挂载路径**，**限制速率**填写扫描过程中的 API 限速，点击开始，等待完成即可。
开启[全局设置 / 写入操作后触发目录更新钩子](/configuration/global#写入操作后触发目录更新钩子)，可以在原驱动下进行上传、重命名、删除、移动、复制、解压操作后自动生成本地文件。
暂不支持定时或监听驱动更改自动生成本地文件。
-:::
diff --git a/pages/guide/drivers/teambition.md b/pages/guide/drivers/teambition.md
index 1f550c21e..7772108fb 100644
--- a/pages/guide/drivers/teambition.md
+++ b/pages/guide/drivers/teambition.md
@@ -1,87 +1,27 @@
---
-title:
- en: Teambition
- zh-CN: Teambition
-icon: iconfont icon-state
-# This control sidebar order
top: 681
-# A page can have multiple categories
categories:
- guide
- drivers
-# A page can have multiple tags
-tag:
- - Storage
- - Guide
- - '302'
-# this page is sticky in article list
-sticky: true
-# this page will appear in starred articles
-star: true
---
+# Teambition
+
-::: en
-Teambition project file, supports Chinese server and international server.
-:::
-::: zh-CN
Teambition 工程文件，支持中国服务器和国际服务器。
-:::
-
-## Cookies { lang="en" }
-## Cookies { lang="zh-CN" }
+## Cookies
-::: en
-After login, the validity period is unknown
-
-:::
-::: zh-CN
登录后获取，有效期未知
-:::
-## Project ID and root folder id { lang="en" }
+## 项目 ID 和根文件夹 ID
-## 项目 ID 和根文件夹 ID { lang="zh-CN" }
-
-::: en
-Get it from the URL after logging in
-
-:::
-::: zh-CN
登录后从网址获取
-:::
-
-## The default download method used { lang="en" }
-# 默认使用的下载方式 { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[302]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[local proxy]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-::: zh-CN
+# 默认使用的下载方式
```mermaid
---
@@ -101,5 +41,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/teldrive.md b/pages/guide/drivers/teldrive.md
index fc59b31c5..633553be2 100644
--- a/pages/guide/drivers/teldrive.md
+++ b/pages/guide/drivers/teldrive.md
@@ -1,39 +1,14 @@
---
-title:
- en: Teldrive
- zh-CN: Teldrive
-icon: iconfont icon-state
-# This control sidebar order
top: 586
-# A page can have multiple categories
categories:
- guide
- drivers
-# A page can have multiple tags
-tag:
- - Storage
- - Guide
- - '302'
-# this page is sticky in article list
-sticky: true
-# this page will appear in starred articles
-star: true
---
-
-
-::: en
-Teldrive is a Telegram-based cloud storage app maintained by a third-party open-source project: [tgdrive/teldrive](https://github.com/tgdrive/teldrive).
+# Teldrive
-**Highlights**
-
-- Unlimited storage
-- No file size limit
-- If you don’t subscribe to Telegram Premium, bandwidth is limited, and speed depends on the distance and bandwidth quality between your account’s data center (DC1–DC5) and the Teldrive server.
+
-Backend deployment requires a **Telegram API (not Bot API)**. See the official guide: [Teldrive installation](https://teldrive-docs.pages.dev/docs/getting-started/prerequisites)
-:::
-::: zh-CN
Teldrive 是一个基于 Telegram 的云存储应用，由第三方开源仓库维护：[tgdrive/teldrive](https://github.com/tgdrive/teldrive)。
**功能特点**
@@ -43,40 +18,15 @@ Teldrive 是一个基于 Telegram 的云存储应用，由第三方开源仓库
- 未订阅 Telegram Premium 时带宽会受限，速度取决于你的账户数据中心（DC1–DC5）与 Teldrive 服务之间的距离和带宽质量。
部署后端需要 **Telegram API（不是 Bot API）**。完整安装指南见：[Teldrive 安装教程](https://teldrive-docs.pages.dev/docs/getting-started/prerequisites)
-:::
-
-## Address { lang="en" }
-## 地址 { lang="zh-CN" }
+## 地址
-::: en
-Enter the base URL of your Teldrive backend **without** a trailing slash.
-
-Example: `https://teldrive.example.com`
-:::
-::: zh-CN
填写 Teldrive 后端的基础网址，**不要**包含末尾斜杠 `/`。
示例：`https://teldrive.example.com`
-:::
-
-## Authentication (Cookie) { lang="en" }
-
-## 认证（Cookie） { lang="zh-CN" }
-
-::: en
-Only **Cookie** authentication is supported.
-After logging in to the Teldrive web UI, grab the cookie from your browser.
+## 认证（Cookie）
-The cookie should **start with** `access_token=` and is a JWT.
-
-
-
-::: tip
-You only need the string **containing** `access_token=`.
-:::
-::: zh-CN
仅支持 **Cookie** 方式认证。
登录 Teldrive 网页端后，从浏览器中获取 Cookie。
@@ -89,84 +39,28 @@ Cookie 应当以 `access_token=` 开头，这是一个 JWT。
只需要**包含** `access_token=` 的那一串字符串。
:::
-## Download methods { lang="en" }
+## 下载方式
-## 下载方式 { lang="zh-CN" }
-
-::: en
-**Note**: If `Use Share Link` is enabled, a shared file link is created and the download URL is valid for **1 hour**.
-
-Otherwise, you need to enable OpenList's `Web Proxy`.
-:::
-::: zh-CN
**注意**：如果启用了 `使用分享链接` 选项，将会创建共享文件链接，下载链接有效期为 **1 小时**。
否则，您需要启用 OpenList 的 Web 代理。
-:::
-
-## Chunk size { lang="en" }
-
-## 分块大小 { lang="zh-CN" }
-::: en
-Upload chunk size in **MiB**.
+## 分块大小
-Default: `10` (10 MiB). If large uploads fail, try a smaller value.
-
-If the chunk size is larger than the file size, the file is uploaded in a single thread without chunking.
-:::
-::: zh-CN
上传时的分块大小，单位 **MiB**。
默认值：`10`（10 MiB）。若大文件上传失败，可尝试调小。
当分块大小大于文件本身大小时，不会分块，文件将以单线程上传。
-:::
-## Upload Concurrency { lang="en" }
+## 上传并发数量
-## 上传并发数量 { lang="zh-CN" }
-
-::: en
-Concurrent upload threads. Default: `4`.
-
-Adjust based on available memory. A handy estimate is:
-`memory ≈ chunk_size × concurrency`
-:::
-::: zh-CN
上传并发线程数，默认：`4`。
请根据可用内存调整，粗略计算：
`内存占用 ≈ 分块大小 × 并发数`
-:::
-## The default download method used { lang="en" }
-
-## 默认使用的下载方式 { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[302]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[local proxy]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-::: zh-CN
+## 默认使用的下载方式
```mermaid
---
@@ -186,5 +80,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-policy"
click c1 "../drivers/common.html#webdav-policy"
```
-
-:::
diff --git a/pages/guide/drivers/terabox.md b/pages/guide/drivers/terabox.md
index e706cc58d..da04a3a6c 100644
--- a/pages/guide/drivers/terabox.md
+++ b/pages/guide/drivers/terabox.md
@@ -1,101 +1,38 @@
---
-title:
- en: Terabox
- zh-CN: Terabox（海外百度）
-icon: iconfont icon-state
-# This control sidebar order
top: 594
-# A page can have multiple categories
categories:
- guide
- drivers
-# A page can have multiple tags
-tag:
- - Storage
- - Guide
- - '302'
-# this page is sticky in article list
-sticky: true
-# this page will appear in starred articles
-star: true
---
+# Terabox（海外百度）
+
https://www.terabox.com/
-## Refresh Token { lang="en" }
-
-## 刷新令牌 { lang="zh-CN" }
+## 刷新令牌
-::: en
-~~[**Click here to log in**](https://www.terabox.com/) to obtain a refresh token~~
-Since F12 is currently disabled on the web page, we can first open F12 on another page and turn on the `Network` → `Preserve log` option.
-
-Then enter https://www.terabox.com in the address bar of this tab to enter the webpage, you can see the reserved request, and then find **`Cookie`** from the reserved request. - -
-::: -::: zh-CN ~~[**点此登录**](https://www.terabox.com/)进行获取刷新令牌，随意找一个请求即可找到 **`Cookie`**~~ 由于目前网页端已经禁用了F12，我们可以先在别的页面打开F12将 `网络` → `保留日志` 选项打开
然后在从这个标签页地址栏输入 https://www.terabox.com 进入网页，就能看到保留的请求，再从保留的请求找找到 **`Cookie`** 
-::: -## Download Api { lang="en" } +## 下载接口 -## 下载接口 { lang="zh-CN" } - -::: en -**Download api needs to choose `Crack`** ，before you can use -
-::: -::: zh-CN **下载接口需要选择 `非官方`** ，才可以使用
-::: - -## Root folder id { lang="en" } - -## 根文件夹ID { lang="zh-CN" } - -::: en -- Root folder id is `/` -- Mount other single subdirectories, put a picture for reference - -
-
-:::
-
-::: zh-CN
+## 根文件夹ID
- 根目录为 `/`
- 挂载其他单个子目录，放一张图参考一下吧
-
-:::
-
-## Download error using Proxy Url link { lang="en" }
-
-## 使用Proxy Url链接下载错误 { lang="zh-CN" }
-
-::: en
-Using [**Proxy Url**](common.md#download-proxy-url) to download error
-
-```json
-{
- "error_code": 31211,
- "error_msg": "access denied"
-}
-```
+## 使用Proxy Url链接下载错误
-View specific reasons：**[https://github.com/alist-org/alist/issues/6508](https://github.com/alist-org/alist/issues/6508#issuecomment-2171762705)**
-
-::: -::: zh-CN 使用了[**Proxy Url**](common.md#下载代理-url)进行下载报错 ```json @@ -107,35 +44,8 @@ View specific reasons：**[https://github.com/alist-org/alist/issues/6508](https 具体原因查看：**[https://github.com/alist-org/alist/issues/6508](https://github.com/alist-org/alist/issues/6508#issuecomment-2171762705)**
-::: - -## The default download method used { lang="en" } - -## 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` -::: -::: zh-CN +## 默认使用的下载方式 ```mermaid --- @@ -155,5 +65,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/thunder.md b/pages/guide/drivers/thunder.md index 970a3274d..cfc931003 100644 --- a/pages/guide/drivers/thunder.md +++ b/pages/guide/drivers/thunder.md @@ -1,41 +1,14 @@ --- -title: - en: Thunder Cloud Disk - zh-CN: 迅雷云盘 / X / 浏览器 -icon: iconfont icon-state -# This control sidebar order top: 685 -# A page can have multiple categories categories: - guide - drivers --- - - -::: en -::: tip -Please use `Thunder` directly instead of `ThunderExpert` if you are not good at it. - -`ThunderExpert` mainly provides more free settings and realizes more login methods - ---- - -`Thunder X` serves overseas users. As of the time of document release, only the Android version is available. Other versions have not yet been released. - -- Thunder X has sufficient speed even without membership. Future changes are unknown. -- Using the APP may require a proxy, but not when mounted on OpenList. - ---- - -`Thunder Browser`：Currently only supports mobile phones (Android, iOS) - -- **https://x.xunlei.com/** -- If you log in to OpenList, the mobile phone will be kicked offline. On the contrary, if you log in to OpenList first and then log in to the mobile phone, OpenList will be kicked offline but there will be no prompt +# 迅雷云盘 / X / 浏览器 -::: + -::: zh-CN ::: tip `迅雷` 前两个是服务**国内用户** @@ -59,72 +32,23 @@ Please use `Thunder` directly instead of `ThunderExpert` if you are not good at ::: -## 1. Thunder { lang="en" } - -## 1. 迅雷 { lang="zh-CN" } - -### Username { lang="en" } +## 1. 迅雷 -### 用户名 { lang="zh-CN" } +### 用户名 -::: en -That is, the mobile phone number, email, and username used for login (there is a probability that you cannot log in, you need to try) - -1. Before obtaining the verification code, do not include the `+86` country code when entering the phone number. -2. After obtaining the verification code, the phone number must include the `+86` country code, for example: +8613722223333. - -::: - -::: zh-CN 即用于登陆的手机号,邮箱,用户名(有概率无法登录,需要尝试) 1. 在获取验证码之前填写手机号先不要携带 `+86` 区号 2. 获取验证码后填写需要携带 `+86` 区号，例如 +8613722223333 这样填写 -::: - -### Password { lang="en" } +### 密码 -### 密码 { lang="zh-CN" } - -::: en -password for login -::: -::: zh-CN 即用于登陆的密码 -::: -
- -### Credit Key { lang="en" } - -### 信用密钥 { lang="zh-CN" } - -::: en -After saving for the first time, an error will occur. This is normal. Please go to the storage management interface. - - - -Copy all the content above. - -[Click here to enter](https://i.xunlei.com/xlcaptcha/android.html) -After entering, open the developer tools (usually by pressing F12), go to the console, and enter `reviewCb()`. **Paste all the previously copied content, including the curly braces,** inside the parentheses, as shown below: - - - -Move the cursor to **after the parentheses** and press Enter. - - - -The webpage will automatically redirect to the mobile number verification page. - -After completing the verification, the page **will not** refresh automatically. Please check the console. The `creditkey` shown below is the required key. - +
-Copy it to the storage management, and you can mount it normally. +### 信用密钥 -::: -::: zh-CN 在第一次保存后会产生报错，这是正常的，请返回存储管理界面  @@ -149,34 +73,7 @@ Copy it to the storage management, and you can mount it normally. 将其复制到存储管理后即可正常挂载 -::: - -### 默认使用的下载方式 { lang="zh-CN" } - -### The default download method used { lang="en" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - c1 - end - c1[local proxy]:::someclass==default===>a2[user equipment] - classDef someclass fill:#f96 - b1[Download proxy URL]-.alternative.->a2[user equipment] - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: - -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -195,65 +92,20 @@ flowchart TB click c1 "../drivers/common.html#webdav-策略" ``` -::: - -## 2. 迅雷专家版 { lang="zh-CN" } +## 2. 迅雷专家版 -## 2. ThunderExpert { lang="en" } - -::: en -::: tip -If Xunlei needs to download, you must specify UserAgent (same as DownUserAgent below). Or use the proxy function in this program to transfer. -::: -::: zh-CN ::: tip 迅雷如果需要下载必须指定 UserAgent(同下 DownUserAgent)，或使用本程序中的代理功能进行中转。 ::: -### 登录类型 { lang="zh-CN" } - -### Login Type { lang="en" } - -::: en - -1. When selecting User, you only need to fill in the username and password - - User You need to bring the `+86` area code, for example +8613722223333 fill in like this -2. **RefreshToken**: Just fill in RefreshToken when selecting RefreshToken - -::: - -::: zh-CN +### 登录类型 1. 选择 `用户名` 时填用户名和密码 - 用户名需要携带 `+86` 区号，例如 +8613722223333 这样填写 2. 选择 `刷新令牌` 时只需填写 `刷新令牌` -::: +### 签名类型 -### 签名类型 { lang="zh-CN" } - -### Signature Type { lang="en" } - -::: en -**Algorithms**：When selecting Algorithms, just fill in the Algorithms (it is difficult to obtain, and needs to be reversed) - -**Captcha sign**: Only fill in CaptchaSign and Timestamp when selecting CaptchaSign - -``` -//signature algorithm -str = ClientID + ClientVersion + PackageName + DeviceID + Timestamp -for (Algorithm in Algorithms) { - str = md5(str + Algorithm) -} -CaptchaSign = "1." + str -``` - -Login type and Sign type recommended options - - - -::: -::: zh-CN 选择 `算法` 时需填写 `算法`(比较难获取,需要逆向) 选择 `验证码签名` 时只需填写 `验证码签名` 和 `时间戳` @@ -271,90 +123,25 @@ CaptchaSign = "1." + str  -::: - -### 设备ID { lang="zh-CN" } - -### DeviceID { lang="en" } +### 设备ID -::: en -The value calculated by md5 is used to determine the logged in device -::: - -::: zh-CN 通过 MD5 计算的值，用于判断登录的设备 -::: -### 客户端ID, 客户端秘钥, 客户端版本, 包名 { lang="zh-CN" } +### 客户端ID, 客户端秘钥, 客户端版本, 包名 -### ClientID, ClientSecret, ClientVersion, PackageName { lang="en" } - -::: en -It is related to the signature, fill in according to the actual situation -::: -::: zh-CN 与签名有关，根据实际情况填写 -::: -### 用户代理 { lang="zh-CN" } +### 用户代理 -### UserAgent { lang="en" } - -::: en -UserAgent used by API requests, may be inaccessible or speed limited if the setting is incorrect -::: -::: zh-CN API 请求使用的 UserAgent，设置错误可能无法访问或限速 -::: -### 下载用户代理 { lang="zh-CN" } +### 下载用户代理 -### DownUserAgent { lang="en" } - -::: en -The User Agent used for downloading, if the setting is wrong, it will not be downloaded (it will be used when the agent is turned on) Fixed parameters: - -`Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36` -::: -::: zh-CN 下载时用到的 User Agent，如果设置错误会无法下载(开启代理会使用) 固定参数： `Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36` -::: - -### 关键数据获取流程 { lang="zh-CN" } - -### Key data acquisition process { lang="en" } - -::: en -Obtain Xunlei request data through network analysis tools (packet capture tools) --- Please read the following information carefully - -Open Xunlei and log in to your account (the picture below uses the PC client to operate, and the web terminal is also available) - -Included in the request https://xluser-ssl.xunlei.com/v1/shield/captcha/init - -CaptchaSign, Timestamp, DeviceID, ClientID, ClientVersion, PackageName, User-Agent - -**Note**: After obtaining the information of the two pictures, slowly select the data from the two data captured and fill in it - -After logging in to Thunder and opening the packet capture tool, it is possible that the information of **v1/shield/captcha/init** cannot be immediately obtained at this time. - -Do not close the Xunlei PC client and the packet capture tool, just wait, it will refresh automatically after **5 minutes** - -You will see the parameters as shown in the figure below, and you can fill in it according to the acquisition (if you can't see it clearly, you can right-click to copy the picture and link it to the browser to open a new window) - -See **v1/shield/captcha/init** and grab it, please **immediately don't delay for a second** Right-click Xunlei in the taskbar in the lower right corner to exit, exit completely and then reopen to get \* \*Figure II\*\* - - -Restarting Thunder will refresh the token - -The request to https://xluser-ssl.xunlei.com/v1/auth/token contains RefreshToken (please use the returned value), ClientSecret (does not exist on the web side) - - -Figure 1 contains **7** parameters | Figure 1 contains **2** parameters | a fixed parameter (Down UserAgent), ten parameters and 3 options and a mount path, just write and save, before saving Remember to check~ -::: -::: zh-CN +### 关键数据获取流程 通过网络分析工具(抓包工具)获取迅雷请求数据 @@ -383,60 +170,18 @@ CaptchaSign、Timestamp、DeviceID、ClientID、ClientVersion、PackageName、Us  图一包含 **7 条** 参数 | 图一包含 \*\*2 条\*\* 参数 | 一条固定参数(Down UserAgent) ，十条参数 和 3 个选项 以及一个挂载路径，写好保存即可，保存前记得检查喔~~ -::: -### 使用视频URL { lang="zh-CN" } +### 使用视频URL -::: en -When the `Video URL` option is enabled, it will attempt to replace the original link with the media link returned by the API. Currently, the official platform throttles the download link for **non-members**, but video streaming is not throttled. Therefore, by replacing the link, you can avoid throttling, which applies to both **OpenList** media file downloads and streaming. For regular files, you can also bypass the throttling by renaming the file extension to a media format (e.g., `.mp4`). - -The **Expert Edition** does not enable the `Video URL` option by default, as it is intended for users who configure detailed parameters themselves, and they should be aware of the significance of this option. Hence, it is not enabled by default. For **Xunlei X** users, this option is enabled by default, primarily for the convenience of less experienced users. -::: - -::: zh-CN `视频URL` 开启后，会尝试使用接口返回的媒体链接进行替换原本的链接。目前官方对 `非会员` 情况下，下载链接进行了限速，但视频播放是不限速的。因此可以通过替换链接的方式来避免限速，这一点对于 `OpenList` 媒体文件下载和在线播放均生效。对于普通文件，也可以采取重命名文件后缀为媒体格式（例如：`.mp4` ）的方式绕过限速。 专家版没默认开启 `视频URL`选项，目的是针对于自行配置详细参数的人群来说，应当知晓该选项的意义，因此默认不启用。对于 `迅雷X` 驱动默认启用该选项，更多的是为了小白用户考虑。 -::: - -### 迅雷专家版 完整的参数填演示图 { lang="zh-CN" } -### ThunderExpert complete parameter filling demo: { lang="en" } +### 迅雷专家版 完整的参数填演示图 -::: en  -::: -::: zh-CN - -::: - -### 默认使用的下载方式 { lang="zh-CN" } - -### The default download method used { lang="en" } -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -457,61 +202,24 @@ flowchart TB click c1 "../drivers/common.html#webdav-策略" ``` -## 3. Thunder X { lang="en" } - -## 3. 迅雷 X { lang="zh-CN" } +## 3. 迅雷 X -::: zh-CN ::: danger 目前官方对于频繁调用接口行为会进行封号处理，请谨慎使用，后果自负。 ::: -::: en -::: danger -At present, the official will ban frequent API calls. Please use with caution and bear the consequences. -::: - -### 用户名、密码 { lang="zh-CN" } -### username、password { lang="en" } +### 用户名、密码 -::: en -The mailbox and password used for login -
-::: -::: zh-CN 即用于登陆的邮箱和密码
-::: -### 验证码 { lang="zh-CN" } +### 验证码 -### CaptchaToken { lang="en" } - -::: en -It will be filled automatically without filling in manually -
-::: -::: zh-CN 会自动填充，不用自己填写
-::: -### 根文件夹ID { lang="zh-CN" } +### 根文件夹ID -### Root folder id { lang="en" } - -::: en -The default is the full directory of the empty display, If you want to use a subfolder to make the root directory, grab the request to get it - -- In the request in the package`https://api-pan.xunleix.com/drive/v1/files?parent_id=&page_token=&filters=`，you can get the following parameters - - `文件夹ID（id）` - - `文件夹名称（name）` - - `父文件夹ID（parent_id）` -- The `folder ID` obtained in the root directory (for example : `我接收的文件`、`我的云盘`、`高速云下载`), **This will change with different account numbers, there is no the same value, In the request in the package** -  - -::: -::: zh-CN 默认为空展示全部目录，如果想用子文件夹做根目录请抓包获取 - 抓包请求中的`https://api-pan.xunleix.com/drive/v1/files?parent_id=&page_token=&filters=`，可以得到下面参数 @@ -521,51 +229,13 @@ The default is the full directory of the empty display, If you want to use a sub - 根目录下获取的`文件夹ID（Folder id）`（例如：`我接收的文件`、`我的云盘`、`高速云下载`），**这个会随着账号不同而变动，没有通用的值，自己抓包获取**  -::: - -### 使用视频URL { lang="zh-CN" } - -### Use video url { lang="en" } +### 使用视频URL -::: en -When the `Video URL` option is enabled, it will attempt to replace the original link with the media link returned by the API. Currently, the official platform throttles the download link for **non-members**, but video streaming is not throttled. Therefore, by replacing the link, you can avoid throttling, which applies to both **OpenList** media file downloads and streaming. For regular files, you can also bypass the throttling by renaming the file extension to a media format (e.g., `.mp4`). - -The **Expert Edition** does not enable the `Video URL` option by default, as it is intended for users who configure detailed parameters themselves, and they should be aware of the significance of this option. Hence, it is not enabled by default. For **Xunlei X** users, this option is enabled by default, primarily for the convenience of less experienced users. -::: - -::: zh-CN `视频URL` 开启后，会尝试使用接口返回的媒体链接进行替换原本的链接。目前官方对 `非会员` 情况下，下载链接进行了限速，但视频播放是不限速的。因此可以通过替换链接的方式来避免限速，这一点对于 `OpenList` 媒体文件下载和在线播放均生效。对于普通文件，也可以采取重命名文件后缀为媒体格式（例如：`.mp4` ）的方式绕过限速。 专家版没默认开启 `视频URL`选项，目的是针对于自行配置详细参数的人群来说，应当知晓该选项的意义，因此默认不启用。对于 `迅雷X` 驱动默认启用该选项，更多的是为了小白用户考虑。 -::: - -### 默认使用的下载方式 { lang="zh-CN" } -### The default download method used { lang="en" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -586,63 +256,24 @@ flowchart TB click c1 "../drivers/common.html#webdav-策略" ``` -::: - -## 4. 迅雷 X 专家版 { lang="zh-CN" } - -## 4. Thunder X Expert { lang="en" } +## 4. 迅雷 X 专家版 -::: en -::: danger -At present, the official will ban frequent API calls. Please use with caution and bear the consequences. -::: -::: zh-CN ::: danger 目前官方对于频繁调用接口行为会进行封号处理，请谨慎使用，后果自负。 ::: -### 用户名、密码 { lang="zh-CN" } - -### username、password { lang="en" } +### 用户名、密码 -::: en -The mailbox and password used for login -
-::: -::: zh-CN 即用于登陆的邮箱和密码
-::: - -### 验证码 { lang="zh-CN" } -### CaptchaToken { lang="en" } +### 验证码 -::: en -It will be filled automatically without filling in manually -
-::: -::: zh-CN 会自动填充，不用自己填写
-::: -### 根文件夹ID { lang="zh-CN" } +### 根文件夹ID -### Root folder id { lang="en" } - -::: en -The default is the full directory of the empty display, If you want to use a subfolder to make the root directory, grab the request to get it - -- In the request in the package`https://api-pan.xunleix.com/drive/v1/files?parent_id=&page_token=&filters=`，you can get the following parameters - - `文件夹ID（id）` - - `文件夹名称（name）` - - `父文件夹ID（parent_id）` -- The `folder ID` obtained in the root directory (for example : `我接收的文件`、`我的云盘`、`高速云下载`), **This will change with different account numbers, there is no the same value, In the request in the package** -  - -::: -::: zh-CN 默认为空展示全部目录，如果想用子文件夹做根目录请抓包获取 - 抓包请求中的`https://api-pan.xunleix.com/drive/v1/files?parent_id=&page_token=&filters=`，可以得到下面参数 @@ -652,75 +283,17 @@ The default is the full directory of the empty display, If you want to use a sub - 根目录下获取的`文件夹ID（Folder id）`（例如：`我接收的文件`、`我的云盘`、`高速云下载`），**这个会随着账号不同而变动，没有固定一样的值，自己抓包获取**  -::: - -### 登录类型 { lang="zh-CN" } - -### Login Type { lang="en" } - -::: en - -- `User`: Only fill in the username and password -- `Refresh token`: Just fill in`RefreshToken` - -::: -::: zh-CN +### 登录类型 - `用户`：选择 `用户`时填`用户名和密码` - `刷新令牌`：选择 `刷新令牌` 时只需填写 `刷新令牌` -::: - -### 签名类型 { lang="zh-CN" } - -### Sign Type { lang="en" } - -::: en - -- `Algorithms`：Choose `Algorithms` Just fill in `Algorithms` (It has been automatically filled. You do n’t have to fill in it yourself. You only need to fill in the username and password.When the algorithm is not invalidated) -- `Captcha sign`: Choose `Captcha sign` Just fill in `Captcha sign` and `Timestamp` - -::: - -::: zh-CN +### 签名类型 - `算法`：选择 `算法（Algorithms）` 时需填写 `算法（Algorithms）` - `验证码签名`：选择 `验证码签名（Captcha sign）` 时只需填写 `验证码签名（Captcha sign）` 和 `时间戳（Timestamp）` -::: - -### 部分参数抓包说明 { lang="zh-CN" } - -### Part of parameter Packet Capture description { lang="en" } - -::: en - -- `Captcha token`：No need to fill in -- `Device id`：The value calculated by MD5 is used to judge the login device -- `Client id`, `Client secret`, `Client version`, `Package name`：It related to the signature, fill in according to the actual situation - ---- - -- `User agent`：API requests `User agent`, setting errors may not access or speed limit -- `Download user agent`：When downloading, use the `user agent `,If the setting error cannot be downloaded (the agent will use it) - - `User agent` and `Download user agent`：You can fill it out by yourself. If you don’t know how to fill it out, you can leave it blank and it will be automatically filled in. - ---- - -In the request in the package `https://xluser-ssl.xunleix.com/v1/shield/captcha/init`，you can get the following parameters6 - -- `Client id`、`Device id`、`Captcha sign` -- `Package name`、`Client version`、`Timestamp` - -  - - In the request in the package `https://xluser-ssl.xunleix.com/v1/auth/signin`, you can get the following parameters2 - - `Client id`、`Client secret` -  - -::: - -::: zh-CN +### 部分参数抓包说明 - `验证码`：无需填写 - `设备id`：通过 MD5 计算的值，用于判断登录的设备 @@ -746,51 +319,13 @@ In the request in the package `https://xluser-ssl.xunleix.com/v1/shield/captcha/ - `客户端ID（Client id）`、`客户端密钥（Client secret）`  -::: +### 使用视频URL -### 使用视频URL { lang="zh-CN" } - -### Use video url { lang="en" } - -::: en -When the `Video URL` option is enabled, it will attempt to replace the original link with the media link returned by the API. Currently, the official platform throttles the download link for **non-members**, but video streaming is not throttled. Therefore, by replacing the link, you can avoid throttling, which applies to both **OpenList** media file downloads and streaming. For regular files, you can also bypass the throttling by renaming the file extension to a media format (e.g., `.mp4`). - -The **Expert Edition** does not enable the `Video URL` option by default, as it is intended for users who configure detailed parameters themselves, and they should be aware of the significance of this option. Hence, it is not enabled by default. For **Xunlei X** users, this option is enabled by default, primarily for the convenience of less experienced users. -::: - -::: zh-CN `视频URL` 开启后，会尝试使用接口返回的媒体链接进行替换原本的链接。目前官方对 `非会员` 情况下，下载链接进行了限速，但视频播放是不限速的。因此可以通过替换链接的方式来避免限速，这一点对于 `OpenList` 媒体文件下载和在线播放均生效。对于普通文件，也可以采取重命名文件后缀为媒体格式（例如：`.mp4` ）的方式绕过限速。 专家版没默认开启 `视频URL`选项，目的是针对于自行配置详细参数的人群来说，应当知晓该选项的意义，因此默认不启用。对于 `迅雷X` 驱动默认启用该选项，更多的是为了小白用户考虑。 -::: - -### 默认使用的下载方式 { lang="zh-CN" } - -### The default download method used { lang="en" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` -::: -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -811,56 +346,20 @@ flowchart TB click c1 "../drivers/common.html#webdav-策略" ``` -::: - -## 5.迅雷浏览器 { lang="zh-CN" } - -## 5. Thunder Browser { lang="en" } +## 5.迅雷浏览器 -### 用户名、密码 { lang="zh-CN" } +### 用户名、密码 -### username、password { lang="en" } - -::: en -Mobile phone number, email, username, and password used to log in - -- When filling in the mobile phone number, please bring the `+86` area code, for example `+8613822334455` - -::: -::: zh-CN 即用于登陆的手机号,邮箱,用户名，以及密码 - 填写手机号要携带 `+86` 区号，例如 `+8613822334455` -::: - -### 验证码 { lang="zh-CN" } - -### CaptchaToken { lang="en" } +### 验证码 -::: en -It will be filled automatically without filling in manually -::: -::: zh-CN 会自动填充，不用自己填写 -::: - -### 根文件夹ID { lang="zh-CN" } -### Root folder id { lang="en" } +### 根文件夹ID -::: en -The default is the full directory of the empty display, If you want to use a subfolder to make the root directory, grab the request to get it - -- In the request in the package`https://x-api-pan.xunlei.com/drive/v1/files?parent_id&page_token&space=`，you can get the following parameters - - `文件夹ID（id）` - - `文件夹名称（name）` - - `父文件夹ID（parent_id）` -- The `folder ID` obtained in the root directory (for example : `来自分享`、`超级保险箱`), **This will change with different account numbers, there is no the same value, In the request in the package** -  - -::: -::: zh-CN 默认为空展示全部目录，如果想用子文件夹做根目录请抓包获取 - 抓包请求中的`https://x-api-pan.xunlei.com/drive/v1/files?parent_id&page_token&space=`，可以得到下面参数 @@ -870,82 +369,24 @@ The default is the full directory of the empty display, If you want to use a sub - 根目录下获取的`文件夹ID（Folder id）`（例如：`来自分享`、`超级保险箱`），**这个会随着账号不同而变动，没有固定一样的值，自己抓包获取**  -::: - -### 保险箱密码 { lang="zh-CN" } - -### Safe password { lang="en" } +### 保险箱密码 -::: en -Thunder Browser Safe password - -- Files in Safe password can only be deleted directly and cannot be deleted to the recycle bin, so the [**Deletion method**](#remove-way) below has nothing to do with this configuration. - -::: -::: zh-CN 迅雷浏览器云盘的保险箱密码 - 超级保险箱內文件只能直接删除 无法删除到回收站，所以下方[**删除方式**](#删除方式)与此配置无关 -::: - -### 删除方式 { lang="zh-CN" } - -### Remove way { lang="en" } +### 删除方式 -::: en -**Trash**：Use OpenList to delete files and then move them to the Recycle Bin. If you delete them accidentally, you can restore them through Thunder Cloud Disk. -**Delete**：Deleting it directly cannot restore it. -::: - -::: zh-CN **回收站**：在OpenList删除后移除到回收站，如果有误删可以通过迅雷云盘恢复 **删除**：直接删除不可以恢复找回 -::: - -### 使用视频URL { lang="zh-CN" } - -### Use video url { lang="en" } - -::: en -When the `Video URL` option is enabled, it will attempt to replace the original link with the media link returned by the API. Currently, the official platform throttles the download link for **non-members**, but video streaming is not throttled. Therefore, by replacing the link, you can avoid throttling, which applies to both **OpenList** media file downloads and streaming. For regular files, you can also bypass the throttling by renaming the file extension to a media format (e.g., `.mp4`). -The **Expert Edition** does not enable the `Video URL` option by default, as it is intended for users who configure detailed parameters themselves, and they should be aware of the significance of this option. Hence, it is not enabled by default. For **Xunlei X** users, this option is enabled by default, primarily for the convenience of less experienced users. -::: +### 使用视频URL -::: zh-CN `视频URL` 开启后，会尝试使用接口返回的媒体链接进行替换原本的链接。目前官方对 `非会员` 情况下，下载链接进行了限速，但视频播放是不限速的。因此可以通过替换链接的方式来避免限速，这一点对于 `OpenList` 媒体文件下载和在线播放均生效。对于普通文件，也可以采取重命名文件后缀为媒体格式（例如：`.mp4` ）的方式绕过限速。 专家版没默认开启 `视频URL`选项，目的是针对于自行配置详细参数的人群来说，应当知晓该选项的意义，因此默认不启用。对于 `迅雷X` 驱动默认启用该选项，更多的是为了小白用户考虑。 -::: - -### 默认使用的下载方式 { lang="zh-CN" } -### The default download method used { lang="en" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -966,59 +407,21 @@ flowchart TB click c1 "../drivers/common.html#webdav-策略" ``` -::: - -## 6. 迅雷浏览器专家版 { lang="zh-CN" } - -## 6. Thunder Browser Expert { lang="en" } - -### 用户名、密码 { lang="zh-CN" } - -### username、password { lang="en" } +## 6. 迅雷浏览器专家版 -::: en -Mobile phone number, email, username, and password used to log in +### 用户名、密码 -- When filling in the mobile phone number, please bring the `+86` area code, for example `+8613822334455` - -::: -::: zh-CN 即用于登陆的手机号,邮箱,用户名，以及密码 - 填写手机号要携带 `+86` 区号，例如 `+8613822334455` -::: +### 验证码 -### 验证码 { lang="zh-CN" } - -### CaptchaToken { lang="en" } - -::: en -It will be filled automatically without filling in manually -
-::: -::: zh-CN 会自动填充，不用自己填写
-::: - -### 根文件夹ID { lang="zh-CN" } -### Root folder id { lang="en" } +### 根文件夹ID -::: en -The default is the full directory of the empty display, If you want to use a subfolder to make the root directory, grab the request to get it - -- In the request in the package`https://x-api-pan.xunlei.com/drive/v1/files?parent_id&page_token&space=`，you can get the following parameters - - `文件夹ID（id）` - - `文件夹名称（name）` - - `父文件夹ID（parent_id）` -- The `folder ID` obtained in the root directory (for example : `来自分享`、`超级保险箱`), **This will change with different account numbers, there is no the same value, In the request in the package** -  - -::: - -::: zh-CN 默认为空展示全部目录，如果想用子文件夹做根目录请抓包获取 - 抓包请求中的`https://x-api-pan.xunlei.com/drive/v1/files?parent_id&page_token&space=`，可以得到下面参数 @@ -1028,104 +431,28 @@ The default is the full directory of the empty display, If you want to use a sub - 根目录下获取的`文件夹ID（Folder id）`（例如：`来自分享`、`超级保险箱`），**这个会随着账号不同而变动，没有固定一样的值，自己抓包获取**  -::: - -### 保险箱密码 { lang="zh-CN" } - -### Safe password { lang="en" } - -::: en -Thunder Browser Safe password - -- Files in Safe password can only be deleted directly and cannot be deleted to the recycle bin, so the [**Deletion method**](#remove-way-1) below has nothing to do with this configuration. +### 保险箱密码 -::: -::: zh-CN 迅雷浏览器云盘的保险箱密码 - 超级保险箱內文件只能直接删除 无法删除到回收站，所以下方[**删除方式**](#删除方式-1)与此配置无关 -::: - -### 删除方式 { lang="zh-CN" } +### 删除方式 -### Remove way { lang="en" } - -::: en -**Trash**：Use OpenList to delete files and then move them to the Recycle Bin. If you delete them accidentally, you can restore them through Thunder Cloud -**Delete**：Deleting it directly cannot restore it. -::: -::: zh-CN **回收站**：在OpenList删除后移除到回收站，如果有误删可以通过迅雷云盘恢复 **删除**：直接删除不可以恢复找回 -::: -### 登录类型 { lang="zh-CN" } - -### Login Type { lang="en" } - -::: en - -- `User`: Only fill in the username and password -- `Refresh token`: Just fill in`RefreshToken` - -::: -::: zh-CN +### 登录类型 - `用户`：选择 `用户`时填`用户名和密码` - `刷新令牌`：选择 `刷新令牌` 时只需填写 `刷新令牌` -::: - -### 签名类型 { lang="zh-CN" } - -### Sign Type { lang="en" } - -::: en - -- `Algorithms`：Choose `Algorithms` Just fill in `Algorithms` (It has been automatically filled. You do n’t have to fill in it yourself. You only need to fill in the username and password.When the algorithm is not invalidated) -- `Captcha sign`: Choose `Captcha sign` Just fill in `Captcha sign` and `Timestamp` - -::: -::: zh-CN +### 签名类型 - `算法`：选择 `算法（Algorithms）` 时需填写 `算法（Algorithms）` - `验证码签名`：选择 `验证码签名（Captcha sign）` 时只需填写 `验证码签名（Captcha sign）` 和 `时间戳（Timestamp）` -::: - -### 部分参数抓包说明 { lang="zh-CN" } - -### Part of parameter Packet Capture description { lang="en" } - -::: en - -- `Captcha token`：No need to fill in -- `Device id`：The value calculated by MD5 is used to judge the login device -- `Client id`, `Client secret`, `Client version`, `Package name`：It related to the signature, fill in according to the actual situation - ---- - -- `User agent`：API requests `User agent`, setting errors may not access or speed limit -- `Download user agent`：When downloading, use the `user agent `,If the setting error cannot be downloaded (the agent will use it) - - `User agent` and `Download user agent`：You can fill it out by yourself. If you don’t know how to fill it out, you can leave it blank and it will be automatically filled in. - ---- - -In the request in the package `https://xluser-ssl.xunlei.com/v1/shield/captcha/init`，you can get the following parameters6 - -- `Client id`、`Device id`、`Captcha sign` -- `Package name`、`Client version`、`Timestamp` -  - - In the request in the package `https://xluser-ssl.xunlei.com/v1/auth/signin/token`, you can get the following parameters3 - - `Client id`、`Client secret`、`Refresh token` - -  - -::: - -::: zh-CN +### 部分参数抓包说明 - `验证码`：无需填写 - `设备id`：通过 MD5 计算的值，用于判断登录的设备 @@ -1150,29 +477,13 @@ In the request in the package `https://xluser-ssl.xunlei.com/v1/shield/captcha/i - `客户端ID（Client id）`、`客户端密钥（Client secret）`、`刷新令牌（Refresh token）`  -::: - -### 使用视频URL { lang="zh-CN" } - -### Use video url { lang="en" } +### 使用视频URL -::: en -When the `Video URL` option is enabled, it will attempt to replace the original link with the media link returned by the API. Currently, the official platform throttles the download link for **non-members**, but video streaming is not throttled. Therefore, by replacing the link, you can avoid throttling, which applies to both **OpenList** media file downloads and streaming. For regular files, you can also bypass the throttling by renaming the file extension to a media format (e.g., `.mp4`). - -The **Expert Edition** does not enable the `Video URL` option by default, as it is intended for users who configure detailed parameters themselves, and they should be aware of the significance of this option. Hence, it is not enabled by default. For **Xunlei X** users, this option is enabled by default, primarily for the convenience of less experienced users. -::: - -::: zh-CN `视频URL` 开启后，会尝试使用接口返回的媒体链接进行替换原本的链接。目前官方对 `非会员` 情况下，下载链接进行了限速，但视频播放是不限速的。因此可以通过替换链接的方式来避免限速，这一点对于 `OpenList` 媒体文件下载和在线播放均生效。对于普通文件，也可以采取重命名文件后缀为媒体格式（例如：`.mp4` ）的方式绕过限速。 专家版没默认开启 `视频URL`选项，目的是针对于自行配置详细参数的人群来说，应当知晓该选项的意义，因此默认不启用。对于 `迅雷X` 驱动默认启用该选项，更多的是为了小白用户考虑。 -::: - -### The default download method used { lang="en" } -### 默认使用的下载方式 { lang="zh-CN" } - -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -1192,28 +503,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: diff --git a/pages/guide/drivers/uc.md b/pages/guide/drivers/uc.md index 33d3d3eca..123306d58 100644 --- a/pages/guide/drivers/uc.md +++ b/pages/guide/drivers/uc.md @@ -1,91 +1,31 @@ --- -title: - en: UC / TV - zh-CN: UC / TV -icon: iconfont icon-state -# This control sidebar order top: 683 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - '本地代理' - - '302' -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- - +# UC / TV -## UC Cloud { lang="en" } + -## UC 网盘 { lang="zh-CN" } +## UC 网盘 **https://drive.uc.cn/** -### Cookie { lang="en" } +### Cookie -### Cookie { lang="zh-CN" } - -::: en -Press F12 to open "Debug", select "Network", select any request on the left, and find the one with the `Cookie` parameter. - -::: -::: zh-CN 在 `F12`任意请求中找到携带 `Cookie` 的值  -::: - -### Root Folder ID { lang="en" } - -### 根文件夹ID { lang="zh-CN" } - -::: en -Root Folder ID is `0` -- After entering the folder, get the directory ID in the top address bar. If the subdirectory is deeper, the directory ID will be at the back of the address bar. Just write the subdirectory ID you want to mount. -  +### 根文件夹ID -::: -::: zh-CN 根目录ID为 `0` - 子文件夹ID进入文件夹后顶部地址栏获取目录ID，如果子目录越深目录ID在地址栏越靠后，想挂载哪个子目录就写那个子目录ID就可以  -::: - -### The default download method used { lang="en" } - -### 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - c1 - end - c1[local proxy]:::someclass==default===>a2[user equipment] - classDef someclass fill:#f96 - b1[Download proxy URL]-.alternative.->a2[user equipment] - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -104,34 +44,11 @@ flowchart TB click c1 "../drivers/common.html#webdav-策略" ``` -::: +## UC TV -## UC TV { lang="en" } - -## UC TV { lang="zh-CN" } - -::: en -The TV version supports `302`, but only `List` and `Download` operations are supported. Other operations are not supported (the interface does not support it). -::: -::: zh-CN TV 版支持 `302`，但是只能 `访问` 和 `下载` 两个操作，其它操作不支持(接口不支持) -::: - -### Add method { lang="en" } -### 添加方式 { lang="zh-CN" } - -::: en - -1. Select the `UC TV` driver, fill in the mounting path, and then save -2. Return to the all driver page and use the mobile APP to scan the QR code (If the QR code is not displayed, click on `Table Layout` in the upper right corner of the driver to switch from list mode to table mode) -3. After scanning the QR code to confirm, disable the driver, then enable the `driver` to use it. - - `Refresh token`、`Device id`、`Query token`,It will be filled in automatically, no manual filling is required - Please do not edit manually and modify it -  - -::: - -::: zh-CN +### 添加方式 1. 选择 `UCTV` 驱动，填写挂载路径，然后保存 2. 返回全部驱动页面，使用手机APP扫描二维码（如果不显示二维码，驱动右上角点击点击`表格布局` 从列表模式切换成表格模式） @@ -139,54 +56,14 @@ TV 版支持 `302`，但是只能 `访问` 和 `下载` 两个操作，其它操 - `Refresh token 刷新令牌`、`Device id 设备ID `、`Query token` 会自动填充，不需要人工填写 - 请不要进行编辑手动修改  -::: - -### Root Folder ID { lang="en" } - -### 根文件夹ID { lang="zh-CN" } +### 根文件夹ID -::: en -Root Folder ID is `0` - -- After entering the folder, get the directory ID in the top address bar. If the subdirectory is deeper, the directory ID will be at the back of the address bar. Just write the subdirectory ID you want to mount. -  - -::: -::: zh-CN 要挂载的根文件夹，默认为`0` - 子文件夹ID进入文件夹后顶部地址栏获取目录ID，如果子目录越深目录ID在地址栏越靠后  -::: - -### The default download method used { lang="en" } - -### 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -206,5 +83,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/url_tree.md b/pages/guide/drivers/url_tree.md index 587103642..b471cb280 100644 --- a/pages/guide/drivers/url_tree.md +++ b/pages/guide/drivers/url_tree.md @@ -1,25 +1,12 @@ --- -title: - en: UrlTree - zh-CN: 地址树 -icon: iconfont icon-state -# This control sidebar order top: 998 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - '302' -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- +# 地址树 + :::tip **`地址树-UrlTree`** 是什么? 是用来挂载单个文件链接的，详情可以查看 **→→→[原需求说明](https://github.com/alist-org/alist/issues/3268)←←←** ::: diff --git a/pages/guide/drivers/uss.md b/pages/guide/drivers/uss.md index 12c45e965..3e14a9d4d 100644 --- a/pages/guide/drivers/uss.md +++ b/pages/guide/drivers/uss.md @@ -1,38 +1,12 @@ --- -title: - en: UPYUN Storage Service - zh-CN: 又拍云存储 -icon: iconfont icon-state -# This control sidebar order top: 894 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - '302' - - '官方' -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- -::: en -::: tip -When using the **302 redirect** strategy, the `_upd` and `_upt` parameters are automatically appended to the URL. If **"Parameter Follow"** is enabled in the Upyun console, the CDN nodes will treat these parameters as part of the file path, resulting in a **404 Not Found** error for existing files. - -Solutions: +# 又拍云存储 -- Method 1: In the Upyun console, under **"Cache Control"**, change **"Parameter Follow"** to **"Parameter Not Follow"**. - -- Method 2: Set the WebDAV policy of OpenList to **"Local Proxy"**. This mode avoids appending interfering parameters but will increase the server's data transfer. -::: - -::: zh-CN ::: tip 在使用 **302 重定向** 策略时，会自动在 URL 后拼接 `_upd` 与 `_upt` 参数，若又拍云控制台开启了 **“参数跟随”**，CDN 节点会将这些参数视为文件路径的一部分进行匹配，从而导致原本存在的文件返回 **404 Not Found**。 @@ -44,134 +18,45 @@ Solutions: ::: -::: en -UPYUN Storage Service，refer to as USS，[**Yupyun USS Official Website**](https://console.upyun.com/services/file/) -::: -::: zh-CN UPYUN 存储服务，简称 USS，[**又拍云USS官网**](https://console.upyun.com/services/file/) -::: -### BucKet { lang="en" } +## 存储桶 -## 存储桶 { lang="zh-CN" } - -::: en -UPYUN Storage Service Name -::: -::: zh-CN **UPYUN 存储桶服务名称** -::: -### Endpoint { lang="en" } +## Endpoint -## Endpoint { lang="zh-CN" } - -::: en -Accelerated domain name (default TEST domain or bound domain, not CNAME domain) -If you use http protocol, please add `http://` protocol header. -The test domain name provided by upyun is not accessible in some network and does not support https, so it is recommended to use your own bound domain name. -::: -::: zh-CN 加速域名（默认的测试域名或已绑定域名，不是CNAME域名） 如果使用http协议，请自行添加`http://`协议头 又拍云提供的默认测试域名在部分网络环境下无法访问，且不支持https，建议使用自行绑定的域名 -::: -### Operator name { lang="en" } +## 操作员名称 -## 操作员名称 { lang="zh-CN" } - -::: en -Operator name -::: -::: zh-CN 操作员名称 -::: - -### Operator password { lang="en" } -## 操作员密码 { lang="zh-CN" } +## 操作员密码 -::: en -Operator password -::: -::: zh-CN 操作员密码 -::: - -### Root folder path { lang="en" } -## 根文件夹 ID { lang="zh-CN" } +## 根文件夹 ID -::: en -Root path, if not filled, it defaults to the root directory. -::: -::: zh-CN 根路径，不填则默认为根目录。 -::: - -### Sign url expire { lang="en" } -## 签名链接有效期 { lang="zh-CN" } +## 签名链接有效期 -::: en -The validity period of the signed download address is 4 hours by default. -::: -::: zh-CN 签名下载地址的有效期默认为 4 小时。 -::: - -## Example of filling in details { lang="en" } -## 详情填写示意图 { lang="zh-CN" } +## 详情填写示意图 -::: en -::: tip -If you want to use the official test domain name, you must manually add http For example: http://xxx.test.upcdn.net -If you want to use HTTPS, of course, you can also add your own domain name, for example: https://you.xxx.com -permission is turned on by itself, and the read permission must be turned on！ -::: -::: en - -::: - -::: zh-CN ::: tip 如果你要用官方提供的的测试域名那必须要手动加http 例如： http://xxx.test.upcdn.net 如果想用HTTPS，当然也可以添加自己的域名就可以使用例如：https://you.xxx.com 操作员的权限自己需要哪个开启哪个，读取权限必须得开！ ::: -::: zh-CN - -::: -### The default download method used { lang="en" } - -### 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` + -::: -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -191,5 +76,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/webdav.md b/pages/guide/drivers/webdav.md index 75c08c730..cdb514c5a 100644 --- a/pages/guide/drivers/webdav.md +++ b/pages/guide/drivers/webdav.md @@ -1,95 +1,33 @@ --- -title: - en: WebDav - zh-CN: WebDAV -icon: iconfont icon-state -# This control sidebar order top: 899 -# A page can have multiple categories categories: - guide - drivers --- -## Address { lang="en" } +# WebDAV -## 地址 { lang="zh-CN" } +## 地址 -::: en -WebDAV root address -::: - -::: zh-CN WebDAV 根地址 -::: - -## Username { lang="en" } -## 用户名 { lang="zh-CN" } +## 用户名 -::: en -username -::: - -::: zh-CN 用户名 -::: - -## Password { lang="en" } -## 密码 { lang="zh-CN" } +## 密码 -::: en -password -::: - -::: zh-CN 密码 -::: - -## Root folder path { lang="en" } - -## 根文件夹ID { lang="zh-CN" } -::: en -The path of fodler you want to mount, same as join in address -::: +## 根文件夹ID -::: zh-CN 要挂载的文件夹路径，与加入地址相同 -::: -## Tls insecure skip verify { lang="en" } +## 跳过 SSL 证书验证 -## 跳过 SSL 证书验证 { lang="zh-CN" } - -::: en -Whether to skip SSL certificate verification. If your WebDAV server uses a self-signed certificate, you may need to enable this option. Enabling it will reduce security, please use it with caution. -::: - -::: zh-CN 是否跳过 SSL 证书验证。如果你的 WebDAV 服务器使用自签名证书，可能需要启用此选项。启用后会降低安全性，请谨慎使用。 -::: - -## Support 302 redirect { lang="en" } - -## 支持 302 重定向 { lang="zh-CN" } - -::: en - -In general, WebDAV servers return the file content directly. Due to the need for authorization, only proxy downloads are possible. However, some servers redirect to the actual file address, such as OpenList `WebDav Policy`'s `302 Redirect`. - -The `Web Proxy` option in WebDAV storage settings is enabled by default. If disabled, OpenList will attempt to obtain the redirected address and return it to the user device for direct download. -Prerequisites: - -1. The WebDAV server must support returning 302; if it returns 200, this feature cannot be used, and disabling Web Proxy will make it unusable. -2. The returned 302 address must be publicly accessible and must not require authorization information; otherwise, the user device cannot download it. -3. Disable the `Web Proxy` option in the storage settings. - -::: - -::: zh-CN +## 支持 302 重定向 通常情况下，WebDAV 服务器会直接返回文件内容，由于需要授权，只能代理下载。但一些服务器会重定向到实际的文件地址，如 OpenList `WebDav 策略` 的 `302 重定向`。 @@ -101,51 +39,15 @@ WebDAV 存储设置的 `Web 代理` 选项默认为开启状态，如果关闭 2. 返回的 302 地址必须是公开可访问的地址，不得需要授权信息，否则用户设备无法下载。 3. 在存储设置中关闭 `Web 代理` 选项。 -::: - -## OneDrive/SharePoint { lang="en" } - -## OneDrive/SharePoint { lang="zh-CN" } - -::: en -Select the vendor as sharepoint, and support the international version/21Vianet. - -For OneDrive/SharePoint, you can obtain the WebDAV root address through [this tool](https://tool.example.com/onedrive/webdav). If you want to mount the specified directory, you can join it later. +## OneDrive/SharePoint -The username is the OneDrive account email, and the password is the OneDrive account password. -::: - -::: zh-CN 选择 vendor 为 sharepoint，支持国际版/世纪互联。 你可以通过[这个工具](https://alist.example.com/tool/onedrive/webdav.html)获取 WebDAV 根地址，如果要挂载指定的目录，在后面拼接即可。 用户名为 OneDrive 账号邮箱，密码即为 OneDrive 账号密码。 -::: - -## Error message { lang="en" } - -## 错误提示 { lang="zh-CN" } - -::: en - -- **failed get objs: failed to list objs: PROPFIND/根目录：403** - Need to log in to [Entra ID](https://entra.microsoft.com/#view/Microsoft_AAD_IAM/TenantOverview.ReactView?Microsoft_AAD_IAM_legacyAADRedirect=true) - - Find 'Manage Security Default' and click to disable it(❗ Note: Closing this option will disable the Authenticator verification for the domain) - -  - - Another situation is that the corresponding OneDrive account has not been used for a long time, which will also prompt this problem. Try to log in to the account again from the OneDrive web page. The system will prompt you to change the password. After updating the password, try again with the changed password. - -- **failed link: failed get link: redirect failed, status: 200** - - This error indicates that the WebDAV server does not support 302 redirects. You need to enable the `Web Proxy` option in the storage settings to use proxy downloads. - -::: - -::: zh-CN +## 错误提示 - **failed get objs: failed to list objs: PROPFIND/根目录：403** @@ -161,36 +63,7 @@ The username is the OneDrive account email, and the password is the OneDrive acc 此错误表示 WebDAV 服务器不支持 302 重定向，需要在存储设置中启用 `Web 代理` 选项以使用代理下载。 -::: - -## The default download method used { lang="en" } - -## 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[local proxy]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[302]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: - -::: zh-CN +## 默认使用的下载方式 ```mermaid --- @@ -210,5 +83,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/weiyun.md b/pages/guide/drivers/weiyun.md index a500b46c5..ce6209d7a 100644 --- a/pages/guide/drivers/weiyun.md +++ b/pages/guide/drivers/weiyun.md @@ -1,43 +1,16 @@ --- -title: - en: Tencent weiyun - zh-CN: 腾讯微云 -icon: iconfont icon-state -# This control sidebar order top: 682 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - '本地代理' -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- - - -::: en -Tencent Weiyun official website: **https://www.weiyun.com** -::: -::: en -::: tip Weiyun login validity period reminder - -- QQ: The login can only keep alive for 48 hours at present, and the cookie has to be replaced -- WeChat: no such problem, use token - It is recommended to use WeChat to log in +# 腾讯微云 -::: + -::: zh-CN 腾讯微云官网：**https://www.weiyun.com** -::: -::: zh-CN + ::: tip 微云登录有效期提示 - QQ：登录目前只能保活48小时就得更换cookie @@ -46,42 +19,15 @@ Tencent Weiyun official website: **https://www.weiyun.com** ::: -## Root folder file_id { lang="en" } - -## 根文件夹ID { lang="zh-CN" } - -::: en - -1. Display the root directory, **`leave blank`**, you don’t need to fill in, the program will automatically fill in -2. If only a single folder ID is displayed, select the folder to be displayed, Copy the ID behind the top address bar - -  - -::: - -::: zh-CN +## 根文件夹ID 1. 展示根目录，**`留空`** 就可以不用填写，程序会自动填充 2. 如果只展示其中单个文件夹ID，进入想展示的文件夹內然后复制顶部地址栏后面的ID  -::: - -## Cookie { lang="en" } - -## Cookie { lang="zh-CN" } - -::: en -After logging in to Weiyun, **Open the developer debugging tool (F12)**, find the request that carries the cookie in any request, copy and fill in it. +## Cookie -- The token obtained by WeChat login is longer than the cookie field of QQ login -- QQ WeChat fills in the `Cookie` field value, and you can see it by just looking for a request - -  - -::: -::: zh-CN 登录微云后，**打开开发者调试工具(F12)**，在任意请求中找到携带cookie的请求复制填写就可以。 - 微信登录获取的token比QQ登录的cookie字段要长 @@ -89,51 +35,12 @@ After logging in to Weiyun, **Open the developer debugging tool (F12)**, find th  -::: - -## Other notes { lang="en" } - -## 其他说明 { lang="zh-CN" } - -::: en - -1. The copy function cannot be used -2. **It is recommended not to share Weiyun with the outside world. After all, it is bound to your own QQ number. If you have a major loss to QQ or other things after being blocked/frozen, you will be responsible for the consequences** - -::: - -::: zh-CN +## 其他说明 1. 复制功能无法使用 2. **建议不要将微云对外共享，毕竟是绑定的自己QQ号码，如果被封/冻结之后对QQ或者其它产生了重大损失后果自负** -::: - -## The default download method used { lang="en" } - -## 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - c1 - end - c1[local proxy]:::someclass==default===>a2[user equipment] - classDef someclass fill:#f96 - b1[Download proxy URL]-.alternative.->a2[user equipment] - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +## 默认使用的下载方式 ```mermaid --- @@ -151,5 +58,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/wopan.md b/pages/guide/drivers/wopan.md index b17debdf8..8acdc555d 100644 --- a/pages/guide/drivers/wopan.md +++ b/pages/guide/drivers/wopan.md @@ -1,44 +1,18 @@ --- -title: - en: WoPan - zh-CN: 中国联通云盘 -icon: iconfont icon-state -# This control sidebar order top: 693 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - '302' -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- +# 中国联通云盘 + [https://pan.wo.cn/](https://pan.wo.cn/) -## GetToken { lang="en" } - -## 获取令牌 { lang="zh-CN" } - -::: en -::: tip -The difference between the two token acquisition methods: - -- Method 1: **Token valid for seven days** Logging in to the web version of China Unicom Cloud Drive will disconnect and invalidate the mount point on OpenList's side. However, logging in to the mobile version is fine, and thereby you can have both open simultaneously. - -- Method 2: **Token valid for two months** There isn't any problem to log into the Unicom Cloud Drive. However, it will be kicked off if you log in on the mobile side. - -::: +## 获取令牌 -::: zh-CN ::: tip 两个令牌获取方法的区别： @@ -48,21 +22,7 @@ The difference between the two token acquisition methods: ::: -### Method 1 { lang="en" } - -### 方法一 { lang="zh-CN" } - -::: en - -1. Open developer tools -2. Open the official website to login
-3. Find the Apps tab in Developer Tools and select Session Storage:
- 
-4. Follow the arrows in the diagram to find the `Refresh Token` and the `Access Token`
-
-:::
-::: zh-CN
+### 方法二
1. 打开开发者工具
2. 打开官网 登录
@@ -94,83 +39,24 @@ The difference between the two token acquisition methods:
4. 根据图中箭头指引找到`刷新令牌`和`访问令牌`
-:::
-
-## Root folder ID { lang="en" }
-
-## 根文件夹ID { lang="zh-CN" }
-
-::: en
-
-- **Personal cloud：**：**0**
- - Single folder ID：Unknown (wait for replenishment)
-- **Family cloud**：Unknown (wait for replenishment)
- - Family cloud Single folder ID：Unknown (wait for replenishment)
-
-:::
-
-::: zh-CN
+## 根文件夹ID
- 个人云：**0**
- 单独文件夹ID：未知(后续补充)
- 家庭云：未知(后续补充)
- 家庭云单独文件夹ID：未知(后续补充)
-:::
-
-## Type { lang="en" }
+## 类型
-## 类型 { lang="zh-CN" }
-
-::: en
-Personal cloud：Put the `family ID` blank is the personal cloud
-Family cloud：add `Family ID` Log in to the [SmartHome] -> [我的] -> [您的家], click"+" [Invite] -> [微信邀请], send the link to yourself, open it and copy all the text after 'groupId='.
-:::
-::: zh-CN
个人云：将`Family ID`空着就是个人云
家庭云：填写`Family ID` 登录【联通智家APP】->【我的】->【您的家】，点击"+"【邀请家人】->【微信邀请】，将链接发送给自己，打开后复制“groupId=”后面的全部文本
-:::
-
-## OpenList fill in examples： { lang="en" }
-## OpenList挂载填写示例： { lang="zh-CN" }
+## OpenList挂载填写示例：
-::: en
-Data obtained by using tools `Refresh_token Fill in the refresh token`, `Access_token fills in access_token`
-
-:::
-::: zh-CN
将使用工具获取的 `refresh_token填入刷新令牌`，`access_token填入访问令牌`
-:::
-
-## The default download method used { lang="en" }
-## 默认使用的下载方式 { lang="zh-CN" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[302]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[local proxy]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-::: zh-CN
+## 默认使用的下载方式
```mermaid
---
@@ -190,5 +76,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/wps.md b/pages/guide/drivers/wps.md
index 69053bf9e..247f63761 100644
--- a/pages/guide/drivers/wps.md
+++ b/pages/guide/drivers/wps.md
@@ -1,28 +1,14 @@
---
-title:
- en: WPS
- zh-CN: WPS 云文档
-# This control sidebar order
top: 675
-# A page can have multiple categories
categories:
- guide
- drivers
---
-
-
-::: en
-OpenList supports mounting WPS cloud document (which is also called KDocs) web.
-
-Official websites:
-
-- KDocs (Personal):
::: -::: en -::: warning -Versions above v3.25.0 change the password to an encrypted hash value, and the password cannot be calculated directly. If the password is forgotten, it can only be re-**`randomly generated`** or **`manually set`**. -::: - -::: zh-CN ::: warning v3.25.0以上版本将密码改成加密方式存储的hash值，无法直接反算出密码，如果忘记了密码只能通过重新 **`随机生成`** 或者 **`手动设置`**。 ::: -::: en -The `xxxx` refers to the names corresponding to different systems/architectures, generally Linux-x86/64 is openlist-linux-amd64. -::: - -::: zh-CN `xxxx` 指的是不同系统/架构对应的名称，一般 Linux-x86/64 为 openlist-linux-amd64。 -::: ### Linux @@ -538,18 +278,11 @@ Expand-Archive .\openlist-xxxx.zip .\openlist.exe admin set NEW_PASSWORD ``` -## Daemon { lang="en" } - -## 守护进程 { lang="zh-CN" } +## 守护进程 ### Linux -::: en -`vim /usr/lib/systemd/system/openlist.service` add the following content, where `path_openlist` is the path where openlist is located: -::: -::: zh-CN 使用任意方式编辑 `/usr/lib/systemd/system/openlist.service` 并添加如下内容，其中 `path_openlist` 为 OpenList 所在的路径： -::: ```ini [Unit] @@ -564,21 +297,6 @@ Restart=on-failure WantedBy=multi-user.target ``` -::: en -Then `systemctl daemon-reload`, now you can use these commands to manage the program: - -- Start: `systemctl start openlist` -- Shut down: `systemctl stop openlist` -- Self-start: `systemctl enable openlist` -- Cancel Self-start: `systemctl disable openlist` -- Status: `systemctl status openlist` -- Restart: `systemctl restart openlist` - -Can't configure daemon? [**Video Tutorial**](https://www.bilibili.com/video/BV1rF41197Qv?t=187.0) - -::: - -::: zh-CN 然后，执行 `systemctl daemon-reload` 重载配置，现在你可以使用这些命令来管理程序： - 启动: `systemctl start openlist` @@ -590,17 +308,9 @@ Can't configure daemon? [**Video Tutorial**](https://www.bilibili.com/video/BV1r 守护进程不会配置? [**视频教程**](https://www.bilibili.com/video/BV1rF41197Qv?t=187.0) -::: - ### macOS -::: en -Edit `~/Library/LaunchAgents/org.openlist.plist` in any way and add the following content, modify `path_openlist` to be the path where OpenList is located, and `path/to/working/dir` to be the working path of OpenList: -::: - -::: zh-CN 使用任意方式编辑 `~/Library/LaunchAgents/org.openlist.plist` 并添加如下内容，修改 `path_openlist` 为 OpenList 所在的路径，`path/to/working/dir` 为 OpenList的工作路径: -::: ```xml @@ -626,45 +336,15 @@ Edit `~/Library/LaunchAgents/org.openlist.plist` in any way and add the followin ``` -::: en -Then, execute `launchctl load ~/Library/LaunchAgents/org.openlist.plist` to load the configuration, now you can use these commands to manage the program: - -- Start: `launchctl start ~/Library/LaunchAgents/org.openlist.plist` -- Close: `launchctl stop ~/Library/LaunchAgents/org.openlist.plist` -- Unload configuration: `launchctl unload ~/Library/LaunchAgents/org.openlist.plist` - -::: - -::: zh-CN 然后，执行 `launchctl load ~/Library/LaunchAgents/org.openlist.plist` 加载配置，现在你可以使用这些命令来管理程序： - 开启: `launchctl start ~/Library/LaunchAgents/org.openlist.plist` - 关闭: `launchctl stop ~/Library/LaunchAgents/org.openlist.plist` - 卸载配置: `launchctl unload ~/Library/LaunchAgents/org.openlist.plist` -::: - ### Windows -#### Method One { lang="en" } - -#### 方法1 { lang="zh-CN" } - -::: en - -1. Download the newest `nssm` from https://nssm.cc/download. -2. Unzip the archive and go to the diretory of `nssm.exe`. -3. Hold Shift and right click on the blank space, then release and press S or select "powershell here", you should now see a blue window named "Windows PowerShell". -4. Type `.\nssm.exe install openlist`. -5. Select the path of `openlist.exe` for "Path", e.g. `D:\openlist\openlist.exe`; type `server` for "Argument". -6. You can custom "Display Name", "Description" and "Startup Type" in "Details" tab. -7. Go to "I/O" tab and select a file for both "Output (stdout)" and "Output (stderr)", e.g. `D:\openlist\stdout.log`. The file itself (`stdout.log`) may not exist, but the folder (`D:\openlist`) must exist. -8. Click on "Install Service". - You can now start the service from services.msc or task manager. - -::: - -::: zh-CN +#### 方法1 1. 在 https://nssm.cc/download 下载最新版本的 `nssm`； 2. 在解压后的文件夹内按住 Shift 并右击空白处，选择“在此处打开 Powershell 窗口”； @@ -675,49 +355,11 @@ Then, execute `launchctl load ~/Library/LaunchAgents/org.openlist.plist` to load 7. 点击“Install Service”即可。 此后可以直接在服务中启动 `openlist`。 -::: - -#### Method Two { lang="en" } +#### 方法2 -#### 方法2 { lang="zh-CN" } - -::: zh-CN 用 **`.VBS`** 脚本启动和停止，分别创建两个脚本 分别是 `启动.vbs` 和 `停止.vbs`。 直接在和 OpenList 启动程序同级文件夹里面双击启动即可，不用担心没有反应 直接去 浏览器访问即可。 -::: - -::: en -Use **`.VBS`** script to start and stop, create two scripts respectively `start.vbs` and `stop.vbs`. -Just double-click to start it in the folder at the same level as the OpenList startup program, don't worry about no response, just go to the browser to access it. -::: - -::: en -::: info Two startup scripts -**start.vbs** - -```bash title="vbscript" -Dim ws -Set ws = Wscript.CreateObject("Wscript.Shell") -ws.run "openlist.exe server",vbhide -Wscript.quit -``` -**stop.vbs** - -```bash title="vbscript" -Dim ws -Set ws = Wscript.CreateObject("Wscript.Shell") -ws.run "taskkill /f /im openlist.exe",0 -Wscript.quit -``` - -1. If the script will not be created, you can download it yourself: [**Script Download**](https://www.alipan.com/s/DHPMhRtKUzY/folder/63e0961eae317bd4d4d945cda69dbb00f9837fb7) -2. If the script will not be used, you can watch the video: [**reference video**](https://www.bilibili.com/video/BV1wWYTzdE4B) - How to realize Windows startup automatically, you can refer to the script mentioned above to use the video (second). - -::: - -::: zh-CN ::: info 两个启动脚本 **启动.vbs** @@ -743,19 +385,6 @@ Wscript.quit ::: -::: en -::: info -For all platform, you can use follow command to silent start, stop and restart. (v3.4.0 and later) - -```bash -openlist start -openlist stop -openlist restart -``` - -::: - -::: zh-CN ::: info 对于所有平台，您可以使用以下命令来静默启动、停止和重新启动。 （v3.4.0 及更高版本） @@ -767,14 +396,6 @@ openlist restart ::: -## How to update { lang="en" } - -## 如何更新 { lang="zh-CN" } +## 如何更新 -::: en -Download the new version of OpenList and replace the previous one. -::: - -::: zh-CN 下载新版 OpenList，把之前的替换了即可。 -::: diff --git a/pages/guide/installation/paas.md b/pages/guide/installation/paas.md index cc32decf4..b6598f064 100644 --- a/pages/guide/installation/paas.md +++ b/pages/guide/installation/paas.md @@ -1,157 +1,73 @@ --- -# This is the title of the article -# title: One-click Script -title: - en: PaaS - zh-CN: PaaS -icon: iconfont icon-module -# This control sidebar order top: 30 -# A page can have multiple categories categories: - guide - installation -# A page can have multiple tags --- -::: zh-CN +# PaaS + ::: tip 文档可能更新不及时，请根据关键信息结合平台当前部署界面进行调整 ::: -::: en -::: tip -The documentation may not be updated in a timely manner. Please make adjustments based on the key information and the current deployment interface of the platform. -::: - -## ClawCloud { lang="en" } - -## 爪云 { lang="zh-CN" } -### One-click deployment { lang="en" } +## 爪云 -### 一键部署 { lang="zh-CN" } +### 一键部署 -::: en -::: danger -Due to the removal of `PUID`/`PGID` environment variable support for better container specifications in [OpenList v4.1.1](https://github.com/OpenListTeam/OpenList/releases/tag/v4.1.1), ClawCloud platform will not be able to function properly due to lack of permission to write data (including using images or app in App Store). - -As of October 20 2025, ClawCloud has not yet merged our Deployment Template. One-click deployment is temporarily unavailable. If you want to deploy on ClawCloud, please refer to [#1209 (comment)](https://github.com/OpenListTeam/OpenList/issues/1209#issuecomment-3243803024). -::: -::: zh-CN ::: danger 由于在[OpenList v4.1.1](https://github.com/OpenListTeam/OpenList/releases/tag/v4.1.1)中为容器规范移除了`PUID`/`PGID`环境变量支持，故在 ClawCloud 平台将由于无权限写入数据而无法正常使用（包括使用镜像和App Store内应用） 截止 2025年10月20日， ClawCloud 官方暂未合并我们的修复部署模板，一键部署暂不可用。如需部署至ClawCloud，请参阅 [#1209 (comment)](https://github.com/OpenListTeam/OpenList/issues/1209#issuecomment-3243803024)。 ::: -::: en -Click the button below to [deploy to Claw Cloud](https://template.run.claw.cloud/?openapp=system-fastdeploy%3FtemplateName%3Dopenlist). It can also be found in App Launchpad. -::: - -::: zh-CN 点击下方按钮[部署到 Claw Cloud](https://template.run.claw.cloud/?openapp=system-fastdeploy%3FtemplateName%3Dopenlist)。亦可在 App Launchpad 中找到。 -::: [](https://template.run.claw.cloud/?openapp=system-fastdeploy%3FtemplateName%3Dopenlist) -### Manual deployment { lang="en" } - -### 手动部署 { lang="zh-CN" } - -#### 关键信息 { lang="zh-CN" } +### 手动部署 -#### Key Information { lang="en" } - -::: en -Name|Value|Description -:--|:--|:--- -Application Name|openlist|Application name -Image|openlistteam/openlist:latest-lite|Image, please make sure to use the one with **lite**, otherwise the error `Pod ephemeral local storage usage exceeds the total limit of containers 100Mi.` may occur -Replicas|1|Number of replicas, set to 1 -CPU|0.2|Number of CPU cores, set according to your own needs -Memory|256M|Memory size, set according to your own needs -Container Port|5244|Mapped port, which is `5244` if you have not modified the startup command or configuration -Public Access|Y|Enable external access -Custom Domain|-|If you have your own domain name, set it according to the prompts; if not, keep the default. Please make sure to use **https** for the protocol -Local Storage|-|Persistent volume --- Capacity|1|Capacity --- Mount Path|/opt/openlist/data|Configured mapped directory, which is `/opt/openlist/data` if you have not modified the startup command or configuration -::: -::: zh-CN -名称|值|说明 -:--|:--|:--- -Application Name|openlist|应用名 -Image|openlistteam/openlist:latest-lite|镜像，请务必使用带有**lite**的镜像，否则可能出现`Pod ephemeral local storage usage exceeds the total limit of containers 100Mi.` -Replicas|1|副本数，设置为1 -CPU|0.2|CPU核心数，请根据自身需求设置 -Memory|256M|内存大小，请根据自身需求设置 -Container Port|5244|映射端口，如果你没有修改启动命令或者配置，则为`5244` -Public Access|Y|打开外部访问 -Custom Domain|-|如果你有自身的域名，请根据提示进行设置，如果没有，保持默认，协议请务必使用**https** -Local Storage|-|持久卷 --- Capacity|1|容量 --- Mount Path|/opt/openlist/data|配置映射的目录，如果你没有修改启动命令或者配置，则为`/opt/openlist/data` -::: +#### 关键信息 -#### 参考图示 { lang="zh-CN" } +| 名称 | 值 | 说明 | +| :--------------- | :-------------------------------- | :------------------------------------------------------------------------------------------------------------------------------- | +| Application Name | openlist | 应用名 | +| Image | openlistteam/openlist:latest-lite | 镜像，请务必使用带有**lite**的镜像，否则可能出现`Pod ephemeral local storage usage exceeds the total limit of containers 100Mi.` | +| Replicas | 1 | 副本数，设置为1 | +| CPU | 0.2 | CPU核心数，请根据自身需求设置 | +| Memory | 256M | 内存大小，请根据自身需求设置 | +| Container Port | 5244 | 映射端口，如果你没有修改启动命令或者配置，则为`5244` | +| Public Access | Y | 打开外部访问 | +| Custom Domain | - | 如果你有自身的域名，请根据提示进行设置，如果没有，保持默认，协议请务必使用**https** | +| Local Storage | - | 持久卷 | +| -- Capacity | 1 | 容量 | +| -- Mount Path | /opt/openlist/data | 配置映射的目录，如果你没有修改启动命令或者配置，则为`/opt/openlist/data` | -#### Reference Diagram { lang="en" } +#### 参考图示  diff --git a/pages/guide/installation/reverse-proxy.md b/pages/guide/installation/reverse-proxy.md index 9b017b223..b9b52b7be 100644 --- a/pages/guide/installation/reverse-proxy.md +++ b/pages/guide/installation/reverse-proxy.md @@ -1,40 +1,11 @@ --- -# This is the title of the article -# title: One-click Script -title: - en: Reverse proxy - zh-CN: 反向代理 -icon: iconfont icon-page -# This control sidebar order top: 10 -# A page can have multiple categories categories: - guide - installation -# A page can have multiple tags -tag: - - Install - - Guide -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- -::: en -OpenList listens to port 5244 by default. If modified, please also update the port number in the configuration below. - -If you are using **reverse proxy**, please ensure that the correct `Host` header is passed, as OpenList will generate the URL based on this information. - -If the `Host` header is unavailable, you can use the higher-priority `X-Forwarded-Host` header (non-standard header). If the issue persists, configure the [site_url](../../configuration/configuration.md#site-url). - -If you want to use a **sub folder**, you should configure the [site_url](../../configuration/configuration.md#site-url). Refer to [reverse proxy with sub folder](../../faq/howto.md#how-to-reverse-proxy-with-sub-directory). - -:::warning -If you need to proxy to a non-standard port, make sure to pass the `domain:port` information through the `Host` or `X-Forwarded-Host` header, otherwise the port will be lost in URLs! -::: - -::: zh-CN +# 反向代理 OpenList 默认监听 5244 端口。如有修改，请一并修改下列配置中的端口号。 @@ -52,12 +23,7 @@ OpenList 默认监听 5244 端口。如有修改，请一并修改下列配置 https://nginx.org/en/docs/http/ngx_http_proxy_module.html -::: en -Add in the `server` field of the website configuration file: -::: -::: zh-CN 在网站配置文件的 `server` 字段中添加： -::: ```nginx location / { @@ -75,26 +41,6 @@ location / { } ``` -::: en -::: warning -If you use the aaPanel, be sure to delete the following default configuration: - -```nginx -location ~ ^/(\.user.ini|\.htaccess|\.git|\.svn|\.project|LICENSE|README.md -location ~ .\*\.(gif|jpg|jpeg|png|bmp|swf)$ -location ~ .\*\.(js|css)?$ -``` - -Disable Nginx caching in `/www/server/nginx/conf/proxy.conf` or the corresponding website configuration file. Otherwise, with the default configuration, when accessing large files, Nginx will attempt to cache the remote file locally first, resulting in playback failures. - -```nginx -proxy_cache cache_one; # Remove this line -proxy_max_temp_file_size 0; # Add this line -``` - -::: - -::: zh-CN ::: warning 如果使用宝塔面板，请务必删除以下默认配置： @@ -113,20 +59,6 @@ proxy_max_temp_file_size 0; #加上这一行 ::: -::: en - -::: note Nginx Host Variables Differences - -| Variable | Description | Includes Port | Notes | -| -------------------- | ------------------------------------------------ | ------------- | ---------------------------------------------------------------------------------------------------- | -| `$http_host` | The original `Host` request header | Yes | If the `Host` request header is missing, the value will be empty; not recommended for best practices | -| `$host` | Server name from the `Host` request header field | No | Defaults to the server's `server_name` if `Host` field is missing | -| `$host:$server_port` | Server name + port | Yes | Use this combination when you need to use a non-default port (other than 80 or 443) | - -::: - -::: zh-CN - ::: tip Nginx 主机变量区别 | 变量 | 内容 | 是否包含端口号 | 备注 | @@ -137,18 +69,6 @@ proxy_max_temp_file_size 0; #加上这一行 ::: -::: en -If HTTP/3 is needed, the corresponding `Host` line should be modified to: - -```nginx -proxy_set_header Host $host:$server_port; -``` - -This modified configuration will be compatible with requests using HTTP/2 or lower versions. - -::: - -::: zh-CN 如果需要使用 HTTP/3，需要将对应 `Host` 行修改为： ```nginx @@ -157,27 +77,8 @@ proxy_set_header Host $host:$server_port; 这样修改后的配置同时也可以兼容 HTTP/2 及更低版本的请求。 -::: - ## Apache -::: en -Add the anti-generation configuration item `ProxyPass` under the `VirtualHost` field, such as: - -```xml -
- ServerName myapp.example.com
- ServerAdmin webmaster@example.com
- DocumentRoot /www/myapp/public
- AllowEncodedSlashes NoDecode
- ProxyPreserveHost On
- ProxyPass "/" "http://127.0.0.1:5244/" nocanon
- ProxyPassReverse "/" "http://127.0.0.1:5244/" nocanon
-
-```
-
-:::
-::: zh-CN
在 `VirtualHost` 字段下添加配置项 `ProxyPass`，如：
```xml
@@ -192,17 +93,9 @@ Add the anti-generation configuration item `ProxyPass` under the `VirtualHost` f
```
-:::
-
## Caddy
-::: en
-Add the reverse proxy configuration item `reverse_proxy` under the `Caddyfile` file, for example:
-:::
-
-::: zh-CN
在 `Caddyfile` 文件下添加 `reverse_proxy` 反向代理配置项，如：
-:::
```
:80 {
@@ -210,17 +103,9 @@ Add the reverse proxy configuration item `reverse_proxy` under the `Caddyfile` f
}
```
-::: en
-If deployed on a server that is functioning properly on port 443 and accessed using a domain name, it is recommended to use this configuration to let Caddy automatically request a certificate:
-
-（Replace example.com with your own resolved domain name）
-:::
-
-::: zh-CN
如果部署在 443 端口正常使用的服务器上且使用域名进行访问，建议使用这种配置让 Caddy 自动申请证书：
（将 `example.com` 替换为你自己解析后的域名）
-:::
```
example.com {
@@ -228,75 +113,23 @@ example.com {
}
```
-## Tutorial: Setting up Reverse Proxy in aaPanel { lang="en" }
-
-## 教程：宝塔面板设置反向代理 { lang="zh-CN" }
-
-::: en
-
-1. Login to the aaPanel and add a new website.
-
-::
-
-::: zh-CN
+## 教程：宝塔面板设置反向代理
1. 登录宝塔面板，添加站点；
-:::
-
-::: en
-
-2. Modify the website settings.
-
-:::
-
-::: zh-CN
-
2. 修改站点设置；
-:::
-
-::: en
-
-3. Remove the default panel code.
-
-:::
-
-::: zh-CN
-
3. 删除面板默认代码；
-:::
-
-::: en
-
-4. Add the reverse proxy.
-
-:::
-
-::: zh-CN
-
4. 添加反向代理；
-:::
-
-::: en
-
-> If you need to apply for an `SSL certificate`, you can first apply for the certificate in the `SSL` option, and then set up the reverse proxy. Alternatively, you can set up the reverse proxy first, disable the proxy function, apply for an `SSL` certificate, and then enable the proxy again.
-
-:::
-
-::: zh-CN
-
> 如需申请`SSL`证书，可先在`SSL`选项中申请证书，然后在设置反向代理。或者设置反向代理之后，关闭反向代理功能，申请`SSL`证书后再次开启代理。
-
-:::
diff --git a/pages/guide/installation/script.md b/pages/guide/installation/script.md
index ce2b6dddf..d51d93b88 100644
--- a/pages/guide/installation/script.md
+++ b/pages/guide/installation/script.md
@@ -1,29 +1,12 @@
---
-# This is the title of the article
-# title: One-click Script
-title:
- en: One-click Script
- zh-CN: 一键脚本
-icon: iconfont icon-script
-# This control sidebar order
top: 70
-# A page can have multiple categories
categories:
- guide
- installation
---
-::: en
-Requirements:
+# 一键脚本
-- Linux with systemd or OpenRC
-- Root privileges for installation
-- `curl`, `tar` installed
-- Architectures listed in the [download page](download)
-
-:::
-
-::: zh-CN
要求：
- 使用 systemd 或者 OpenRC 的 Linux 系统
@@ -31,15 +14,9 @@ Requirements:
- 已安装 `curl`, `tar`
- 在[下载页面](download)中列出的架构
-:::
-
-## Latest { lang="en" }
-
-## 正式版 { lang="zh-CN" }
+## 正式版
-### Install { lang="en" }
-
-### 安装 { lang="zh-CN" }
+### 安装
::: code-group
@@ -87,24 +64,13 @@ curl -fsSL https://raw.githubusercontent.com/OpenListTeam/OpenList-Resource/refs
根据界面提示，输入`1`即可安装
-### openlist-manager { lang="en" }
-
-### 面板管理命令 { lang="zh-CN" }
+### 面板管理命令
-::: zh-CN
::: tip
**安装完成后才可使用**
:::
-::: en
-::: tip
-**It can only be used after the installation is complete.**
-:::
-::: zh-CN
+
使用命令：`openlist` 或者 `openlist-manager`
-:::
-::: en
-Use command: `openlist` or `openlist-manager`
-:::
```bash
欢迎使用 OpenList 管理脚本
@@ -134,22 +100,8 @@ Use command: `openlist` or `openlist-manager`
0、退出脚本
```
-### FAQ { lang="en" }
-
-### 常见问题 { lang="zh-CN" }
-
-::: en
-
-1. Q: The architecture I am using is listed as supported on the download page, why does the installation script say it is not?
-
- A: This is because the installation script is currently unable to recognise your CPU architecture. To help us add CPU architecture recognition to the installation script, please submit the output of the `arch` and `uname -m` commands to the issue page.
-
-:::
-
-::: zh-CN
+### 常见问题
1. Q：我使用的架构在下载页面支持的架构列表中，但安装脚本提示不支持？
A：这是因为安装脚本暂时还没法识别您的CPU架构，请将`arch`和`uname -m`的输出信息提交到 issue 中，方便我们补充安装脚本的CPU架构识别。
-
-:::
diff --git a/pages/guide/installation/source.md b/pages/guide/installation/source.md
index 1caab8a0f..9ec24e8bb 100644
--- a/pages/guide/installation/source.md
+++ b/pages/guide/installation/source.md
@@ -1,37 +1,19 @@
---
-# This is the title of the article
-# title: One-click Script
-title:
- en: Run from source
- zh-CN: 从源码运行
-icon: iconfont icon-code
-# This control sidebar order
top: 20
-# A page can have multiple categories
categories:
- guide
- installation
---
-::: en
-:::danger
-This step is only for users who need to modify the source code by themselves. If you don't understand, please skip it.
-:::
-::: zh-CN
+# 从源码运行
+
:::danger
此步骤仅适用于需要自行修改源代码的用户。不明白的请跳过。
:::
-## Environmental preparation { lang="en" }
+## 环境准备
-## 环境准备 { lang="zh-CN" }
-
-::: en
-First, you need to have an environment of `git`, `nodejs>=24`, `pnpm`, `golang>=1.24`, `gcc`
-:::
-::: zh-CN
首先，你需要一个有`git`，`nodejs>=24`，`pnpm`，`golang>=1.24`，`gcc`的环境
-:::
On **Windows**, use Scoop:
@@ -61,9 +43,7 @@ brew install node@24 go
corepack enable pnpm
```
-## Building the frontend { lang="en" }
-
-## 构建前端 { lang="zh-CN" }
+## 构建前端
```bash
git clone https://github.com/OpenListTeam/OpenList-Frontend.git
@@ -71,16 +51,9 @@ cd OpenList-Frontend
pnpm install && pnpm build
```
-## Build the backend { lang="en" }
-
-## 构建后端 { lang="zh-CN" }
+## 构建后端
-::: en
-Clone `https://github.com/OpenListTeam/OpenList` for this project, copy the `dist` directory of the previous step to the `public` directory under the project, and then:
-:::
-::: zh-CN
克隆 `https://github.com/OpenListTeam/OpenList` ，将上一步的 `dist` 目录复制到项目下的 `public` 目录下，然后执行：
-:::
```bash
appName="openlist"
@@ -105,13 +78,6 @@ ldflags="\
go build -ldflags="$ldflags" .
```
-::: en
-::: details compilation tutorial videos you may need
-Windows version: **https://www.bilibili.com/video/BV1Xr4y1z723** (Although it is V2 version, it is the same as V3 version..)
-Linux version: **https://www.bilibili.com/video/BV1GW4y1s742**
-Compile documents: **https://www.yuque.com/anwenya/alist/glqlhu**
-:::
-::: zh-CN
::: details 你可能需要的编译教程视频
Windows版本：**https://www.bilibili.com/video/BV1Xr4y1z723**
（虽然是V2版的，但是跟V3版本一样的..）
@@ -119,44 +85,25 @@ Linux版本：**https://www.bilibili.com/video/BV1GW4y1s742**
番外编译文档：**https://www.yuque.com/anwenya/alist/glqlhu**
:::
-## Building within Docker { lang="en" }
-
-## 使用 Docker 构建 { lang="zh-CN" }
+## 使用 Docker 构建
-::: en
-Install Docker, clone the repository, then navigate to the root directory of the repository. No further preparation is required.
-:::
-::: zh-CN
安装 Docker，克隆仓库后进入仓库根目录，无需其他准备
-:::
-
-#### Basic { lang="en" }
-#### 基础用法 { lang="zh-CN" }
+#### 基础用法
```bash
docker build -t openlistteam/openlist:beta .
```
-#### build-arg { lang="en" }
-
-#### 构建参数 { lang="zh-CN" }
+#### 构建参数
```bash
docker build -t openlistteam/openlist:beta-ffmpeg --build-arg INSTALL_FFMPEG=true .
```
-::: en
-Available build args:
-| | Desc |
-|:----------------------|----------------|
-| `INSTALL_FFMPEG=true` | Install ffmpeg |
-| `INSTALL_ARIA2=true` | Install aria2 |
-:::
-::: zh-CN
可用 build args：
-| | 说明 |
+
+| | 说明 |
| :-------------------- | ----------- |
| `INSTALL_FFMPEG=true` | 安装 ffmpeg |
-| `INSTALL_ARIA2=true` | 安装 aria2 |
-:::
+| `INSTALL_ARIA2=true` | 安装 aria2 |
diff --git a/pages/guide/installation/truenas.md b/pages/guide/installation/truenas.md
index 5f76b34a2..552e6d628 100644
--- a/pages/guide/installation/truenas.md
+++ b/pages/guide/installation/truenas.md
@@ -1,102 +1,14 @@
---
-title:
- en: Use TrueNAS Scale
- zh-CN: 使用 TrueNAS Scale
-icon: iconfont icon-geometry
-# This control sidebar order
top: 44
-# A page can have multiple categories
categories:
- guide
- installation
---
-## Install the App { lang="en" }
+# 使用 TrueNAS Scale
-## 安装应用程序 { lang="zh-CN" }
+## 安装应用程序
-::: en
-Since OpenList is not officially available in the TrueNAS Apps catalog, you must use the **Custom App** feature to install it.
-
-Follow these steps to deploy OpenList via the **Install iX App** wizard:
-
-1. **Application Name**
- Enter a name for your application (e.g., `openlist`). Keep the default version unless you require a specific tag.
-
- 
-
-2. **Image Configuration**
- - **Repository**: `openlistteam/openlist`
- - **Tag**: `latest` (or specify another version if needed)
- Leave all other fields at their defaults.
-
- 
-
-3. **Container Configuration**
- - **Environment Variables**:
- Add a new variable:
- - Name: `UMASK`
- - Value: `022`
- - **Restart Policy**: Select `Unless Stopped` to ensure automatic restart on failure.
- - **Entrypoint**: Leave unchanged — it is pre-configured.
- Other settings may be adjusted as desired.
-
- 
-
-4. **Device**
- No device passthrough is required for basic operation. Keep defaults.
-
-5. **Security Context Configuration**
- - ✅ Check **Custom User**
- - Set **UID** and **GID** to match a non-root user with permissions to access your storage volumes.
- Default: `568/568` (apps/apps) — recommended for security.
- - ⚠️ Avoid using `root` (UID/GID = 0) unless absolutely necessary — it poses a security risk.
- > 💡 If you plan to use an **ixVolume** later, ensure this user has write permissions to the target dataset.
-
- 
-
-6. **Network Configuration**
- - Add a port mapping:
- - **Host Port**: Any unused port (e.g., `10544`)
- - **Container Port**: `5244`
- - **Host IP**: `0.0.0.0` (accessible from any network) or restrict to a local IP if preferred.
- Add additional mappings only if exposing other services.
-
- 
-
-7. **Portal Configuration**
- - **Port**: Match the Host Port from Step 6 (e.g., `10544`)
- - **Name**: Optional — set to something descriptive like “OpenList Web UI”
- Once saved, a **Web UI** button will appear on the Apps page.
-
- 
-
-8. **Storage Configuration**
- - ✅ **Mandatory**: At least one volume must be configured.
- - Click **Add** → Select storage type (`ixVolume` recommended for persistence).
- - **Mount Path**: `/opt/openlist/data`
- - Ensure the container’s user (from Step 5) has **write permissions** to this location.
- - Optionally add more volumes for logs, configs, etc.
-
- > 📌 Tip: Use **ixVolume** instead of host paths when possible — it ensures better integration with TrueNAS backup and snapshot features.
-
- 
-
-9. **Labels Configuration**
- Skip — not required for basic operation.
-
-10. **Resources Configuration** _(Optional)_
- Set CPU/memory limits if you wish to constrain resource usage (e.g., 1 core, 512MB RAM).
-
- 
-
-11. **Final Step**
- Click **Install** to deploy the OpenList container.
- Wait for status to turn green → then click **Web UI** to access the interface.
-
-:::
-
-::: zh-CN
由于 OpenList 未在 TrueNAS 应用市场官方提供，您必须使用 **自定义应用** 功能进行安装。
请按以下步骤通过 **安装 iX App** 向导部署 OpenList：
@@ -172,7 +84,5 @@ Follow these steps to deploy OpenList via the **Install iX App** wizard:
11. **完成安装**
- 点击 **安装** 启动容器。
- 等待状态变为绿色后，点击 **Web UI** 按钮即可访问 OpenList 界面。
-
-:::
+ 点击 **安装** 启动容器。
+ 等待状态变为绿色后，点击 **Web UI** 按钮即可访问 OpenList 界面。
diff --git a/pages/guide/installation/worker.md b/pages/guide/installation/worker.md
index 615a03d59..566c5d131 100644
--- a/pages/guide/installation/worker.md
+++ b/pages/guide/installation/worker.md
@@ -1,207 +1,68 @@
---
-title:
- en: OpenList Worker
- zh-CN: OpenList Worker
-icon: iconfont icon-cloud
-# This control sidebar order
top: 40
-# A page can have multiple categories
categories:
- guide
- installation
-tag:
- - Worker
- - Cloudflare
- - EdgeOne
- - Install
---
-## What is OpenList Worker { lang="en" }
+# OpenList Worker
-## OpenList Worker 是什么 { lang="zh-CN" }
+## OpenList Worker 是什么
-::: en
-[**OpenList Worker**](https://github.com/OpenListTeam/OpenList-Worker)（仓库 `OpenList-TSWorker`）是 OpenList 官方的 TypeScript + Serverless 移植版。后端由 Go 重写为运行于边缘平台上的 TypeScript 服务，前端复用官方 [OpenList-Frontend](https://github.com/OpenListTeam/OpenList-Frontend)（SolidJS），无需自备服务器即可一键部署。
-
-- **后端**：Hono.js（TypeScript）
-- **运行平台**：Cloudflare Workers / EdgeOne Functions / Alibaba Cloud ESA / Vercel / AWS Lambda
-- **数据库**：Cloudflare D1（SQLite）、MySQL / MariaDB / PostgreSQL / SQL Server、Cloudflare KV
-- **许可证**：AGPL-3.0
- :::
-
-::: zh-CN
[**OpenList Worker**](https://github.com/OpenListTeam/OpenList-Worker)（仓库 `OpenList-TSWorker`）是 OpenList 官方的 TypeScript + Serverless 移植版。后端由 Go 重写为运行于边缘平台上的 TypeScript 服务，前端复用官方 [OpenList-Frontend](https://github.com/OpenListTeam/OpenList-Frontend)（SolidJS），无需自备服务器即可一键部署。
- **后端**：Hono.js（TypeScript）
- **运行平台**：Cloudflare Workers / EdgeOne Functions / 阿里云 ESA / Vercel / AWS Lambda
- **数据库**：Cloudflare D1（SQLite）、MySQL / MariaDB / PostgreSQL / SQL Server、Cloudflare KV
- **许可证**：AGPL-3.0
- :::
-
-## Supported Platforms { lang="en" }
-
-## 支持平台 { lang="zh-CN" }
-
-::: en
-| Platform | Persistence | One-click | Notes |
-| :--- | :--- | :---: | :--- |
-| Cloudflare Workers | D1 / KV / JSON | ✅ | Recommended, global edge network |
-| EdgeOne Makers（国际站 / 中国站） | EdgeOne Blob / KV | ✅ | Tencent Cloud edge platform |
-| Alibaba Cloud ESA | EdgeKV | ✅ | Alibaba edge function |
-| Vercel | In-memory（JSON） | — | No persistence by default |
-| AWS Lambda（Serverless Framework） | In-memory（JSON） | — | `serverless.yml` |
-:::
-
-::: zh-CN
-| 平台 | 持久化 | 一键部署 | 说明 |
-| :--- | :--- | :---: | :--- |
-| Cloudflare Workers | D1 / KV / JSON | ✅ | 推荐，全球边缘网络 |
-| EdgeOne Makers（国际站 / 中国站） | EdgeOne Blob / KV | ✅ | 腾讯云边缘平台 |
-| 阿里云 ESA | EdgeKV | ✅ | 阿里云边缘函数 |
-| Vercel | 内存（JSON） | — | 默认无持久化 |
-| AWS Lambda（Serverless Framework） | 内存（JSON） | — | `serverless.yml` |
-:::
-## One-click Deploy { lang="en" }
+## 支持平台
-## 一键部署 { lang="zh-CN" }
+| 平台 | 持久化 | 一键部署 | 说明 |
+| :--------------------------------- | :---------------- | :------: | :----------------- |
+| Cloudflare Workers | D1 / KV / JSON | ✅ | 推荐，全球边缘网络 |
+| EdgeOne Makers（国际站 / 中国站） | EdgeOne Blob / KV | ✅ | 腾讯云边缘平台 |
+| 阿里云 ESA | EdgeKV | ✅ | 阿里云边缘函数 |
+| Vercel | 内存（JSON） | — | 默认无持久化 |
+| AWS Lambda（Serverless Framework） | 内存（JSON） | — | `serverless.yml` |
-::: en
-Click the button below to deploy to the corresponding platform:
-:::
+## 一键部署
-::: zh-CN
点击下方按钮，即可将本项目一键部署到对应平台：
-:::
| EdgeOne Makers · 国际站 | EdgeOne Makers · 中国站 | Cloudflare Workers · 全球站 |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| [](https://edgeone.ai/pages/new?project-name=openlist-tsworker&repository-url=https://github.com/OpenListTeam/OpenList-Worker&install-command=pnpm%20install%20--no-frozen-lockfile&build-command=pnpm%20run%20build&output-directory=dist&env=JWT_SECRET) | [](https://console.cloud.tencent.com/edgeone/pages/new?project-name=openlist-tsworker&repository-url=https://github.com/OpenListTeam/OpenList-Worker&install-command=pnpm%20install%20--no-frozen-lockfile&build-command=pnpm%20run%20build&output-directory=dist&env=JWT_SECRET) | [](https://deploy.workers.cloudflare.com/?url=https://github.com/OpenListTeam/OpenList-Worker) |
-::: en
-
-> If Cloudflare prompts `无法获取存储库内容`（cannot fetch repository content）, fork this project first, then deploy by connecting to the GitHub repository.
-> :::
-
-::: zh-CN
-
> 若 Cloudflare 提示 `无法获取存储库内容`，则您需要先 Fork 本项目，再通过连接到 GitHub 仓库功能部署。
-> :::
-## Initialization { lang="en" }
+## 部署后初始化
-## 部署后初始化 { lang="zh-CN" }
-
-::: en
-::: tip
-After deployment, the first visit to the site automatically enters an **installation wizard**. Set the admin account and password in the browser to complete initialization — no pre-configured `ADMIN_PASS` is required.
-:::
-
-::: zh-CN
::: tip
部署完成后，首次访问站点会自动进入**安装向导**，在浏览器中设置管理员账号与密码即可完成初始化，无需预先配置 `ADMIN_PASS`。
:::
-## Environment Variables { lang="en" }
-
-## 环境变量 / Secrets { lang="zh-CN" }
-
-::: en
-| Variable | Required | Default | Description |
-| :--- | :--- | :--- | :--- |
-| `JWT_SECRET` | Recommended | — | JWT signing key, also used for data encryption and cron task auth. Auto-generated and persisted to KV when unset |
-| `DB_FORMAT` | Optional | `map` | Storage format: `map` (whole JSON) / `key` (per-key) / `sql` (relational, Go-compatible) |
-| `DB_DRIVER` | Optional | `auto` | Database driver: `auto` / `blob` / `cfkv` / `kv` / `d1` / `do` / `mysql` |
-| `CF_ACCOUNT` | Optional | — | Cloudflare account ID (required for `cfkv` mode) |
-| `CF_KV_UUID` | Optional | — | Cloudflare KV namespace ID (required for `cfkv` mode) |
-| `CF_API_KEY` | Optional | — | Cloudflare API token (required for `cfkv` mode) |
-| `MYSQL_URL` | Optional | — | MySQL connection string (or use `MYSQL_*` fields below) |
-| `MYSQL_HOST` / `MYSQL_PORT` / `MYSQL_USER` / `MYSQL_PASS` / `MYSQL_NAME` | Optional | — | MySQL connection fields (`DB_DRIVER = mysql`) |
-| `ADMIN_PASS` | Optional | — | Skip the install wizard and auto-initialize admin with this password |
-| `ALLOW_URLS` | Optional | — | Comma-separated CORS allowlist |
-| `MAX_UPLOAD` | Optional | `26214400` | Max size (bytes) for a whole upload (`/put`, `/form`) |
-| `MAX_UPPART` | Optional | `16777216` | Max size (bytes) per chunk in multipart upload |
-| `ASSET_URLS` | Optional | — | Frontend asset CDN base URL, supports the `$version` placeholder |
-| `ALLOW_SEED` | Optional | — | Allowlist of hosts permitted as seed-data sources |
-:::
-
-::: zh-CN
-| 变量 | 必要 | 默认值 | 说明 |
-| :--- | :--- | :--- | :--- |
-| `JWT_SECRET` | 推荐 | — | JWT 签名密钥，同时用于数据加密与定时任务鉴权。未配置时自动生成并持久化到 KV |
-| `DB_FORMAT` | 可选 | `map` | 数据存储格式：`map`（整对象 JSON）/ `key`（分 key 存储）/ `sql`（关系表，与 Go 后端一致） |
-| `DB_DRIVER` | 可选 | `auto` | 数据库驱动：`auto` / `blob` / `cfkv` / `kv` / `d1` / `do` / `mysql` |
-| `CF_ACCOUNT` | 可选 | — | Cloudflare 账号 ID（`cfkv` 模式必填） |
-| `CF_KV_UUID` | 可选 | — | Cloudflare KV namespace ID（`cfkv` 模式必填） |
-| `CF_API_KEY` | 可选 | — | Cloudflare API token（`cfkv` 模式必填） |
-| `MYSQL_URL` | 可选 | — | MySQL 连接串（或用下方 `MYSQL_*` 分项） |
-| `MYSQL_HOST` / `MYSQL_PORT` / `MYSQL_USER` / `MYSQL_PASS` / `MYSQL_NAME` | 可选 | — | MySQL 分项连接配置（`DB_DRIVER = mysql`） |
-| `ADMIN_PASS` | 可选 | — | 跳过安装向导，以该密码自动初始化 admin |
-| `ALLOW_URLS` | 可选 | — | CORS 允许白名单（逗号分隔） |
-| `MAX_UPLOAD` | 可选 | `26214400` | 单次整体上传（`/put`、`/form`）大小上限（字节） |
-| `MAX_UPPART` | 可选 | `16777216` | 分片上传单片大小上限（字节） |
-| `ASSET_URLS` | 可选 | — | 前端静态资源 CDN 地址，支持 `$version` 占位符 |
-| `ALLOW_SEED` | 可选 | — | 允许作为种子数据来源的主机白名单 |
-:::
-
-## Data Backend（DB_FORMAT & DB_DRIVER） { lang="en" }
-
-## 数据存储后端（DB_FORMAT 与 DB_DRIVER） { lang="zh-CN" }
-
-::: en
-OpenList Worker separates persistence into two orthogonal layers:
-
-- **`DB_FORMAT`** — how data is serialized and stored
-- **`DB_DRIVER`** — which underlying storage system is used
-
-### `DB_FORMAT`（data storage format）
-
-| Value | Description |
-| :--------------- | :-------------------------------------------------------------------------- |
-| `map`（default） | Whole object serialized as a single JSON value, ideal for KV / Blob storage |
-| `key` | Per-key storage, one record per entity (avoids large JSON) |
-| `sql` | Relational tables, fully compatible with the Go backend (for D1 / MySQL) |
-
-### `DB_DRIVER`（database driver）
-
-| Value | Description | Suitable platform |
-| :---------------- | :---------------------------------------------------------------------------- | :------------------------ |
-| `auto`（default） | Auto-detect available driver（priority: blob → cfkv → kv → d1 → memory） | Universal, works anywhere |
-| `blob` | Tencent EdgeOne Blob / Alibaba ESA Blob | EdgeOne / ESA |
-| `cfkv` | Cloudflare KV REST API（requires `CF_ACCOUNT` / `CF_KV_UUID` / `CF_API_KEY`） | External / cross-account |
-| `kv` | Cloudflare KV binding | Cloudflare Workers |
-| `d1` | Cloudflare D1 (SQLite) | Cloudflare Workers |
-| `do` | Cloudflare Durable Objects (SQLite) | Cloudflare Workers |
-| `mysql` | External MySQL | Node.js container runtime |
-
-### Recommended combinations
+## 环境变量 / Secrets
+
+| 变量 | 必要 | 默认值 | 说明 |
+| :----------------------------------------------------------------------- | :--- | :--------- | :---------------------------------------------------------------------------------------- |
+| `JWT_SECRET` | 推荐 | — | JWT 签名密钥，同时用于数据加密与定时任务鉴权。未配置时自动生成并持久化到 KV |
+| `DB_FORMAT` | 可选 | `map` | 数据存储格式：`map`（整对象 JSON）/ `key`（分 key 存储）/ `sql`（关系表，与 Go 后端一致） |
+| `DB_DRIVER` | 可选 | `auto` | 数据库驱动：`auto` / `blob` / `cfkv` / `kv` / `d1` / `do` / `mysql` |
+| `CF_ACCOUNT` | 可选 | — | Cloudflare 账号 ID（`cfkv` 模式必填） |
+| `CF_KV_UUID` | 可选 | — | Cloudflare KV namespace ID（`cfkv` 模式必填） |
+| `CF_API_KEY` | 可选 | — | Cloudflare API token（`cfkv` 模式必填） |
+| `MYSQL_URL` | 可选 | — | MySQL 连接串（或用下方 `MYSQL_*` 分项） |
+| `MYSQL_HOST` / `MYSQL_PORT` / `MYSQL_USER` / `MYSQL_PASS` / `MYSQL_NAME` | 可选 | — | MySQL 分项连接配置（`DB_DRIVER = mysql`） |
+| `ADMIN_PASS` | 可选 | — | 跳过安装向导，以该密码自动初始化 admin |
+| `ALLOW_URLS` | 可选 | — | CORS 允许白名单（逗号分隔） |
+| `MAX_UPLOAD` | 可选 | `26214400` | 单次整体上传（`/put`、`/form`）大小上限（字节） |
+| `MAX_UPPART` | 可选 | `16777216` | 分片上传单片大小上限（字节） |
+| `ASSET_URLS` | 可选 | — | 前端静态资源 CDN 地址，支持 `$version` 占位符 |
+| `ALLOW_SEED` | 可选 | — | 允许作为种子数据来源的主机白名单 |
+
+## 数据存储后端（DB_FORMAT 与 DB_DRIVER）
-```bash
-# Cloudflare Workers + D1 (recommended, SQL format compatible with Go backend)
-DB_FORMAT=sql
-DB_DRIVER=d1
-```
-
-> **Backward compatibility:** the legacy `DB_DRIVER=json` auto-converts to `DB_FORMAT=map` + auto-detected driver.
-
-#### Table naming (SQL format)
-
-The `sql` format uses columnar tables with the same naming strategy as the Go backend's GORM: snake*case + pluralized table names, plus the fixed `x*` prefix.
-
-| Go struct | Table name |
-| :------------ | :---------------- |
-| `SettingItem` | `x_setting_items` |
-| `SharingDB` | `x_sharing_dbs` |
-| `Storage` | `x_storages` |
-| `User` | `x_users` |
-| `Meta` | `x_metas` |
-| _(TS only)_ | `x_plugins` |
-
-The prefix is fixed to `x_` (matching the Go backend default), so no extra configuration is needed to share the same physical database with the Go backend.
-
-:::
-
-::: zh-CN
OpenList Worker 将持久化拆分为两个正交的层：
- **`DB_FORMAT`** — 决定数据的序列化与存储方式
@@ -252,53 +113,7 @@ DB_DRIVER=d1
前缀固定为 `x_`（与 Go 后端默认值一致），无需额外配置即可与 Go 后端共享同一物理数据库。
-:::
-
-## Deploy to Cloudflare Workers { lang="en" }
-
-## 部署到 Cloudflare Workers { lang="zh-CN" }
-
-::: en
-
-### Prerequisites
-
-- A [Cloudflare](https://dash.cloudflare.com/) account
-- Node.js 18+ and pnpm
-
-### Option 1: One-click deploy
-
-Click the **Deploy to Cloudflare Workers** button above. If it prompts that the repository cannot be fetched, fork the project first and deploy via the GitHub repository connection.
-
-### Option 2: Manual deploy with Wrangler
-
-```bash
-# 1. Clone and install dependencies
-git clone https://github.com/OpenListTeam/OpenList-Worker.git
-cd OpenList-Worker
-pnpm install
-
-# 2. Configure wrangler.jsonc (JWT_SECRET, KV / D1 bindings)
-
-# 3. Deploy to Cloudflare Workers
-pnpm run deploy:worker
-# or: pnpm run deploy (builds frontend + deploys backend)
-```
-
-### D1 database
-
-Use Cloudflare's _Automatic resource provisioning_: omit `database_id` in `wrangler.d1.jsonc`, and wrangler (>= 4.45.0) auto-creates a D1 database with the same name and writes back the ID on deploy:
-
-```jsonc
-{
- "vars": { "DB_FORMAT": "sql", "DB_DRIVER": "d1" },
- "d1_databases": [{ "binding": "DB", "database_name": "openlist-data-base" }],
-}
-```
-
-After deployment, configure the KV namespace binding and environment variables in the [Worker dashboard](https://dash.cloudflare.com/).
-:::
-
-::: zh-CN
+## 部署到 Cloudflare Workers
### 前置要求
@@ -336,47 +151,8 @@ pnpm run deploy:worker
```
部署完成后，请在 [Worker 后台](https://dash.cloudflare.com/) 配置 KV namespace 绑定与环境变量。
-:::
-
-## Deploy to EdgeOne { lang="en" }
-
-## 部署到 EdgeOne { lang="zh-CN" }
-
-::: en
-
-### One-click deploy
-
-Click the **EdgeOne** deploy button above, choose the international or China site:
-- [International console](https://console.edgeone.ai/makers)
-- [China console](https://console.cloud.tencent.com/edgeone/makers)
-
-### Persistence
-
-EdgeOne Makers uses `@edgeone/pages-blob` for persistence. The default `auto` driver auto-detects Blob. You can also explicitly set `DB_DRIVER = "blob"` (with `DB_FORMAT = "map"`) or `DB_DRIVER = "kv"` (with `DB_FORMAT = "key"`).
-
-### Scheduled tasks
-
-EdgeOne supports scheduled refresh via `edgeone.json`. Set `cron_secret` in the payload to your `JWT_SECRET` value, and configure the schedule:
-
-```jsonc
-{
- "schedules": [
- {
- "name": "token-refresh",
- "cron": "0 2 * * *",
- "path": "/api/task/refresh",
- "method": "POST",
- "payload": { "cron_secret": "" },
- "timezone": "Asia/Shanghai",
- },
- ],
-}
-```
-
-:::
-
-::: zh-CN
+## 部署到 EdgeOne
### 一键部署
@@ -408,47 +184,8 @@ EdgeOne 通过 `edgeone.json` 支持定时刷新。将 payload 中的 `cron_secr
}
```
-:::
-
-## Deploy to Alibaba Cloud ESA { lang="en" }
-
-## 部署到阿里云 ESA { lang="zh-CN" }
-
-::: en
-OpenList Worker ships a dedicated ESA edge function entry (`esa-entry.ts`), which adapts Alibaba Cloud EdgeKV into the project's KV interface.
-
-### Build & deploy
-
-```bash
-# 1. Install dependencies
-pnpm install
-
-# 2. Build (produces dist/esa-entry.js)
-pnpm run build
-```
-
-`esa.jsonc` defines the edge function entry, install/build commands, and static assets directory:
-
-```jsonc
-{
- "name": "openlist",
- "entry": "./dist/esa-entry.js",
- "installCommand": "pnpm install --no-frozen-lockfile",
- "buildCommand": "pnpm run build",
- "assets": { "directory": "./dist" },
-}
-```
+## 部署到阿里云 ESA
-### KV namespace
-
-Configure the EdgeKV namespace via the `KV_NAMESPACE` environment variable (default `openlist`).
-
-::: tip
-ESA EdgeKV is eventually consistent. The entry implements a module-level TTL cache (60s) to avoid "saved settings revert after refresh" caused by cross-node sync delay.
-:::
-:::
-
-::: zh-CN
OpenList Worker 内置了专用的 ESA 边缘函数入口（`esa-entry.ts`），将阿里云 EdgeKV 适配为项目的 KV 接口。
### 构建与部署
@@ -479,29 +216,9 @@ pnpm run build
::: tip
ESA EdgeKV 是最终一致性的。入口实现了带 TTL（60 秒）的模块级缓存，避免跨节点同步延迟导致的「保存设置后刷新复原」问题。
-:::
-:::
-
-## Local Development { lang="en" }
-
-## 本地开发 { lang="zh-CN" }
-
-::: en
-
-```bash
-# 1. Install backend dependencies
-pnpm install
-
-# 2. Fetch frontend and run the backend (unified dev server)
-pnpm run dev:unified
-
-# Or run the worker directly (frontend built separately)
-pnpm run dev:worker
-```
-
:::
-::: zh-CN
+## 本地开发
```bash
# 1. 安装后端依赖
@@ -514,49 +231,15 @@ pnpm run dev:unified
pnpm run dev:worker
```
-:::
-
-## Production Deploy { lang="en" }
-
-## 生产部署 { lang="zh-CN" }
-
-::: en
-
-```bash
-# One-click deploy (frontend build + backend deploy to Cloudflare Workers)
-pnpm run deploy
-```
-
-:::
-
-::: zh-CN
+## 生产部署
```bash
# 一键部署（前端构建 + 后端部署到 Cloudflare Workers）
pnpm run deploy
```
-:::
-
-## Troubleshooting { lang="en" }
+## 常见问题
-## 常见问题 { lang="zh-CN" }
-
-::: en
-::: details Cloudflare prompts "cannot fetch repository content"
-Fork the project first, then deploy by connecting to the GitHub repository instead of the direct one-click URL.
-:::
-
-::: details Settings revert after save (ESA / EdgeOne)
-This is usually a KV/CDN cache consistency issue. The entry already forces `no-cache` on `/api/*` GET responses and implements a module-level KV cache. If it persists, check that your KV namespace is correctly bound and not read-only.
-:::
-
-::: details How do I reset the admin password?
-The admin password is set during the install wizard. To reset, you can set `ADMIN_PASS` temporarily and redeploy, or clear the persisted config and re-run the wizard.
-:::
-:::
-
-::: zh-CN
::: details Cloudflare 提示「无法获取存储库内容」
请先 Fork 本项目，再通过连接到 GitHub 仓库功能部署，而不是直接使用一键部署 URL。
:::
@@ -568,10 +251,7 @@ The admin password is set during the install wizard. To reset, you can set `ADMI
::: details 如何重置管理员密码？
管理员密码在安装向导中设置。如需重置，可临时设置 `ADMIN_PASS` 并重新部署，或清空已持久化的配置后重新运行向导。
:::
-:::
-
-## Repository { lang="en" }
-## 项目仓库 { lang="zh-CN" }
+## 项目仓库
- [OpenListTeam/OpenList-Worker](https://github.com/OpenListTeam/OpenList-Worker)
diff --git a/pages/guide/migrate.md b/pages/guide/migrate.md
index 543160536..cd5109412 100644
--- a/pages/guide/migrate.md
+++ b/pages/guide/migrate.md
@@ -1,62 +1,26 @@
---
-title:
- en: Migrate from AList V3
- zh-CN: 从 AList V3 迁移
categories:
- guide
top: 99999
---
-::: en
-::: danger
-Smooth migration is not compatible with Alist v3.46 and higher versions. If you want to migrate, please avoid upgrading to a higher version.
-:::
-::: zh-CN
+# 从 AList V3 迁移
+
::: danger
不兼容 Alist v3.46 及更高版本的平滑迁移，如需迁移请勿升级到更高版本。
:::
-## 1. Revoke Authorization for Alist API { lang="en" }
-
-## 1. 解除授权 Alist API { lang="zh-CN" }
+## 1. 解除授权 Alist API
-::: en
-As the API service provided by the original author may have been taken over by a third party, there is a risk of information leakage or account bans. If you have concerns, it is recommended to revoke authorization or log in again to ensure your security.
-
-Since it's not possible to provide detailed steps for every platform, we invite helpful users to visit [https://github.com/OpenListTeam/OpenList-Docs](https://github.com/OpenListTeam/OpenList-Docs) and share screenshots of the authorization revocation process.
-
-The following content is provided by helpful online users in [OpenListTeam/OpenList-Docs#5](https://github.com/OpenListTeam/OpenList-Docs/issues/5) and [OpenListTeam/OpenList-Docs#6](https://github.com/OpenListTeam/OpenList-Docs/issues/6). We thank them for their contributions!🙏✨💖
-:::
-::: zh-CN
由于原作者提供的 API 服务可能已被第三方控制，存在信息泄露或账号封禁的风险。如果您对此有所顾虑，建议解除授权或重新登录以确保安全。
由于无法对各平台一一截取详细流程，欢迎各位热心网友前往 https://github.com/OpenListTeam/OpenList-Docs 提供解除授权的流程截图。
以下内容由热心网友提供（[OpenListTeam/OpenList-Docs#5](https://github.com/OpenListTeam/OpenList-Docs/issues/5)、[OpenListTeam/OpenList-Docs#6](https://github.com/OpenListTeam/OpenList-Docs/issues/6)），特别感谢！🙏✨💖
-:::
-::: en
-::: info The following methods only apply to cloud drives mounted using officially supported Open API methods.
-:::
-
-::: zh-CN
::: info 以下方法仅适用于采用 Open API 官方支持的方式挂载的网盘。
:::
-::: en
-::: tip Quick overview of how to revoke authorization for each cloud drive ♿️
-
-- **Baidu Netdisk App** - My - Settings - Account Management - Authorization Management - Alist - Revoke Authorization
-- **Aliyun Drive** - My - Upper right gear icon - Privacy Settings - Authorization Management - Alist - Revoke Authorization
-- **115 APP** - Life (scroll down) - Account & Security - Multi-device Login Management - Third-party Login
-- **China Unicom Cloud** - Check login account on webpage - Future recommendation: follow tutorial for packet capture login
-- **Baidu Photo** - Avatar - App Settings - Account Management - Authorization Management
-- **JianGuoYun** - Upper left three lines - Settings - Third-party App Management - Revoke Authorization
-- **OneDrive** - https://account.live.com/consent/Manage - Revoke Authorization
-
-:::
-
-::: zh-CN
::: tip 速览各网盘解除授权方式 ♿️
- **百度网盘App** - 我的 - 设置 - 帐号管理 - 授权管理 - Alist - 解除授权
@@ -69,22 +33,7 @@ The following content is provided by helpful online users in [OpenListTeam/OpenL
:::
-### Aliyun Drive { lang="en" }
-
-### 阿里云盘 { lang="zh-CN" }
-
-::: en
-
-1. Log in to Aliyun Drive
-2. Visit the link: [https://www.alipan.com/o/oauth/auth-list](https://www.alipan.com/o/oauth/auth-list)
- 
-3. Find Alist under “**Authorized Cloud Services**,” click to enter, then click "**Revoke Authorization**"
- 
-4. Successfully revoked
- 
-
-:::
-::: zh-CN
+### 阿里云盘
1. 登陆阿里云盘
2. 访问链接 https://www.alipan.com/o/oauth/auth-list
@@ -94,30 +43,11 @@ The following content is provided by helpful online users in [OpenListTeam/OpenL
4. 解除成功
-:::
-
-### Aliyun Drive APP { lang="en" }
-
-### 阿里云盘 APP { lang="zh-CN" }
+### 阿里云盘 APP
-### Baidu Netdisk { lang="en" }
-
-### 百度网盘 { lang="zh-CN" }
-
-::: en
-
-1. Log in to Baidu Netdisk
-2. Visit the link: [https://passport.baidu.com/v6/appAuthority](https://passport.baidu.com/v6/appAuthority)
- 
-3. Find Alist in Authorization Management, click to enter, then click "**Revoke Authorization**"
- 
-4. Successfully revoked
-
-:::
-
-::: zh-CN
+### 百度网盘
1. 登陆百度网盘
2. 访问链接 https://passport.baidu.com/v6/appAuthority
@@ -126,25 +56,17 @@ The following content is provided by helpful online users in [OpenListTeam/OpenL
4. 解除成功
-:::
-
-### Baidu Netdisk APP { lang="en" }
-
-### 百度网盘 APP { lang="zh-CN" }
+### 百度网盘 APP
-### OneDrive Business { lang="en" }
-
-### OneDrive 商业版 { lang="zh-CN" }
+### OneDrive 商业版
Link: https://entra.microsoft.com/#view/Microsoft_AAD_RegisteredApps/ApplicationsListBlade/quickStartType~/null/sourceType/Microsoft_AAD_IAM?Microsoft_AAD_IAM_legacyAADRedirect=true
-### OneDrive Personal { lang="en" }
-
-### OneDrive 个人版 { lang="zh-CN" }
+### OneDrive 个人版
Link: https://account.live.com/consent/Manage
@@ -160,78 +82,32 @@ Link: https://console.cloud.google.com
-## 2. Backup Configuration Files { lang="en" }
-
-## 2. 备份配置文件 { lang="zh-CN" }
+## 2. 备份配置文件
-::: en
-Use the [Backup & Restore](/guide/advanced/backup) function to back up the configuration files to your local device.
-
-Additionally, you will need to back up the `data` folder from Alist V3, which contains site configuration files and the database.
-:::
-::: zh-CN
使用 [备份&恢复](/guide/advanced/backup) 功能，将配置文件进行备份到本地。
此外，您还需要备份 Alist V3 的 `data` 文件夹，里面包含着站点的配置文件以及数据库。
-:::
-
-## 3. Uninstall Alist V3 { lang="en" }
-## 3. 卸载 Alist V3 { lang="zh-CN" }
+## 3. 卸载 Alist V3
-::: en
-Uninstall according to the method you used for installation.
-:::
-::: zh-CN
根据您安装的方式进行卸载。
-:::
-
-## 4. Install OpenList { lang="en" }
-## 4. 安装 OpenList { lang="zh-CN" }
+## 4. 安装 OpenList
-::: en
-Follow the instructions provided in the documentation to install OpenList.
-:::
-::: zh-CN
通过文档提供的方式安装 OpenList。
-:::
-::: en
-::: danger
-If you are using Docker for deployment, make sure to modify the Volume mapping by changing the configuration file path from `/opt/alist/data` to `/opt/openlist/data`. Otherwise, your configuration files will be lost after updating the version and rebuilding the container!
-
-In addition, it is recommended to delete the previous container and then recreate it to avoid failure to run due to environmental changes.
-:::
-::: zh-CN
::: danger
如果您使用 Docker 部署，请确保修改 Volume 映射，将配置文件的路径从 `/opt/alist/data` 修改为 `/opt/openlist/data`。否则，更新版本、重建容器后您的配置文件将丢失！
此外，建议删除之前的容器，然后重新创建，避免环境变化导致无法运行。
:::
-## 5. Restore Configuration Files{ lang="en" }
+## 5. 恢复配置文件
-## 5. 恢复配置文件 { lang="zh-CN" }
-
-::: en
-If your Alist V3 version is below v3.46, you can migrate directly—keeping the previous `data` folder and only replacing the OpenList binary files.
-
-Otherwise, use the [Backup & Restore](/guide/advanced/backup) function to restore the backed-up configuration files to OpenList.
-:::
-::: zh-CN
如果您的 Alist V3 版本低于 v3.46，正常情况下，您可以直接迁移——即保留之前的 `data` 文件夹，仅替换 OpenList 的二进制文件。
否则，请使用 [备份&恢复](/guide/advanced/backup) 功能，将备份的配置文件恢复到 OpenList。
-:::
-## 6. Reset Settings { lang="en" }
+## 6. 重置设置
-## 6. 重置设置 { lang="zh-CN" }
-
-::: en
-Once in OpenList’s admin panel, on each settings page, click the `Load Default Settings` button at the bottom, then click `Save`.
-:::
-::: zh-CN
进入 OpenList 后台，在设置的各个页面下，点击下方的 `加载默认设置`，然后 `保存`。
-:::
diff --git a/pages/index.md b/pages/index.md
index d206df874..be04a26ad 100644
--- a/pages/index.md
+++ b/pages/index.md
@@ -1,36 +1,28 @@
---
-style: home
+layout: home
title: OpenList
-description:
- en: OpenList is a resilient, community-driven file list program that supports multiple cloud storage platforms. Built as a secure fork of AList with enhanced security and long-term governance.
- zh-CN: OpenList 是一个支持多种云存储平台的韧性文件列表程序。作为 AList 的安全分支，具有增强的安全性和长期治理保障。
-# titleTemplate: '%s - Next Generation Static Blog Framework'
+titleTemplate: OpenList 文档
+description: OpenList 是一个支持多种云存储平台的韧性文件列表程序。作为 AList 的安全分支，具有增强的安全性和长期治理保障。
+comment: false
-hero:
+# rendered by .vitepress/theme/components/HomeHero.vue
+landing:
name: OpenList
- text:
+ tagline: |-
+ 🗂️ 一个支持多种存储的文件列表程序，
+ 由 Gin 和 SolidJS 强力驱动！
actions:
- theme: brand
- text: hero.actions.get-started
- link: /guide
- type: fly
+ text: 快速上手
+ link: /guide/
- theme: alt
- text: hero.actions.view-github
+ text: 查看 GitHub
link: https://github.com/OpenListTeam/OpenList
- - theme: alt
- external: true
- text: hero.actions.disclaimer
+ links:
+ - text: 免责声明
link: /terms#disclaimer
- - theme: alt
- external: true
- text: hero.actions.terms
+ - text: 使用条款
link: /terms
- - theme: alt
- external: true
- text: hero.actions.privacy
+ - text: 隐私政策
link: /privacy
-# todo, rewrite with valaxy
-# features:
---
-
-
diff --git a/pages/privacy.md b/pages/privacy.md
index 95148022c..c542fa5bc 100644
--- a/pages/privacy.md
+++ b/pages/privacy.md
@@ -1,27 +1,17 @@
---
-title:
- en: Privacy Policy
- zh-CN: 隐私政策
-# This is the icon of the page
-nav: false
-hide: true
-toc: false
-layout: statement
-top: 1000
-# A page can have multiple categories
+sidebar: false
+aside: false
+outline: false
+pageClass: statement-page
+comment: false
+contributors: false
---
-::: zh-CN
-我们非常重视您的隐私。我们**不收集任何您的个人信息**。但请注意，您的IP地址等信息可能会被您的互联网服务提供商（ISP）或网络中转节点收集，这超出我们的控制范围。
-:::
-
-::: en
-We highly value your privacy. We **DO NOT collect any of your personal information**. However, please be aware that your IP address and other metadata might be collected by your ISP or intermediate network nodes beyond our control.
-:::
+# 隐私政策
-## 隐私政策 { lang="zh-CN" }
+我们非常重视您的隐私。我们**不收集任何您的个人信息**。但请注意，您的IP地址等信息可能会被您的互联网服务提供商（ISP）或网络中转节点收集，这超出我们的控制范围。
-::: zh-CN
+## 隐私政策
- 我们不会收集、存储、处理或分析您的任何个人信息。
- 我们不会使用任何追踪技术（如Cookies、指纹识别、Web Beacon等）来收集您的信息。
@@ -29,18 +19,3 @@ We highly value your privacy. We **DO NOT collect any of your personal informati
- 您在本服务中的所有操作均不会被我们记录。
- 但您的IP地址、访问时间等信息可能会被您的ISP或网络中转节点收集，这属于互联网基础设施的正常行为，我们无法控制。
- 如有任何隐私相关疑问，欢迎随时联系我们。
-
-:::
-
-## Privacy Policy { lang="en" }
-
-::: en
-
-- We DO NOT collect, store, process, or analyze any of your personal data.
-- We DO NOT use any tracking technologies (such as cookies, fingerprinting, web beacons, etc.) to gather your data.
-- We DO NOT share your information with any third parties.
-- Your actions within this service are NOT recorded by us.
-- HOWEVER, your IP address and visit time may be collected by your ISP or transit nodes as part of normal Internet infrastructure behavior, which is BEYOND our control.
-- If you have any privacy-related concerns, please feel free to contact us.
-
-:::
diff --git a/public/algolia-verify.html b/pages/public/algolia-verify.html
similarity index 100%
rename from public/algolia-verify.html
rename to pages/public/algolia-verify.html
diff --git a/public/favicon.svg b/pages/public/favicon.svg
similarity index 100%
rename from public/favicon.svg
rename to pages/public/favicon.svg
diff --git a/public/img/1panel/container.png b/pages/public/img/1panel/container.png
similarity index 100%
rename from public/img/1panel/container.png
rename to pages/public/img/1panel/container.png
diff --git a/public/img/1panel/install.png b/pages/public/img/1panel/install.png
similarity index 100%
rename from public/img/1panel/install.png
rename to pages/public/img/1panel/install.png
diff --git a/public/img/1panel/installed.png b/pages/public/img/1panel/installed.png
similarity index 100%
rename from public/img/1panel/installed.png
rename to pages/public/img/1panel/installed.png
diff --git a/public/img/1panel/search.png b/pages/public/img/1panel/search.png
similarity index 100%
rename from public/img/1panel/search.png
rename to pages/public/img/1panel/search.png
diff --git a/public/img/1panel/terminal.png b/pages/public/img/1panel/terminal.png
similarity index 100%
rename from public/img/1panel/terminal.png
rename to pages/public/img/1panel/terminal.png
diff --git a/public/img/advanced/TrollStore.jpg b/pages/public/img/advanced/TrollStore.jpg
similarity index 100%
rename from public/img/advanced/TrollStore.jpg
rename to pages/public/img/advanced/TrollStore.jpg
diff --git a/public/img/advanced/backup.png b/pages/public/img/advanced/backup.png
similarity index 100%
rename from public/img/advanced/backup.png
rename to pages/public/img/advanced/backup.png
diff --git a/public/img/advanced/balance.png b/pages/public/img/advanced/balance.png
similarity index 100%
rename from public/img/advanced/balance.png
rename to pages/public/img/advanced/balance.png
diff --git a/public/img/advanced/casdoor-user.png b/pages/public/img/advanced/casdoor-user.png
similarity index 100%
rename from public/img/advanced/casdoor-user.png
rename to pages/public/img/advanced/casdoor-user.png
diff --git a/public/img/advanced/casdoor.png b/pages/public/img/advanced/casdoor.png
similarity index 100%
rename from public/img/advanced/casdoor.png
rename to pages/public/img/advanced/casdoor.png
diff --git a/public/img/advanced/dingding.png b/pages/public/img/advanced/dingding.png
similarity index 100%
rename from public/img/advanced/dingding.png
rename to pages/public/img/advanced/dingding.png
diff --git a/public/img/advanced/github-login.png b/pages/public/img/advanced/github-login.png
similarity index 100%
rename from public/img/advanced/github-login.png
rename to pages/public/img/advanced/github-login.png
diff --git a/public/img/advanced/github.png b/pages/public/img/advanced/github.png
similarity index 100%
rename from public/img/advanced/github.png
rename to pages/public/img/advanced/github.png
diff --git a/public/img/advanced/google.png b/pages/public/img/advanced/google.png
similarity index 100%
rename from public/img/advanced/google.png
rename to pages/public/img/advanced/google.png
diff --git a/public/img/advanced/hide-tips.png b/pages/public/img/advanced/hide-tips.png
similarity index 100%
rename from public/img/advanced/hide-tips.png
rename to pages/public/img/advanced/hide-tips.png
diff --git a/public/img/advanced/home.png b/pages/public/img/advanced/home.png
similarity index 100%
rename from public/img/advanced/home.png
rename to pages/public/img/advanced/home.png
diff --git a/public/img/advanced/index_settings_panel.png b/pages/public/img/advanced/index_settings_panel.png
similarity index 100%
rename from public/img/advanced/index_settings_panel.png
rename to pages/public/img/advanced/index_settings_panel.png
diff --git a/public/img/advanced/meta/password_b.png b/pages/public/img/advanced/meta/password_b.png
similarity index 100%
rename from public/img/advanced/meta/password_b.png
rename to pages/public/img/advanced/meta/password_b.png
diff --git a/public/img/advanced/meta/password_h.png b/pages/public/img/advanced/meta/password_h.png
similarity index 100%
rename from public/img/advanced/meta/password_h.png
rename to pages/public/img/advanced/meta/password_h.png
diff --git a/public/img/advanced/offline-download.png b/pages/public/img/advanced/offline-download.png
similarity index 100%
rename from public/img/advanced/offline-download.png
rename to pages/public/img/advanced/offline-download.png
diff --git a/public/img/advanced/qbittorrent.png b/pages/public/img/advanced/qbittorrent.png
similarity index 100%
rename from public/img/advanced/qbittorrent.png
rename to pages/public/img/advanced/qbittorrent.png
diff --git a/public/img/advanced/r_upload_1.png b/pages/public/img/advanced/r_upload_1.png
similarity index 100%
rename from public/img/advanced/r_upload_1.png
rename to pages/public/img/advanced/r_upload_1.png
diff --git a/public/img/advanced/r_upload_2.png b/pages/public/img/advanced/r_upload_2.png
similarity index 100%
rename from public/img/advanced/r_upload_2.png
rename to pages/public/img/advanced/r_upload_2.png
diff --git a/public/img/advanced/s3/s3_add_backup.png b/pages/public/img/advanced/s3/s3_add_backup.png
similarity index 100%
rename from public/img/advanced/s3/s3_add_backup.png
rename to pages/public/img/advanced/s3/s3_add_backup.png
diff --git a/public/img/advanced/s3/s3_config.png b/pages/public/img/advanced/s3/s3_config.png
similarity index 100%
rename from public/img/advanced/s3/s3_config.png
rename to pages/public/img/advanced/s3/s3_config.png
diff --git a/public/img/advanced/s3/s3browser.png b/pages/public/img/advanced/s3/s3browser.png
similarity index 100%
rename from public/img/advanced/s3/s3browser.png
rename to pages/public/img/advanced/s3/s3browser.png
diff --git a/public/img/advanced/s3/s3drive.png b/pages/public/img/advanced/s3/s3drive.png
similarity index 100%
rename from public/img/advanced/s3/s3drive.png
rename to pages/public/img/advanced/s3/s3drive.png
diff --git a/public/img/advanced/sqlite-mysql.png b/pages/public/img/advanced/sqlite-mysql.png
similarity index 100%
rename from public/img/advanced/sqlite-mysql.png
rename to pages/public/img/advanced/sqlite-mysql.png
diff --git a/public/img/advanced/sqlite3.png b/pages/public/img/advanced/sqlite3.png
similarity index 100%
rename from public/img/advanced/sqlite3.png
rename to pages/public/img/advanced/sqlite3.png
diff --git a/public/img/advanced/sso-add.png b/pages/public/img/advanced/sso-add.png
similarity index 100%
rename from public/img/advanced/sso-add.png
rename to pages/public/img/advanced/sso-add.png
diff --git a/public/img/advanced/sso-dir.png b/pages/public/img/advanced/sso-dir.png
similarity index 100%
rename from public/img/advanced/sso-dir.png
rename to pages/public/img/advanced/sso-dir.png
diff --git a/public/img/advanced/sso-group.png b/pages/public/img/advanced/sso-group.png
similarity index 100%
rename from public/img/advanced/sso-group.png
rename to pages/public/img/advanced/sso-group.png
diff --git a/public/img/advanced/sso-org-config.png b/pages/public/img/advanced/sso-org-config.png
similarity index 100%
rename from public/img/advanced/sso-org-config.png
rename to pages/public/img/advanced/sso-org-config.png
diff --git a/public/img/advanced/sso-permission_b.png b/pages/public/img/advanced/sso-permission_b.png
similarity index 100%
rename from public/img/advanced/sso-permission_b.png
rename to pages/public/img/advanced/sso-permission_b.png
diff --git a/public/img/advanced/sso-permission_h.png b/pages/public/img/advanced/sso-permission_h.png
similarity index 100%
rename from public/img/advanced/sso-permission_h.png
rename to pages/public/img/advanced/sso-permission_h.png
diff --git a/public/img/advanced/sso/keycloak-01.png b/pages/public/img/advanced/sso/keycloak-01.png
similarity index 100%
rename from public/img/advanced/sso/keycloak-01.png
rename to pages/public/img/advanced/sso/keycloak-01.png
diff --git a/public/img/advanced/sso/keycloak-02.png b/pages/public/img/advanced/sso/keycloak-02.png
similarity index 100%
rename from public/img/advanced/sso/keycloak-02.png
rename to pages/public/img/advanced/sso/keycloak-02.png
diff --git a/public/img/advanced/sso/keycloak-03.png b/pages/public/img/advanced/sso/keycloak-03.png
similarity index 100%
rename from public/img/advanced/sso/keycloak-03.png
rename to pages/public/img/advanced/sso/keycloak-03.png
diff --git a/public/img/advanced/sso_add_app.png b/pages/public/img/advanced/sso_add_app.png
similarity index 100%
rename from public/img/advanced/sso_add_app.png
rename to pages/public/img/advanced/sso_add_app.png
diff --git a/public/img/advanced/sso_cm.png b/pages/public/img/advanced/sso_cm.png
similarity index 100%
rename from public/img/advanced/sso_cm.png
rename to pages/public/img/advanced/sso_cm.png
diff --git a/public/img/advanced/sso_fix_logo.png b/pages/public/img/advanced/sso_fix_logo.png
similarity index 100%
rename from public/img/advanced/sso_fix_logo.png
rename to pages/public/img/advanced/sso_fix_logo.png
diff --git a/public/img/advanced/user_manage.png b/pages/public/img/advanced/user_manage.png
similarity index 100%
rename from public/img/advanced/user_manage.png
rename to pages/public/img/advanced/user_manage.png
diff --git a/public/img/advanced/user_read_archives_dark.png b/pages/public/img/advanced/user_read_archives_dark.png
similarity index 100%
rename from public/img/advanced/user_read_archives_dark.png
rename to pages/public/img/advanced/user_read_archives_dark.png
diff --git a/public/img/advanced/user_read_archives_light.png b/pages/public/img/advanced/user_read_archives_light.png
similarity index 100%
rename from public/img/advanced/user_read_archives_light.png
rename to pages/public/img/advanced/user_read_archives_light.png
diff --git a/public/img/advanced/video.png b/pages/public/img/advanced/video.png
similarity index 100%
rename from public/img/advanced/video.png
rename to pages/public/img/advanced/video.png
diff --git a/public/img/advanced/weiruan.png b/pages/public/img/advanced/weiruan.png
similarity index 100%
rename from public/img/advanced/weiruan.png
rename to pages/public/img/advanced/weiruan.png
diff --git a/public/img/api/apifox-dark.png b/pages/public/img/api/apifox-dark.png
similarity index 100%
rename from public/img/api/apifox-dark.png
rename to pages/public/img/api/apifox-dark.png
diff --git a/public/img/api/apifox-light.png b/pages/public/img/api/apifox-light.png
similarity index 100%
rename from public/img/api/apifox-light.png
rename to pages/public/img/api/apifox-light.png
diff --git a/public/img/config/open-with.png b/pages/public/img/config/open-with.png
similarity index 100%
rename from public/img/config/open-with.png
rename to pages/public/img/config/open-with.png
diff --git a/public/img/config/readme_b.png b/pages/public/img/config/readme_b.png
similarity index 100%
rename from public/img/config/readme_b.png
rename to pages/public/img/config/readme_b.png
diff --git a/public/img/config/readme_h.png b/pages/public/img/config/readme_h.png
similarity index 100%
rename from public/img/config/readme_h.png
rename to pages/public/img/config/readme_h.png
diff --git a/public/img/config/side/offline-download-modal-en.png b/pages/public/img/config/side/offline-download-modal-en.png
similarity index 100%
rename from public/img/config/side/offline-download-modal-en.png
rename to pages/public/img/config/side/offline-download-modal-en.png
diff --git a/public/img/config/side/offline-download-modal-zh.png b/pages/public/img/config/side/offline-download-modal-zh.png
similarity index 100%
rename from public/img/config/side/offline-download-modal-zh.png
rename to pages/public/img/config/side/offline-download-modal-zh.png
diff --git a/public/img/config/side/upload-modal-en.png b/pages/public/img/config/side/upload-modal-en.png
similarity index 100%
rename from public/img/config/side/upload-modal-en.png
rename to pages/public/img/config/side/upload-modal-en.png
diff --git a/public/img/config/side/upload-modal-zh.png b/pages/public/img/config/side/upload-modal-zh.png
similarity index 100%
rename from public/img/config/side/upload-modal-zh.png
rename to pages/public/img/config/side/upload-modal-zh.png
diff --git a/public/img/desktop/dashboard.png b/pages/public/img/desktop/dashboard.png
similarity index 100%
rename from public/img/desktop/dashboard.png
rename to pages/public/img/desktop/dashboard.png
diff --git a/public/img/desktop/logs.png b/pages/public/img/desktop/logs.png
similarity index 100%
rename from public/img/desktop/logs.png
rename to pages/public/img/desktop/logs.png
diff --git a/public/img/desktop/mount.png b/pages/public/img/desktop/mount.png
similarity index 100%
rename from public/img/desktop/mount.png
rename to pages/public/img/desktop/mount.png
diff --git a/public/img/drivers/115/115-add_error.png b/pages/public/img/drivers/115/115-add_error.png
similarity index 100%
rename from public/img/drivers/115/115-add_error.png
rename to pages/public/img/drivers/115/115-add_error.png
diff --git a/public/img/drivers/115/115-file_cid.png b/pages/public/img/drivers/115/115-file_cid.png
similarity index 100%
rename from public/img/drivers/115/115-file_cid.png
rename to pages/public/img/drivers/115/115-file_cid.png
diff --git a/public/img/drivers/115/115-open-01-d.png b/pages/public/img/drivers/115/115-open-01-d.png
similarity index 100%
rename from public/img/drivers/115/115-open-01-d.png
rename to pages/public/img/drivers/115/115-open-01-d.png
diff --git a/public/img/drivers/115/115-open-01-l.png b/pages/public/img/drivers/115/115-open-01-l.png
similarity index 100%
rename from public/img/drivers/115/115-open-01-l.png
rename to pages/public/img/drivers/115/115-open-01-l.png
diff --git a/public/img/drivers/115/115-open-02-01-d.png b/pages/public/img/drivers/115/115-open-02-01-d.png
similarity index 100%
rename from public/img/drivers/115/115-open-02-01-d.png
rename to pages/public/img/drivers/115/115-open-02-01-d.png
diff --git a/public/img/drivers/115/115-open-02-01-l.png b/pages/public/img/drivers/115/115-open-02-01-l.png
similarity index 100%
rename from public/img/drivers/115/115-open-02-01-l.png
rename to pages/public/img/drivers/115/115-open-02-01-l.png
diff --git a/public/img/drivers/115/115-open-02-02-d.png b/pages/public/img/drivers/115/115-open-02-02-d.png
similarity index 100%
rename from public/img/drivers/115/115-open-02-02-d.png
rename to pages/public/img/drivers/115/115-open-02-02-d.png
diff --git a/public/img/drivers/115/115-open-02-02-l.png b/pages/public/img/drivers/115/115-open-02-02-l.png
similarity index 100%
rename from public/img/drivers/115/115-open-02-02-l.png
rename to pages/public/img/drivers/115/115-open-02-02-l.png
diff --git a/public/img/drivers/115/115-open-03.png b/pages/public/img/drivers/115/115-open-03.png
similarity index 100%
rename from public/img/drivers/115/115-open-03.png
rename to pages/public/img/drivers/115/115-open-03.png
diff --git a/public/img/drivers/115/115-open-04-d.png b/pages/public/img/drivers/115/115-open-04-d.png
similarity index 100%
rename from public/img/drivers/115/115-open-04-d.png
rename to pages/public/img/drivers/115/115-open-04-d.png
diff --git a/public/img/drivers/115/115-open-04-l.png b/pages/public/img/drivers/115/115-open-04-l.png
similarity index 100%
rename from public/img/drivers/115/115-open-04-l.png
rename to pages/public/img/drivers/115/115-open-04-l.png
diff --git a/public/img/drivers/115/115-open-05-d.png b/pages/public/img/drivers/115/115-open-05-d.png
similarity index 100%
rename from public/img/drivers/115/115-open-05-d.png
rename to pages/public/img/drivers/115/115-open-05-d.png
diff --git a/public/img/drivers/115/115-open-05-l.png b/pages/public/img/drivers/115/115-open-05-l.png
similarity index 100%
rename from public/img/drivers/115/115-open-05-l.png
rename to pages/public/img/drivers/115/115-open-05-l.png
diff --git a/public/img/drivers/115/115-open-application.jpg b/pages/public/img/drivers/115/115-open-application.jpg
similarity index 100%
rename from public/img/drivers/115/115-open-application.jpg
rename to pages/public/img/drivers/115/115-open-application.jpg
diff --git a/public/img/drivers/115/115-root_cid.png b/pages/public/img/drivers/115/115-root_cid.png
similarity index 100%
rename from public/img/drivers/115/115-root_cid.png
rename to pages/public/img/drivers/115/115-root_cid.png
diff --git a/public/img/drivers/115/115-url_demo.png b/pages/public/img/drivers/115/115-url_demo.png
similarity index 100%
rename from public/img/drivers/115/115-url_demo.png
rename to pages/public/img/drivers/115/115-url_demo.png
diff --git a/public/img/drivers/123/123.png b/pages/public/img/drivers/123/123.png
similarity index 100%
rename from public/img/drivers/123/123.png
rename to pages/public/img/drivers/123/123.png
diff --git a/public/img/drivers/123/123_add_demo.png b/pages/public/img/drivers/123/123_add_demo.png
similarity index 100%
rename from public/img/drivers/123/123_add_demo.png
rename to pages/public/img/drivers/123/123_add_demo.png
diff --git a/public/img/drivers/123/123_fl_id.png b/pages/public/img/drivers/123/123_fl_id.png
similarity index 100%
rename from public/img/drivers/123/123_fl_id.png
rename to pages/public/img/drivers/123/123_fl_id.png
diff --git a/public/img/drivers/123/123_link_1.png b/pages/public/img/drivers/123/123_link_1.png
similarity index 100%
rename from public/img/drivers/123/123_link_1.png
rename to pages/public/img/drivers/123/123_link_1.png
diff --git a/public/img/drivers/123/123_link_2.png b/pages/public/img/drivers/123/123_link_2.png
similarity index 100%
rename from public/img/drivers/123/123_link_2.png
rename to pages/public/img/drivers/123/123_link_2.png
diff --git a/public/img/drivers/123/123_link_3.png b/pages/public/img/drivers/123/123_link_3.png
similarity index 100%
rename from public/img/drivers/123/123_link_3.png
rename to pages/public/img/drivers/123/123_link_3.png
diff --git a/public/img/drivers/123/123_link_4.png b/pages/public/img/drivers/123/123_link_4.png
similarity index 100%
rename from public/img/drivers/123/123_link_4.png
rename to pages/public/img/drivers/123/123_link_4.png
diff --git a/public/img/drivers/123/123open-02.png b/pages/public/img/drivers/123/123open-02.png
similarity index 100%
rename from public/img/drivers/123/123open-02.png
rename to pages/public/img/drivers/123/123open-02.png
diff --git a/public/img/drivers/123/123open-03.png b/pages/public/img/drivers/123/123open-03.png
similarity index 100%
rename from public/img/drivers/123/123open-03.png
rename to pages/public/img/drivers/123/123open-03.png
diff --git a/public/img/drivers/139/139_new_au.png b/pages/public/img/drivers/139/139_new_au.png
similarity index 100%
rename from public/img/drivers/139/139_new_au.png
rename to pages/public/img/drivers/139/139_new_au.png
diff --git a/public/img/drivers/139/add-family.png b/pages/public/img/drivers/139/add-family.png
similarity index 100%
rename from public/img/drivers/139/add-family.png
rename to pages/public/img/drivers/139/add-family.png
diff --git a/public/img/drivers/139/add-personal.png b/pages/public/img/drivers/139/add-personal.png
similarity index 100%
rename from public/img/drivers/139/add-personal.png
rename to pages/public/img/drivers/139/add-personal.png
diff --git a/public/img/drivers/139/add_new_personal.png b/pages/public/img/drivers/139/add_new_personal.png
similarity index 100%
rename from public/img/drivers/139/add_new_personal.png
rename to pages/public/img/drivers/139/add_new_personal.png
diff --git a/public/img/drivers/139/ch-family.png b/pages/public/img/drivers/139/ch-family.png
similarity index 100%
rename from public/img/drivers/139/ch-family.png
rename to pages/public/img/drivers/139/ch-family.png
diff --git a/public/img/drivers/139/ch-personal.png b/pages/public/img/drivers/139/ch-personal.png
similarity index 100%
rename from public/img/drivers/139/ch-personal.png
rename to pages/public/img/drivers/139/ch-personal.png
diff --git a/public/img/drivers/139/new_personal.png b/pages/public/img/drivers/139/new_personal.png
similarity index 100%
rename from public/img/drivers/139/new_personal.png
rename to pages/public/img/drivers/139/new_personal.png
diff --git a/public/img/drivers/139/other-family.png b/pages/public/img/drivers/139/other-family.png
similarity index 100%
rename from public/img/drivers/139/other-family.png
rename to pages/public/img/drivers/139/other-family.png
diff --git a/public/img/drivers/139/other-personal.png b/pages/public/img/drivers/139/other-personal.png
similarity index 100%
rename from public/img/drivers/139/other-personal.png
rename to pages/public/img/drivers/139/other-personal.png
diff --git a/public/img/drivers/163/163_cookie.png b/pages/public/img/drivers/163/163_cookie.png
similarity index 100%
rename from public/img/drivers/163/163_cookie.png
rename to pages/public/img/drivers/163/163_cookie.png
diff --git a/public/img/drivers/189/189-0.png b/pages/public/img/drivers/189/189-0.png
similarity index 100%
rename from public/img/drivers/189/189-0.png
rename to pages/public/img/drivers/189/189-0.png
diff --git a/public/img/drivers/189/189-1.png b/pages/public/img/drivers/189/189-1.png
similarity index 100%
rename from public/img/drivers/189/189-1.png
rename to pages/public/img/drivers/189/189-1.png
diff --git a/public/img/drivers/189/189-2.png b/pages/public/img/drivers/189/189-2.png
similarity index 100%
rename from public/img/drivers/189/189-2.png
rename to pages/public/img/drivers/189/189-2.png
diff --git a/public/img/drivers/189/189.png b/pages/public/img/drivers/189/189.png
similarity index 100%
rename from public/img/drivers/189/189.png
rename to pages/public/img/drivers/189/189.png
diff --git a/public/img/drivers/189/3.png b/pages/public/img/drivers/189/3.png
similarity index 100%
rename from public/img/drivers/189/3.png
rename to pages/public/img/drivers/189/3.png
diff --git a/public/img/drivers/189/4.png b/pages/public/img/drivers/189/4.png
similarity index 100%
rename from public/img/drivers/189/4.png
rename to pages/public/img/drivers/189/4.png
diff --git a/public/img/drivers/OneDrive/onedrive-new-password.png b/pages/public/img/drivers/OneDrive/onedrive-new-password.png
similarity index 100%
rename from public/img/drivers/OneDrive/onedrive-new-password.png
rename to pages/public/img/drivers/OneDrive/onedrive-new-password.png
diff --git a/public/img/drivers/OneDrive/onedrive-register-app.png b/pages/public/img/drivers/OneDrive/onedrive-register-app.png
similarity index 100%
rename from public/img/drivers/OneDrive/onedrive-register-app.png
rename to pages/public/img/drivers/OneDrive/onedrive-register-app.png
diff --git a/public/img/drivers/OneDrive/onedrive-update-permission.png b/pages/public/img/drivers/OneDrive/onedrive-update-permission.png
similarity index 100%
rename from public/img/drivers/OneDrive/onedrive-update-permission.png
rename to pages/public/img/drivers/OneDrive/onedrive-update-permission.png
diff --git a/public/img/drivers/OneDrive/online_api.png b/pages/public/img/drivers/OneDrive/online_api.png
similarity index 100%
rename from public/img/drivers/OneDrive/online_api.png
rename to pages/public/img/drivers/OneDrive/online_api.png
diff --git a/public/img/drivers/OneDrive/online_api_config.png b/pages/public/img/drivers/OneDrive/online_api_config.png
similarity index 100%
rename from public/img/drivers/OneDrive/online_api_config.png
rename to pages/public/img/drivers/OneDrive/online_api_config.png
diff --git a/public/img/drivers/alias/alias-2.png b/pages/public/img/drivers/alias/alias-2.png
similarity index 100%
rename from public/img/drivers/alias/alias-2.png
rename to pages/public/img/drivers/alias/alias-2.png
diff --git a/public/img/drivers/alias/alias-3.png b/pages/public/img/drivers/alias/alias-3.png
similarity index 100%
rename from public/img/drivers/alias/alias-3.png
rename to pages/public/img/drivers/alias/alias-3.png
diff --git a/public/img/drivers/alias/alias.png b/pages/public/img/drivers/alias/alias.png
similarity index 100%
rename from public/img/drivers/alias/alias.png
rename to pages/public/img/drivers/alias/alias.png
diff --git a/public/img/drivers/alias/read_policy_all.png b/pages/public/img/drivers/alias/read_policy_all.png
similarity index 100%
rename from public/img/drivers/alias/read_policy_all.png
rename to pages/public/img/drivers/alias/read_policy_all.png
diff --git a/public/img/drivers/alist/alist.png b/pages/public/img/drivers/alist/alist.png
similarity index 100%
rename from public/img/drivers/alist/alist.png
rename to pages/public/img/drivers/alist/alist.png
diff --git a/public/img/drivers/aliyun/aliyun-open-01-d.png b/pages/public/img/drivers/aliyun/aliyun-open-01-d.png
similarity index 100%
rename from public/img/drivers/aliyun/aliyun-open-01-d.png
rename to pages/public/img/drivers/aliyun/aliyun-open-01-d.png
diff --git a/public/img/drivers/aliyun/aliyun-open-01-l.png b/pages/public/img/drivers/aliyun/aliyun-open-01-l.png
similarity index 100%
rename from public/img/drivers/aliyun/aliyun-open-01-l.png
rename to pages/public/img/drivers/aliyun/aliyun-open-01-l.png
diff --git a/public/img/drivers/aliyun/aliyun-open-02-01-d.png b/pages/public/img/drivers/aliyun/aliyun-open-02-01-d.png
similarity index 100%
rename from public/img/drivers/aliyun/aliyun-open-02-01-d.png
rename to pages/public/img/drivers/aliyun/aliyun-open-02-01-d.png
diff --git a/public/img/drivers/aliyun/aliyun-open-02-01-l.png b/pages/public/img/drivers/aliyun/aliyun-open-02-01-l.png
similarity index 100%
rename from public/img/drivers/aliyun/aliyun-open-02-01-l.png
rename to pages/public/img/drivers/aliyun/aliyun-open-02-01-l.png
diff --git a/public/img/drivers/aliyun/aliyun-open-02-02-d.png b/pages/public/img/drivers/aliyun/aliyun-open-02-02-d.png
similarity index 100%
rename from public/img/drivers/aliyun/aliyun-open-02-02-d.png
rename to pages/public/img/drivers/aliyun/aliyun-open-02-02-d.png
diff --git a/public/img/drivers/aliyun/aliyun-open-02-02-l.png b/pages/public/img/drivers/aliyun/aliyun-open-02-02-l.png
similarity index 100%
rename from public/img/drivers/aliyun/aliyun-open-02-02-l.png
rename to pages/public/img/drivers/aliyun/aliyun-open-02-02-l.png
diff --git a/public/img/drivers/aliyun/aliyun-open-03.png b/pages/public/img/drivers/aliyun/aliyun-open-03.png
similarity index 100%
rename from public/img/drivers/aliyun/aliyun-open-03.png
rename to pages/public/img/drivers/aliyun/aliyun-open-03.png
diff --git a/public/img/drivers/aliyun/aliyun-open-04-d.png b/pages/public/img/drivers/aliyun/aliyun-open-04-d.png
similarity index 100%
rename from public/img/drivers/aliyun/aliyun-open-04-d.png
rename to pages/public/img/drivers/aliyun/aliyun-open-04-d.png
diff --git a/public/img/drivers/aliyun/aliyun-open-04-l.png b/pages/public/img/drivers/aliyun/aliyun-open-04-l.png
similarity index 100%
rename from public/img/drivers/aliyun/aliyun-open-04-l.png
rename to pages/public/img/drivers/aliyun/aliyun-open-04-l.png
diff --git a/public/img/drivers/aliyun/aliyun-open-05-d.png b/pages/public/img/drivers/aliyun/aliyun-open-05-d.png
similarity index 100%
rename from public/img/drivers/aliyun/aliyun-open-05-d.png
rename to pages/public/img/drivers/aliyun/aliyun-open-05-d.png
diff --git a/public/img/drivers/aliyun/aliyun-open-05-l.png b/pages/public/img/drivers/aliyun/aliyun-open-05-l.png
similarity index 100%
rename from public/img/drivers/aliyun/aliyun-open-05-l.png
rename to pages/public/img/drivers/aliyun/aliyun-open-05-l.png
diff --git a/public/img/drivers/aliyun/aliyun-open-06-d.png b/pages/public/img/drivers/aliyun/aliyun-open-06-d.png
similarity index 100%
rename from public/img/drivers/aliyun/aliyun-open-06-d.png
rename to pages/public/img/drivers/aliyun/aliyun-open-06-d.png
diff --git a/public/img/drivers/aliyun/aliyun-open-06-l.png b/pages/public/img/drivers/aliyun/aliyun-open-06-l.png
similarity index 100%
rename from public/img/drivers/aliyun/aliyun-open-06-l.png
rename to pages/public/img/drivers/aliyun/aliyun-open-06-l.png
diff --git a/public/img/drivers/aliyun/aliyun-open-07-d.png b/pages/public/img/drivers/aliyun/aliyun-open-07-d.png
similarity index 100%
rename from public/img/drivers/aliyun/aliyun-open-07-d.png
rename to pages/public/img/drivers/aliyun/aliyun-open-07-d.png
diff --git a/public/img/drivers/aliyun/aliyun-open-07-l.png b/pages/public/img/drivers/aliyun/aliyun-open-07-l.png
similarity index 100%
rename from public/img/drivers/aliyun/aliyun-open-07-l.png
rename to pages/public/img/drivers/aliyun/aliyun-open-07-l.png
diff --git a/public/img/drivers/aliyun/aliyun_api.png b/pages/public/img/drivers/aliyun/aliyun_api.png
similarity index 100%
rename from public/img/drivers/aliyun/aliyun_api.png
rename to pages/public/img/drivers/aliyun/aliyun_api.png
diff --git a/public/img/drivers/aliyun/aliyun_type.png b/pages/public/img/drivers/aliyun/aliyun_type.png
similarity index 100%
rename from public/img/drivers/aliyun/aliyun_type.png
rename to pages/public/img/drivers/aliyun/aliyun_type.png
diff --git a/public/img/drivers/aliyundrive.png b/pages/public/img/drivers/aliyundrive.png
similarity index 100%
rename from public/img/drivers/aliyundrive.png
rename to pages/public/img/drivers/aliyundrive.png
diff --git a/public/img/drivers/baidu/BDUSS.png b/pages/public/img/drivers/baidu/BDUSS.png
similarity index 100%
rename from public/img/drivers/baidu/BDUSS.png
rename to pages/public/img/drivers/baidu/BDUSS.png
diff --git a/public/img/drivers/baidu/aria2-ua.png b/pages/public/img/drivers/baidu/aria2-ua.png
similarity index 100%
rename from public/img/drivers/baidu/aria2-ua.png
rename to pages/public/img/drivers/baidu/aria2-ua.png
diff --git a/public/img/drivers/baidu/bdUA.png b/pages/public/img/drivers/baidu/bdUA.png
similarity index 100%
rename from public/img/drivers/baidu/bdUA.png
rename to pages/public/img/drivers/baidu/bdUA.png
diff --git a/public/img/drivers/baidu/crack_dev_token.png b/pages/public/img/drivers/baidu/crack_dev_token.png
similarity index 100%
rename from public/img/drivers/baidu/crack_dev_token.png
rename to pages/public/img/drivers/baidu/crack_dev_token.png
diff --git a/public/img/drivers/baidu/dev_app_console.png b/pages/public/img/drivers/baidu/dev_app_console.png
similarity index 100%
rename from public/img/drivers/baidu/dev_app_console.png
rename to pages/public/img/drivers/baidu/dev_app_console.png
diff --git a/public/img/drivers/baidu/dev_app_create_button.png b/pages/public/img/drivers/baidu/dev_app_create_button.png
similarity index 100%
rename from public/img/drivers/baidu/dev_app_create_button.png
rename to pages/public/img/drivers/baidu/dev_app_create_button.png
diff --git a/public/img/drivers/baidu/dev_app_create_panel.png b/pages/public/img/drivers/baidu/dev_app_create_panel.png
similarity index 100%
rename from public/img/drivers/baidu/dev_app_create_panel.png
rename to pages/public/img/drivers/baidu/dev_app_create_panel.png
diff --git a/public/img/drivers/baidu/dev_app_info.png b/pages/public/img/drivers/baidu/dev_app_info.png
similarity index 100%
rename from public/img/drivers/baidu/dev_app_info.png
rename to pages/public/img/drivers/baidu/dev_app_info.png
diff --git a/public/img/drivers/baidu/dev_app_settings_safety.png b/pages/public/img/drivers/baidu/dev_app_settings_safety.png
similarity index 100%
rename from public/img/drivers/baidu/dev_app_settings_safety.png
rename to pages/public/img/drivers/baidu/dev_app_settings_safety.png
diff --git a/public/img/drivers/baidu/dev_platform.png b/pages/public/img/drivers/baidu/dev_platform.png
similarity index 100%
rename from public/img/drivers/baidu/dev_platform.png
rename to pages/public/img/drivers/baidu/dev_platform.png
diff --git a/public/img/drivers/baidu/dev_platform_console.png b/pages/public/img/drivers/baidu/dev_platform_console.png
similarity index 100%
rename from public/img/drivers/baidu/dev_platform_console.png
rename to pages/public/img/drivers/baidu/dev_platform_console.png
diff --git a/public/img/drivers/baidu/dev_platform_login.png b/pages/public/img/drivers/baidu/dev_platform_login.png
similarity index 100%
rename from public/img/drivers/baidu/dev_platform_login.png
rename to pages/public/img/drivers/baidu/dev_platform_login.png
diff --git a/public/img/drivers/baidu/dev_token.png b/pages/public/img/drivers/baidu/dev_token.png
similarity index 100%
rename from public/img/drivers/baidu/dev_token.png
rename to pages/public/img/drivers/baidu/dev_token.png
diff --git a/public/img/drivers/baidu/idm-ua.png b/pages/public/img/drivers/baidu/idm-ua.png
similarity index 100%
rename from public/img/drivers/baidu/idm-ua.png
rename to pages/public/img/drivers/baidu/idm-ua.png
diff --git a/public/img/drivers/baidu/motrix-ua.png b/pages/public/img/drivers/baidu/motrix-ua.png
similarity index 100%
rename from public/img/drivers/baidu/motrix-ua.png
rename to pages/public/img/drivers/baidu/motrix-ua.png
diff --git a/public/img/drivers/baidu/non_dev_token.png b/pages/public/img/drivers/baidu/non_dev_token.png
similarity index 100%
rename from public/img/drivers/baidu/non_dev_token.png
rename to pages/public/img/drivers/baidu/non_dev_token.png
diff --git a/public/img/drivers/baidu/openapi.png b/pages/public/img/drivers/baidu/openapi.png
similarity index 100%
rename from public/img/drivers/baidu/openapi.png
rename to pages/public/img/drivers/baidu/openapi.png
diff --git a/public/img/drivers/baidu/yike_cookie.png b/pages/public/img/drivers/baidu/yike_cookie.png
similarity index 100%
rename from public/img/drivers/baidu/yike_cookie.png
rename to pages/public/img/drivers/baidu/yike_cookie.png
diff --git a/public/img/drivers/chaoxing/chaoxing_bbsid.png b/pages/public/img/drivers/chaoxing/chaoxing_bbsid.png
similarity index 100%
rename from public/img/drivers/chaoxing/chaoxing_bbsid.png
rename to pages/public/img/drivers/chaoxing/chaoxing_bbsid.png
diff --git a/public/img/drivers/chaoxing/chaoxing_folder_id.gif b/pages/public/img/drivers/chaoxing/chaoxing_folder_id.gif
similarity index 100%
rename from public/img/drivers/chaoxing/chaoxing_folder_id.gif
rename to pages/public/img/drivers/chaoxing/chaoxing_folder_id.gif
diff --git a/public/img/drivers/chunk/chunk_large_only_disabled.png b/pages/public/img/drivers/chunk/chunk_large_only_disabled.png
similarity index 100%
rename from public/img/drivers/chunk/chunk_large_only_disabled.png
rename to pages/public/img/drivers/chunk/chunk_large_only_disabled.png
diff --git a/public/img/drivers/chunk/chunk_large_only_enabled.png b/pages/public/img/drivers/chunk/chunk_large_only_enabled.png
similarity index 100%
rename from public/img/drivers/chunk/chunk_large_only_enabled.png
rename to pages/public/img/drivers/chunk/chunk_large_only_enabled.png
diff --git a/public/img/drivers/chunk/custom_ext_disabled.png b/pages/public/img/drivers/chunk/custom_ext_disabled.png
similarity index 100%
rename from public/img/drivers/chunk/custom_ext_disabled.png
rename to pages/public/img/drivers/chunk/custom_ext_disabled.png
diff --git a/public/img/drivers/chunk/custom_ext_enabled.png b/pages/public/img/drivers/chunk/custom_ext_enabled.png
similarity index 100%
rename from public/img/drivers/chunk/custom_ext_enabled.png
rename to pages/public/img/drivers/chunk/custom_ext_enabled.png
diff --git a/public/img/drivers/chunk/example.png b/pages/public/img/drivers/chunk/example.png
similarity index 100%
rename from public/img/drivers/chunk/example.png
rename to pages/public/img/drivers/chunk/example.png
diff --git a/public/img/drivers/cloudflare-imgbed/cloudflare-imgbed-1.png b/pages/public/img/drivers/cloudflare-imgbed/cloudflare-imgbed-1.png
similarity index 100%
rename from public/img/drivers/cloudflare-imgbed/cloudflare-imgbed-1.png
rename to pages/public/img/drivers/cloudflare-imgbed/cloudflare-imgbed-1.png
diff --git a/public/img/drivers/cloudreve/cloudreve_get_cookie.png b/pages/public/img/drivers/cloudreve/cloudreve_get_cookie.png
similarity index 100%
rename from public/img/drivers/cloudreve/cloudreve_get_cookie.png
rename to pages/public/img/drivers/cloudreve/cloudreve_get_cookie.png
diff --git a/public/img/drivers/cloudreve_v4/cloudreve_v4_token_local_storage.png b/pages/public/img/drivers/cloudreve_v4/cloudreve_v4_token_local_storage.png
similarity index 100%
rename from public/img/drivers/cloudreve_v4/cloudreve_v4_token_local_storage.png
rename to pages/public/img/drivers/cloudreve_v4/cloudreve_v4_token_local_storage.png
diff --git a/public/img/drivers/cloudreve_v4/cloudreve_v4_token_resp.png b/pages/public/img/drivers/cloudreve_v4/cloudreve_v4_token_resp.png
similarity index 100%
rename from public/img/drivers/cloudreve_v4/cloudreve_v4_token_resp.png
rename to pages/public/img/drivers/cloudreve_v4/cloudreve_v4_token_resp.png
diff --git a/public/img/drivers/common/path_b.png b/pages/public/img/drivers/common/path_b.png
similarity index 100%
rename from public/img/drivers/common/path_b.png
rename to pages/public/img/drivers/common/path_b.png
diff --git a/public/img/drivers/common/path_h.png b/pages/public/img/drivers/common/path_h.png
similarity index 100%
rename from public/img/drivers/common/path_h.png
rename to pages/public/img/drivers/common/path_h.png
diff --git a/public/img/drivers/crypt/crypt-demo1.png b/pages/public/img/drivers/crypt/crypt-demo1.png
similarity index 100%
rename from public/img/drivers/crypt/crypt-demo1.png
rename to pages/public/img/drivers/crypt/crypt-demo1.png
diff --git a/public/img/drivers/crypt/crypt-demo2.png b/pages/public/img/drivers/crypt/crypt-demo2.png
similarity index 100%
rename from public/img/drivers/crypt/crypt-demo2.png
rename to pages/public/img/drivers/crypt/crypt-demo2.png
diff --git a/public/img/drivers/doubao/doubao-cookie.png b/pages/public/img/drivers/doubao/doubao-cookie.png
similarity index 100%
rename from public/img/drivers/doubao/doubao-cookie.png
rename to pages/public/img/drivers/doubao/doubao-cookie.png
diff --git a/public/img/drivers/doubao/doubao-root-folder-id.png b/pages/public/img/drivers/doubao/doubao-root-folder-id.png
similarity index 100%
rename from public/img/drivers/doubao/doubao-root-folder-id.png
rename to pages/public/img/drivers/doubao/doubao-root-folder-id.png
diff --git a/public/img/drivers/dropbox/1.png b/pages/public/img/drivers/dropbox/1.png
similarity index 100%
rename from public/img/drivers/dropbox/1.png
rename to pages/public/img/drivers/dropbox/1.png
diff --git a/public/img/drivers/dropbox/2.png b/pages/public/img/drivers/dropbox/2.png
similarity index 100%
rename from public/img/drivers/dropbox/2.png
rename to pages/public/img/drivers/dropbox/2.png
diff --git a/public/img/drivers/dropbox/3.png b/pages/public/img/drivers/dropbox/3.png
similarity index 100%
rename from public/img/drivers/dropbox/3.png
rename to pages/public/img/drivers/dropbox/3.png
diff --git a/public/img/drivers/dropbox/4.png b/pages/public/img/drivers/dropbox/4.png
similarity index 100%
rename from public/img/drivers/dropbox/4.png
rename to pages/public/img/drivers/dropbox/4.png
diff --git a/public/img/drivers/dropbox/5.png b/pages/public/img/drivers/dropbox/5.png
similarity index 100%
rename from public/img/drivers/dropbox/5.png
rename to pages/public/img/drivers/dropbox/5.png
diff --git a/public/img/drivers/dropbox/6.png b/pages/public/img/drivers/dropbox/6.png
similarity index 100%
rename from public/img/drivers/dropbox/6.png
rename to pages/public/img/drivers/dropbox/6.png
diff --git a/public/img/drivers/dropbox/7.png b/pages/public/img/drivers/dropbox/7.png
similarity index 100%
rename from public/img/drivers/dropbox/7.png
rename to pages/public/img/drivers/dropbox/7.png
diff --git a/public/img/drivers/dropbox/folder_id.png b/pages/public/img/drivers/dropbox/folder_id.png
similarity index 100%
rename from public/img/drivers/dropbox/folder_id.png
rename to pages/public/img/drivers/dropbox/folder_id.png
diff --git a/public/img/drivers/febbox/febox.png b/pages/public/img/drivers/febbox/febox.png
similarity index 100%
rename from public/img/drivers/febbox/febox.png
rename to pages/public/img/drivers/febbox/febox.png
diff --git a/public/img/drivers/feiji/feiji.png b/pages/public/img/drivers/feiji/feiji.png
similarity index 100%
rename from public/img/drivers/feiji/feiji.png
rename to pages/public/img/drivers/feiji/feiji.png
diff --git a/public/img/drivers/github/1.png b/pages/public/img/drivers/github/1.png
similarity index 100%
rename from public/img/drivers/github/1.png
rename to pages/public/img/drivers/github/1.png
diff --git a/public/img/drivers/github/2.png b/pages/public/img/drivers/github/2.png
similarity index 100%
rename from public/img/drivers/github/2.png
rename to pages/public/img/drivers/github/2.png
diff --git a/public/img/drivers/github/3.png b/pages/public/img/drivers/github/3.png
similarity index 100%
rename from public/img/drivers/github/3.png
rename to pages/public/img/drivers/github/3.png
diff --git a/public/img/drivers/google/google-00-d.png b/pages/public/img/drivers/google/google-00-d.png
similarity index 100%
rename from public/img/drivers/google/google-00-d.png
rename to pages/public/img/drivers/google/google-00-d.png
diff --git a/public/img/drivers/google/google-00-l.png b/pages/public/img/drivers/google/google-00-l.png
similarity index 100%
rename from public/img/drivers/google/google-00-l.png
rename to pages/public/img/drivers/google/google-00-l.png
diff --git a/public/img/drivers/google/google-01-01-d.png b/pages/public/img/drivers/google/google-01-01-d.png
similarity index 100%
rename from public/img/drivers/google/google-01-01-d.png
rename to pages/public/img/drivers/google/google-01-01-d.png
diff --git a/public/img/drivers/google/google-01-01-l.png b/pages/public/img/drivers/google/google-01-01-l.png
similarity index 100%
rename from public/img/drivers/google/google-01-01-l.png
rename to pages/public/img/drivers/google/google-01-01-l.png
diff --git a/public/img/drivers/google/google-01-02-d.png b/pages/public/img/drivers/google/google-01-02-d.png
similarity index 100%
rename from public/img/drivers/google/google-01-02-d.png
rename to pages/public/img/drivers/google/google-01-02-d.png
diff --git a/public/img/drivers/google/google-01-02-l.png b/pages/public/img/drivers/google/google-01-02-l.png
similarity index 100%
rename from public/img/drivers/google/google-01-02-l.png
rename to pages/public/img/drivers/google/google-01-02-l.png
diff --git a/public/img/drivers/google/google-02.png b/pages/public/img/drivers/google/google-02.png
similarity index 100%
rename from public/img/drivers/google/google-02.png
rename to pages/public/img/drivers/google/google-02.png
diff --git a/public/img/drivers/google/google-03.png b/pages/public/img/drivers/google/google-03.png
similarity index 100%
rename from public/img/drivers/google/google-03.png
rename to pages/public/img/drivers/google/google-03.png
diff --git a/public/img/drivers/google/google-04.png b/pages/public/img/drivers/google/google-04.png
similarity index 100%
rename from public/img/drivers/google/google-04.png
rename to pages/public/img/drivers/google/google-04.png
diff --git a/public/img/drivers/google/google-05-d.png b/pages/public/img/drivers/google/google-05-d.png
similarity index 100%
rename from public/img/drivers/google/google-05-d.png
rename to pages/public/img/drivers/google/google-05-d.png
diff --git a/public/img/drivers/google/google-05-l.png b/pages/public/img/drivers/google/google-05-l.png
similarity index 100%
rename from public/img/drivers/google/google-05-l.png
rename to pages/public/img/drivers/google/google-05-l.png
diff --git a/public/img/drivers/google/google-06-d.png b/pages/public/img/drivers/google/google-06-d.png
similarity index 100%
rename from public/img/drivers/google/google-06-d.png
rename to pages/public/img/drivers/google/google-06-d.png
diff --git a/public/img/drivers/google/google-06-l.png b/pages/public/img/drivers/google/google-06-l.png
similarity index 100%
rename from public/img/drivers/google/google-06-l.png
rename to pages/public/img/drivers/google/google-06-l.png
diff --git a/public/img/drivers/google/google-07-d.png b/pages/public/img/drivers/google/google-07-d.png
similarity index 100%
rename from public/img/drivers/google/google-07-d.png
rename to pages/public/img/drivers/google/google-07-d.png
diff --git a/public/img/drivers/google/google-07-l.png b/pages/public/img/drivers/google/google-07-l.png
similarity index 100%
rename from public/img/drivers/google/google-07-l.png
rename to pages/public/img/drivers/google/google-07-l.png
diff --git a/public/img/drivers/google/google-08-d.png b/pages/public/img/drivers/google/google-08-d.png
similarity index 100%
rename from public/img/drivers/google/google-08-d.png
rename to pages/public/img/drivers/google/google-08-d.png
diff --git a/public/img/drivers/google/google-08-l.png b/pages/public/img/drivers/google/google-08-l.png
similarity index 100%
rename from public/img/drivers/google/google-08-l.png
rename to pages/public/img/drivers/google/google-08-l.png
diff --git a/public/img/drivers/google/google-oauth-00.png b/pages/public/img/drivers/google/google-oauth-00.png
similarity index 100%
rename from public/img/drivers/google/google-oauth-00.png
rename to pages/public/img/drivers/google/google-oauth-00.png
diff --git a/public/img/drivers/google/google-oauth-01.png b/pages/public/img/drivers/google/google-oauth-01.png
similarity index 100%
rename from public/img/drivers/google/google-oauth-01.png
rename to pages/public/img/drivers/google/google-oauth-01.png
diff --git a/public/img/drivers/google/google-oauth-02.png b/pages/public/img/drivers/google/google-oauth-02.png
similarity index 100%
rename from public/img/drivers/google/google-oauth-02.png
rename to pages/public/img/drivers/google/google-oauth-02.png
diff --git a/public/img/drivers/google/google-oauth-03.png b/pages/public/img/drivers/google/google-oauth-03.png
similarity index 100%
rename from public/img/drivers/google/google-oauth-03.png
rename to pages/public/img/drivers/google/google-oauth-03.png
diff --git a/public/img/drivers/google/google-oauth-eng-00.png b/pages/public/img/drivers/google/google-oauth-eng-00.png
similarity index 100%
rename from public/img/drivers/google/google-oauth-eng-00.png
rename to pages/public/img/drivers/google/google-oauth-eng-00.png
diff --git a/public/img/drivers/google/google-oauth-eng-01.png b/pages/public/img/drivers/google/google-oauth-eng-01.png
similarity index 100%
rename from public/img/drivers/google/google-oauth-eng-01.png
rename to pages/public/img/drivers/google/google-oauth-eng-01.png
diff --git a/public/img/drivers/google/google-oauth-eng-02.png b/pages/public/img/drivers/google/google-oauth-eng-02.png
similarity index 100%
rename from public/img/drivers/google/google-oauth-eng-02.png
rename to pages/public/img/drivers/google/google-oauth-eng-02.png
diff --git a/public/img/drivers/google/google-oauth-eng-03.png b/pages/public/img/drivers/google/google-oauth-eng-03.png
similarity index 100%
rename from public/img/drivers/google/google-oauth-eng-03.png
rename to pages/public/img/drivers/google/google-oauth-eng-03.png
diff --git a/public/img/drivers/google/googledrive-dir.png b/pages/public/img/drivers/google/googledrive-dir.png
similarity index 100%
rename from public/img/drivers/google/googledrive-dir.png
rename to pages/public/img/drivers/google/googledrive-dir.png
diff --git a/public/img/drivers/halalcloud/halalcloud_add_authorization.png b/pages/public/img/drivers/halalcloud/halalcloud_add_authorization.png
similarity index 100%
rename from public/img/drivers/halalcloud/halalcloud_add_authorization.png
rename to pages/public/img/drivers/halalcloud/halalcloud_add_authorization.png
diff --git a/public/img/drivers/kodbox/kodbox_root_folder_path_en.jpg b/pages/public/img/drivers/kodbox/kodbox_root_folder_path_en.jpg
similarity index 100%
rename from public/img/drivers/kodbox/kodbox_root_folder_path_en.jpg
rename to pages/public/img/drivers/kodbox/kodbox_root_folder_path_en.jpg
diff --git a/public/img/drivers/kodbox/kodbox_root_folder_path_zh.jpg b/pages/public/img/drivers/kodbox/kodbox_root_folder_path_zh.jpg
similarity index 100%
rename from public/img/drivers/kodbox/kodbox_root_folder_path_zh.jpg
rename to pages/public/img/drivers/kodbox/kodbox_root_folder_path_zh.jpg
diff --git a/public/img/drivers/lanzou/ilanzou_folder.png b/pages/public/img/drivers/lanzou/ilanzou_folder.png
similarity index 100%
rename from public/img/drivers/lanzou/ilanzou_folder.png
rename to pages/public/img/drivers/lanzou/ilanzou_folder.png
diff --git a/public/img/drivers/lanzou/lanzou1.png b/pages/public/img/drivers/lanzou/lanzou1.png
similarity index 100%
rename from public/img/drivers/lanzou/lanzou1.png
rename to pages/public/img/drivers/lanzou/lanzou1.png
diff --git a/public/img/drivers/lanzou/lanzou2.gif b/pages/public/img/drivers/lanzou/lanzou2.gif
similarity index 100%
rename from public/img/drivers/lanzou/lanzou2.gif
rename to pages/public/img/drivers/lanzou/lanzou2.gif
diff --git a/public/img/drivers/lanzou/lanzou3.png b/pages/public/img/drivers/lanzou/lanzou3.png
similarity index 100%
rename from public/img/drivers/lanzou/lanzou3.png
rename to pages/public/img/drivers/lanzou/lanzou3.png
diff --git a/public/img/drivers/lanzou/lanzou_add.png b/pages/public/img/drivers/lanzou/lanzou_add.png
similarity index 100%
rename from public/img/drivers/lanzou/lanzou_add.png
rename to pages/public/img/drivers/lanzou/lanzou_add.png
diff --git a/public/img/drivers/lenovonasshare/lenovonasshare_fileid.png b/pages/public/img/drivers/lenovonasshare/lenovonasshare_fileid.png
similarity index 100%
rename from public/img/drivers/lenovonasshare/lenovonasshare_fileid.png
rename to pages/public/img/drivers/lenovonasshare/lenovonasshare_fileid.png
diff --git a/public/img/drivers/mediafire/mediafire-cookie.png b/pages/public/img/drivers/mediafire/mediafire-cookie.png
similarity index 100%
rename from public/img/drivers/mediafire/mediafire-cookie.png
rename to pages/public/img/drivers/mediafire/mediafire-cookie.png
diff --git a/public/img/drivers/mediafire/mediafire-sessiontoken.png b/pages/public/img/drivers/mediafire/mediafire-sessiontoken.png
similarity index 100%
rename from public/img/drivers/mediafire/mediafire-sessiontoken.png
rename to pages/public/img/drivers/mediafire/mediafire-sessiontoken.png
diff --git a/public/img/drivers/mediatrack-projectid.png b/pages/public/img/drivers/mediatrack-projectid.png
similarity index 100%
rename from public/img/drivers/mediatrack-projectid.png
rename to pages/public/img/drivers/mediatrack-projectid.png
diff --git a/public/img/drivers/mediatrack-rootid.png b/pages/public/img/drivers/mediatrack-rootid.png
similarity index 100%
rename from public/img/drivers/mediatrack-rootid.png
rename to pages/public/img/drivers/mediatrack-rootid.png
diff --git a/public/img/drivers/mediatrack-token.png b/pages/public/img/drivers/mediatrack-token.png
similarity index 100%
rename from public/img/drivers/mediatrack-token.png
rename to pages/public/img/drivers/mediatrack-token.png
diff --git a/public/img/drivers/mega/mega_2fa.png b/pages/public/img/drivers/mega/mega_2fa.png
similarity index 100%
rename from public/img/drivers/mega/mega_2fa.png
rename to pages/public/img/drivers/mega/mega_2fa.png
diff --git a/public/img/drivers/mega/mega_2fa_code.png b/pages/public/img/drivers/mega/mega_2fa_code.png
similarity index 100%
rename from public/img/drivers/mega/mega_2fa_code.png
rename to pages/public/img/drivers/mega/mega_2fa_code.png
diff --git a/public/img/drivers/mega/mega_add.png b/pages/public/img/drivers/mega/mega_add.png
similarity index 100%
rename from public/img/drivers/mega/mega_add.png
rename to pages/public/img/drivers/mega/mega_add.png
diff --git a/public/img/drivers/mopan/add-mopan.png b/pages/public/img/drivers/mopan/add-mopan.png
similarity index 100%
rename from public/img/drivers/mopan/add-mopan.png
rename to pages/public/img/drivers/mopan/add-mopan.png
diff --git a/public/img/drivers/offline_download_error.png b/pages/public/img/drivers/offline_download_error.png
similarity index 100%
rename from public/img/drivers/offline_download_error.png
rename to pages/public/img/drivers/offline_download_error.png
diff --git a/public/img/drivers/onedrive_app/od_app_ok.png b/pages/public/img/drivers/onedrive_app/od_app_ok.png
similarity index 100%
rename from public/img/drivers/onedrive_app/od_app_ok.png
rename to pages/public/img/drivers/onedrive_app/od_app_ok.png
diff --git a/public/img/drivers/onedrive_app/od_share_add.png b/pages/public/img/drivers/onedrive_app/od_share_add.png
similarity index 100%
rename from public/img/drivers/onedrive_app/od_share_add.png
rename to pages/public/img/drivers/onedrive_app/od_share_add.png
diff --git a/public/img/drivers/onedrive_app/onedrive_app0.png b/pages/public/img/drivers/onedrive_app/onedrive_app0.png
similarity index 100%
rename from public/img/drivers/onedrive_app/onedrive_app0.png
rename to pages/public/img/drivers/onedrive_app/onedrive_app0.png
diff --git a/public/img/drivers/onedrive_app/onedrive_app1.png b/pages/public/img/drivers/onedrive_app/onedrive_app1.png
similarity index 100%
rename from public/img/drivers/onedrive_app/onedrive_app1.png
rename to pages/public/img/drivers/onedrive_app/onedrive_app1.png
diff --git a/public/img/drivers/onedrive_app/onedrive_app3.png b/pages/public/img/drivers/onedrive_app/onedrive_app3.png
similarity index 100%
rename from public/img/drivers/onedrive_app/onedrive_app3.png
rename to pages/public/img/drivers/onedrive_app/onedrive_app3.png
diff --git a/public/img/drivers/onedrive_app/onedrive_app4.png b/pages/public/img/drivers/onedrive_app/onedrive_app4.png
similarity index 100%
rename from public/img/drivers/onedrive_app/onedrive_app4.png
rename to pages/public/img/drivers/onedrive_app/onedrive_app4.png
diff --git a/public/img/drivers/onedrive_app/onedrive_app5.png b/pages/public/img/drivers/onedrive_app/onedrive_app5.png
similarity index 100%
rename from public/img/drivers/onedrive_app/onedrive_app5.png
rename to pages/public/img/drivers/onedrive_app/onedrive_app5.png
diff --git a/public/img/drivers/onedrive_app/onedrive_app6.png b/pages/public/img/drivers/onedrive_app/onedrive_app6.png
similarity index 100%
rename from public/img/drivers/onedrive_app/onedrive_app6.png
rename to pages/public/img/drivers/onedrive_app/onedrive_app6.png
diff --git a/public/img/drivers/onedrive_app/onedrive_app7.png b/pages/public/img/drivers/onedrive_app/onedrive_app7.png
similarity index 100%
rename from public/img/drivers/onedrive_app/onedrive_app7.png
rename to pages/public/img/drivers/onedrive_app/onedrive_app7.png
diff --git a/public/img/drivers/onedrive_app/onedrive_app_Denmo.png b/pages/public/img/drivers/onedrive_app/onedrive_app_Denmo.png
similarity index 100%
rename from public/img/drivers/onedrive_app/onedrive_app_Denmo.png
rename to pages/public/img/drivers/onedrive_app/onedrive_app_Denmo.png
diff --git a/public/img/drivers/onedrive_app/onedrive_app_user.png b/pages/public/img/drivers/onedrive_app/onedrive_app_user.png
similarity index 100%
rename from public/img/drivers/onedrive_app/onedrive_app_user.png
rename to pages/public/img/drivers/onedrive_app/onedrive_app_user.png
diff --git a/public/img/drivers/pikpak.png b/pages/public/img/drivers/pikpak.png
similarity index 100%
rename from public/img/drivers/pikpak.png
rename to pages/public/img/drivers/pikpak.png
diff --git a/public/img/drivers/pikpak/pikpak-error-1.png b/pages/public/img/drivers/pikpak/pikpak-error-1.png
similarity index 100%
rename from public/img/drivers/pikpak/pikpak-error-1.png
rename to pages/public/img/drivers/pikpak/pikpak-error-1.png
diff --git a/public/img/drivers/pikpak/pikpak-error-2.png b/pages/public/img/drivers/pikpak/pikpak-error-2.png
similarity index 100%
rename from public/img/drivers/pikpak/pikpak-error-2.png
rename to pages/public/img/drivers/pikpak/pikpak-error-2.png
diff --git a/public/img/drivers/pikpak/pikpak-share-rootfolder.png b/pages/public/img/drivers/pikpak/pikpak-share-rootfolder.png
similarity index 100%
rename from public/img/drivers/pikpak/pikpak-share-rootfolder.png
rename to pages/public/img/drivers/pikpak/pikpak-share-rootfolder.png
diff --git a/public/img/drivers/pikpak/pikpak-share.png b/pages/public/img/drivers/pikpak/pikpak-share.png
similarity index 100%
rename from public/img/drivers/pikpak/pikpak-share.png
rename to pages/public/img/drivers/pikpak/pikpak-share.png
diff --git a/public/img/drivers/pikpak/pikpak-token-1.png b/pages/public/img/drivers/pikpak/pikpak-token-1.png
similarity index 100%
rename from public/img/drivers/pikpak/pikpak-token-1.png
rename to pages/public/img/drivers/pikpak/pikpak-token-1.png
diff --git a/public/img/drivers/pikpak/pikpak-token-2.png b/pages/public/img/drivers/pikpak/pikpak-token-2.png
similarity index 100%
rename from public/img/drivers/pikpak/pikpak-token-2.png
rename to pages/public/img/drivers/pikpak/pikpak-token-2.png
diff --git a/public/img/drivers/quark-rootid.png b/pages/public/img/drivers/quark-rootid.png
similarity index 100%
rename from public/img/drivers/quark-rootid.png
rename to pages/public/img/drivers/quark-rootid.png
diff --git a/public/img/drivers/quark.png b/pages/public/img/drivers/quark.png
similarity index 100%
rename from public/img/drivers/quark.png
rename to pages/public/img/drivers/quark.png
diff --git a/public/img/drivers/quark/quark_cookie.png b/pages/public/img/drivers/quark/quark_cookie.png
similarity index 100%
rename from public/img/drivers/quark/quark_cookie.png
rename to pages/public/img/drivers/quark/quark_cookie.png
diff --git a/public/img/drivers/quark/quark_fileid.png b/pages/public/img/drivers/quark/quark_fileid.png
similarity index 100%
rename from public/img/drivers/quark/quark_fileid.png
rename to pages/public/img/drivers/quark/quark_fileid.png
diff --git a/public/img/drivers/ref_token.png b/pages/public/img/drivers/ref_token.png
similarity index 100%
rename from public/img/drivers/ref_token.png
rename to pages/public/img/drivers/ref_token.png
diff --git a/public/img/drivers/s3/139.png b/pages/public/img/drivers/s3/139.png
similarity index 100%
rename from public/img/drivers/s3/139.png
rename to pages/public/img/drivers/s3/139.png
diff --git a/public/img/drivers/s3/al.png b/pages/public/img/drivers/s3/al.png
similarity index 100%
rename from public/img/drivers/s3/al.png
rename to pages/public/img/drivers/s3/al.png
diff --git a/public/img/drivers/s3/aws.png b/pages/public/img/drivers/s3/aws.png
similarity index 100%
rename from public/img/drivers/s3/aws.png
rename to pages/public/img/drivers/s3/aws.png
diff --git a/public/img/drivers/s3/b2.png b/pages/public/img/drivers/s3/b2.png
similarity index 100%
rename from public/img/drivers/s3/b2.png
rename to pages/public/img/drivers/s3/b2.png
diff --git a/public/img/drivers/s3/bd.png b/pages/public/img/drivers/s3/bd.png
similarity index 100%
rename from public/img/drivers/s3/bd.png
rename to pages/public/img/drivers/s3/bd.png
diff --git a/public/img/drivers/s3/cfr2.png b/pages/public/img/drivers/s3/cfr2.png
similarity index 100%
rename from public/img/drivers/s3/cfr2.png
rename to pages/public/img/drivers/s3/cfr2.png
diff --git a/public/img/drivers/s3/doge.png b/pages/public/img/drivers/s3/doge.png
similarity index 100%
rename from public/img/drivers/s3/doge.png
rename to pages/public/img/drivers/s3/doge.png
diff --git a/public/img/drivers/s3/googleStorage1.png b/pages/public/img/drivers/s3/googleStorage1.png
similarity index 100%
rename from public/img/drivers/s3/googleStorage1.png
rename to pages/public/img/drivers/s3/googleStorage1.png
diff --git a/public/img/drivers/s3/googleStorage2.png b/pages/public/img/drivers/s3/googleStorage2.png
similarity index 100%
rename from public/img/drivers/s3/googleStorage2.png
rename to pages/public/img/drivers/s3/googleStorage2.png
diff --git a/public/img/drivers/s3/googleStorage3.png b/pages/public/img/drivers/s3/googleStorage3.png
similarity index 100%
rename from public/img/drivers/s3/googleStorage3.png
rename to pages/public/img/drivers/s3/googleStorage3.png
diff --git a/public/img/drivers/s3/googleStorage4.png b/pages/public/img/drivers/s3/googleStorage4.png
similarity index 100%
rename from public/img/drivers/s3/googleStorage4.png
rename to pages/public/img/drivers/s3/googleStorage4.png
diff --git a/public/img/drivers/s3/hw.png b/pages/public/img/drivers/s3/hw.png
similarity index 100%
rename from public/img/drivers/s3/hw.png
rename to pages/public/img/drivers/s3/hw.png
diff --git a/public/img/drivers/s3/jd.png b/pages/public/img/drivers/s3/jd.png
similarity index 100%
rename from public/img/drivers/s3/jd.png
rename to pages/public/img/drivers/s3/jd.png
diff --git a/public/img/drivers/s3/mini-io.png b/pages/public/img/drivers/s3/mini-io.png
similarity index 100%
rename from public/img/drivers/s3/mini-io.png
rename to pages/public/img/drivers/s3/mini-io.png
diff --git a/public/img/drivers/s3/qn.png b/pages/public/img/drivers/s3/qn.png
similarity index 100%
rename from public/img/drivers/s3/qn.png
rename to pages/public/img/drivers/s3/qn.png
diff --git a/public/img/drivers/s3/sc.png b/pages/public/img/drivers/s3/sc.png
similarity index 100%
rename from public/img/drivers/s3/sc.png
rename to pages/public/img/drivers/s3/sc.png
diff --git a/public/img/drivers/s3/tx.png b/pages/public/img/drivers/s3/tx.png
similarity index 100%
rename from public/img/drivers/s3/tx.png
rename to pages/public/img/drivers/s3/tx.png
diff --git a/public/img/drivers/s3/ty.png b/pages/public/img/drivers/s3/ty.png
similarity index 100%
rename from public/img/drivers/s3/ty.png
rename to pages/public/img/drivers/s3/ty.png
diff --git a/public/img/drivers/s3/up.png b/pages/public/img/drivers/s3/up.png
similarity index 100%
rename from public/img/drivers/s3/up.png
rename to pages/public/img/drivers/s3/up.png
diff --git a/public/img/drivers/s3/v1andv2.png b/pages/public/img/drivers/s3/v1andv2.png
similarity index 100%
rename from public/img/drivers/s3/v1andv2.png
rename to pages/public/img/drivers/s3/v1andv2.png
diff --git a/public/img/drivers/s3/zijie_tos.png b/pages/public/img/drivers/s3/zijie_tos.png
similarity index 100%
rename from public/img/drivers/s3/zijie_tos.png
rename to pages/public/img/drivers/s3/zijie_tos.png
diff --git a/public/img/drivers/teambition-cookie.png b/pages/public/img/drivers/teambition-cookie.png
similarity index 100%
rename from public/img/drivers/teambition-cookie.png
rename to pages/public/img/drivers/teambition-cookie.png
diff --git a/public/img/drivers/teambition-id.png b/pages/public/img/drivers/teambition-id.png
similarity index 100%
rename from public/img/drivers/teambition-id.png
rename to pages/public/img/drivers/teambition-id.png
diff --git a/public/img/drivers/teldrive/fetch_teldrive_cookie.png b/pages/public/img/drivers/teldrive/fetch_teldrive_cookie.png
similarity index 100%
rename from public/img/drivers/teldrive/fetch_teldrive_cookie.png
rename to pages/public/img/drivers/teldrive/fetch_teldrive_cookie.png
diff --git a/public/img/drivers/terabox/terabox1.png b/pages/public/img/drivers/terabox/terabox1.png
similarity index 100%
rename from public/img/drivers/terabox/terabox1.png
rename to pages/public/img/drivers/terabox/terabox1.png
diff --git a/public/img/drivers/terabox/terabox2.png b/pages/public/img/drivers/terabox/terabox2.png
similarity index 100%
rename from public/img/drivers/terabox/terabox2.png
rename to pages/public/img/drivers/terabox/terabox2.png
diff --git a/public/img/drivers/terabox/terabox3.png b/pages/public/img/drivers/terabox/terabox3.png
similarity index 100%
rename from public/img/drivers/terabox/terabox3.png
rename to pages/public/img/drivers/terabox/terabox3.png
diff --git a/public/img/drivers/terabox/terabox_cookie.png b/pages/public/img/drivers/terabox/terabox_cookie.png
similarity index 100%
rename from public/img/drivers/terabox/terabox_cookie.png
rename to pages/public/img/drivers/terabox/terabox_cookie.png
diff --git a/public/img/drivers/terabox/terabox_f12.png b/pages/public/img/drivers/terabox/terabox_f12.png
similarity index 100%
rename from public/img/drivers/terabox/terabox_f12.png
rename to pages/public/img/drivers/terabox/terabox_f12.png
diff --git a/public/img/drivers/terabox/terabox_js_token.png b/pages/public/img/drivers/terabox/terabox_js_token.png
similarity index 100%
rename from public/img/drivers/terabox/terabox_js_token.png
rename to pages/public/img/drivers/terabox/terabox_js_token.png
diff --git a/public/img/drivers/tv_qrcode.png b/pages/public/img/drivers/tv_qrcode.png
similarity index 100%
rename from public/img/drivers/tv_qrcode.png
rename to pages/public/img/drivers/tv_qrcode.png
diff --git a/public/img/drivers/uc/uc_cookie.png b/pages/public/img/drivers/uc/uc_cookie.png
similarity index 100%
rename from public/img/drivers/uc/uc_cookie.png
rename to pages/public/img/drivers/uc/uc_cookie.png
diff --git a/public/img/drivers/uc/uc_fileid.png b/pages/public/img/drivers/uc/uc_fileid.png
similarity index 100%
rename from public/img/drivers/uc/uc_fileid.png
rename to pages/public/img/drivers/uc/uc_fileid.png
diff --git a/public/img/drivers/vtencent/vtencent_close.png b/pages/public/img/drivers/vtencent/vtencent_close.png
similarity index 100%
rename from public/img/drivers/vtencent/vtencent_close.png
rename to pages/public/img/drivers/vtencent/vtencent_close.png
diff --git a/public/img/drivers/vtencent/vtencent_cookie.png b/pages/public/img/drivers/vtencent/vtencent_cookie.png
similarity index 100%
rename from public/img/drivers/vtencent/vtencent_cookie.png
rename to pages/public/img/drivers/vtencent/vtencent_cookie.png
diff --git a/public/img/drivers/webdav/webdav_Security.png b/pages/public/img/drivers/webdav/webdav_Security.png
similarity index 100%
rename from public/img/drivers/webdav/webdav_Security.png
rename to pages/public/img/drivers/webdav/webdav_Security.png
diff --git a/public/img/drivers/weiyun/weiyun_cookie.png b/pages/public/img/drivers/weiyun/weiyun_cookie.png
similarity index 100%
rename from public/img/drivers/weiyun/weiyun_cookie.png
rename to pages/public/img/drivers/weiyun/weiyun_cookie.png
diff --git a/public/img/drivers/weiyun/weiyun_dir_id.png b/pages/public/img/drivers/weiyun/weiyun_dir_id.png
similarity index 100%
rename from public/img/drivers/weiyun/weiyun_dir_id.png
rename to pages/public/img/drivers/weiyun/weiyun_dir_id.png
diff --git a/public/img/drivers/weiyun/weiyun_fl_id.png b/pages/public/img/drivers/weiyun/weiyun_fl_id.png
similarity index 100%
rename from public/img/drivers/weiyun/weiyun_fl_id.png
rename to pages/public/img/drivers/weiyun/weiyun_fl_id.png
diff --git a/public/img/drivers/wopan/add-wopan.png b/pages/public/img/drivers/wopan/add-wopan.png
similarity index 100%
rename from public/img/drivers/wopan/add-wopan.png
rename to pages/public/img/drivers/wopan/add-wopan.png
diff --git a/public/img/drivers/wopan/wopan-req.png b/pages/public/img/drivers/wopan/wopan-req.png
similarity index 100%
rename from public/img/drivers/wopan/wopan-req.png
rename to pages/public/img/drivers/wopan/wopan-req.png
diff --git a/public/img/drivers/wopan/wopan-resp.png b/pages/public/img/drivers/wopan/wopan-resp.png
similarity index 100%
rename from public/img/drivers/wopan/wopan-resp.png
rename to pages/public/img/drivers/wopan/wopan-resp.png
diff --git a/public/img/drivers/wopan/wopan-session-storage.png b/pages/public/img/drivers/wopan/wopan-session-storage.png
similarity index 100%
rename from public/img/drivers/wopan/wopan-session-storage.png
rename to pages/public/img/drivers/wopan/wopan-session-storage.png
diff --git a/public/img/drivers/xunlei/SMS.png b/pages/public/img/drivers/xunlei/SMS.png
similarity index 100%
rename from public/img/drivers/xunlei/SMS.png
rename to pages/public/img/drivers/xunlei/SMS.png
diff --git a/public/img/drivers/xunlei/input.png b/pages/public/img/drivers/xunlei/input.png
similarity index 100%
rename from public/img/drivers/xunlei/input.png
rename to pages/public/img/drivers/xunlei/input.png
diff --git a/public/img/drivers/xunlei/output.png b/pages/public/img/drivers/xunlei/output.png
similarity index 100%
rename from public/img/drivers/xunlei/output.png
rename to pages/public/img/drivers/xunlei/output.png
diff --git a/public/img/drivers/xunlei/storage_error.png b/pages/public/img/drivers/xunlei/storage_error.png
similarity index 100%
rename from public/img/drivers/xunlei/storage_error.png
rename to pages/public/img/drivers/xunlei/storage_error.png
diff --git a/public/img/drivers/xunlei/x3.png b/pages/public/img/drivers/xunlei/x3.png
similarity index 100%
rename from public/img/drivers/xunlei/x3.png
rename to pages/public/img/drivers/xunlei/x3.png
diff --git a/public/img/drivers/xunlei/x4.png b/pages/public/img/drivers/xunlei/x4.png
similarity index 100%
rename from public/img/drivers/xunlei/x4.png
rename to pages/public/img/drivers/xunlei/x4.png
diff --git a/public/img/drivers/xunlei/x5.png b/pages/public/img/drivers/xunlei/x5.png
similarity index 100%
rename from public/img/drivers/xunlei/x5.png
rename to pages/public/img/drivers/xunlei/x5.png
diff --git a/public/img/drivers/xunlei/x6.png b/pages/public/img/drivers/xunlei/x6.png
similarity index 100%
rename from public/img/drivers/xunlei/x6.png
rename to pages/public/img/drivers/xunlei/x6.png
diff --git a/public/img/drivers/xunlei/x_br_add1.png b/pages/public/img/drivers/xunlei/x_br_add1.png
similarity index 100%
rename from public/img/drivers/xunlei/x_br_add1.png
rename to pages/public/img/drivers/xunlei/x_br_add1.png
diff --git a/public/img/drivers/xunlei/x_br_add2.png b/pages/public/img/drivers/xunlei/x_br_add2.png
similarity index 100%
rename from public/img/drivers/xunlei/x_br_add2.png
rename to pages/public/img/drivers/xunlei/x_br_add2.png
diff --git a/public/img/drivers/xunlei/x_br_error.png b/pages/public/img/drivers/xunlei/x_br_error.png
similarity index 100%
rename from public/img/drivers/xunlei/x_br_error.png
rename to pages/public/img/drivers/xunlei/x_br_error.png
diff --git a/public/img/drivers/xunlei/x_br_foled.png b/pages/public/img/drivers/xunlei/x_br_foled.png
similarity index 100%
rename from public/img/drivers/xunlei/x_br_foled.png
rename to pages/public/img/drivers/xunlei/x_br_foled.png
diff --git a/public/img/drivers/xunlei/xlx_name.jpg b/pages/public/img/drivers/xunlei/xlx_name.jpg
similarity index 100%
rename from public/img/drivers/xunlei/xlx_name.jpg
rename to pages/public/img/drivers/xunlei/xlx_name.jpg
diff --git a/public/img/drivers/xunlei/xlx_z1.jpg b/pages/public/img/drivers/xunlei/xlx_z1.jpg
similarity index 100%
rename from public/img/drivers/xunlei/xlx_z1.jpg
rename to pages/public/img/drivers/xunlei/xlx_z1.jpg
diff --git a/public/img/drivers/xunlei/xlx_z2.jpg b/pages/public/img/drivers/xunlei/xlx_z2.jpg
similarity index 100%
rename from public/img/drivers/xunlei/xlx_z2.jpg
rename to pages/public/img/drivers/xunlei/xlx_z2.jpg
diff --git a/public/img/faq/123error.png b/pages/public/img/faq/123error.png
similarity index 100%
rename from public/img/faq/123error.png
rename to pages/public/img/faq/123error.png
diff --git a/public/img/faq/add.jpeg b/pages/public/img/faq/add.jpeg
similarity index 100%
rename from public/img/faq/add.jpeg
rename to pages/public/img/faq/add.jpeg
diff --git a/public/img/faq/alist-admin.gif b/pages/public/img/faq/alist-admin.gif
similarity index 100%
rename from public/img/faq/alist-admin.gif
rename to pages/public/img/faq/alist-admin.gif
diff --git a/public/img/faq/alist-admin.png b/pages/public/img/faq/alist-admin.png
similarity index 100%
rename from public/img/faq/alist-admin.png
rename to pages/public/img/faq/alist-admin.png
diff --git a/public/img/faq/download.png b/pages/public/img/faq/download.png
similarity index 100%
rename from public/img/faq/download.png
rename to pages/public/img/faq/download.png
diff --git a/public/img/faq/error.png b/pages/public/img/faq/error.png
similarity index 100%
rename from public/img/faq/error.png
rename to pages/public/img/faq/error.png
diff --git a/public/img/guide/installation/clawcloud-01.png b/pages/public/img/guide/installation/clawcloud-01.png
similarity index 100%
rename from public/img/guide/installation/clawcloud-01.png
rename to pages/public/img/guide/installation/clawcloud-01.png
diff --git a/public/img/guide/installation/clawcloud-run.svg b/pages/public/img/guide/installation/clawcloud-run.svg
similarity index 100%
rename from public/img/guide/installation/clawcloud-run.svg
rename to pages/public/img/guide/installation/clawcloud-run.svg
diff --git a/public/img/guide/migrate/aliyun_remove1.png b/pages/public/img/guide/migrate/aliyun_remove1.png
similarity index 100%
rename from public/img/guide/migrate/aliyun_remove1.png
rename to pages/public/img/guide/migrate/aliyun_remove1.png
diff --git a/public/img/guide/migrate/aliyun_remove2.png b/pages/public/img/guide/migrate/aliyun_remove2.png
similarity index 100%
rename from public/img/guide/migrate/aliyun_remove2.png
rename to pages/public/img/guide/migrate/aliyun_remove2.png
diff --git a/public/img/guide/migrate/aliyun_remove3.png b/pages/public/img/guide/migrate/aliyun_remove3.png
similarity index 100%
rename from public/img/guide/migrate/aliyun_remove3.png
rename to pages/public/img/guide/migrate/aliyun_remove3.png
diff --git a/public/img/guide/migrate/aliyun_remove4.jpg b/pages/public/img/guide/migrate/aliyun_remove4.jpg
similarity index 100%
rename from public/img/guide/migrate/aliyun_remove4.jpg
rename to pages/public/img/guide/migrate/aliyun_remove4.jpg
diff --git a/public/img/guide/migrate/baidu_remove1.png b/pages/public/img/guide/migrate/baidu_remove1.png
similarity index 100%
rename from public/img/guide/migrate/baidu_remove1.png
rename to pages/public/img/guide/migrate/baidu_remove1.png
diff --git a/public/img/guide/migrate/baidu_remove2.png b/pages/public/img/guide/migrate/baidu_remove2.png
similarity index 100%
rename from public/img/guide/migrate/baidu_remove2.png
rename to pages/public/img/guide/migrate/baidu_remove2.png
diff --git a/public/img/guide/migrate/baidu_remove3.jpg b/pages/public/img/guide/migrate/baidu_remove3.jpg
similarity index 100%
rename from public/img/guide/migrate/baidu_remove3.jpg
rename to pages/public/img/guide/migrate/baidu_remove3.jpg
diff --git a/public/img/guide/migrate/google_remove1.png b/pages/public/img/guide/migrate/google_remove1.png
similarity index 100%
rename from public/img/guide/migrate/google_remove1.png
rename to pages/public/img/guide/migrate/google_remove1.png
diff --git a/public/img/guide/migrate/google_remove2.png b/pages/public/img/guide/migrate/google_remove2.png
similarity index 100%
rename from public/img/guide/migrate/google_remove2.png
rename to pages/public/img/guide/migrate/google_remove2.png
diff --git a/public/img/guide/migrate/google_remove3.png b/pages/public/img/guide/migrate/google_remove3.png
similarity index 100%
rename from public/img/guide/migrate/google_remove3.png
rename to pages/public/img/guide/migrate/google_remove3.png
diff --git a/public/img/guide/migrate/odb_remove1.jpg b/pages/public/img/guide/migrate/odb_remove1.jpg
similarity index 100%
rename from public/img/guide/migrate/odb_remove1.jpg
rename to pages/public/img/guide/migrate/odb_remove1.jpg
diff --git a/public/img/guide/migrate/odp_remove1.jpg b/pages/public/img/guide/migrate/odp_remove1.jpg
similarity index 100%
rename from public/img/guide/migrate/odp_remove1.jpg
rename to pages/public/img/guide/migrate/odp_remove1.jpg
diff --git a/public/img/guide/reverse_proxy/bt_delete_default_config_01.png b/pages/public/img/guide/reverse_proxy/bt_delete_default_config_01.png
similarity index 100%
rename from public/img/guide/reverse_proxy/bt_delete_default_config_01.png
rename to pages/public/img/guide/reverse_proxy/bt_delete_default_config_01.png
diff --git a/public/img/guide/reverse_proxy/bt_delete_default_config_02.png b/pages/public/img/guide/reverse_proxy/bt_delete_default_config_02.png
similarity index 100%
rename from public/img/guide/reverse_proxy/bt_delete_default_config_02.png
rename to pages/public/img/guide/reverse_proxy/bt_delete_default_config_02.png
diff --git a/public/img/guide/reverse_proxy/bt_new_website.png b/pages/public/img/guide/reverse_proxy/bt_new_website.png
similarity index 100%
rename from public/img/guide/reverse_proxy/bt_new_website.png
rename to pages/public/img/guide/reverse_proxy/bt_new_website.png
diff --git a/public/img/guide/reverse_proxy/bt_new_website_01.png b/pages/public/img/guide/reverse_proxy/bt_new_website_01.png
similarity index 100%
rename from public/img/guide/reverse_proxy/bt_new_website_01.png
rename to pages/public/img/guide/reverse_proxy/bt_new_website_01.png
diff --git a/public/img/guide/reverse_proxy/bt_reverse_proxy.png b/pages/public/img/guide/reverse_proxy/bt_reverse_proxy.png
similarity index 100%
rename from public/img/guide/reverse_proxy/bt_reverse_proxy.png
rename to pages/public/img/guide/reverse_proxy/bt_reverse_proxy.png
diff --git a/public/img/guide/webdav/es-android.png b/pages/public/img/guide/webdav/es-android.png
similarity index 100%
rename from public/img/guide/webdav/es-android.png
rename to pages/public/img/guide/webdav/es-android.png
diff --git a/public/img/guide/webdav/es-ios.png b/pages/public/img/guide/webdav/es-ios.png
similarity index 100%
rename from public/img/guide/webdav/es-ios.png
rename to pages/public/img/guide/webdav/es-ios.png
diff --git a/public/img/guide/webdav/fileball.png b/pages/public/img/guide/webdav/fileball.png
similarity index 100%
rename from public/img/guide/webdav/fileball.png
rename to pages/public/img/guide/webdav/fileball.png
diff --git a/public/img/guide/webdav/infuse.png b/pages/public/img/guide/webdav/infuse.png
similarity index 100%
rename from public/img/guide/webdav/infuse.png
rename to pages/public/img/guide/webdav/infuse.png
diff --git a/public/img/guide/webdav/nas.png b/pages/public/img/guide/webdav/nas.png
similarity index 100%
rename from public/img/guide/webdav/nas.png
rename to pages/public/img/guide/webdav/nas.png
diff --git a/public/img/guide/webdav/nplayer.png b/pages/public/img/guide/webdav/nplayer.png
similarity index 100%
rename from public/img/guide/webdav/nplayer.png
rename to pages/public/img/guide/webdav/nplayer.png
diff --git a/public/img/guide/webdav/potplayer.png b/pages/public/img/guide/webdav/potplayer.png
similarity index 100%
rename from public/img/guide/webdav/potplayer.png
rename to pages/public/img/guide/webdav/potplayer.png
diff --git a/public/img/guide/webdav/reex.png b/pages/public/img/guide/webdav/reex.png
similarity index 100%
rename from public/img/guide/webdav/reex.png
rename to pages/public/img/guide/webdav/reex.png
diff --git a/public/img/koyeb/db_host.png b/pages/public/img/koyeb/db_host.png
similarity index 100%
rename from public/img/koyeb/db_host.png
rename to pages/public/img/koyeb/db_host.png
diff --git a/public/img/koyeb/deployment.png b/pages/public/img/koyeb/deployment.png
similarity index 100%
rename from public/img/koyeb/deployment.png
rename to pages/public/img/koyeb/deployment.png
diff --git a/public/img/koyeb/environment.png b/pages/public/img/koyeb/environment.png
similarity index 100%
rename from public/img/koyeb/environment.png
rename to pages/public/img/koyeb/environment.png
diff --git a/public/img/koyeb/file.png b/pages/public/img/koyeb/file.png
similarity index 100%
rename from public/img/koyeb/file.png
rename to pages/public/img/koyeb/file.png
diff --git a/public/img/koyeb/success.png b/pages/public/img/koyeb/success.png
similarity index 100%
rename from public/img/koyeb/success.png
rename to pages/public/img/koyeb/success.png
diff --git a/public/img/truenas/InstallCustomAppApplicationName.png b/pages/public/img/truenas/InstallCustomAppApplicationName.png
similarity index 100%
rename from public/img/truenas/InstallCustomAppApplicationName.png
rename to pages/public/img/truenas/InstallCustomAppApplicationName.png
diff --git a/public/img/truenas/InstallCustomAppContainerEntrypoint.png b/pages/public/img/truenas/InstallCustomAppContainerEntrypoint.png
similarity index 100%
rename from public/img/truenas/InstallCustomAppContainerEntrypoint.png
rename to pages/public/img/truenas/InstallCustomAppContainerEntrypoint.png
diff --git a/public/img/truenas/InstallCustomAppImageConfiguration.png b/pages/public/img/truenas/InstallCustomAppImageConfiguration.png
similarity index 100%
rename from public/img/truenas/InstallCustomAppImageConfiguration.png
rename to pages/public/img/truenas/InstallCustomAppImageConfiguration.png
diff --git a/public/img/truenas/InstallCustomAppNetworkConfiguration.png b/pages/public/img/truenas/InstallCustomAppNetworkConfiguration.png
similarity index 100%
rename from public/img/truenas/InstallCustomAppNetworkConfiguration.png
rename to pages/public/img/truenas/InstallCustomAppNetworkConfiguration.png
diff --git a/public/img/truenas/InstallCustomAppPortalConfiguration.png b/pages/public/img/truenas/InstallCustomAppPortalConfiguration.png
similarity index 100%
rename from public/img/truenas/InstallCustomAppPortalConfiguration.png
rename to pages/public/img/truenas/InstallCustomAppPortalConfiguration.png
diff --git a/public/img/truenas/InstallCustomAppSecurityContextConfiguration.png b/pages/public/img/truenas/InstallCustomAppSecurityContextConfiguration.png
similarity index 100%
rename from public/img/truenas/InstallCustomAppSecurityContextConfiguration.png
rename to pages/public/img/truenas/InstallCustomAppSecurityContextConfiguration.png
diff --git a/public/img/truenas/InstallCustomAppStorageConfiguration.png b/pages/public/img/truenas/InstallCustomAppStorageConfiguration.png
similarity index 100%
rename from public/img/truenas/InstallCustomAppStorageConfiguration.png
rename to pages/public/img/truenas/InstallCustomAppStorageConfiguration.png
diff --git a/public/img/truenas/InstallCustomResourcesConfiguration.png b/pages/public/img/truenas/InstallCustomResourcesConfiguration.png
similarity index 100%
rename from public/img/truenas/InstallCustomResourcesConfiguration.png
rename to pages/public/img/truenas/InstallCustomResourcesConfiguration.png
diff --git a/public/img/worker/create_app1.png b/pages/public/img/worker/create_app1.png
similarity index 100%
rename from public/img/worker/create_app1.png
rename to pages/public/img/worker/create_app1.png
diff --git a/public/img/worker/create_app2.png b/pages/public/img/worker/create_app2.png
similarity index 100%
rename from public/img/worker/create_app2.png
rename to pages/public/img/worker/create_app2.png
diff --git a/public/img/worker/create_app3.png b/pages/public/img/worker/create_app3.png
similarity index 100%
rename from public/img/worker/create_app3.png
rename to pages/public/img/worker/create_app3.png
diff --git a/public/img/worker/create_app4.png b/pages/public/img/worker/create_app4.png
similarity index 100%
rename from public/img/worker/create_app4.png
rename to pages/public/img/worker/create_app4.png
diff --git a/public/img/worker/create_app5.png b/pages/public/img/worker/create_app5.png
similarity index 100%
rename from public/img/worker/create_app5.png
rename to pages/public/img/worker/create_app5.png
diff --git a/public/img/worker/create_app6.png b/pages/public/img/worker/create_app6.png
similarity index 100%
rename from public/img/worker/create_app6.png
rename to pages/public/img/worker/create_app6.png
diff --git a/public/img/worker/edgeone_ui1.png b/pages/public/img/worker/edgeone_ui1.png
similarity index 100%
rename from public/img/worker/edgeone_ui1.png
rename to pages/public/img/worker/edgeone_ui1.png
diff --git a/public/img/worker/edgeone_ui2.png b/pages/public/img/worker/edgeone_ui2.png
similarity index 100%
rename from public/img/worker/edgeone_ui2.png
rename to pages/public/img/worker/edgeone_ui2.png
diff --git a/public/img/worker/edgeone_ui3.png b/pages/public/img/worker/edgeone_ui3.png
similarity index 100%
rename from public/img/worker/edgeone_ui3.png
rename to pages/public/img/worker/edgeone_ui3.png
diff --git a/assets/logo.svg b/pages/public/logo.svg
similarity index 100%
rename from assets/logo.svg
rename to pages/public/logo.svg
diff --git a/assets/logo.webp b/pages/public/logo.webp
similarity index 100%
rename from assets/logo.webp
rename to pages/public/logo.webp
diff --git a/pages/seeds/background.md b/pages/seeds/background.md
index 1d360058a..d4af69b4f 100644
--- a/pages/seeds/background.md
+++ b/pages/seeds/background.md
@@ -1,35 +1,18 @@
---
-title:
- en: Background
- zh-CN: 需求背景
categories:
- seeds
top: 990
---
-## 需求概述 { lang="zh-CN" }
+# 需求背景
-## Overview { lang="en" }
-
-::::: zh-CN
+## 需求概述
1. 用户上传文件到网盘、或在本地/网盘上，可对单个或多个文件生成种子，用于分享文件信息，以及文件丢失后重新上传。
2. 用户可分享种子，跨网盘、跨用户、跨设备进行离线秒传、分享文件、备份释放空间。
3. 通用 BT 客户端可通过服务器代理网盘驱动下载种子内文件；兼容 OSS 的客户端可秒传或经服务器代理下载。
- :::::
-
-::::: en
-
-1. Users can generate a seed for one or more files — on local disk or on a drive — to share file information, or to re-upload after the files are lost.
-2. Users can share seeds to perform offline rapid upload, file sharing, backup, and space release across drives, users, and devices.
-3. Generic BT clients can download the files inside a seed through a server proxy over the drive; OSS-compatible clients can rapid-upload or download via the server proxy.
- :::::
-
-## 术语表 { lang="zh-CN" }
-
-## Glossary { lang="en" }
-::::: zh-CN
+## 术语表
| 术语 | 说明 |
| ------------------------- | ---------------------------------------------------------------------------------- |
@@ -44,30 +27,7 @@ top: 990
| 中转（Relay / Transit） | 先同步保存到中间网盘，再服务器端复制到最终目标 |
| 渠道（Channel） | 种子在某个网盘驱动上的挂载位置（`driver` + `mount_path`） |
-:::::
-
-::::: en
-
-| Term | Meaning |
-| --------------- | ---------------------------------------------------------------------------------------------------- |
-| Transfer Seed | A portable file-metadata system built on three sidecar formats |
-| Sidecar | A companion file alongside the main file, e.g. `movie.mp4.torrent` |
-| Seed | An `openlist-sharing-seed` v1 document describing path, size, hashes, and sources for a set of files |
-| Hash Matrix | Specifies which hashes to compute per file (md5/sha1/sha256 × whole/pieces) |
-| Piece | A block produced by splitting a file at `piece_size`; each piece has its own hash |
-| Whole hash | A single hash computed over the entire file |
-| Piece hashes | An array of hashes, one per piece |
-| Rapid upload | Reusing known hashes so a drive completes instantly without re-sending content |
-| Relay / Transit | Save synchronously to an intermediate drive, then copy server-side to the final drive |
-| Channel | Where a seed is mounted on a drive (`driver` + `mount_path`) |
-
-:::::
-
-## 三种格式的定位 { lang="zh-CN" }
-
-## Format roles { lang="en" }
-
-::::: zh-CN
+## 三种格式的定位
| 格式 | 后缀 | 编码 | 信息完整度 | 主要用途 |
| --------------------- | ---------- | ----------- | ------------------------------------ | ------------------------------- |
@@ -76,35 +36,10 @@ top: 990
| CAS | `.cas` | Base64 JSON | 低，仅秒传所需哈希 | 天翼云 189pc 秒传 |
三者是同一份文件元数据的不同投影，`.oss` 是信息超集，`.torrent` 与 `.cas` 是其语义投影（详见[设计理念](/seeds/design)）。
-:::::
-
-::::: en
-
-| Format | Suffix | Encoding | Completeness | Primary use |
-| --------------------- | ---------- | ----------- | --------------------------------------------------------- | -------------------------------------------- |
-| OpenList Sharing Seed | `.oss` | JSON | Highest, losslessly carries all fields | OpenList-internal share / edit / recalculate |
-| BitTorrent | `.torrent` | bencode | Medium, standard fields + `x-openlist` lossless extension | Generic BT clients / offline tools |
-| CAS | `.cas` | Base64 JSON | Low, only rapid-upload hashes | 189pc rapid upload |
-
-The three are projections of the same file metadata: `.oss` is the superset, while `.torrent` and `.cas` are its semantic projections (see [Design principles](/seeds/design)).
-:::::
-## 典型应用场景 { lang="zh-CN" }
-
-## Typical scenarios { lang="en" }
-
-::::: zh-CN
+## 典型应用场景
1. **跨盘迁移**：用户要把阿里云盘的文件迁到天翼云盘。生成含 SHA1 + MD5 + 分片哈希的种子，目标盘命中哈希即可秒传，无需下载再上传。
2. **分享给他人**：分享 `.oss` 或 `.torrent` 给好友，好友在其自己的网盘上秒传/离线下载，无需占用分享者的出流量。
3. **备份与释放空间**：把文件生成种子后删除原文件，需要时用种子重新秒传回来。
4. **断点校验**：种子的逐片哈希可用于校验已下载文件是否完整，支持按片定位损坏位置。
- :::::
-
-::::: en
-
-1. **Cross-drive migration**: move files from Aliyundrive to 189pc. A seed carrying SHA1 + MD5 + piece hashes lets the destination hit the hash and rapid-upload without a full download-then-upload.
-2. **Sharing**: share a `.oss` or `.torrent` so a friend rapid-uploads or offline-downloads on their own drive without consuming the sharer's egress.
-3. **Backup and space release**: generate a seed, delete the original, and re-rapid-upload it later from the seed.
-4. **Integrity verification**: per-piece hashes verify whether a downloaded file is complete and locate damaged pieces.
- :::::
diff --git a/pages/seeds/design.md b/pages/seeds/design.md
index 07c5faf98..ceaeef1b8 100644
--- a/pages/seeds/design.md
+++ b/pages/seeds/design.md
@@ -1,37 +1,20 @@
---
-title:
- en: Design principles
- zh-CN: 设计理念
categories:
- seeds
top: 980
---
-## 设计目标 { lang="zh-CN" }
+# 设计理念
-## Goals { lang="en" }
-
-::::: zh-CN
+## 设计目标
1. **可移植**：三种侧车格式可相互转换，跨网盘、跨用户、跨设备分享文件信息。
2. **复用哈希避免重复下载**：依据各网盘提供的哈希，生成时直接复用或流式计算。
3. **兼容第三方**：`.torrent` 遵循 BT v1 规范，`.cas` 单文件五字段与参考项目字节级兼容。
4. **安全有界**：所有解析受字节数、文件数、深度、路径穿越限制，种子内不序列化凭据。
- :::::
-
-::::: en
-
-1. **Portable**: three convertible sidecar formats for sharing file information across drives, users, and devices.
-2. **Reuse hashes to avoid redundant downloads**: reuse drive-provided hashes or stream-hash files.
-3. **Third-party compatible**: `.torrent` follows BT v1, and the `.cas` single-file five fields are byte-compatible with the reference project.
-4. **Safe and bounded**: parsing is bounded by byte/file/depth/path-traversal limits, and seeds never serialize credentials.
- :::::
-## 三格式关系 { lang="zh-CN" }
+## 三格式关系
-## Format relationships { lang="en" }
-
-::::: zh-CN
三种格式是同一份文件元数据的不同投影，`.oss` 信息最全，`.torrent` 与 `.cas` 是它的语义投影：
- `.oss` ⊇ `.torrent`：`.oss` 含 BT 必要信息（SHA-1 完整 + 分片）时可转 `.torrent`；`.torrent` 无论如何都可转 `.oss`。
@@ -48,32 +31,7 @@ graph TD
CAS -.->|缺 SHA1 分片，不可直接转| TORRENT
```
-:::::
-
-::::: en
-The three formats are different projections of the same file metadata. `.oss` is the most complete; `.torrent` and `.cas` are its semantic projections:
-
-- `.oss` ⊇ `.torrent`: `.oss` converts to `.torrent` when it has the required BT info (SHA-1 whole + pieces); `.torrent` always converts to `.oss`.
-- `.oss` ⊇ `.cas`: `.oss` converts to `.cas` when it has whole + piece MD5; `.cas` always converts to `.oss`.
-- Conversion diagnostics report exactly what is missing.
-
-```mermaid
-graph TD
- OSS[.oss most complete] -->|has BT-required info| TORRENT[.torrent]
- TORRENT -->|always convertible| OSS
- OSS -->|has whole + piece MD5| CAS[.cas]
- CAS -->|always convertible| OSS
- TORRENT -.->|has x-cas extension| CAS
- CAS -.->|missing SHA1 pieces, not directly convertible| TORRENT
-```
-
-:::::
-
-## 种子设计结构 { lang="zh-CN" }
-
-## Seed design { lang="en" }
-
-::::: zh-CN
+## 种子设计结构
### `.oss` 文件结构
@@ -129,71 +87,8 @@ Base64 编码的 JSON，兼容参考项目的五字段单文件格式，并扩
- 单文件时使用顶层五字段（与参考项目字节级兼容）；多文件时使用 `files` 数组。
- `slice_md5s` / `slice_size` 为可选扩展，保存逐片 MD5 列表，供天翼云秒传复用。
- 三方 CAS 客户端使用标准 JSON 解析，忽略额外字段，向后兼容。
- :::::
-
-::::: en
-
-### `.oss` structure
-
-`.oss` is the most complete JSON container:
-
-| Field | Description |
-| --------------------------- | ----------------------------------------------------------------- |
-| `format` / `version` | fixed `openlist-sharing-seed` / `1` |
-| `name` | seed name (editable, auto-derived if empty) |
-| `comment` | overall comment |
-| `created_at` / `created_by` | creation time / creator |
-| `piece_size` | piece size (default 10 MiB) |
-| `trackers` | tracker list |
-| `channels` | channels (`driver` + optional `mount_path`), public metadata only |
-| `files` | file array |
-
-Each file (`files[]`) carries:
-
-| Field | Description |
-| ----------------------------------- | ----------------------------------------------- |
-| `path` / `size` / `modified` | path / size / mtime |
-| `comment` | per-file comment |
-| `hashes.md5` / `sha1` / `sha256` | whole-file hashes |
-| `hashes.pieces` | per-algorithm piece hashes |
-| `sources` | public direct (`/d/`) or share (`/sd/`) sources |
-| `cas_slice_md5` / `cas_create_time` | CAS aggregate slice MD5 / create time |
-| `missing_channels` | drives that failed rapid upload |
-
-### `.torrent` structure
-
-A standard BitTorrent v1 file whose info dict holds `piece length` and `pieces` (SHA-1), plus two extension keys:
-
-- `x-openlist`: the full OpenList seed (MD5/SHA256, comments, channels, shares, etc.).
-- `x-cas`: 189pc CAS info (`file_md5` / `slice_md5` / `slice_size`).
-
-### `.cas` structure
-A base64-encoded JSON, compatible with the reference five-field single-file payload and extended for multiple files:
-
-```json
-{
- "name": "example",
- "size": 12345,
- "md5": "d41d8cd98f00b204e9800998ecf8427e",
- "sliceMd5": "…",
- "create_time": "1720000000",
- "slice_md5s": ["…", "…"],
- "slice_size": 10485760,
- "files": [{ "name": "a.txt", "size": 100, "md5": "…", "sliceMd5": "…", "create_time": "…" }]
-}
-```
-
-- Single file uses the top-level five fields (byte-compatible with the reference project); multiple files use the `files` array.
-- `slice_md5s` / `slice_size` are optional extensions preserving the per-piece MD5 list for 189pc rapid upload.
-- Third-party CAS clients use standard JSON parsing and ignore extra fields, remaining backward compatible.
- :::::
-
-## 字段级规范与安全边界 { lang="zh-CN" }
-
-## Field spec and safety bounds { lang="en" }
-
-::::: zh-CN
+## 字段级规范与安全边界
所有入站种子（无论来源是 `.oss` / `.torrent` / `.cas` 还是任意 JSON）都会先经过**规范化（normalize）**，在解析阶段即施加以下硬性限制：
@@ -218,40 +113,8 @@ A base64-encoded JSON, compatible with the reference five-field single-file payl
- 缺少 `format` / `version` 时补齐为 `openlist-sharing-seed` / `1`。
- 缺少 `created_at` / `created_by` 时补当前时间 / `OpenList`。
- 重复文件路径直接报错。
- :::::
-
-::::: en
-
-Every inbound seed (regardless of whether it comes from `.oss` / `.torrent` / `.cas` or arbitrary JSON) first passes through **normalization**, which enforces these hard limits at parse time:
-
-| Constraint | Value |
-| ------------------------- | ------------------------------------------------------------------ |
-| `piece_size` valid range | 16 KiB ~ 64 MiB (default 10 MiB) |
-| File count | 1 ~ 100,000 |
-| Max per-file path length | 4096 bytes |
-| Max path depth | 64 levels |
-| Piece hash count | must equal `ceil(size / piece_size)` (0 for empty files) |
-| Max bencode nesting depth | 32 |
-| Max bencode item count | 100,000 |
-| Path safety | reject `\0`, backslash `\`, leading `/`, empty segments, `.`, `..` |
-| Name safety | reject empty, `.`, `..`, or names containing `/` or `\` |
-| `sources` URL | must be absolute with a scheme |
-| `channels.mount_path` | reject `?`, `#`, `\0` |
-
-Seeds **never serialize credentials** (e.g. `cookie`, `access_token`); `channels` keeps only public metadata like `driver` and `mount_path`. Normalization also applies these fixes:
-
-- Hashes are lowercased; invalid hashes error (md5 32, sha1 40, sha256 64 hex chars).
-- Missing `name` falls back to the first segment of `files[0].path`.
-- Missing `format` / `version` default to `openlist-sharing-seed` / `1`.
-- Missing `created_at` / `created_by` default to now / `OpenList`.
-- Duplicate file paths error.
- :::::
-
-## 哈希矩阵设计 { lang="zh-CN" }
-
-## Hash matrix design { lang="en" }
-::::: zh-CN
+## 哈希矩阵设计
哈希矩阵是一个 3×2 的布尔选择，指定为每个文件计算哪些哈希：
@@ -273,37 +136,8 @@ Seeds **never serialize credentials** (e.g. `cookie`, `access_token`); `channels
3. **复用驱动哈希**：生成向导会先调用 `capabilities` 预检，把驱动已在列表里提供的哈希默认勾选，从而避免重复下载计算。
矩阵决定生成时是否需要下载：只要矩阵要求分片哈希（`pieces`），网盘列表通常不提供分片哈希，就必须下载流式计算；整文件哈希缺一也需下载。
-:::::
-::::: en
-
-The hash matrix is a 3×2 boolean selection specifying which hashes to compute per file:
-
-```json
-{
- "md5": { "whole": true, "pieces": true },
- "sha1": { "whole": true, "pieces": true },
- "sha256": { "whole": true, "pieces": true }
-}
-```
-
-- **whole**: a single whole-file hash (`hashes.md5` / `sha1` / `sha256`).
-- **pieces**: per-piece hash arrays (`hashes.pieces.md5[]` / `sha1[]` / `sha256[]`).
-
-Normalization rules:
-
-1. **All-empty means all-on**: when all six flags are `false`, they are treated as all `true` ("compute as much as possible").
-2. **Format forcing**: selecting `.torrent` forces `sha1.whole = true` and `sha1.pieces = true`; selecting `.cas` forces `md5.whole = true` and `md5.pieces = true`. The UI disables these checkboxes with a "required by this format" hint.
-3. **Reuse drive hashes**: the generation wizard calls `capabilities` first and pre-selects the hashes the drive already exposes, avoiding redundant downloads.
-
-The matrix decides whether generation must download: piece hashes are generally not exposed by drive listings, so any `pieces` requirement forces a streaming download; a missing whole hash also forces a download.
-:::::
-
-## 编解码与转换细节 { lang="zh-CN" }
-
-## Encoding and conversion details { lang="en" }
-
-::::: zh-CN
+## 编解码与转换细节
### bencode（`.torrent` 的底层编码）
@@ -350,62 +184,8 @@ BT v1 中所有文件共享同一个分片序列，因此当 `files.length > 1`
### 格式自动探测
`parse` 接口按首字符自动识别格式：`{` → `.oss`（JSON）、`d` → `.torrent`（bencode 字典）、其余 → `.cas`。也可用显式 `format` 提示强制指定。
-:::::
-
-::::: en
-
-### bencode (the encoding underneath `.torrent`)
-
-`.torrent` uses bencode. Dictionary keys must be sorted by byte order. The encoder handles the four value types:
-
-- integer → `ie` (errors when out of safe-integer range)
-- byte string → `:`
-- list → `le`
-- dictionary → `de`
-
-The parser enforces depth ≤ 32, items ≤ 100,000, and rejects trailing data.
-
-### The `.torrent` info dictionary
-
-- Single file: `info` holds `name`, `piece length`, `pieces`, `length`, optional `md5sum`.
-- Multi-file: `info` holds `name`, `piece length`, `pieces`, `files` (each with `length`, `path`, optional `md5sum`).
-- `pieces` is the concatenation of all SHA-1 piece hashes in order (20 bytes each); parsing verifies the piece count equals `ceil(total_size / piece_size)`.
-- `info_hash` = SHA-1(bencode(info)), used for magnet links and BT identification.
-
-OpenList extension keys:
-- `x-openlist`: a lossless bencode-embedding of the full `.oss` seed (JSON values recursively mapped to bencode values), letting OpenList clients fully reconstruct the metadata.
-- `x-cas`: `{ cloud, file_md5, slice_md5, slice_md5s, slice_size }` for 189pc rapid upload; written only for a single file with MD5.
-- `announce` / `announce-list`: derived from `trackers` (first tracker becomes `announce`).
-- `creation date` / `comment` / `created by`: standard metadata.
-
-When `x-openlist` is present at parse time, its consistency with the info dict is validated (name, piece_size, file count, each file's path and size); any mismatch errors out to prevent forgery.
-
-### Multi-file `.torrent` boundary limit
-
-All files in a BT v1 torrent share one piece sequence, so when `files.length > 1`, every file except the last must have a size divisible by `piece_size`; otherwise a piece is split by a file boundary and cannot be legally divided. Conversion reports `a file boundary splits a piece`.
-
-### `.cas` `sliceMd5` rules
-
-- When the piece size equals 10 MiB (`DEFAULT_PIECE_SIZE`) and a per-piece MD5 list exists:
- - one piece → `sliceMd5 = that piece MD5`.
- - multiple pieces → `sliceMd5 = md5(per-piece MD5s uppercased and joined by newline)`.
-- When per-piece MD5 is absent:
- - file ≤ 10 MiB → use the whole-file MD5 as `sliceMd5`.
- - file > 10 MiB and no legacy `cas_slice_md5` → conversion errors (cannot derive safely).
-
-Encoding `.cas` emits base64-encoded JSON; decoding tries base64 first and falls back to plain JSON (for legacy files).
-
-### Format auto-detection
-
-The `parse` API detects the format by the first character: `{` → `.oss` (JSON), `d` → `.torrent` (bencode dict), otherwise → `.cas`. An explicit `format` hint can override this.
-:::::
-
-## 架构与实现 { lang="zh-CN" }
-
-## Architecture { lang="en" }
-
-::::: zh-CN
+## 架构与实现
种子能力由**两套等价实现**提供，分别对应两套后端：
@@ -432,42 +212,8 @@ graph LR
- **规范化层**：`normalizeSeed` / Go 侧等价函数，统一字段补全与安全校验。
- **转换层**：`.oss` ↔ `.torrent` ↔ `.cas` 的相互编码/解码，含缺失信息诊断。
- **能力预检**：`capabilities` 汇总每个文件「已提供的哈希 / 是否需要下载 / 是否可流式下载」，供前端与生成逻辑复用。
- :::::
-
-::::: en
-
-Seed capability is provided by two equivalent implementations, one per backend:
-
-| Backend | Language | Format library | API layer |
-| ----------------- | ---------- | ------------------------------------------------------------------------- | --------------------------- |
-| OpenList-Backends | Go | `pkg/torrent/` (bencode, hash writer, generate, parse, convert, diagnose) | `server/handles/torrent.go` |
-| OpenList-TSWorker | TypeScript | `internal/seed/` (`codec.ts`, `hash.ts`, `types.ts`) | `server/seed.ts` |
-
-Both share the same field spec and codec logic (bencode sorting, CAS `sliceMd5` derivation, hash-matrix normalization, consistency validation), so seeds produced by the Cloudflare Worker and Go versions interoperate.
-
-```mermaid
-graph LR
- UI[HopeUI frontend] -->|POST /fs/seed/*| GO[Go backend]
- UI -->|POST /fs/seed/*| TS[TS Worker backend]
- GO --> FMT[pkg/torrent format library]
- TS --> TSFMT[internal/seed codec]
- GO --> DRV[drivers: 189pc / PutURL / offline]
- TS --> TSDRV[drivers: rapid / session / stream]
-```
-
-Core components:
-
-- **`HashWriter` / `TorrentPieceHasher`**: streaming hashers that maintain whole-file hashes (md5/sha1/sha256) plus per-piece hashes in a single pass, avoiding a second read.
-- **Normalization layer**: `normalizeSeed` (and the Go equivalent) applies field defaults and safety validation.
-- **Conversion layer**: encode/decode between `.oss` ↔ `.torrent` ↔ `.cas`, with missing-information diagnostics.
-- **Capability preflight**: `capabilities` summarizes per file "hashes available / download needed / streamable", reused by the UI and generation logic.
- :::::
-
-## 数据模型 { lang="zh-CN" }
-
-## Data model { lang="en" }
-::::: zh-CN
+## 数据模型
种子系统在 Go 与 TS 两端共享同一套数据模型，字段命名保持一致，保证两种后端产出的种子可互操作。核心结构体如下：
@@ -539,78 +285,3 @@ Core components:
| `files` | `CASFile[]` | 多文件时的文件数组（可选扩展） |
> 单文件用顶层五字段（`name`/`size`/`md5`/`sliceMd5`/`create_time`），与参考项目字节级兼容；多文件用 `files` 数组；`slice_md5s`/`slice_size` 保存逐片 MD5，供天翼云秒传复用。
-> :::::
-
-::::: en
-
-Both the Go and TS backends share one data model with identical field names, ensuring seeds from either backend interoperate. The core structures are:
-
-### `Seed`
-
-| Field | Type | Description |
-| ------------ | ------------------- | ----------------------------------- |
-| `format` | `string` | fixed `openlist-sharing-seed` |
-| `version` | `number` | fixed `1` |
-| `name` | `string` | seed name |
-| `comment` | `string` | overall comment |
-| `created_at` | `string` (ISO 8601) | creation time |
-| `created_by` | `string` | creator |
-| `piece_size` | `number` | piece size in bytes, default 10 MiB |
-| `trackers` | `string[]` | tracker list |
-| `channels` | `SeedChannel[]` | channels that saved successfully |
-| `files` | `SeedFile[]` | file array |
-
-### `SeedFile`
-
-| Field | Type | Description |
-| ------------------ | -------------- | -------------------------------- |
-| `path` | `string` | relative path |
-| `size` | `number` | size in bytes |
-| `modified` | `string` | mtime (ISO 8601) |
-| `comment` | `string` | per-file comment |
-| `hashes` | `SeedHashes` | hash collection |
-| `sources` | `SeedSource[]` | public direct / share sources |
-| `cas_slice_md5` | `string` | CAS aggregate slice MD5 (legacy) |
-| `cas_create_time` | `string` | CAS creation time (legacy) |
-| `missing_channels` | `string[]` | drives that failed rapid upload |
-
-### `SeedHashes`
-
-| Field | Type | Description |
-| -------- | -------- | ---------------------------------------------- |
-| `md5` | `string` | whole-file MD5 |
-| `sha1` | `string` | whole-file SHA-1 |
-| `sha256` | `string` | whole-file SHA-256 |
-| `pieces` | `object` | `{ md5[], sha1[], sha256[] }` per-piece arrays |
-
-### `SeedSource`
-
-| Field | Type | Description |
-| ------------ | -------- | --------------------------------------------------- |
-| `type` | `string` | `openlist-direct` or `openlist-share` |
-| `url` | `string` | absolute URL, restricted to the configured site URL |
-| `expires_at` | `string` | expiry time (optional) |
-| `share_id` | `string` | share ID (for `openlist-share`) |
-
-### `SeedChannel`
-
-| Field | Type | Description |
-| ------------ | -------- | --------------------- |
-| `driver` | `string` | driver name |
-| `mount_path` | `string` | mount path (optional) |
-
-### `CASPayload` (`.cas` payload)
-
-| Field | Type | Description |
-| ------------- | ----------- | -------------------------------------------------- |
-| `name` | `string` | file name |
-| `size` | `number` | file size |
-| `md5` | `string` | whole MD5 |
-| `sliceMd5` | `string` | aggregate slice MD5 |
-| `create_time` | `string` | creation time |
-| `slice_md5s` | `string[]` | per-piece MD5 (optional extension) |
-| `slice_size` | `number` | piece size (optional extension, default 10 MiB) |
-| `files` | `CASFile[]` | per-file array for multi-file (optional extension) |
-
-> Single file uses the top-level five fields (`name`/`size`/`md5`/`sliceMd5`/`create_time`), byte-compatible with the reference project; multiple files use the `files` array; `slice_md5s`/`slice_size` preserve per-piece MD5 for 189pc rapid upload.
-> :::::
diff --git a/pages/seeds/faq.md b/pages/seeds/faq.md
index 13fb4ff22..d9789e534 100644
--- a/pages/seeds/faq.md
+++ b/pages/seeds/faq.md
@@ -1,39 +1,20 @@
---
-title:
- en: FAQ
- zh-CN: 常见问题
categories:
- seeds
top: 940
---
-## 注意事项 { lang="zh-CN" }
+# 常见问题
-## Notes { lang="en" }
-
-::::: zh-CN
+## 注意事项
- `.cas` 的逐片 MD5 与多文件结构依赖可选扩展字段，单文件五字段与参考项目字节级兼容。
- 中转秒传要求中间存储支持同步原生复用或 PutURL。
- 重算要求源文件已存在于服务端。
- 生成的 `.torrent` 是合法 BT 文件，但 OpenList 本身不作为 BT peer。
- 所有种子解析均受字节数、文件数、深度与路径穿越限制。
- :::::
-
-::::: en
-
-- `.cas` per-piece MD5 and multi-file support rely on optional extension fields; the single-file five fields remain byte-compatible with the reference project.
-- Relayed transfer requires an intermediate storage with synchronous native reuse or PutURL.
-- Recalculation requires the source file to already exist on the server.
-- The generated `.torrent` is a valid BT file, but OpenList itself is not a BT peer.
-- All seed parsing is bounded by byte, file-count, depth, and path-traversal limits.
- :::::
-
-## 常见问题 { lang="zh-CN" }
-## Common questions { lang="en" }
-
-::::: zh-CN
+## 常见问题
### 生成的 `.cas` 被标记为 Legacy CAS 是什么原因？
@@ -82,55 +63,3 @@ BT v1 中所有文件共享同一个分片序列。多文件时除最后一个
### 为什么异步种子生成任务在服务重启后会丢失？
超过 1 GiB 的生成请求会转为后台任务，但异步任务不持久化；服务重启后未完成的任务会丢失，需要重新发起生成。小文件（≤ 1 GiB）同步生成，不受影响。
-:::::
-
-::::: en
-
-### Why is my generated `.cas` flagged as Legacy CAS?
-
-A legacy CAS only carries the five fields `name`, `size`, `md5`, aggregate `sliceMd5`, and creation time, with no per-piece MD5 list, so conversion is lossy. Newer generation writes `slice_md5s` / `slice_size` to preserve per-piece MD5, and the preview no longer shows the Legacy CAS warning when piece hashes are present.
-
-### Why can't a seed with only MD5 convert to `.torrent`?
-
-`.torrent` follows the BT v1 spec and requires SHA-1 whole + piece hashes. MD5 alone cannot produce a valid `pieces` field; conversion reports the missing SHA-1 pieces explicitly.
-
-### Why does multi-file `.torrent` conversion report "a file boundary splits a piece"?
-
-All files in a BT v1 torrent share one piece sequence. In multi-file mode, every file except the last must have a size divisible by `piece_size`; otherwise a piece is cut by a file boundary and cannot be legally divided. Adjust the piece size or use a single file so sizes align.
-
-### Why does rapid upload report `unavailable`?
-
-When the destination drive cannot reuse the hashes in the current seed, the operation reports `unavailable` instead of silently degrading to a normal upload. Make sure the seed contains the hashes the target drive requires (see the [rapid upload matrix](/seeds/rapid-upload)).
-
-### Why can't relayed transfer use asynchronous offline download?
-
-Asynchronous offline download cannot guarantee the intermediate storage has fully landed before the server-side copy to the final drive. Relaying therefore requires the intermediate storage to support synchronous native reuse or PutURL.
-
-### Can a generated `.torrent` be downloaded by a generic BT client?
-
-The generated `.torrent` is a valid BT v1 file and can be handed to an offline tool via magnet. However, OpenList itself is not a BT peer; whether generic BT clients can download depends on the tracker/webseed deployment.
-
-### Why does recalculation require the source file on the server?
-
-Recalculation re-reads an existing server-side file to recompute hashes; it never downloads from an external source. Upload or save the file to the server first if it is not already there.
-
-### How do I enable automatic sidecar generation on upload?
-
-The upload API is controlled by headers: set `X-Seed-Sidecars` (e.g. `oss,torrent,cas`) to specify formats directly, or combine `X-Generate-Seed: on` with the storage-level `seed_policy` and the global `seed_auto_generate_policy`. The global policy defaults to `off`, so nothing is generated by default.
-
-### Why can't asynchronous upload (`as_task=true`) generate sidecars?
-
-Sidecar generation must read the full upload stream and hash it in one pass. An async task cannot guarantee the complete stream is available in the same process and written synchronously, so the upload API returns 400 for the "sidecars + async upload" combination.
-
-### What does an all-empty hash matrix mean?
-
-When all six flags (md5/sha1/sha256 × whole/pieces) are `false`, the system treats it as "compute as much as possible", equivalent to selecting everything. To produce a minimal seed, explicitly select only the hashes you need.
-
-### What is `x-openlist` inside a `.torrent`?
-
-`x-openlist` is OpenList's lossless extension key that bencode-embeds the full `.oss` seed into a standard torrent. OpenList clients use it to fully reconstruct MD5/SHA256, comments, channels, and shares; parsing also validates its consistency with the info dictionary to prevent forgery.
-
-### Why are background seed-generation tasks lost on restart?
-
-Requests over 1 GiB are queued as background tasks, but those tasks are not persisted; an unfinished task is lost when the service restarts and must be re-triggered. Small files (≤ 1 GiB) are generated synchronously and are unaffected.
-:::::
diff --git a/pages/seeds/generate.md b/pages/seeds/generate.md
index 5538cf960..1723c55f4 100644
--- a/pages/seeds/generate.md
+++ b/pages/seeds/generate.md
@@ -1,29 +1,17 @@
---
-title:
- en: Generating seeds
- zh-CN: 生成种子
categories:
- seeds
top: 970
---
-## 上传时生成 { lang="zh-CN" }
+# 生成种子
-## Generate on upload { lang="en" }
+## 上传时生成
-::::: zh-CN
上传文件时，可勾选生成 `.oss` / `.torrent` / `.cas` 侧车（默认全部关闭）。系统会在上传流式计算哈希时一并生成侧车，无需二次读取。
-:::::
-::::: en
-While uploading, you can enable `.oss` / `.torrent` / `.cas` sidecars (all off by default). The sidecars are produced alongside the streaming hash calculation without a second read.
-:::::
+## 右键生成
-## 右键生成 { lang="zh-CN" }
-
-## Generate from the context menu { lang="en" }
-
-::::: zh-CN
在文件列表右键（支持多选）选择「生成传输种子」，进入生成向导：
1. **种子名**：可编辑，缺省自动推导（单选用文件名、多选公共前缀或文件夹名）。
@@ -32,24 +20,8 @@ While uploading, you can enable `.oss` / `.torrent` / `.cas` sidecars (all off b
4. **分片大小**：默认 10 MiB，可自定义。
5. **文件列表**：展示每个文件的大小、驱动已提供哈希、是否需下载、生成方式（直接/下载），每文件可填注释、可单独勾选分享/直链。
6. **Tracker**：从系统配置的 tracker 列表中勾选。
- :::::
-
-::::: en
-Right-click one or more files and choose "Generate transfer seed" to open the wizard:
-
-1. **Seed name**: editable, auto-derived when empty (file name for single selection, common prefix or folder for multiple).
-2. **Formats**: enable `.oss` / `.torrent` / `.cas` (any combination).
-3. **Hash matrix**: choose MD5 / SHA-1 / SHA-256 whole and piece hashes, pre-selecting the hashes the drive already provides.
-4. **Piece size**: defaults to 10 MiB.
-5. **File list**: shows each file's size, drive-provided hashes, whether a download is needed, and the generation mode (direct/download); per-file comments and per-file share/direct toggles.
-6. **Trackers**: picked from the system-configured tracker list.
- :::::
-
-## 种子命名 { lang="zh-CN" }
-## Seed naming { lang="en" }
-
-::::: zh-CN
+## 种子命名
种子名可编辑，缺省时按以下优先级自动推导：
@@ -59,43 +31,14 @@ Right-click one or more files and choose "Generate transfer seed" to open the wi
4. **兜底**：`OpenList Seed`。
命名同样受安全检查约束（拒绝空名、`.`、`..`、含 `/` 或 `\` 的名称）。
-:::::
-
-::::: en
-
-The seed name is editable; when empty it is auto-derived in this priority:
-
-1. **Single file**: the file name with its extension removed.
-2. **Multiple files sharing a base name**: if all files share the same name after removing extensions (e.g. `a.mkv`, `a.srt`, `a.ass` in one folder), use that common name.
-3. **Otherwise**: the common parent directory name.
-4. **Fallback**: `OpenList Seed`.
-Naming is subject to the same safety checks (rejecting empty names, `.`, `..`, or names containing `/` or `\`).
-:::::
-
-## 生成方式 { lang="zh-CN" }
-
-## Generation modes { lang="en" }
-
-::::: zh-CN
+## 生成方式
- **直接生成**：驱动已提供全部所需哈希，无需下载。
- **下载后生成**：需下载文件边下载边计算，界面显示预计流量。
- 若驱动不支持服务器流式下载，会禁止生成并提示；超过 1 GiB 的请求会自动转为后台任务异步生成。
- :::::
-
-::::: en
-
-- **Direct**: the drive already provides all required hashes, no download needed.
-- **Download**: files are streamed and hashed on the fly, with estimated traffic shown.
-- If the drive cannot stream files, generation is blocked with a hint; requests over 1 GiB are queued as a background task.
- :::::
-## 生成接口 { lang="zh-CN" }
-
-## Generate API { lang="en" }
-
-::::: zh-CN
+## 生成接口
右键生成调用 `POST /fs/seed/generate`（兼容旧接口 `POST /fs/torrent/generate`），请求体字段：
@@ -114,34 +57,8 @@ Naming is subject to the same safety checks (rejecting empty names, `.`, `..`, o
| `output_path` | `string` | 生成侧车的保存目录 |
返回 `SeedGenerateResult`：同步完成时包含产物路径；`task` 或 `async` 字段非空表示已转入后台异步任务。
-:::::
-
-::::: en
-
-Right-click generation calls `POST /fs/seed/generate` (compatible with the legacy `POST /fs/torrent/generate`). Request body:
-| Field | Type | Description |
-| --------------- | ---------------------- | ---------------------------------------------------- |
-| `paths` | `string[]` | source file/directory paths |
-| `formats` | `SeedFormat[]` | target formats: `oss` / `torrent` / `cas` |
-| `hash_matrix` | `SeedHashMatrix` | hash matrix (see [Design principles](/seeds/design)) |
-| `piece_size` | `number` | piece size in bytes, default 10 MiB |
-| `name` | `string` | seed name (optional, auto-derived) |
-| `comment` | `string` | overall comment (optional) |
-| `file_comments` | `Record` | per-file comments (optional) |
-| `trackers` | `string[]` | tracker list (optional) |
-| `share_files` | `string[]` | file paths to record share links (`/sd/`) |
-| `direct_files` | `string[]` | file paths to record public direct links (`/d/`) |
-| `output_path` | `string` | directory to save the generated sidecars |
-
-Returns `SeedGenerateResult`: on synchronous completion it carries the produced paths; a non-empty `task` or `async` field means the request was queued as a background task.
-:::::
-
-## 上传侧车机制 { lang="zh-CN" }
-
-## Upload sidecar mechanics { lang="en" }
-
-::::: zh-CN
+## 上传侧车机制
上传接口（`POST /fs/put`）会在上传流中**边传边哈希**，完成后把侧车与主文件一并写入目标目录。是否生成由以下优先级判定：
@@ -165,57 +82,15 @@ Returns `SeedGenerateResult`: on synchronous completion it carries the produced
- 上传结束后校验 `HashWriter` 实际读到的字节数等于声明大小，不等则报错（保证侧车哈希与落盘文件一致）。
- 侧车按 `<文件名>.<格式>` 命名写入同一目录（如 `movie.mp4.torrent`、`movie.mp4.cas`、`movie.mp4.oss`）。
- 生成格式缺省时，从全局设置 `seed_format_policies` 解析出已启用的格式。
- :::::
-
-::::: en
-
-The upload API (`POST /fs/put`) hashes **while streaming** and then writes the sidecars alongside the main file. Whether to generate is decided in this priority order:
-
-1. Header `X-Seed-Sidecars`: explicit formats (e.g. `oss,torrent,cas`); non-empty enables generation.
-2. Header `X-Generate-Seed`: `on` / `true` / `1` enables, `off` disables, `inherit` or empty falls through.
-3. Storage-level `seed_policy`: the target storage's `on` / `off` / `inherit`.
-4. Global setting `seed_auto_generate_policy`: defaults to `off`.
-
-Other sidecar headers:
-
-| Header | Purpose |
-| -------------------- | ------------------------------------------------------------ |
-| `X-Seed-Format` | Equivalent to `X-Seed-Sidecars`, specifies formats |
-| `X-Seed-Piece-Size` | Piece size in bytes; forced to 10 MiB when `cas` is included |
-| `X-Seed-Hash-Matrix` | JSON hash matrix controlling which hashes are written |
-Constraints and details:
-
-- Upload sidecars require **synchronous upload**; an async upload (`as_task=true`) returns 400 (sidecars need a complete streaming hash, which cannot be guaranteed in a background task).
-- Hashing reuses the upload stream via `io.TeeReader`, so one read both uploads and hashes — no second read.
-- After upload, the byte count read by the `HashWriter` is verified against the declared size; a mismatch errors out (keeping sidecar hashes consistent with the landed file).
-- Sidecars are written as `.` in the same directory (e.g. `movie.mp4.torrent`, `movie.mp4.cas`, `movie.mp4.oss`).
-- When no format is given, enabled formats are resolved from the global `seed_format_policies`.
- :::::
-
-## 异步任务 { lang="zh-CN" }
-
-## Background tasks { lang="en" }
-
-::::: zh-CN
+## 异步任务
当生成请求的文件总大小超过 1 GiB 时，系统会将其转为一个后台任务异步执行，避免阻塞请求线程。任务完成后，产物写入指定的 `output_path`，用户可在任务中心查看进度与结果。
超过 1 GiB 阈值自动转后台；其余情况同步完成后直接返回产物路径。
-:::::
-
-::::: en
-
-When the total size of a generation request exceeds 1 GiB, it is queued as a background task so the request thread is not blocked. On completion the sidecars are written to `output_path`, and progress/result can be checked in the task center.
-
-Requests over the 1 GiB threshold go background automatically; everything else returns the produced paths synchronously.
-:::::
-
-## 预览种子 { lang="zh-CN" }
-## Previewing seeds { lang="en" }
+## 预览种子
-::::: zh-CN
打开 `.oss` / `.torrent` / `.cas` 文件会进入统一预览，展示：
- 文件列表与大小
@@ -224,15 +99,3 @@ Requests over the 1 GiB threshold go background automatically; everything else r
- Tracker、渠道（channels）、分享/直链（sources）
- 格式转换可行性（✓/✗，悬停或点击查看缺失原因）
- 可执行的操作（秒传、离线下载、中转、转换、编辑、重算、预览/删除单个文件）
- :::::
-
-::::: en
-Opening a `.oss` / `.torrent` / `.cas` file shows a unified preview with:
-
-- file list and sizes
-- per-file hashes (whole + pieces, copyable with a per-piece popup)
-- file comments, timestamps, multi-line overall comment
-- trackers, channels, and share/direct sources
-- conversion feasibility (✓/✗, hover or click for missing reasons)
-- available operations (rapid upload, offline download, transfer, convert, edit, recalculate, preview/remove a single file)
- :::::
diff --git a/pages/seeds/index.md b/pages/seeds/index.md
index d78811db6..e1e515ecf 100644
--- a/pages/seeds/index.md
+++ b/pages/seeds/index.md
@@ -1,17 +1,13 @@
---
-title:
- en: Transfer Seeds
- zh-CN: 传输种子
categories:
- seeds
top: 1000
---
-## 什么是传输种子 { lang="zh-CN" }
+# 传输种子
-## What are Transfer Seeds { lang="en" }
+## 什么是传输种子
-:::: zh-CN
传输种子是一套可移植的文件元数据系统，围绕三种侧车（sidecar）格式构建，用于跨网盘、跨用户、跨设备分享文件信息、离线秒传、备份释放空间。
- **`.oss`（openlist-sharing-seed v1）**：信息最完整的 JSON 格式，所有字段均可缺省。
@@ -19,23 +15,8 @@ top: 1000
- **`.cas`**：与参考项目 [OpenList-CAS](https://github.com/GitYuA/OpenList-CAS) 兼容的内容寻址载荷，用于天翼云秒传。
三者可以相互转换（在信息足够时），并支持生成、预览、秒传、离线下载、中转保存、编辑与重算。
-::::
-:::: en
-Transfer Seeds are a portable file-metadata system built on three sidecar formats for sharing file information, offline rapid-upload, backup, and space release across drives, users, and devices.
-
-- **`.oss`** (`openlist-sharing-seed` v1): the most complete JSON format; every field is optional.
-- **`.torrent`**: a standard BitTorrent v1 file with OpenList extensions.
-- **`.cas`**: a content-addressable payload compatible with the reference project [OpenList-CAS](https://github.com/GitYuA/OpenList-CAS), used for 189pc rapid upload.
-
-The three formats convert between each other (when enough information is present) and support generation, preview, rapid upload, offline download, relayed save, editing, and recalculation.
-::::
-
-## 章节导航 { lang="zh-CN" }
-
-## Sections { lang="en" }
-
-:::: zh-CN
+## 章节导航
- [需求背景](/seeds/background) — 为什么需要传输种子，以及现有能力边界
- [设计理念](/seeds/design) — 设计目标与三种格式的设计结构
@@ -43,14 +24,3 @@ The three formats convert between each other (when enough information is present
- [使用种子](/seeds/usage) — 秒传、离线下载、中转、转换、编辑、重算
- [秒传矩阵](/seeds/rapid-upload) — 各驱动提供的哈希与秒传所需哈希
- [常见问题](/seeds/faq) — 注意事项与常见疑问
- ::::
-
-:::: en
-
-- [Background](/seeds/background) — why transfer seeds exist and current capability boundaries
-- [Design principles](/seeds/design) — design goals and the structure of the three formats
-- [Generating seeds](/seeds/generate) — generate on upload / from the context menu / preview
-- [Using seeds](/seeds/usage) — rapid upload, offline download, relay, convert, edit, recalculate
-- [Rapid upload matrix](/seeds/rapid-upload) — hashes each drive exposes and requires
-- [FAQ](/seeds/faq) — notes and common questions
- ::::
diff --git a/pages/seeds/rapid-upload.md b/pages/seeds/rapid-upload.md
index f34906112..e92117580 100644
--- a/pages/seeds/rapid-upload.md
+++ b/pages/seeds/rapid-upload.md
@@ -1,73 +1,35 @@
---
-title:
- en: Rapid upload matrix
- zh-CN: 秒传矩阵
categories:
- seeds
top: 950
---
-:::::: zh-CN
-种子系统依赖网盘提供的哈希来避免重复下载。不同网盘「列表提供的哈希」与「秒传所需的哈希」各不相同。下面把这两个维度合并为一张二维矩阵：**行 = 源驱动列表提供的哈希，列 = 目标驱动秒传所需的哈希**，交叉格即「从源到目标能否秒传」。
-::::::
-
-:::::: en
-The seed system relies on drive-provided hashes to avoid redundant downloads. Different drives differ in the hashes they "provide in listing" and "require for rapid upload". The two dimensions are merged below into a single two-dimensional matrix: **rows = hashes provided by the source listing, columns = hashes required by the target for rapid upload**; each cell answers "can this source rapid-upload to this target".
-::::::
-
-## 图例 { lang="zh-CN" }
-
-## Legend { lang="en" }
-
-:::::: zh-CN
-| 符号 | 含义 |
-|---|---|
-| ✅ | 可直接秒传：源列表已提供目标所需的全部哈希，无需下载文件内容 |
-| 🔶 | 需补算哈希：源提供了部分所需哈希，但缺少分片哈希或其它算法，需下载文件补算后才能秒传 |
-| ❌ | 无法秒传：源缺少目标秒传所需的关键哈希 |
-| ➖ | 不适用：目标驱动本身不支持秒传（只能普通上传） |
-::::::
-
-:::::: en
-| Symbol | Meaning |
-|---|---|
-| ✅ | Direct rapid upload: the source listing already provides every hash the target needs, no content download |
-| 🔶 | Needs hashing: the source provides part of the required hashes but is missing piece hashes or another algorithm, so the file must be downloaded to compute the rest first |
-| ❌ | Cannot rapid upload: the source lacks the key hash the target requires |
-| ➖ | Not applicable: the target drive does not support rapid upload (normal upload only) |
-::::::
+# 秒传矩阵
-## 秒传矩阵 { lang="zh-CN" }
+种子系统依赖网盘提供的哈希来避免重复下载。不同网盘「列表提供的哈希」与「秒传所需的哈希」各不相同。下面把这两个维度合并为一张二维矩阵：**行 = 源驱动列表提供的哈希，列 = 目标驱动秒传所需的哈希**，交叉格即「从源到目标能否秒传」。
-## Rapid upload matrix { lang="en" }
+## 图例
-:::::: zh-CN
-| 源提供 \ 目标需要 | MD5 | MD5 + 分片 | SHA1 | MD5 + SHA1 | SHA1 或 MD5 | GCID | SHA256 | 无秒传 |
-|---|---|---|---|---|---|---|---|---|
-| **MD5** | ✅ | 🔶 | ❌ | 🔶 | ✅ | ❌ | ❌ | ➖ |
-| **SHA1** | ❌ | ❌ | ✅ | 🔶 | ✅ | ❌ | ❌ | ➖ |
-| **MD5 + SHA1** | ✅ | 🔶 | ✅ | ✅ | ✅ | ❌ | ❌ | ➖ |
-| **MD5 + SHA1 + SHA256** | ✅ | 🔶 | ✅ | ✅ | ✅ | ❌ | ✅ | ➖ |
-| **GCID**（分块 SHA1） | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ➖ |
-| **无** | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ➖ |
-::::::
+| 符号 | 含义 |
+| ---- | ------------------------------------------------------------------------------------ |
+| ✅ | 可直接秒传：源列表已提供目标所需的全部哈希，无需下载文件内容 |
+| 🔶 | 需补算哈希：源提供了部分所需哈希，但缺少分片哈希或其它算法，需下载文件补算后才能秒传 |
+| ❌ | 无法秒传：源缺少目标秒传所需的关键哈希 |
+| ➖ | 不适用：目标驱动本身不支持秒传（只能普通上传） |
-:::::: en
-| Source provides \ Target needs | MD5 | MD5 + pieces | SHA1 | MD5 + SHA1 | SHA1 or MD5 | GCID | SHA256 | no rapid upload |
-|---|---|---|---|---|---|---|---|---|
-| **MD5** | ✅ | 🔶 | ❌ | 🔶 | ✅ | ❌ | ❌ | ➖ |
-| **SHA1** | ❌ | ❌ | ✅ | 🔶 | ✅ | ❌ | ❌ | ➖ |
-| **MD5 + SHA1** | ✅ | 🔶 | ✅ | ✅ | ✅ | ❌ | ❌ | ➖ |
-| **MD5 + SHA1 + SHA256** | ✅ | 🔶 | ✅ | ✅ | ✅ | ❌ | ✅ | ➖ |
-| **GCID** (block SHA1) | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ➖ |
-| **none** | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ➖ |
-::::::
+## 秒传矩阵
-## 驱动哈希能力映射 { lang="zh-CN" }
+| 源提供 \ 目标需要 | MD5 | MD5 + 分片 | SHA1 | MD5 + SHA1 | SHA1 或 MD5 | GCID | SHA256 | 无秒传 |
+| ----------------------- | --- | ---------- | ---- | ---------- | ----------- | ---- | ------ | ------ |
+| **MD5** | ✅ | 🔶 | ❌ | 🔶 | ✅ | ❌ | ❌ | ➖ |
+| **SHA1** | ❌ | ❌ | ✅ | 🔶 | ✅ | ❌ | ❌ | ➖ |
+| **MD5 + SHA1** | ✅ | 🔶 | ✅ | ✅ | ✅ | ❌ | ❌ | ➖ |
+| **MD5 + SHA1 + SHA256** | ✅ | 🔶 | ✅ | ✅ | ✅ | ❌ | ✅ | ➖ |
+| **GCID**（分块 SHA1） | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ➖ |
+| **无** | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ➖ |
-## Drive hash capability mapping { lang="en" }
+## 驱动哈希能力映射
-:::::: zh-CN
下表把每个驱动映射到矩阵的行（列表提供）与列（秒传所需），据此即可在矩阵中定位任意「源 → 目标」组合。
| 驱动 | 列表提供哈希（源 / 行） | 秒传所需哈希（目标 / 列） |
@@ -93,86 +55,21 @@ The seed system relies on drive-provided hashes to avoid redundant downloads. Di
| Google Drive | MD5 + SHA1 + SHA256 | 无秒传（普通上传） |
| OneDrive | 无 | 无秒传（普通上传） |
-::::::
-
-:::::: en
-The table maps each drive to the matrix's rows (listing provides) and columns (rapid upload needs), so any "source → target" pair can be located in the matrix.
-
-| Drive | Hashes provided (source / row) | Rapid upload requires (target / column) |
-| ------------------ | -------------------------------- | --------------------------------------- |
-| 189pc | MD5 | MD5 + piece MD5 (`slice_md5`) |
-| 189 (legacy) | MD5 | MD5 + piece MD5 |
-| 189tv | MD5 | MD5 |
-| Aliyundrive | SHA1 | SHA1 (`pre_hash` + `content_hash`) |
-| Aliyundrive Open | SHA1 | SHA1 (`pre_hash`) |
-| Baidu | none (returned MD5 is untrusted) | MD5 (`content-md5` + `slice-md5`) |
-| PikPak | GCID (block SHA1) | GCID |
-| 115 | SHA1 | SHA1 |
-| 115 Open | SHA1 | SHA1 |
-| Thunder | GCID | GCID |
-| Thunder X | GCID | GCID |
-| Thunder Browser | GCID | GCID |
-| Quark Open | SHA1 | MD5 + SHA1 |
-| Quark UC | none | MD5 + SHA1 |
-| febbox | GCID | GCID |
-| 139 (China Mobile) | none (`digest` not exposed) | SHA256 (rapid upload) |
-| 123 | MD5 (`etag`) | MD5 |
-| 123 Open | SHA1 / MD5 | SHA1 (`sha1_reuse`) or MD5 |
-| Google Drive | MD5 + SHA1 + SHA256 | no rapid upload (normal upload) |
-| OneDrive | none | no rapid upload (normal upload) |
-
-::::::
-
-## 如何阅读矩阵 { lang="zh-CN" }
-
-## How to read the matrix { lang="en" }
-
-:::::: zh-CN
+## 如何阅读矩阵
- **阿里云盘 → 115**：源提供 SHA1，目标需 SHA1 → 矩阵 `SHA1 × SHA1` = ✅ 可直接秒传。
- **123 网盘 → 天翼云 189pc**：源提供 MD5，目标需 MD5 + 分片 → 矩阵 `MD5 × MD5+分片` = 🔶 需下载补算分片 MD5。
- **PikPak → 阿里云盘**：源提供 GCID，目标需 SHA1 → 矩阵 `GCID × SHA1` = ❌ 无法秒传。
- **任意源 → Google Drive / OneDrive**：目标无秒传 → 矩阵末列 = ➖，只能普通上传。
- ::::::
-
-:::::: en
-
-- **Aliyundrive → 115**: source provides SHA1, target needs SHA1 → matrix `SHA1 × SHA1` = ✅ direct rapid upload.
-- **123 → 189pc**: source provides MD5, target needs MD5 + pieces → matrix `MD5 × MD5+pieces` = 🔶 must download to compute piece MD5.
-- **PikPak → Aliyundrive**: source provides GCID, target needs SHA1 → matrix `GCID × SHA1` = ❌ cannot rapid upload.
-- **Any source → Google Drive / OneDrive**: target has no rapid upload → last column = ➖, normal upload only.
- ::::::
-
-## 与种子矩阵的关系 { lang="zh-CN" }
-## Relation to the hash matrix { lang="en" }
+## 与种子矩阵的关系
-:::::: zh-CN
生成种子时，内容矩阵会依据上述能力预检：若源驱动已提供目标所需全部哈希，则无需下载文件即可生成；否则会下载后边下载边计算。勾选 `.torrent` 会强制计算 SHA-1 完整 + 分片；勾选 `.cas` 会强制计算 MD5 完整 + 分片（固定 10 MiB），以满足天翼云秒传。
-::::::
-:::::: en
-The hash matrix is preflighted against these capabilities: if the source drive already provides every hash the target needs, no download is required; otherwise files are streamed and hashed on the fly. Selecting `.torrent` forces SHA-1 whole + pieces; selecting `.cas` forces MD5 whole + pieces (fixed 10 MiB) for 189pc rapid upload.
-::::::
-
-## 说明 { lang="zh-CN" }
-
-## Notes { lang="en" }
-
-:::::: zh-CN
+## 说明
- **GCID** 为分块 SHA1（40 位），用于 PikPak / 迅雷族 / febbox。
- 天翼云 189 与百度网盘的分片上传另需逐片 MD5（`slice_md5`），因此矩阵中对应列为 `MD5 + 分片`，源仅提供 MD5 时记为 🔶（需下载补算分片）。
- 阿里云盘族使用 `pre_hash`（文件头 1024 字节 SHA1）触发秒传，命中后补算完整 SHA1。
- 移动云盘 139 快传使用 SHA256；123 Open 支持 SHA1 复用（`sha1_reuse`）或 MD5 任选其一。
- **注意**：矩阵反映各驱动的原生秒传能力。当前种子「秒传保存」流程仅天翼云 189pc 的 CAS 秒传被完整接入，其余驱动的秒传在普通上传（`Put` / `PutRapid`）路径中生效。
- ::::::
-
-:::::: en
-
-- **GCID** is a block SHA1 (40 hex chars), used by PikPak / Thunder family / febbox.
-- 189 and Baidu chunked uploads additionally need per-piece MD5 (`slice_md5`), so their column is `MD5 + pieces`; a source providing only MD5 is marked 🔶 (must download to compute pieces).
-- The Aliyundrive family uses `pre_hash` (SHA1 of the first 1024 bytes) to trigger rapid upload, then computes the full SHA1 on hit.
-- 139 rapid upload uses SHA256; 123 Open supports either SHA1 reuse (`sha1_reuse`) or MD5.
-- **Note**: the matrix reflects each drive's native rapid-upload capability. Currently only 189pc CAS rapid upload is wired into the seed "rapid save" flow; other drives' rapid upload takes effect in the normal upload path (`Put` / `PutRapid`).
- ::::::
diff --git a/pages/seeds/usage.md b/pages/seeds/usage.md
index 12876ae21..9f15bfb15 100644
--- a/pages/seeds/usage.md
+++ b/pages/seeds/usage.md
@@ -1,17 +1,12 @@
---
-title:
- en: Using seeds
- zh-CN: 使用种子
categories:
- seeds
top: 960
---
-## 种子接口总览 { lang="zh-CN" }
+# 使用种子
-## Seed API overview { lang="en" }
-
-::::: zh-CN
+## 种子接口总览
种子能力暴露在 `POST /fs/seed/*` 下（旧 `/fs/torrent/*` 路由仍兼容）：
@@ -42,46 +37,8 @@ top: 960
| `recalc_files` | 待重算的文件（`path` + `source_path`） |
| `hash_matrix` | 重算用的内容矩阵 |
-:::::
-
-::::: en
-
-Seed capability is exposed under `POST /fs/seed/*` (the legacy `/fs/torrent/*` routes remain compatible):
-
-| API | Purpose |
-| ------------------ | ------------------------------------------------------------------------------------------------------------------ |
-| `parse` | Parse a seed (auto-detects `.oss` / `.torrent` / `.cas`) |
-| `upload_parse` | Upload a seed file and parse it |
-| `generate` | Generate a seed (see [Generating seeds](/seeds/generate)) |
-| `convert` | Convert between formats |
-| `diagnose` | Diagnose missing information for conversion |
-| `capabilities` | Preflight: per-file hashes available / download needed / streamable; or probe a destination storage's save methods |
-| `rapid_upload` | Rapid-upload save |
-| `offline_download` | Offline download / relayed transfer |
-| `update` | Edit / recalculate / remove files |
-| `update_channels` | Update channels (write `channels` / `missing_channels` on success/failure) |
-| `quick_save` | Quick save (alias of `rapid_upload` / `offline_download`) |
-
-All seed payloads are base64-encoded in the request body. Common `SeedOperationRequest` fields:
+## 秒传保存
-| Field | Description |
-| ---------------------- | ------------------------------------------------------------------------------- |
-| `seed_data` | base64 seed content (aliases `content` / `data` / `torrent_data` also accepted) |
-| `file_name` | original seed file name |
-| `path` / `target_path` | destination directory |
-| `selected_files` | indices into the seed's `files[]` |
-| `update_channel` | whether to update channels on success |
-| `remove_files` | file paths to remove |
-| `recalc_files` | files to recalculate (`path` + `source_path`) |
-| `hash_matrix` | hash matrix for recalculation |
-
-:::::
-
-## 秒传保存 { lang="zh-CN" }
-
-## Rapid upload { lang="en" }
-
-::::: zh-CN
勾选文件后选择目标网盘和路径，界面会展示目标驱动支持的秒传方式（如天翼云 CAS）以及当前是否可秒传。系统优先使用原生秒传，若目标驱动无法复用哈希，会明确提示 `unavailable`，不会静默降级。
秒传保存的逐文件判定（`capabilities` 返回的 `method`）：
@@ -95,119 +52,42 @@ All seed payloads are base64-encoded in the request body. Common `SeedOperationR
| `unavailable` | 目标驱动不支持任何可用方式 | 红 |
只有 `189pc_cas` 与 `put_url` 属于真正的「秒传」，无需下载文件内容。
-:::::
-
-::::: en
-Select files and choose a destination drive/path. The UI shows the destination drive's supported rapid-upload methods (e.g. 189pc CAS) and whether rapid upload is currently possible. Native rapid upload is preferred; if the drive cannot reuse hashes, the operation reports `unavailable` instead of silently degrading.
-Per-file save decision (`method` returned by `capabilities`):
+## 离线下载
-| Method | Meaning | Badge |
-| ------------------- | ------------------------------------------------------------------------------------------ | ------ |
-| `189pc_cas` | destination is 189pc and the seed has the MD5 + piece MD5 CAS needs, so rapid upload works | green |
-| `put_url` | the seed has a usable direct link, so PutURL pulls server-side | green |
-| `offline_download` | falls back to an offline download tool | blue |
-| `download_required` | hashes cannot be reused; the server streams and re-uploads | yellow |
-| `unavailable` | the destination drive supports no usable method | red |
-
-Only `189pc_cas` and `put_url` are true "rapid upload" (no content download).
-:::::
-
-## 离线下载 { lang="zh-CN" }
-
-## Offline download { lang="en" }
-
-::::: zh-CN
当种子内含可用直链/分享链接时，可将文件下载到目标网盘（PutURL / 离线工具 / 服务器流式）。BT 种子可通过 magnet 交给离线工具下载。
- `.torrent` 种子：整体转 magnet 后交给离线工具（`announce` → `tr`、`name` → `dn`、`length` → `xl`）。
- 其它种子：逐文件按 `sources`（`/d/` 直链或 `/sd/` 分享链接）离线下载。
- :::::
-
-::::: en
-When the seed contains usable direct/share sources, files can be downloaded into the destination drive (PutURL / offline tool / server streaming). Torrent seeds can be handed to an offline tool via magnet.
-- `.torrent`: converted to magnet as a whole (`announce` → `tr`, `name` → `dn`, `length` → `xl`) and handed to the offline tool.
-- Other seeds: downloaded per file from `sources` (`/d/` direct or `/sd/` share links).
- :::::
+## 中转秒传
-## 中转秒传 { lang="zh-CN" }
-
-## Relayed transfer { lang="en" }
-
-::::: zh-CN
先选择一个中间网盘（支持原生秒传或 PutURL），保存后再服务器端复制到最终目标网盘。异步离线下载不可用于中转。
请求中设置 `transit_path`（中间路径）并携带 `options: { mode: "transfer" }`，系统会先同步保存到中间存储，再复制到最终 `path`。
-:::::
-
-::::: en
-Save synchronously into an intermediate drive (native rapid upload or PutURL), then copy server-side to the final drive. Asynchronous offline downloads cannot be relayed.
-
-Set `transit_path` (the intermediate path) with `options: { mode: "transfer" }`; the system saves synchronously to the intermediate storage, then copies to the final `path`.
-:::::
-## 成功后更新渠道 { lang="zh-CN" }
+## 成功后更新渠道
-## Update channel on success { lang="en" }
-
-::::: zh-CN
勾选「成功后更新渠道」后，秒传成功会把当前网盘追加到种子的 `channels`，失败则记录到 `missing_channels`，方便下次选择可秒传的驱动。
- `channels`：`{ driver, mount_path }` 数组，记录种子已成功落盘的渠道。
- `missing_channels`：秒传失败的驱动名数组，避免下次重复尝试。
- :::::
-
-::::: en
-With "update channel on success" enabled, a successful save appends the current drive to the seed's `channels`, while a failure is recorded in `missing_channels`.
-
-- `channels`: an array of `{ driver, mount_path }` marking drives where the seed has landed successfully.
-- `missing_channels`: an array of drive names that failed rapid upload, avoiding repeat attempts.
- :::::
-## 格式转换 { lang="zh-CN" }
+## 格式转换
-## Convert { lang="en" }
-
-::::: zh-CN
可将种子转换为其他格式。转换前会展示缺失信息，例如缺少 SHA-1 分片时无法转为 `.torrent`。
- 目标格式由 `format` / `to_format` / `target_format` 任一字段指定。
- `diagnose` 接口可单独列出转换每个目标格式所需但缺失的哈希，前端据此显示 ✓/✗ 与缺失原因。
- 转换的可行性规则与生成一致：`.torrent` 需 SHA-1 完整 + 分片；`.cas` 需 MD5 完整 + 分片（或 ≤ 10 MiB 的整文件 MD5）。
- :::::
-
-::::: en
-Convert between formats; missing information (e.g. no SHA-1 pieces) is reported before conversion.
-- The target format is given by `format` / `to_format` / `target_format`.
-- `diagnose` lists the hashes required but missing for each target format, driving the ✓/✗ UI and its reasons.
-- Feasibility mirrors generation: `.torrent` needs SHA-1 whole + pieces; `.cas` needs MD5 whole + pieces (or a whole-file MD5 for files ≤ 10 MiB).
- :::::
-
-## 编辑与重算 { lang="zh-CN" }
-
-## Edit and recalculate { lang="en" }
-
-::::: zh-CN
+## 编辑与重算
- **编辑**：修改整体注释、tracker、渠道、每文件注释、分享直链；编辑时会校验分享链接是否仍有效（无效分享会明确提示其 ID）。
- **重算**：选择源目录后重算哈希（可勾选哈希矩阵）。源文件路径 = 源目录 + 种子内相对路径；重算只读服务端已有文件，不从外部下载。
- **删除文件**：通过 `remove_files` 从种子中移除指定文件。
- :::::
-
-::::: en
-
-- **Edit**: update overall comment, trackers, channels, per-file comments, and share sources; share validity is checked during editing (invalid shares report their IDs).
-- **Recalculate**: pick a source directory and recompute hashes (with a selectable hash matrix). The source path is the source directory plus the seed's relative path; recalculation only reads existing server-side files.
-- **Remove files**: drop specified files from the seed via `remove_files`.
- :::::
-## 文件操作侧车跟随 { lang="zh-CN" }
-
-## File-operation sidecar follow { lang="en" }
-
-::::: zh-CN
+## 文件操作侧车跟随
对主文件执行复制 / 移动 / 重命名 / 删除时，可勾选「跟随传输种子侧车」，让伴随的 `.oss` / `.torrent` / `.cas` / `.cas.torrent` 一起操作，保持主文件与侧车一致。
@@ -220,51 +100,17 @@ Convert between formats; missing information (e.g. no SHA-1 pieces) is reported
- 侧车路径规则：主文件路径 + `.oss` / `.torrent` / `.cas` / `.cas.torrent`。
- 仅对文件生效（目录不跟随）；仅处理实际存在的侧车，缺失时静默跳过。
- :::::
-
-::::: en
-
-When copying / moving / renaming / deleting a main file, enable "Follow transfer seed sidecars" to move the companion `.oss` / `.torrent` / `.cas` / `.cas.torrent` along, keeping the main file and sidecars consistent.
-
-| Operation | API | `follow_seed` behavior |
-| --------- | ----------------- | ---------------------------------------------- |
-| Copy | `POST /fs/copy` | synchronously copy sidecars to the destination |
-| Move | `POST /fs/move` | synchronously move sidecars to the destination |
-| Rename | `POST /fs/rename` | rename sidecars to `newName + original suffix` |
-| Remove | `POST /fs/remove` | synchronously delete sidecars |
-
-- Sidecar path rule: main path + `.oss` / `.torrent` / `.cas` / `.cas.torrent`.
-- Files only (directories are skipped); missing sidecars are silently ignored.
- :::::
-
-## 设置 { lang="zh-CN" }
-
-## Settings { lang="en" }
-
-::::: zh-CN
-| 设置 | 说明 | 默认 |
-|---|---|---|
-| `seed_site_url` | 生成分享/直链使用的公开站点 URL | 空 |
-| `seed_default_matrix` | 右键生成的默认内容矩阵 | md5/sha1/sha256 whole=true |
-| `seed_default_trackers` | 生成时可选勾选的 tracker 列表 | 空 |
-| `seed_default_format` | 默认种子格式 | oss |
-| `seed_format_policies` | 各格式自动生成开关 | 全关 |
-| `seed_auto_generate_policy` | 全局自动生成策略 | off |
-| `seed_single_direct_preview` | 单文件种子直接预览 | false |
-| `seed_cas_direct_access` | 打开 CAS 立即秒传+预览 | false |
-| 每存储 `seed_policy` | 存储级 `inherit`/`on`/`off` 覆盖 | inherit |
-:::::
-::::: en
-| Setting | Description | Default |
-|---|---|---|
-| `seed_site_url` | Public site URL for share/direct sources | empty |
-| `seed_default_matrix` | Default right-click hash matrix | md5/sha1/sha256 whole=true |
-| `seed_default_trackers` | Tracker list offered at generation | empty |
-| `seed_default_format` | Default seed format | oss |
-| `seed_format_policies` | Per-format auto-generation switches | all off |
-| `seed_auto_generate_policy` | Global auto-generation policy | off |
-| `seed_single_direct_preview` | Direct preview for single-file seeds | false |
-| `seed_cas_direct_access` | Rapid-upload and preview CAS on open | false |
-| per-storage `seed_policy` | Storage-level `inherit`/`on`/`off` override | inherit |
-:::::
+## 设置
+
+| 设置 | 说明 | 默认 |
+| ---------------------------- | -------------------------------- | -------------------------- |
+| `seed_site_url` | 生成分享/直链使用的公开站点 URL | 空 |
+| `seed_default_matrix` | 右键生成的默认内容矩阵 | md5/sha1/sha256 whole=true |
+| `seed_default_trackers` | 生成时可选勾选的 tracker 列表 | 空 |
+| `seed_default_format` | 默认种子格式 | oss |
+| `seed_format_policies` | 各格式自动生成开关 | 全关 |
+| `seed_auto_generate_policy` | 全局自动生成策略 | off |
+| `seed_single_direct_preview` | 单文件种子直接预览 | false |
+| `seed_cas_direct_access` | 打开 CAS 立即秒传+预览 | false |
+| 每存储 `seed_policy` | 存储级 `inherit`/`on`/`off` 覆盖 | inherit |
diff --git a/pages/snippets/reverse-tip.md b/pages/snippets/reverse-tip.md
new file mode 100644
index 000000000..8ad713a64
--- /dev/null
+++ b/pages/snippets/reverse-tip.md
@@ -0,0 +1,5 @@
+::: danger 请仔细阅读注意事项
+
+本接口是基于历史产物的逆向接口，项目组不会主动进行维护，请勿针对此驱动提出有关于任何修复或进行进一步逆向行为需求的issue。
+
+:::
diff --git a/pages/snippets/tos-tip.md b/pages/snippets/tos-tip.md
new file mode 100644
index 000000000..ae29c75c3
--- /dev/null
+++ b/pages/snippets/tos-tip.md
@@ -0,0 +1,5 @@
+::: danger
+
+请规范使用帐号，包含但不限于 **`多人共享使用`**、**`图床、软件床`** 和 **`视频外链到视频网站播放`** 等分发服务以及一些没有提到的不规范使用的方式导致帐号被封禁的，后果自负！
+
+:::
diff --git a/pages/terms.md b/pages/terms.md
index 1b9202622..a020ba5db 100644
--- a/pages/terms.md
+++ b/pages/terms.md
@@ -1,31 +1,19 @@
---
-title:
- en: Terms of Service
- zh-CN: 使用条款
-# This is the icon of the page
-nav: false
-hide: true
-toc: false
-layout: statement
-top: 1000
-# A page can have multiple categories
+sidebar: false
+aside: false
+outline: false
+pageClass: statement-page
+comment: false
+contributors: false
---
-## AGPL 授权声明 { lang="zh-CN" }
+# 使用条款
-::: zh-CN
-本软件受 [GNU Affero General Public License v3.0 (AGPL-3.0)](https://www.gnu.org/licenses/agpl-3.0.html) 许可协议保护。您可以自由使用、修改和分发本软件，但必须遵守 AGPL-3.0 的相关条款，包括在分发和提供服务时公开源代码。详情请参阅上述链接。
-:::
-
-## AGPL License Notice { lang="en" }
+## AGPL 授权声明
-::: en
-This software is licensed under the [GNU Affero General Public License v3.0 (AGPL-3.0)](https://www.gnu.org/licenses/agpl-3.0.html). You are free to use, modify, and distribute the software, but must comply with AGPL-3.0 terms, including disclosing source code when distributing or offering as a service. See the link above for details.
-:::
-
-## 使用条款 { lang="zh-CN" }
+本软件受 [GNU Affero General Public License v3.0 (AGPL-3.0)](https://www.gnu.org/licenses/agpl-3.0.html) 许可协议保护。您可以自由使用、修改和分发本软件，但必须遵守 AGPL-3.0 的相关条款，包括在分发和提供服务时公开源代码。详情请参阅上述链接。
-::: zh-CN
+## 使用条款
- 本服务仅供合法用途，用户不得利用本服务从事任何违法活动。
- 用户应自行承担因使用本服务而产生的所有风险和责任。
@@ -35,25 +23,7 @@ This software is licensed under the [GNU Affero General Public License v3.0 (AGP
- OpenListTeam 保留要求下游项目以相同协议进行分发及对任何违反授权协议的行为追究相关法律责任的权利。
- 如有任何疑问，请随时联系我们。
-:::
-
-## Terms of Use { lang="en" }
-
-::: en
-
-- This service is for lawful use only. Users must not engage in any illegal activity through this service.
-- Users assume all risks and responsibilities resulting from the use of this service.
-- We reserve the right to modify, suspend, or terminate the service at any time without prior notice.
-- The service is provided "as is" without any express or implied warranties of availability, accuracy, or fitness for a particular purpose.
-- All downstream projects based on OpenList must strictly comply with the full terms of the AGPL 3.0 license, including proper attribution, maintaining open-source status, and adopting the same license.
-- The OpenListTeam reserves the right to require downstream projects to be distributed under the same license and to pursue any violations of the license terms.
-- If you have any questions, please contact us.
-
-:::
-
-## 免责声明 { #disclaimer lang="zh-CN" }
-
-::: zh-CN
+## 免责声明 {#disclaimer}
- OpenList 项目为免费开源软件，基于上游 Alist 项目分叉开发，由 OpenListTeam 负责维护。
- 本软件按“原样”提供，不附带任何明示或暗示的担保，包括但不限于适销性或特定用途的适用性。
@@ -66,23 +36,3 @@ This software is licensed under the [GNU Affero General Public License v3.0 (AGP
- 您需自行承担使用本软件的所有风险，包括但不限于账号被封、下载限速等。
- 任何基于 OpenList 产生的分叉、分支或衍生项目，均为相互独立的项目，具备各自的创建者、维护者和独立反馈渠道，OpenListTeam 不提供任何支持。
- 对任何分叉、分支、衍生项目的任何行为、内容及由此引发的任何后果，均由相应负责人独立承担，OpenListTeam 概不承担任何责任。
-
-:::
-
-## DISCLAIMER { lang="en" }
-
-::: en
-
-- THE OPENLIST PROJECT IS FREE AND OPEN-SOURCE SOFTWARE, FORKED FROM THE UPSTREAM ALIST PROJECT AND MAINTAINED BY THE OPENLISTTEAM.
-- THIS SOFTWARE IS PROVIDED "AS IS" WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-- THIS SOFTWARE IS LICENSED UNDER THE [GNU Affero General Public License v3.0 (AGPL-3.0)](https://www.gnu.org/licenses/agpl-3.0.html). YOU ARE FREE TO USE, MODIFY, AND DISTRIBUTE THE SOFTWARE, BUT MUST COMPLY WITH AGPL-3.0 TERMS, INCLUDING DISCLOSING SOURCE CODE WHEN DISTRIBUTING OR OFFERING AS A SERVICE. SEE THE LINK ABOVE FOR DETAILS.
-- PLEASE COMPLY WITH RELEVANT LAWS AND REGULATIONS WHEN USING THIS SOFTWARE, AND REFRAIN FROM ANY FORM OF ABUSE.
-- THIS SOFTWARE IS IMPLEMENTED BASED ON OFFICIAL SDKS OR APIS, WITHOUT MODIFYING, DAMAGING, OR INTERFERING WITH THEIR BEHAVIOR.
-- IT ONLY PERFORMS HTTP 302 REDIRECTS OR TRAFFIC FORWARDING, WITHOUT INTERCEPTING, STORING, OR TAMPERING WITH ANY USER DATA.
-- THIS PROJECT IS NOT AFFILIATED WITH ANY OFFICIAL PLATFORM OR SERVICE PROVIDER.
-- THE MAINTAINERS ARE NOT RESPONSIBLE FOR ANY DIRECT OR INDIRECT LOSSES RESULTING FROM THE USE OR INABILITY TO USE THIS SOFTWARE.
-- YOU ASSUME ALL RISKS ASSOCIATED WITH USING THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ACCOUNT BANS, DOWNLOAD SPEED LIMITS, ETC.
-- ANY FORKS, BRANCHES, OR DERIVATIVE PROJECTS BASED ON OPENLIST ARE INDEPENDENT PROJECTS WITH THEIR OWN CREATORS, MAINTAINERS, AND FEEDBACK CHANNELS. THE OPENLISTTEAM DOES NOT PROVIDE ANY SUPPORT FOR THEM.
-- ANY ACTIONS, CONTENT, AND CONSEQUENCES ARISING FROM SUCH FORKS, BRANCHES, OR DERIVATIVE PROJECTS ARE THE SOLE RESPONSIBILITY OF THEIR RESPECTIVE MAINTAINERS, AND THE OPENLISTTEAM IS NOT LIABLE FOR ANY SUCH ISSUES.
-
-:::
diff --git a/patches/README.md b/patches/README.md
deleted file mode 100644
index 85f9ed707..000000000
--- a/patches/README.md
+++ /dev/null
@@ -1,15 +0,0 @@
-# Patches
-
-This dir contains patches of node modules.
-
-## Create
-
-```bash
-pnpm patch package@version
-```
-
-Edit `./node_modules/.pnpm_patches/package@version`, then commit your changes:
-
-```bash
-pnpm patch-commit ./node_modules/.pnpm_patches/package@version
-```
diff --git a/patches/valaxy-theme-press@0.25.9.patch b/patches/valaxy-theme-press@0.25.9.patch
deleted file mode 100644
index 580bae5eb..000000000
--- a/patches/valaxy-theme-press@0.25.9.patch
+++ /dev/null
@@ -1,21 +0,0 @@
-diff --git a/components/PressCategory.vue b/components/PressCategory.vue
-index b2ffedd2e205ffca4545bb355735463114d95088..b30ce35243b0eb6d727aa35d464a811eaec194f3 100644
---- a/components/PressCategory.vue
-+++ b/components/PressCategory.vue
-@@ -58,7 +58,15 @@ const { $tO } = useValaxyI18n()
-
-
-
-- , posts: Post[] = []) {
- posts = site.postList
- }
-
-+ posts.sort((a, b) => {
-+ // console.log(a.top, b.top, 'sort post list')
-+ return (b.top || 0) - (a.top || 0)
-+ })
-+
- const categoryList: CategoryList = {
- name: 'All',
- total: posts.length,
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index f54dcfbc1..3717f1877 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -1,392 +1,370 @@
+---
+lockfileVersion: '9.0'
+
+importers:
+
+ .:
+ configDependencies: {}
+ packageManagerDependencies:
+ pnpm:
+ specifier: 12.6.0
+ version: 12.6.0
+
+packages:
+
+ '@pnpm/exe.android-arm64@12.6.0':
+ resolution: {integrity: sha512-kviIHft9h02q+7N2In7tSL9T/HRUSGwYmU74YPtsWU5ee7vgqPyC0JT6RRX6miW+NxX1CvHgQxg69qq1qTLJYQ==}
+ cpu: [arm64]
+ os: [android]
+
+ '@pnpm/exe.android-x64@12.6.0':
+ resolution: {integrity: sha512-CT8aJKLq2mtZFE71pr4E5Z2xHL8uGnRGr+NclDqsXlVF4SVcQ2QAs14mWi0C8gjT4hbmi+Q0lJRRIkMAWfjjng==}
+ cpu: [x64]
+ os: [android]
+
+ '@pnpm/exe.darwin-arm64@12.6.0':
+ resolution: {integrity: sha512-rafpVkjzugKBMxSvGQd5wK1x5eOTkD/+lcJIFHeQhvd+BJ8kDisOOvwhQDrpGd4vd2Fx+hhW0P2Ptt638OlhFg==}
+ cpu: [arm64]
+ os: [darwin]
+
+ '@pnpm/exe.darwin-x64@12.6.0':
+ resolution: {integrity: sha512-72Jpuv1m24gI8zUNcaylYpBWEhBzz1VPhnDIU2GYM2eRP+KsOqVLwV78i+JrihI39zY2NNXmaN4eAKX1inpaDQ==}
+ cpu: [x64]
+ os: [darwin]
+
+ '@pnpm/exe.freebsd-x64@12.6.0':
+ resolution: {integrity: sha512-LON4QgNy1w/XF4uySZIyC/5hEB0oGdelXsY9tSKqstER+2j2X2oHz67skD11RRd/HWFRtMr64shQZ4I9ZoZ0zg==}
+ cpu: [x64]
+ os: [freebsd]
+
+ '@pnpm/exe.linux-arm64-musl@12.6.0':
+ resolution: {integrity: sha512-BdDpX+DeaMUc5x6WNcE6FkmFy36NwrBbBvwsZU737Zt3u1fTY+iKFPchjEQNCM4rT6q6xvF2oN3ZwExGsJCkxQ==}
+ cpu: [arm64]
+ os: [linux]
+ libc: [musl]
+
+ '@pnpm/exe.linux-arm64@12.6.0':
+ resolution: {integrity: sha512-8h2sNoIhHDpHDYqZZCh9PXr6krqW10btb0GHVGuw710muDHlFAHMtUG2ogmaHge6zJG1xgY4Y7mwX5g/LWvrYg==}
+ cpu: [arm64]
+ os: [linux]
+ libc: [glibc]
+
+ '@pnpm/exe.linux-ppc64@12.6.0':
+ resolution: {integrity: sha512-ld6xgcEhFCFrsVsJhbmdmR714PnsEspO/Ij8w0/D7OSiz2hYGu3fZd5tKRxOI5m6H6Gl0/RRFAPncTHbsgXVjQ==}
+ cpu: [ppc64]
+ os: [linux]
+ libc: [glibc]
+
+ '@pnpm/exe.linux-riscv64@12.6.0':
+ resolution: {integrity: sha512-HIbImydoC3J8NFt+8MXfhTCf5rO6NjCMyinSAHac0VmV8uCHw+kbQkyAzxV84rzz9ZOzmBOnj0b1N461UIYGsw==}
+ cpu: [riscv64]
+ os: [linux]
+ libc: [glibc]
+
+ '@pnpm/exe.linux-s390x@12.6.0':
+ resolution: {integrity: sha512-DjSqT7+BZ/lWcDHwNMuzsRVfyxUimh+D54Xw4tSWbdVVQhtWtNMUyI93LVnwCmsoEpar2gC3SFeAgywx37svKQ==}
+ cpu: [s390x]
+ os: [linux]
+ libc: [glibc]
+
+ '@pnpm/exe.linux-x64-musl@12.6.0':
+ resolution: {integrity: sha512-31lKeGPmRE6xfV6I3VjaEGVFRei14pl/zgoFDK4w+UkbJqOuNl2Ht3O1GuqNIg3Gl14qTEb4kZRAYFHXifDx9A==}
+ cpu: [x64]
+ os: [linux]
+ libc: [musl]
+
+ '@pnpm/exe.linux-x64@12.6.0':
+ resolution: {integrity: sha512-qFWBneHJAJ73W4whtbaFOL1M/7DBC6ILHXuxc7ZPtEhfPuT1zeZiGrmKHoMAfJA+mcm6xhOFljqVTUS+00Jabw==}
+ cpu: [x64]
+ os: [linux]
+ libc: [glibc]
+
+ '@pnpm/exe.win32-arm64@12.6.0':
+ resolution: {integrity: sha512-OhfefXEEykZlslSUhR8PPRe6MVPV3Oink/dVfIecE5velpc7j80cZYsHlaDrtRDcm3TPwQHkaRW1SJ1efX9oFg==}
+ cpu: [arm64]
+ os: [win32]
+
+ '@pnpm/exe.win32-x64@12.6.0':
+ resolution: {integrity: sha512-L2tuyrD2+Imgxs3VK/ST/2L3xD6vDP0ktJQxM0TaGw7TbAQEMq+RMc8iK6Ew7Id579uzjJe8jSfJID2ZGsOHCA==}
+ cpu: [x64]
+ os: [win32]
+
+ pnpm@12.6.0:
+ resolution: {integrity: sha512-PvaPlRyxEawgS0paFvCy3fDaVqluBBPoHYVdnwtV75JnFHCQKOHNAMQFwsX7e56OxNxGd3yAXQNzwvL/AP0g7A==}
+ engines: {node: '>=18.*'}
+ hasBin: true
+
+snapshots:
+
+ '@pnpm/exe.android-arm64@12.6.0':
+ optional: true
+
+ '@pnpm/exe.android-x64@12.6.0':
+ optional: true
+
+ '@pnpm/exe.darwin-arm64@12.6.0':
+ optional: true
+
+ '@pnpm/exe.darwin-x64@12.6.0':
+ optional: true
+
+ '@pnpm/exe.freebsd-x64@12.6.0':
+ optional: true
+
+ '@pnpm/exe.linux-arm64-musl@12.6.0':
+ optional: true
+
+ '@pnpm/exe.linux-arm64@12.6.0':
+ optional: true
+
+ '@pnpm/exe.linux-ppc64@12.6.0':
+ optional: true
+
+ '@pnpm/exe.linux-riscv64@12.6.0':
+ optional: true
+
+ '@pnpm/exe.linux-s390x@12.6.0':
+ optional: true
+
+ '@pnpm/exe.linux-x64-musl@12.6.0':
+ optional: true
+
+ '@pnpm/exe.linux-x64@12.6.0':
+ optional: true
+
+ '@pnpm/exe.win32-arm64@12.6.0':
+ optional: true
+
+ '@pnpm/exe.win32-x64@12.6.0':
+ optional: true
+
+ pnpm@12.6.0:
+ optionalDependencies:
+ '@pnpm/exe.android-arm64': 12.6.0
+ '@pnpm/exe.android-x64': 12.6.0
+ '@pnpm/exe.darwin-arm64': 12.6.0
+ '@pnpm/exe.darwin-x64': 12.6.0
+ '@pnpm/exe.freebsd-x64': 12.6.0
+ '@pnpm/exe.linux-arm64': 12.6.0
+ '@pnpm/exe.linux-arm64-musl': 12.6.0
+ '@pnpm/exe.linux-ppc64': 12.6.0
+ '@pnpm/exe.linux-riscv64': 12.6.0
+ '@pnpm/exe.linux-s390x': 12.6.0
+ '@pnpm/exe.linux-x64': 12.6.0
+ '@pnpm/exe.linux-x64-musl': 12.6.0
+ '@pnpm/exe.win32-arm64': 12.6.0
+ '@pnpm/exe.win32-x64': 12.6.0
+
+---
lockfileVersion: '9.0'
settings:
autoInstallPeers: true
excludeLinksFromLockfile: false
-patchedDependencies:
- valaxy-theme-press@0.25.9:
- hash: a6c7859cddc4d023eca0c3ca0820314f6456487482af67a4b4ba28719d385f3d
- path: patches/valaxy-theme-press@0.25.9.patch
- valaxy@0.25.9:
- hash: 4e8a0c516f0006cdaf6f1333cca04b01a402f6dc55935ae6f485f932da77c611
- path: patches/valaxy@0.25.9.patch
-
importers:
.:
dependencies:
'@giscus/vue':
specifier: ^3.1.1
- version: 3.1.1(vue@3.5.17(typescript@5.8.3))
- '@iconify-json/devicon-plain':
- specifier: ^1.2.31
- version: 1.2.31
- '@iconify-json/logos':
- specifier: ^1.2.4
- version: 1.2.4
- '@iconify-json/ri':
- specifier: ^1.2.5
- version: 1.2.5
- '@iconify-json/vscode-icons':
- specifier: ^1.2.23
- version: 1.2.23
- valaxy:
- specifier: 0.25.9
- version: 0.25.9(patch_hash=4e8a0c516f0006cdaf6f1333cca04b01a402f6dc55935ae6f485f932da77c611)(@babel/parser@7.28.0)(@types/markdown-it@14.1.2)(@types/node@24.0.15)(@vue/compiler-dom@3.5.17)(@vue/compiler-sfc@3.5.17)(axios@1.10.0)(eslint@9.29.0(jiti@2.4.2))(focus-trap@7.6.5)(postcss@8.5.6)(prettier@3.6.2)(rollup@4.45.1)(terser@5.43.1)(typescript@5.8.3)(yaml@2.8.0)
- valaxy-addon-algolia:
- specifier: 0.2.0
- version: 0.2.0(@algolia/client-search@5.34.0)(search-insights@2.17.3)(valaxy@0.25.9(patch_hash=4e8a0c516f0006cdaf6f1333cca04b01a402f6dc55935ae6f485f932da77c611)(@babel/parser@7.28.0)(@types/markdown-it@14.1.2)(@types/node@24.0.15)(@vue/compiler-dom@3.5.17)(@vue/compiler-sfc@3.5.17)(axios@1.10.0)(eslint@9.29.0(jiti@2.4.2))(focus-trap@7.6.5)(postcss@8.5.6)(prettier@3.6.2)(rollup@4.45.1)(terser@5.43.1)(typescript@5.8.3)(yaml@2.8.0))
- valaxy-addon-components:
- specifier: 0.1.0
- version: 0.1.0
- valaxy-addon-git-log:
- specifier: 0.3.2
- version: 0.3.2(valaxy@0.25.9(patch_hash=4e8a0c516f0006cdaf6f1333cca04b01a402f6dc55935ae6f485f932da77c611)(@babel/parser@7.28.0)(@types/markdown-it@14.1.2)(@types/node@24.0.15)(@vue/compiler-dom@3.5.17)(@vue/compiler-sfc@3.5.17)(axios@1.10.0)(eslint@9.29.0(jiti@2.4.2))(focus-trap@7.6.5)(postcss@8.5.6)(prettier@3.6.2)(rollup@4.45.1)(terser@5.43.1)(typescript@5.8.3)(yaml@2.8.0))
- valaxy-theme-press:
- specifier: 0.25.9
- version: 0.25.9(patch_hash=a6c7859cddc4d023eca0c3ca0820314f6456487482af67a4b4ba28719d385f3d)(@algolia/client-search@5.34.0)(search-insights@2.17.3)
+ version: 3.1.1(vue@3.5.43(typescript@6.0.3))
+ '@vueuse/core':
+ specifier: ^12.8.2
+ version: 12.8.2(typescript@6.0.3)
+ gray-matter:
+ specifier: ^4.0.3
+ version: 4.0.3
+ medium-zoom:
+ specifier: ^1.1.0
+ version: 1.1.0
+ mermaid:
+ specifier: ^12.0.0
+ version: 12.0.0
+ vitepress:
+ specifier: ^1.6.4
+ version: 1.6.4(@algolia/client-search@5.59.0)(@types/node@24.19.0)(postcss@8.5.28)(search-insights@2.17.3)(typescript@6.0.3)
vitepress-plugin-group-icons:
- specifier: ^1.6.1
- version: 1.6.1(markdown-it@14.1.0)(vite@6.3.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))
+ specifier: ^1.7.6
+ version: 1.7.6(vite@5.4.21(@types/node@24.19.0))
+ vue:
+ specifier: ^3.5.43
+ version: 3.5.43(typescript@6.0.3)
devDependencies:
- '@iconify-json/carbon':
- specifier: 1.2.9
- version: 1.2.9
- '@iconify-json/devicon':
- specifier: ^1.2.32
- version: 1.2.32
- '@iconify-json/simple-icons':
- specifier: 1.2.39
- version: 1.2.39
+ '@eslint/js':
+ specifier: ^10.0.1
+ version: 10.0.1(eslint@10.11.0)
'@types/node':
- specifier: ^24.0.15
- version: 24.0.15
+ specifier: ^24.19.0
+ version: 24.19.0
+ eslint:
+ specifier: ^10.11.0
+ version: 10.11.0
+ eslint-config-prettier:
+ specifier: ^10.1.8
+ version: 10.1.8(eslint@10.11.0)
+ eslint-plugin-vue:
+ specifier: ^10.11.1
+ version: 10.11.1(@typescript-eslint/parser@8.70.1(eslint@10.11.0)(typescript@6.0.3))(eslint@10.11.0)(vue-eslint-parser@10.4.1(eslint@10.11.0))
+ globals:
+ specifier: ^17.12.0
+ version: 17.12.0
husky:
specifier: ^9.1.7
version: 9.1.7
lint-staged:
- specifier: ^16.1.2
- version: 16.1.2
- nodemon:
- specifier: ^3.1.10
- version: 3.1.10
+ specifier: ^17.6.0
+ version: 17.6.0
prettier:
- specifier: ^3.6.2
- version: 3.6.2
- vite:
- specifier: 6.3.5
- version: 6.3.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0)
- vitepress:
- specifier: 1.1.4
- version: 1.1.4(@algolia/client-search@5.34.0)(@types/node@24.0.15)(axios@1.10.0)(fuse.js@7.1.0)(nprogress@0.2.0)(postcss@8.5.6)(qrcode@1.5.4)(sass@1.89.2)(search-insights@2.17.3)(terser@5.43.1)(typescript@5.8.3)
- vue:
- specifier: ^3.5.17
- version: 3.5.17(typescript@5.8.3)
- vue-i18n:
- specifier: ^11.1.10
- version: 11.1.10(vue@3.5.17(typescript@5.8.3))
+ specifier: ^3.9.9
+ version: 3.9.9
+ typescript:
+ specifier: ^6.0.3
+ version: 6.0.3
+ typescript-eslint:
+ specifier: ^8.70.1
+ version: 8.70.1(eslint@10.11.0)(typescript@6.0.3)
+ vue-eslint-parser:
+ specifier: ^10.4.1
+ version: 10.4.1(eslint@10.11.0)
vue-tsc:
- specifier: ^2.2.12
- version: 2.2.12(typescript@5.8.3)
+ specifier: ^3.3.11
+ version: 3.3.11(typescript@6.0.3)
packages:
- '@algolia/autocomplete-core@1.17.9':
- resolution: {integrity: sha512-O7BxrpLDPJWWHv/DLA9DRFWs+iY1uOJZkqUwjS5HSZAGcl0hIVCQ97LTLewiZmZ402JYUrun+8NqFP+hCknlbQ==}
+ '@algolia/abtesting@1.25.0':
+ resolution: {integrity: sha512-rSTin9Uta23uaewYVQEp8XI9T3iA/zrg0/1G2vhf8oFFDxFL5vybnZ5IQwsVAg4JpKxPX4/WYNKdcfWrZymk7w==}
+ engines: {node: '>= 14.0.0'}
+
+ '@algolia/autocomplete-core@1.17.7':
+ resolution: {integrity: sha512-BjiPOW6ks90UKl7TwMv7oNQMnzU+t/wk9mgIDi6b1tXpUek7MW0lbNOUHpvam9pe3lVCf4xPFT+lK7s+e+fs7Q==}
- '@algolia/autocomplete-plugin-algolia-insights@1.17.9':
- resolution: {integrity: sha512-u1fEHkCbWF92DBeB/KHeMacsjsoI0wFhjZtlCq2ddZbAehshbZST6Hs0Avkc0s+4UyBGbMDnSuXHLuvRWK5iDQ==}
+ '@algolia/autocomplete-plugin-algolia-insights@1.17.7':
+ resolution: {integrity: sha512-Jca5Ude6yUOuyzjnz57og7Et3aXjbwCSDf/8onLHSQgw1qW3ALl9mrMWaXb5FmPVkV3EtkD2F/+NkT6VHyPu9A==}
peerDependencies:
search-insights: '>= 1 < 3'
- '@algolia/autocomplete-preset-algolia@1.17.9':
- resolution: {integrity: sha512-Na1OuceSJeg8j7ZWn5ssMu/Ax3amtOwk76u4h5J4eK2Nx2KB5qt0Z4cOapCsxot9VcEN11ADV5aUSlQF4RhGjQ==}
+ '@algolia/autocomplete-preset-algolia@1.17.7':
+ resolution: {integrity: sha512-ggOQ950+nwbWROq2MOCIL71RE0DdQZsceqrg32UqnhDz8FlO9rL8ONHNsI2R1MH0tkgVIDKI/D0sMiUchsFdWA==}
peerDependencies:
'@algolia/client-search': '>= 4.9.1 < 6'
algoliasearch: '>= 4.9.1 < 6'
- '@algolia/autocomplete-shared@1.17.9':
- resolution: {integrity: sha512-iDf05JDQ7I0b7JEA/9IektxN/80a2MZ1ToohfmNS3rfeuQnIKI3IJlIafD0xu4StbtQTghx9T3Maa97ytkXenQ==}
+ '@algolia/autocomplete-shared@1.17.7':
+ resolution: {integrity: sha512-o/1Vurr42U/qskRSuhBH+VKxMvkkUVTLU6WZQr+L5lGZZLYWyhdzWjW0iGXY7EkwRTjBqvN2EsR81yCTGV/kmg==}
peerDependencies:
'@algolia/client-search': '>= 4.9.1 < 6'
algoliasearch: '>= 4.9.1 < 6'
- '@algolia/client-abtesting@5.34.0':
- resolution: {integrity: sha512-d6ardhDtQsnMpyr/rPrS3YuIE9NYpY4rftkC7Ap9tyuhZ/+V3E/LH+9uEewPguKzVqduApdwJzYq2k+vAXVEbQ==}
+ '@algolia/client-abtesting@5.59.0':
+ resolution: {integrity: sha512-bm2XN0hCSMYwStSsCBT0/PUB2BDxoyR1Lnub3c392HMEy9bi8PUSW8vR6zltVEKWG2t4PQFWMD5C07bmJxGgPg==}
engines: {node: '>= 14.0.0'}
- '@algolia/client-analytics@5.34.0':
- resolution: {integrity: sha512-WXIByjHNA106JO1Dj6b4viSX/yMN3oIB4qXr2MmyEmNq0MgfuPfPw8ayLRIZPa9Dp27hvM3G8MWJ4RG978HYFw==}
+ '@algolia/client-analytics@5.59.0':
+ resolution: {integrity: sha512-XOFPOTa69WuqHR6c5tMgnUUwwqQgNSzMpxmhrgA9KmxRf8WIqEa0cokHJvohk5CYb7CZx0xeSL6Bk2IUJ7Lv7Q==}
engines: {node: '>= 14.0.0'}
- '@algolia/client-common@5.34.0':
- resolution: {integrity: sha512-JeN1XJLZIkkv6yK0KT93CIXXk+cDPUGNg5xeH4fN9ZykYFDWYRyqgaDo+qvg4RXC3WWkdQ+hogQuuCk4Y3Eotw==}
+ '@algolia/client-common@5.59.0':
+ resolution: {integrity: sha512-PC8ipLOYFKRTfIUY1J3FJxS6ryzWziaXmIX9/sNMoUR8L+XhF7hX2QAeUI87YVl5zujvlYTSOb+HAIqKXDjyHQ==}
engines: {node: '>= 14.0.0'}
- '@algolia/client-insights@5.34.0':
- resolution: {integrity: sha512-gdFlcQa+TWXJUsihHDlreFWniKPFIQ15i5oynCY4m9K3DCex5g5cVj9VG4Hsquxf2t6Y0yv8w6MvVTGDO8oRLw==}
+ '@algolia/client-insights@5.59.0':
+ resolution: {integrity: sha512-yFNcCMM5fHiyoR0HuxMrzy+VjDcmhFUZTm2IJ2DHwGsVH3B5SEob4zTmeEZ3j/AZqNnmrJOCKl/tJnBg7+84bA==}
engines: {node: '>= 14.0.0'}
- '@algolia/client-personalization@5.34.0':
- resolution: {integrity: sha512-g91NHhIZDkh1IUeNtsUd8V/ZxuBc2ByOfDqhCkoQY3Z/mZszhpn3Czn6AR5pE81fx793vMaiOZvQVB5QttArkQ==}
+ '@algolia/client-personalization@5.59.0':
+ resolution: {integrity: sha512-GYja6HkDt2VrQhWmB2cLx3Z5fDwI9no7q+xwCWcFrTPm5CLH9QZvK0XLO9co1FcNIDxxkMaP3AXM39/XcecEOg==}
engines: {node: '>= 14.0.0'}
- '@algolia/client-query-suggestions@5.34.0':
- resolution: {integrity: sha512-cvRApDfFrlJ3Vcn37U4Nd/7S6T8cx7FW3mVLJPqkkzixv8DQ/yV+x4VLirxOtGDdq3KohcIbIGWbg1QuyOZRvQ==}
+ '@algolia/client-query-suggestions@5.59.0':
+ resolution: {integrity: sha512-Wofg7bMpWh8N5qDDZs0wy6whc+KMmdNsxgrIGp9Ug2s1Bka0uq7AjyckdxReKPHLA0Q1qH8X/SNh0wn2t2X2Lw==}
engines: {node: '>= 14.0.0'}
- '@algolia/client-search@5.34.0':
- resolution: {integrity: sha512-m9tK4IqJmn+flEPRtuxuHgiHmrKV0su5fuVwVpq8/es4DMjWMgX1a7Lg1PktvO8AbKaTp9kTtBAPnwXpuCwmEg==}
+ '@algolia/client-search@5.59.0':
+ resolution: {integrity: sha512-fHnALZfbEnODczGk14Y/1YBRApp6UEpZUTexGcMUPzY7RDc7q4HN2Y6jh0KUG8Jo9B+q+wOoQEc3ziR0ErbuFg==}
engines: {node: '>= 14.0.0'}
- '@algolia/ingestion@1.34.0':
- resolution: {integrity: sha512-2rxy4XoeRtIpzxEh5u5UgDC5HY4XbNdjzNgFx1eDrfFkSHpEVjirtLhISMy2N5uSFqYu1uUby5/NC1Soq8J7iw==}
+ '@algolia/ingestion@1.59.0':
+ resolution: {integrity: sha512-Fa38s1mHgoaLCT117sfJ6P78rtxUt93CYxBYpq1VOIcslaF+cH+1h5uikAPsKfxLnsuEDZHiBiaI6eNPTsQMRA==}
engines: {node: '>= 14.0.0'}
- '@algolia/monitoring@1.34.0':
- resolution: {integrity: sha512-OJiDhlJX8ZdWAndc50Z6aUEW/YmnhFK2ul3rahMw5/c9Damh7+oY9SufoK2LimJejy+65Qka06YPG29v2G/vww==}
+ '@algolia/monitoring@1.59.0':
+ resolution: {integrity: sha512-NyNsRSqM2tF1MX7ZGw/j4rduoEJiQ5wfvbSo/CFVdEzYCjyxbGFRPOZyS/GETJG9rk1TdHOq8NZqKqk/u1fm4g==}
engines: {node: '>= 14.0.0'}
- '@algolia/recommend@5.34.0':
- resolution: {integrity: sha512-fzNQZAdVxu/Gnbavy8KW5gurApwdYcPW6+pjO7Pw8V5drCR3eSqnOxSvp79rhscDX8ezwqMqqK4F3Hsq+KpRzg==}
+ '@algolia/recommend@5.59.0':
+ resolution: {integrity: sha512-nXBK2uygWtvbCOffMWqqfjjcEtp9enDKY5/2Pw/Hhw8VVaOyK2ThbGK04bNX/Le+qoK1VHYkodWGVTKfw0Otkw==}
engines: {node: '>= 14.0.0'}
- '@algolia/requester-browser-xhr@5.34.0':
- resolution: {integrity: sha512-gEI0xjzA/xvMpEdYmgQnf6AQKllhgKRtnEWmwDrnct+YPIruEHlx1dd7nRJTy/33MiYcCxkB4khXpNrHuqgp3Q==}
+ '@algolia/requester-browser-xhr@5.59.0':
+ resolution: {integrity: sha512-yb+4afX/zja8QwX0KmV4/ae2kyYkRknsE79CRusYS2U5D8qwn2wq0cn1x12f3tm3F3+5FgmDdbuGdQTuCLSKMQ==}
engines: {node: '>= 14.0.0'}
- '@algolia/requester-fetch@5.34.0':
- resolution: {integrity: sha512-5SwGOttpbACT4jXzfSJ3mnTcF46SVNSnZ1JjxC3qBa3qKi4U0CJGzuVVy3L798u8dG5H0SZ2MAB5v7180Gnqew==}
+ '@algolia/requester-fetch@5.59.0':
+ resolution: {integrity: sha512-Lp52TmpA1QtNmdHzs505Xwf4tgII7RAapkDSF9AAtWIBETcGaTIaXci4Rd9nS6SdaWK1BWTSqAPp5wzh6UN3Ag==}
engines: {node: '>= 14.0.0'}
- '@algolia/requester-node-http@5.34.0':
- resolution: {integrity: sha512-409XlyIyEXrxyGjWxd0q5RASizHSRVUU0AXPCEdqnbcGEzbCgL1n7oYI8YxzE/RqZLha+PNwWCcTVn7EE5tyyQ==}
+ '@algolia/requester-node-http@5.59.0':
+ resolution: {integrity: sha512-YYHLEs5rC6oRTFwT7bJaKBR9NSFzikeVHGAT1ffATmUQzR8XqyhHXjoieAUoR7fBU6I5cfy1FVeh5GoRgriuzA==}
engines: {node: '>= 14.0.0'}
- '@ampproject/remapping@2.3.0':
- resolution: {integrity: sha512-30iZtAPgz+LTIYoeivqYo853f02jBYSd5uGnGpkFV0M3xOt9aN73erkgYAmZU43x4VfqcnLxW9Kpg3R5LC4YYw==}
- engines: {node: '>=6.0.0'}
-
- '@antfu/install-pkg@1.1.0':
- resolution: {integrity: sha512-MGQsmw10ZyI+EJo45CdSER4zEb+p31LpDAFp2Z3gkSd1yqVZGi0Ebx++YTEMonJy4oChEMLsxZ64j8FH6sSqtQ==}
-
- '@antfu/utils@0.7.10':
- resolution: {integrity: sha512-+562v9k4aI80m1+VuMHehNJWLOFjBnXn3tdOitzD0il5b7smkSBal4+a3oKiQTbrwMmN/TBUMDvbdoWDehgOww==}
-
- '@antfu/utils@8.1.1':
- resolution: {integrity: sha512-Mex9nXf9vR6AhcXmMrlz/HVgYYZpVGJ6YlPgwl7UnaFpnshXs6EK/oa5Gpf3CzENMjkvEx2tQtntGnb7UtSTOQ==}
-
- '@antfu/utils@9.2.0':
- resolution: {integrity: sha512-Oq1d9BGZakE/FyoEtcNeSwM7MpDO2vUBi11RWBZXf75zPsbUVWmUs03EqkRFrcgbXyKTas0BdZWC1wcuSoqSAw==}
-
- '@asamuzakjp/css-color@3.2.0':
- resolution: {integrity: sha512-K1A6z8tS3XsmCMM86xoWdn7Fkdn9m6RSVtocUrJYIwZnFVkng/PvkEoWtOWmP+Scc6saYWHWZYbndEEXxl24jw==}
-
- '@babel/code-frame@7.27.1':
- resolution: {integrity: sha512-cjQ7ZlQ0Mv3b47hABuTevyTuYN4i+loJKGeV9flcCgIK37cCXRh+L1bd3iBHlynerhQ7BhCkn2BPbQUL+rGqFg==}
- engines: {node: '>=6.9.0'}
-
- '@babel/compat-data@7.28.0':
- resolution: {integrity: sha512-60X7qkglvrap8mn1lh2ebxXdZYtUcpd7gsmy9kLaBJ4i/WdY8PqTSdxyA8qraikqKQK5C1KRBKXqznrVapyNaw==}
- engines: {node: '>=6.9.0'}
-
- '@babel/core@7.28.0':
- resolution: {integrity: sha512-UlLAnTPrFdNGoFtbSXwcGFQBtQZJCNjaN6hQNP3UPvuNXT1i82N26KL3dZeIpNalWywr9IuQuncaAfUaS1g6sQ==}
- engines: {node: '>=6.9.0'}
-
- '@babel/generator@7.28.0':
- resolution: {integrity: sha512-lJjzvrbEeWrhB4P3QBsH7tey117PjLZnDbLiQEKjQ/fNJTjuq4HSqgFA+UNSwZT8D7dxxbnuSBMsa1lrWzKlQg==}
- engines: {node: '>=6.9.0'}
-
- '@babel/helper-annotate-as-pure@7.27.3':
- resolution: {integrity: sha512-fXSwMQqitTGeHLBC08Eq5yXz2m37E4pJX1qAU1+2cNedz/ifv/bVXft90VeSav5nFO61EcNgwr0aJxbyPaWBPg==}
- engines: {node: '>=6.9.0'}
-
- '@babel/helper-compilation-targets@7.27.2':
- resolution: {integrity: sha512-2+1thGUUWWjLTYTHZWK1n8Yga0ijBz1XAhUXcKy81rd5g6yh7hGqMp45v7cadSbEHc9G3OTv45SyneRN3ps4DQ==}
- engines: {node: '>=6.9.0'}
-
- '@babel/helper-create-class-features-plugin@7.27.1':
- resolution: {integrity: sha512-QwGAmuvM17btKU5VqXfb+Giw4JcN0hjuufz3DYnpeVDvZLAObloM77bhMXiqry3Iio+Ai4phVRDwl6WU10+r5A==}
- engines: {node: '>=6.9.0'}
- peerDependencies:
- '@babel/core': ^7.0.0
-
- '@babel/helper-globals@7.28.0':
- resolution: {integrity: sha512-+W6cISkXFa1jXsDEdYA8HeevQT/FULhxzR99pxphltZcVaugps53THCeiWA8SguxxpSp3gKPiuYfSWopkLQ4hw==}
- engines: {node: '>=6.9.0'}
-
- '@babel/helper-member-expression-to-functions@7.27.1':
- resolution: {integrity: sha512-E5chM8eWjTp/aNoVpcbfM7mLxu9XGLWYise2eBKGQomAk/Mb4XoxyqXTZbuTohbsl8EKqdlMhnDI2CCLfcs9wA==}
- engines: {node: '>=6.9.0'}
-
- '@babel/helper-module-imports@7.27.1':
- resolution: {integrity: sha512-0gSFWUPNXNopqtIPQvlD5WgXYI5GY2kP2cCvoT8kczjbfcfuIljTbcWrulD1CIPIX2gt1wghbDy08yE1p+/r3w==}
- engines: {node: '>=6.9.0'}
-
- '@babel/helper-module-transforms@7.27.3':
- resolution: {integrity: sha512-dSOvYwvyLsWBeIRyOeHXp5vPj5l1I011r52FM1+r1jCERv+aFXYk4whgQccYEGYxK2H3ZAIA8nuPkQ0HaUo3qg==}
- engines: {node: '>=6.9.0'}
- peerDependencies:
- '@babel/core': ^7.0.0
-
- '@babel/helper-optimise-call-expression@7.27.1':
- resolution: {integrity: sha512-URMGH08NzYFhubNSGJrpUEphGKQwMQYBySzat5cAByY1/YgIRkULnIy3tAMeszlL/so2HbeilYloUmSpd7GdVw==}
- engines: {node: '>=6.9.0'}
-
- '@babel/helper-plugin-utils@7.27.1':
- resolution: {integrity: sha512-1gn1Up5YXka3YYAHGKpbideQ5Yjf1tDa9qYcgysz+cNCXukyLl6DjPXhD3VRwSb8c0J9tA4b2+rHEZtc6R0tlw==}
- engines: {node: '>=6.9.0'}
-
- '@babel/helper-replace-supers@7.27.1':
- resolution: {integrity: sha512-7EHz6qDZc8RYS5ElPoShMheWvEgERonFCs7IAonWLLUTXW59DP14bCZt89/GKyreYn8g3S83m21FelHKbeDCKA==}
- engines: {node: '>=6.9.0'}
- peerDependencies:
- '@babel/core': ^7.0.0
-
- '@babel/helper-skip-transparent-expression-wrappers@7.27.1':
- resolution: {integrity: sha512-Tub4ZKEXqbPjXgWLl2+3JpQAYBJ8+ikpQ2Ocj/q/r0LwE3UhENh7EUabyHjz2kCEsrRY83ew2DQdHluuiDQFzg==}
- engines: {node: '>=6.9.0'}
-
- '@babel/helper-string-parser@7.27.1':
- resolution: {integrity: sha512-qMlSxKbpRlAridDExk92nSobyDdpPijUq2DW6oDnUqd0iOGxmQjyqhMIihI9+zv4LPyZdRje2cavWPbCbWm3eA==}
- engines: {node: '>=6.9.0'}
-
- '@babel/helper-validator-identifier@7.27.1':
- resolution: {integrity: sha512-D2hP9eA+Sqx1kBZgzxZh0y1trbuU+JoDkiEwqhQ36nodYqJwyEIhPSdMNd7lOm/4io72luTPWH20Yda0xOuUow==}
- engines: {node: '>=6.9.0'}
+ '@antfu/install-pkg@2.1.0':
+ resolution: {integrity: sha512-sdg9NxU3zR4Mnawfbc/x6GB5Wf17WYud5qOuEuxXjaKpYpMkISSJEjItGebXJ2bQ4DIcly4NYH23mtkGJjvKUw==}
- '@babel/helper-validator-option@7.27.1':
- resolution: {integrity: sha512-YvjJow9FxbhFFKDSuFnVCe2WxXk1zWc22fFePVNEaWJEu8IrZVlda6N0uHwzZrUM1il7NC9Mlp4MaJYbYd9JSg==}
+ '@babel/helper-string-parser@7.29.7':
+ resolution: {integrity: sha512-Pb5ijPrZ89GDH8223L4UP8i6QApWxs04RbPQJTeWDV0/keR2E36MeKnyr6LYmUUvqRRI+Iv87SuF1W6ErINzYw==}
engines: {node: '>=6.9.0'}
- '@babel/helpers@7.27.6':
- resolution: {integrity: sha512-muE8Tt8M22638HU31A3CgfSUciwz1fhATfoVai05aPXGor//CdWDCbnlY1yvBPo07njuVOCNGCSp/GTt12lIug==}
+ '@babel/helper-validator-identifier@7.29.7':
+ resolution: {integrity: sha512-qehxGkRj55h/ff8EMaJ+cYhyaKlHIxqYDn682wQD7RNp9UujOQsHog2uS0r2vzr4pW+sXf90NeeayjcNaX3fFg==}
engines: {node: '>=6.9.0'}
- '@babel/parser@7.28.0':
- resolution: {integrity: sha512-jVZGvOxOuNSsuQuLRTh13nU0AogFlw32w/MT+LV6D3sP5WdbW61E77RnkbaO2dUvmPAYrBDJXGn5gGS6tH4j8g==}
+ '@babel/parser@7.29.9':
+ resolution: {integrity: sha512-CjXrNHTnvqBVqHgdBysY3vk2T8tpJHb5/RMeHJBTyVa9xgugCB0CJTx/3oO8RV2QRQP391RWpB7D6hLjm8V9uA==}
engines: {node: '>=6.0.0'}
hasBin: true
- '@babel/plugin-proposal-decorators@7.28.0':
- resolution: {integrity: sha512-zOiZqvANjWDUaUS9xMxbMcK/Zccztbe/6ikvUXaG9nsPH3w6qh5UaPGAnirI/WhIbZ8m3OHU0ReyPrknG+ZKeg==}
- engines: {node: '>=6.9.0'}
- peerDependencies:
- '@babel/core': ^7.0.0-0
-
- '@babel/plugin-syntax-decorators@7.27.1':
- resolution: {integrity: sha512-YMq8Z87Lhl8EGkmb0MwYkt36QnxC+fzCgrl66ereamPlYToRpIk5nUjKUY3QKLWq8mwUB1BgbeXcTJhZOCDg5A==}
- engines: {node: '>=6.9.0'}
- peerDependencies:
- '@babel/core': ^7.0.0-0
-
- '@babel/plugin-syntax-import-attributes@7.27.1':
- resolution: {integrity: sha512-oFT0FrKHgF53f4vOsZGi2Hh3I35PfSmVs4IBFLFj4dnafP+hIWDLg3VyKmUHfLoLHlyxY4C7DGtmHuJgn+IGww==}
- engines: {node: '>=6.9.0'}
- peerDependencies:
- '@babel/core': ^7.0.0-0
-
- '@babel/plugin-syntax-import-meta@7.10.4':
- resolution: {integrity: sha512-Yqfm+XDx0+Prh3VSeEQCPU81yC+JWZ2pDPFSS4ZdpfZhp4MkFMaDC1UqseovEKwSUpnIL7+vK+Clp7bfh0iD7g==}
- peerDependencies:
- '@babel/core': ^7.0.0-0
-
- '@babel/plugin-syntax-jsx@7.27.1':
- resolution: {integrity: sha512-y8YTNIeKoyhGd9O0Jiyzyyqk8gdjnumGTQPsz0xOZOQ2RmkVJeZ1vmmfIvFEKqucBG6axJGBZDE/7iI5suUI/w==}
- engines: {node: '>=6.9.0'}
- peerDependencies:
- '@babel/core': ^7.0.0-0
-
- '@babel/plugin-syntax-typescript@7.27.1':
- resolution: {integrity: sha512-xfYCBMxveHrRMnAWl1ZlPXOZjzkN82THFvLhQhFXFt81Z5HnN+EtUkZhv/zcKpmT3fzmWZB0ywiBrbC3vogbwQ==}
- engines: {node: '>=6.9.0'}
- peerDependencies:
- '@babel/core': ^7.0.0-0
-
- '@babel/plugin-transform-typescript@7.28.0':
- resolution: {integrity: sha512-4AEiDEBPIZvLQaWlc9liCavE0xRM0dNca41WtBeM3jgFptfUOSG9z0uteLhq6+3rq+WB6jIvUwKDTpXEHPJ2Vg==}
+ '@babel/types@7.29.8':
+ resolution: {integrity: sha512-Vj1jF3cPfxg7OAfoI7QnVKLoILlm2JF9pnVHrX8qx7AHMiYWT+NDAA7jChlNgRS4WTLc/fD1lXLmPixluj+3Gg==}
engines: {node: '>=6.9.0'}
- peerDependencies:
- '@babel/core': ^7.0.0-0
-
- '@babel/template@7.27.2':
- resolution: {integrity: sha512-LPDZ85aEJyYSd18/DkjNh4/y1ntkE5KwUHWTiqgRxruuZL2F1yuHligVHLvcHY2vMHXttKFpJn6LwfI7cw7ODw==}
- engines: {node: '>=6.9.0'}
-
- '@babel/traverse@7.28.0':
- resolution: {integrity: sha512-mGe7UK5wWyh0bKRfupsUchrQGqvDbZDbKJw+kcRGSmdHVYrv+ltd0pnpDTVpiTqnaBru9iEvA8pz8W46v0Amwg==}
- engines: {node: '>=6.9.0'}
-
- '@babel/types@7.28.1':
- resolution: {integrity: sha512-x0LvFTekgSX+83TI28Y9wYPUfzrnl2aT5+5QLnO6v7mSJYtEEevuDRN0F0uSHRk1G1IWZC43o00Y0xDDrpBGPQ==}
- engines: {node: '>=6.9.0'}
-
- '@braintree/sanitize-url@7.1.1':
- resolution: {integrity: sha512-i1L7noDNxtFyL5DmZafWy1wRVhGehQmzZaz1HiN5e7iylJMSZR7ekOV7NsIqa5qBldlLrsKv4HbgFUVlQrz8Mw==}
- '@chevrotain/cst-dts-gen@11.0.3':
- resolution: {integrity: sha512-BvIKpRLeS/8UbfxXxgC33xOumsacaeCKAjAeLyOn7Pcp95HiRbrpl14S+9vaZLolnbssPIUuiUd8IvgkRyt6NQ==}
+ '@braintree/sanitize-url@7.1.2':
+ resolution: {integrity: sha512-jigsZK+sMF/cuiB7sERuo9V7N9jx+dhmHHnQyDSVdpZwVutaBu7WvNYqMDLSgFgfB30n452TP3vjDAvFC973mA==}
- '@chevrotain/gast@11.0.3':
- resolution: {integrity: sha512-+qNfcoNk70PyS/uxmj3li5NiECO+2YKZZQMbmjTqRI3Qchu8Hig/Q9vgkHpI3alNjr7M+a2St5pw5w5F6NL5/Q==}
+ '@cacheable/memory@2.2.0':
+ resolution: {integrity: sha512-CTLKqLItRCEixEAewD3/j9DB3/o96gpTPD4eJ1v+DGOlxZRZncRQkGYqqnAGCscYd6RNeXfGeiuCphsPtqyIfQ==}
- '@chevrotain/regexp-to-ast@11.0.3':
- resolution: {integrity: sha512-1fMHaBZxLFvWI067AVbGJav1eRY7N8DDvYCTwGBiE/ytKBgP8azTdgyrKyWZ9Mfh09eHWb5PgTSO8wi7U824RA==}
+ '@cacheable/utils@2.5.0':
+ resolution: {integrity: sha512-buipgOVDkkPXNR5+xBpDw7Zk2n1EvU7qBJCNUcL7rhQ//kfpOXPAvQ511Os0vpLYJ1pZnvudNytkQt2hst3wqA==}
- '@chevrotain/types@11.0.3':
- resolution: {integrity: sha512-gsiM3G8b58kZC2HaWR50gu6Y1440cHiJ+i3JUvcp/35JchYejb2+5MVeJK0iKThYpAa/P2PYFV4hoi44HD+aHQ==}
+ '@chevrotain/cst-dts-gen@11.1.2':
+ resolution: {integrity: sha512-XTsjvDVB5nDZBQB8o0o/0ozNelQtn2KrUVteIHSlPd2VAV2utEb6JzyCJaJ8tGxACR4RiBNWy5uYUHX2eji88Q==}
- '@chevrotain/utils@11.0.3':
- resolution: {integrity: sha512-YslZMgtJUyuMbZ+aKvfF3x1f5liK4mWNxghFRv7jqRR9C3R3fAOGTTKvxXDa2Y1s9zSbcpuO0cAxDYsc9SrXoQ==}
+ '@chevrotain/gast@11.1.2':
+ resolution: {integrity: sha512-Z9zfXR5jNZb1Hlsd/p+4XWeUFugrHirq36bKzPWDSIacV+GPSVXdk+ahVWZTwjhNwofAWg/sZg58fyucKSQx5g==}
- '@clack/core@0.5.0':
- resolution: {integrity: sha512-p3y0FIOwaYRUPRcMO7+dlmLh8PSRcrjuTndsiA0WAFbWES0mLZlrjVoBRZ9DzkPFJZG6KGkJmoEAY0ZcVWTkow==}
+ '@chevrotain/regexp-to-ast@11.1.2':
+ resolution: {integrity: sha512-nMU3Uj8naWer7xpZTYJdxbAs6RIv/dxYzkYU8GSwgUtcAAlzjcPfX1w+RKRcYG8POlzMeayOQ/znfwxEGo5ulw==}
- '@clack/prompts@0.11.0':
- resolution: {integrity: sha512-pMN5FcrEw9hUkZA4f+zLlzivQSeQf5dRGJjSUbvVYDLvpKCdQx5OaknvKzgbtXOizhP+SJJJjqEbOe55uKKfAw==}
+ '@chevrotain/types@11.1.2':
+ resolution: {integrity: sha512-U+HFai5+zmJCkK86QsaJtoITlboZHBqrVketcO2ROv865xfCMSFpELQoz1GkX5GzME8pTa+3kbKrZHQtI0gdbw==}
- '@csstools/color-helpers@5.0.2':
- resolution: {integrity: sha512-JqWH1vsgdGcw2RR6VliXXdA0/59LttzlU8UlRT/iUUsEeWfYq8I+K0yhihEUTTHLRm1EXvpsCx3083EU15ecsA==}
- engines: {node: '>=18'}
-
- '@csstools/css-calc@2.1.4':
- resolution: {integrity: sha512-3N8oaj+0juUw/1H3YwmDDJXCgTB1gKU6Hc/bB502u9zR0q2vd786XJH9QfrKIEgFlZmhZiq6epXl4rHqhzsIgQ==}
- engines: {node: '>=18'}
- peerDependencies:
- '@csstools/css-parser-algorithms': ^3.0.5
- '@csstools/css-tokenizer': ^3.0.4
-
- '@csstools/css-color-parser@3.0.10':
- resolution: {integrity: sha512-TiJ5Ajr6WRd1r8HSiwJvZBiJOqtH86aHpUjq5aEKWHiII2Qfjqd/HCWKPOW8EP4vcspXbHnXrwIDlu5savQipg==}
- engines: {node: '>=18'}
- peerDependencies:
- '@csstools/css-parser-algorithms': ^3.0.5
- '@csstools/css-tokenizer': ^3.0.4
-
- '@csstools/css-parser-algorithms@3.0.5':
- resolution: {integrity: sha512-DaDeUkXZKjdGhgYaHNJTV9pV7Y9B3b644jCLs9Upc3VeNGg6LWARAT6O+Q+/COo+2gg/bM5rhpMAtf70WqfBdQ==}
- engines: {node: '>=18'}
- peerDependencies:
- '@csstools/css-tokenizer': ^3.0.4
-
- '@csstools/css-tokenizer@3.0.4':
- resolution: {integrity: sha512-Vd/9EVDiu6PPJt9yAh6roZP6El1xHrdvIVGjyBsHR0RYwNHgL7FJPyIIW4fANJNG6FtyZfvlRPpFI4ZM/lubvw==}
- engines: {node: '>=18'}
+ '@chevrotain/utils@11.1.2':
+ resolution: {integrity: sha512-4mudFAQ6H+MqBTfqLmU7G1ZwRzCLfJEooL/fsF6rCX5eePMbGhoy5n4g+G4vlh2muDcsCTJtL+uKbOzWxs5LHA==}
- '@docsearch/css@3.9.0':
- resolution: {integrity: sha512-cQbnVbq0rrBwNAKegIac/t6a8nWoUAn8frnkLFW6YARaRmAQr5/Eoe6Ln2fqkUCZ40KpdrKbpSAmgrkviOxuWA==}
+ '@docsearch/css@3.8.2':
+ resolution: {integrity: sha512-y05ayQFyUmCXze79+56v/4HpycYF3uFqB78pLPrSV5ZKAlDuIAAJNhaRi8tTdRNXh05yxX/TyNnzD6LwSM89vQ==}
- '@docsearch/js@3.9.0':
- resolution: {integrity: sha512-4bKHcye6EkLgRE8ze0vcdshmEqxeiJM77M0JXjef7lrYZfSlMunrDOCqyLjiZyo1+c0BhUqA2QpFartIjuHIjw==}
+ '@docsearch/js@3.8.2':
+ resolution: {integrity: sha512-Q5wY66qHn0SwA7Taa0aDbHiJvaFJLOJyHmooQ7y8hlwwQLQ/5WwCcoX0g7ii04Qi2DJlHsd0XXzJ8Ypw9+9YmQ==}
- '@docsearch/react@3.9.0':
- resolution: {integrity: sha512-mb5FOZYZIkRQ6s/NWnM98k879vu5pscWqTLubLFBO87igYYT4VzVazh4h5o/zCvTIZgEt3PvsCOMOswOUo9yHQ==}
+ '@docsearch/react@3.8.2':
+ resolution: {integrity: sha512-xCRrJQlTt8N9GU0DG4ptwHRkfnSnD/YpdeaXe02iKfqs97TkZJv60yE+1eq/tjPcVnTW8dP5qLP7itifFVV5eg==}
peerDependencies:
- '@types/react': '>= 16.8.0 < 20.0.0'
- react: '>= 16.8.0 < 20.0.0'
- react-dom: '>= 16.8.0 < 20.0.0'
+ '@types/react': '>= 16.8.0 < 19.0.0'
+ react: '>= 16.8.0 < 19.0.0'
+ react-dom: '>= 16.8.0 < 19.0.0'
search-insights: '>= 1 < 3'
peerDependenciesMeta:
'@types/react':
@@ -404,255 +382,117 @@ packages:
cpu: [ppc64]
os: [aix]
- '@esbuild/aix-ppc64@0.25.8':
- resolution: {integrity: sha512-urAvrUedIqEiFR3FYSLTWQgLu5tb+m0qZw0NBEasUeo6wuqatkMDaRT+1uABiGXEu5vqgPd7FGE1BhsAIy9QVA==}
- engines: {node: '>=18'}
- cpu: [ppc64]
- os: [aix]
-
'@esbuild/android-arm64@0.21.5':
resolution: {integrity: sha512-c0uX9VAUBQ7dTDCjq+wdyGLowMdtR/GoC2U5IYk/7D1H1JYC0qseD7+11iMP2mRLN9RcCMRcjC4YMclCzGwS/A==}
engines: {node: '>=12'}
cpu: [arm64]
os: [android]
- '@esbuild/android-arm64@0.25.8':
- resolution: {integrity: sha512-OD3p7LYzWpLhZEyATcTSJ67qB5D+20vbtr6vHlHWSQYhKtzUYrETuWThmzFpZtFsBIxRvhO07+UgVA9m0i/O1w==}
- engines: {node: '>=18'}
- cpu: [arm64]
- os: [android]
-
'@esbuild/android-arm@0.21.5':
resolution: {integrity: sha512-vCPvzSjpPHEi1siZdlvAlsPxXl7WbOVUBBAowWug4rJHb68Ox8KualB+1ocNvT5fjv6wpkX6o/iEpbDrf68zcg==}
engines: {node: '>=12'}
cpu: [arm]
os: [android]
- '@esbuild/android-arm@0.25.8':
- resolution: {integrity: sha512-RONsAvGCz5oWyePVnLdZY/HHwA++nxYWIX1atInlaW6SEkwq6XkP3+cb825EUcRs5Vss/lGh/2YxAb5xqc07Uw==}
- engines: {node: '>=18'}
- cpu: [arm]
- os: [android]
-
'@esbuild/android-x64@0.21.5':
resolution: {integrity: sha512-D7aPRUUNHRBwHxzxRvp856rjUHRFW1SdQATKXH2hqA0kAZb1hKmi02OpYRacl0TxIGz/ZmXWlbZgjwWYaCakTA==}
engines: {node: '>=12'}
cpu: [x64]
os: [android]
- '@esbuild/android-x64@0.25.8':
- resolution: {integrity: sha512-yJAVPklM5+4+9dTeKwHOaA+LQkmrKFX96BM0A/2zQrbS6ENCmxc4OVoBs5dPkCCak2roAD+jKCdnmOqKszPkjA==}
- engines: {node: '>=18'}
- cpu: [x64]
- os: [android]
-
'@esbuild/darwin-arm64@0.21.5':
resolution: {integrity: sha512-DwqXqZyuk5AiWWf3UfLiRDJ5EDd49zg6O9wclZ7kUMv2WRFr4HKjXp/5t8JZ11QbQfUS6/cRCKGwYhtNAY88kQ==}
engines: {node: '>=12'}
cpu: [arm64]
os: [darwin]
- '@esbuild/darwin-arm64@0.25.8':
- resolution: {integrity: sha512-Jw0mxgIaYX6R8ODrdkLLPwBqHTtYHJSmzzd+QeytSugzQ0Vg4c5rDky5VgkoowbZQahCbsv1rT1KW72MPIkevw==}
- engines: {node: '>=18'}
- cpu: [arm64]
- os: [darwin]
-
'@esbuild/darwin-x64@0.21.5':
resolution: {integrity: sha512-se/JjF8NlmKVG4kNIuyWMV/22ZaerB+qaSi5MdrXtd6R08kvs2qCN4C09miupktDitvh8jRFflwGFBQcxZRjbw==}
engines: {node: '>=12'}
cpu: [x64]
os: [darwin]
- '@esbuild/darwin-x64@0.25.8':
- resolution: {integrity: sha512-Vh2gLxxHnuoQ+GjPNvDSDRpoBCUzY4Pu0kBqMBDlK4fuWbKgGtmDIeEC081xi26PPjn+1tct+Bh8FjyLlw1Zlg==}
- engines: {node: '>=18'}
- cpu: [x64]
- os: [darwin]
-
'@esbuild/freebsd-arm64@0.21.5':
resolution: {integrity: sha512-5JcRxxRDUJLX8JXp/wcBCy3pENnCgBR9bN6JsY4OmhfUtIHe3ZW0mawA7+RDAcMLrMIZaf03NlQiX9DGyB8h4g==}
engines: {node: '>=12'}
cpu: [arm64]
os: [freebsd]
- '@esbuild/freebsd-arm64@0.25.8':
- resolution: {integrity: sha512-YPJ7hDQ9DnNe5vxOm6jaie9QsTwcKedPvizTVlqWG9GBSq+BuyWEDazlGaDTC5NGU4QJd666V0yqCBL2oWKPfA==}
- engines: {node: '>=18'}
- cpu: [arm64]
- os: [freebsd]
-
'@esbuild/freebsd-x64@0.21.5':
resolution: {integrity: sha512-J95kNBj1zkbMXtHVH29bBriQygMXqoVQOQYA+ISs0/2l3T9/kj42ow2mpqerRBxDJnmkUDCaQT/dfNXWX/ZZCQ==}
engines: {node: '>=12'}
cpu: [x64]
os: [freebsd]
- '@esbuild/freebsd-x64@0.25.8':
- resolution: {integrity: sha512-MmaEXxQRdXNFsRN/KcIimLnSJrk2r5H8v+WVafRWz5xdSVmWLoITZQXcgehI2ZE6gioE6HirAEToM/RvFBeuhw==}
- engines: {node: '>=18'}
- cpu: [x64]
- os: [freebsd]
-
'@esbuild/linux-arm64@0.21.5':
resolution: {integrity: sha512-ibKvmyYzKsBeX8d8I7MH/TMfWDXBF3db4qM6sy+7re0YXya+K1cem3on9XgdT2EQGMu4hQyZhan7TeQ8XkGp4Q==}
engines: {node: '>=12'}
cpu: [arm64]
os: [linux]
- '@esbuild/linux-arm64@0.25.8':
- resolution: {integrity: sha512-WIgg00ARWv/uYLU7lsuDK00d/hHSfES5BzdWAdAig1ioV5kaFNrtK8EqGcUBJhYqotlUByUKz5Qo6u8tt7iD/w==}
- engines: {node: '>=18'}
- cpu: [arm64]
- os: [linux]
-
'@esbuild/linux-arm@0.21.5':
resolution: {integrity: sha512-bPb5AHZtbeNGjCKVZ9UGqGwo8EUu4cLq68E95A53KlxAPRmUyYv2D6F0uUI65XisGOL1hBP5mTronbgo+0bFcA==}
engines: {node: '>=12'}
cpu: [arm]
os: [linux]
- '@esbuild/linux-arm@0.25.8':
- resolution: {integrity: sha512-FuzEP9BixzZohl1kLf76KEVOsxtIBFwCaLupVuk4eFVnOZfU+Wsn+x5Ryam7nILV2pkq2TqQM9EZPsOBuMC+kg==}
- engines: {node: '>=18'}
- cpu: [arm]
- os: [linux]
-
'@esbuild/linux-ia32@0.21.5':
resolution: {integrity: sha512-YvjXDqLRqPDl2dvRODYmmhz4rPeVKYvppfGYKSNGdyZkA01046pLWyRKKI3ax8fbJoK5QbxblURkwK/MWY18Tg==}
engines: {node: '>=12'}
cpu: [ia32]
os: [linux]
- '@esbuild/linux-ia32@0.25.8':
- resolution: {integrity: sha512-A1D9YzRX1i+1AJZuFFUMP1E9fMaYY+GnSQil9Tlw05utlE86EKTUA7RjwHDkEitmLYiFsRd9HwKBPEftNdBfjg==}
- engines: {node: '>=18'}
- cpu: [ia32]
- os: [linux]
-
'@esbuild/linux-loong64@0.21.5':
resolution: {integrity: sha512-uHf1BmMG8qEvzdrzAqg2SIG/02+4/DHB6a9Kbya0XDvwDEKCoC8ZRWI5JJvNdUjtciBGFQ5PuBlpEOXQj+JQSg==}
engines: {node: '>=12'}
cpu: [loong64]
os: [linux]
- '@esbuild/linux-loong64@0.25.8':
- resolution: {integrity: sha512-O7k1J/dwHkY1RMVvglFHl1HzutGEFFZ3kNiDMSOyUrB7WcoHGf96Sh+64nTRT26l3GMbCW01Ekh/ThKM5iI7hQ==}
- engines: {node: '>=18'}
- cpu: [loong64]
- os: [linux]
-
'@esbuild/linux-mips64el@0.21.5':
resolution: {integrity: sha512-IajOmO+KJK23bj52dFSNCMsz1QP1DqM6cwLUv3W1QwyxkyIWecfafnI555fvSGqEKwjMXVLokcV5ygHW5b3Jbg==}
engines: {node: '>=12'}
cpu: [mips64el]
os: [linux]
- '@esbuild/linux-mips64el@0.25.8':
- resolution: {integrity: sha512-uv+dqfRazte3BzfMp8PAQXmdGHQt2oC/y2ovwpTteqrMx2lwaksiFZ/bdkXJC19ttTvNXBuWH53zy/aTj1FgGw==}
- engines: {node: '>=18'}
- cpu: [mips64el]
- os: [linux]
-
'@esbuild/linux-ppc64@0.21.5':
resolution: {integrity: sha512-1hHV/Z4OEfMwpLO8rp7CvlhBDnjsC3CttJXIhBi+5Aj5r+MBvy4egg7wCbe//hSsT+RvDAG7s81tAvpL2XAE4w==}
engines: {node: '>=12'}
cpu: [ppc64]
os: [linux]
- '@esbuild/linux-ppc64@0.25.8':
- resolution: {integrity: sha512-GyG0KcMi1GBavP5JgAkkstMGyMholMDybAf8wF5A70CALlDM2p/f7YFE7H92eDeH/VBtFJA5MT4nRPDGg4JuzQ==}
- engines: {node: '>=18'}
- cpu: [ppc64]
- os: [linux]
-
'@esbuild/linux-riscv64@0.21.5':
resolution: {integrity: sha512-2HdXDMd9GMgTGrPWnJzP2ALSokE/0O5HhTUvWIbD3YdjME8JwvSCnNGBnTThKGEB91OZhzrJ4qIIxk/SBmyDDA==}
engines: {node: '>=12'}
cpu: [riscv64]
os: [linux]
- '@esbuild/linux-riscv64@0.25.8':
- resolution: {integrity: sha512-rAqDYFv3yzMrq7GIcen3XP7TUEG/4LK86LUPMIz6RT8A6pRIDn0sDcvjudVZBiiTcZCY9y2SgYX2lgK3AF+1eg==}
- engines: {node: '>=18'}
- cpu: [riscv64]
- os: [linux]
-
'@esbuild/linux-s390x@0.21.5':
resolution: {integrity: sha512-zus5sxzqBJD3eXxwvjN1yQkRepANgxE9lgOW2qLnmr8ikMTphkjgXu1HR01K4FJg8h1kEEDAqDcZQtbrRnB41A==}
engines: {node: '>=12'}
cpu: [s390x]
os: [linux]
- '@esbuild/linux-s390x@0.25.8':
- resolution: {integrity: sha512-Xutvh6VjlbcHpsIIbwY8GVRbwoviWT19tFhgdA7DlenLGC/mbc3lBoVb7jxj9Z+eyGqvcnSyIltYUrkKzWqSvg==}
- engines: {node: '>=18'}
- cpu: [s390x]
- os: [linux]
-
'@esbuild/linux-x64@0.21.5':
resolution: {integrity: sha512-1rYdTpyv03iycF1+BhzrzQJCdOuAOtaqHTWJZCWvijKD2N5Xu0TtVC8/+1faWqcP9iBCWOmjmhoH94dH82BxPQ==}
engines: {node: '>=12'}
cpu: [x64]
os: [linux]
- '@esbuild/linux-x64@0.25.8':
- resolution: {integrity: sha512-ASFQhgY4ElXh3nDcOMTkQero4b1lgubskNlhIfJrsH5OKZXDpUAKBlNS0Kx81jwOBp+HCeZqmoJuihTv57/jvQ==}
- engines: {node: '>=18'}
- cpu: [x64]
- os: [linux]
-
- '@esbuild/netbsd-arm64@0.25.8':
- resolution: {integrity: sha512-d1KfruIeohqAi6SA+gENMuObDbEjn22olAR7egqnkCD9DGBG0wsEARotkLgXDu6c4ncgWTZJtN5vcgxzWRMzcw==}
- engines: {node: '>=18'}
- cpu: [arm64]
- os: [netbsd]
-
'@esbuild/netbsd-x64@0.21.5':
resolution: {integrity: sha512-Woi2MXzXjMULccIwMnLciyZH4nCIMpWQAs049KEeMvOcNADVxo0UBIQPfSmxB3CWKedngg7sWZdLvLczpe0tLg==}
engines: {node: '>=12'}
cpu: [x64]
os: [netbsd]
- '@esbuild/netbsd-x64@0.25.8':
- resolution: {integrity: sha512-nVDCkrvx2ua+XQNyfrujIG38+YGyuy2Ru9kKVNyh5jAys6n+l44tTtToqHjino2My8VAY6Lw9H7RI73XFi66Cg==}
- engines: {node: '>=18'}
- cpu: [x64]
- os: [netbsd]
-
- '@esbuild/openbsd-arm64@0.25.8':
- resolution: {integrity: sha512-j8HgrDuSJFAujkivSMSfPQSAa5Fxbvk4rgNAS5i3K+r8s1X0p1uOO2Hl2xNsGFppOeHOLAVgYwDVlmxhq5h+SQ==}
- engines: {node: '>=18'}
- cpu: [arm64]
- os: [openbsd]
-
'@esbuild/openbsd-x64@0.21.5':
resolution: {integrity: sha512-HLNNw99xsvx12lFBUwoT8EVCsSvRNDVxNpjZ7bPn947b8gJPzeHWyNVhFsaerc0n3TsbOINvRP2byTZ5LKezow==}
engines: {node: '>=12'}
cpu: [x64]
os: [openbsd]
- '@esbuild/openbsd-x64@0.25.8':
- resolution: {integrity: sha512-1h8MUAwa0VhNCDp6Af0HToI2TJFAn1uqT9Al6DJVzdIBAd21m/G0Yfc77KDM3uF3T/YaOgQq3qTJHPbTOInaIQ==}
- engines: {node: '>=18'}
- cpu: [x64]
- os: [openbsd]
-
- '@esbuild/openharmony-arm64@0.25.8':
- resolution: {integrity: sha512-r2nVa5SIK9tSWd0kJd9HCffnDHKchTGikb//9c7HX+r+wHYCpQrSgxhlY6KWV1nFo1l4KFbsMlHk+L6fekLsUg==}
- engines: {node: '>=18'}
- cpu: [arm64]
- os: [openharmony]
-
- '@esbuild/sunos-x64@0.21.5':
- resolution: {integrity: sha512-6+gjmFpfy0BHU5Tpptkuh8+uw3mnrvgs+dSPQXQOv3ekbordwnzTVEb4qnIvQcYXq6gzkyTnoZ9dZG+D4garKg==}
- engines: {node: '>=12'}
- cpu: [x64]
- os: [sunos]
-
- '@esbuild/sunos-x64@0.25.8':
- resolution: {integrity: sha512-zUlaP2S12YhQ2UzUfcCuMDHQFJyKABkAjvO5YSndMiIkMimPmxA+BYSBikWgsRpvyxuRnow4nS5NPnf9fpv41w==}
- engines: {node: '>=18'}
+ '@esbuild/sunos-x64@0.21.5':
+ resolution: {integrity: sha512-6+gjmFpfy0BHU5Tpptkuh8+uw3mnrvgs+dSPQXQOv3ekbordwnzTVEb4qnIvQcYXq6gzkyTnoZ9dZG+D4garKg==}
+ engines: {node: '>=12'}
cpu: [x64]
os: [sunos]
@@ -662,562 +502,290 @@ packages:
cpu: [arm64]
os: [win32]
- '@esbuild/win32-arm64@0.25.8':
- resolution: {integrity: sha512-YEGFFWESlPva8hGL+zvj2z/SaK+pH0SwOM0Nc/d+rVnW7GSTFlLBGzZkuSU9kFIGIo8q9X3ucpZhu8PDN5A2sQ==}
- engines: {node: '>=18'}
- cpu: [arm64]
- os: [win32]
-
'@esbuild/win32-ia32@0.21.5':
resolution: {integrity: sha512-SWXFF1CL2RVNMaVs+BBClwtfZSvDgtL//G/smwAc5oVK/UPu2Gu9tIaRgFmYFFKrmg3SyAjSrElf0TiJ1v8fYA==}
engines: {node: '>=12'}
cpu: [ia32]
os: [win32]
- '@esbuild/win32-ia32@0.25.8':
- resolution: {integrity: sha512-hiGgGC6KZ5LZz58OL/+qVVoZiuZlUYlYHNAmczOm7bs2oE1XriPFi5ZHHrS8ACpV5EjySrnoCKmcbQMN+ojnHg==}
- engines: {node: '>=18'}
- cpu: [ia32]
- os: [win32]
-
'@esbuild/win32-x64@0.21.5':
resolution: {integrity: sha512-tQd/1efJuzPC6rCFwEvLtci/xNFcTZknmXs98FYDfGE4wP9ClFV98nyKrzJKVPMhdDnjzLhdUyMX4PsQAPjwIw==}
engines: {node: '>=12'}
cpu: [x64]
os: [win32]
- '@esbuild/win32-x64@0.25.8':
- resolution: {integrity: sha512-cn3Yr7+OaaZq1c+2pe+8yxC8E144SReCQjN6/2ynubzYjvyqZjTXfQJpAcQpsdJq3My7XADANiYGHoFC69pLQw==}
- engines: {node: '>=18'}
- cpu: [x64]
- os: [win32]
-
- '@eslint-community/eslint-utils@4.7.0':
- resolution: {integrity: sha512-dyybb3AcajC7uha6CvhdVRJqaKyn7w2YKqKyAN37NKYgZT36w+iRb0Dymmc5qEJ549c/S31cMMSFd75bteCpCw==}
+ '@eslint-community/eslint-utils@4.10.1':
+ resolution: {integrity: sha512-cuadcxVFE8sDK6iWJbs8Sn0av2Nrh2QSGQhVlBW9AaAHqHwjWsZHT8LJ4hFGPh7ASBV2deFdM7H/DPjulmh8rg==}
engines: {node: ^12.22.0 || ^14.17.0 || >=16.0.0}
peerDependencies:
eslint: ^6.0.0 || ^7.0.0 || >=8.0.0
- '@eslint-community/regexpp@4.12.1':
- resolution: {integrity: sha512-CCZCDJuduB9OUkFkY2IgppNZMi2lBQgD2qzwXkEia16cge2pijY/aXi96CJMquDMn3nJdlPV1A5KrJEXwfLNzQ==}
+ '@eslint-community/regexpp@4.12.2':
+ resolution: {integrity: sha512-EriSTlt5OC9/7SXkRSCAhfSxxoSUgBm33OH+IkwbdpgoqsSsUg7y3uh+IICI/Qg4BBWr3U2i39RpmycbxMq4ew==}
engines: {node: ^12.0.0 || ^14.0.0 || >=16.0.0}
- '@eslint/config-array@0.20.1':
- resolution: {integrity: sha512-OL0RJzC/CBzli0DrrR31qzj6d6i6Mm3HByuhflhl4LOBiWxN+3i6/t/ZQQNii4tjksXi8r2CRW1wMpWA2ULUEw==}
- engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
-
- '@eslint/config-helpers@0.2.3':
- resolution: {integrity: sha512-u180qk2Um1le4yf0ruXH3PYFeEZeYC3p/4wCTKrr2U1CmGdzGi3KtY0nuPDH48UJxlKCC5RDzbcbh4X0XlqgHg==}
- engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
-
- '@eslint/core@0.14.0':
- resolution: {integrity: sha512-qIbV0/JZr7iSDjqAc60IqbLdsj9GDt16xQtWD+B78d/HAlvysGdZZ6rpJHGAc2T0FQx1X6thsSPdnoiGKdNtdg==}
- engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
-
- '@eslint/core@0.15.1':
- resolution: {integrity: sha512-bkOp+iumZCCbt1K1CmWf0R9pM5yKpDv+ZXtvSyQpudrI9kuFLp+bM2WOPXImuD/ceQuaa8f5pj93Y7zyECIGNA==}
- engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
-
- '@eslint/eslintrc@3.3.1':
- resolution: {integrity: sha512-gtF186CXhIl1p4pJNGZw8Yc6RlshoePRvE0X91oPGb3vZ8pM3qOS9W9NGPat9LziaBV7XrJWGylNQXkGcnM3IQ==}
- engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
-
- '@eslint/js@9.29.0':
- resolution: {integrity: sha512-3PIF4cBw/y+1u2EazflInpV+lYsSG0aByVIQzAgb1m1MhHFSbqTyNqtBKHgWf/9Ykud+DhILS9EGkmekVhbKoQ==}
- engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
+ '@eslint/config-array@0.23.5':
+ resolution: {integrity: sha512-Y3kKLvC1dvTOT+oGlqNQ1XLqK6D1HU2YXPc52NmAlJZbMMWDzGYXMiPRJ8TYD39muD/OTjlZmNJ4ib7dvSrMBA==}
+ engines: {node: ^20.19.0 || ^22.13.0 || >=24}
- '@eslint/object-schema@2.1.6':
- resolution: {integrity: sha512-RBMg5FRL0I0gs51M/guSAj5/e14VQ4tpZnQNWwuDT66P14I43ItmPfIZRhO9fUVIPOAQXU47atlywZ/czoqFPA==}
- engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
+ '@eslint/config-helpers@0.7.0':
+ resolution: {integrity: sha512-DObd/KKUsU+FaFv4PLxSRenpXfQWmPXXP3pPZ6/K1PCrMu2vQpMDMuQe/BqYeoLcz8ro0bVDF1RxOJgfVEdhUw==}
+ engines: {node: ^20.19.0 || ^22.13.0 || >=24}
- '@eslint/plugin-kit@0.3.3':
- resolution: {integrity: sha512-1+WqvgNMhmlAambTvT3KPtCl/Ibr68VldY2XY40SL1CE0ZXiakFR/cbTspaF5HsnpDMvcYYoJHfl4980NBjGag==}
- engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
+ '@eslint/core@1.2.1':
+ resolution: {integrity: sha512-MwcE1P+AZ4C6DWlpin/OmOA54mmIZ/+xZuJiQd4SyB29oAJjN30UW9wkKNptW2ctp4cEsvhlLY/CsQ1uoHDloQ==}
+ engines: {node: ^20.19.0 || ^22.13.0 || >=24}
- '@floating-ui/core@1.7.2':
- resolution: {integrity: sha512-wNB5ooIKHQc+Kui96jE/n69rHFWAVoxn5CAzL1Xdd8FG03cgY3MLO+GF9U3W737fYDSgPWA6MReKhBQBop6Pcw==}
+ '@eslint/js@10.0.1':
+ resolution: {integrity: sha512-zeR9k5pd4gxjZ0abRoIaxdc7I3nDktoXZk2qOv9gCNWx3mVwEn32VRhyLaRsDiJjTs0xq/T8mfPtyuXu7GWBcA==}
+ engines: {node: ^20.19.0 || ^22.13.0 || >=24}
+ peerDependencies:
+ eslint: ^10.0.0
+ peerDependenciesMeta:
+ eslint:
+ optional: true
- '@floating-ui/dom@1.1.1':
- resolution: {integrity: sha512-TpIO93+DIujg3g7SykEAGZMDtbJRrmnYRCNYSjJlvIbGhBjRSNTLVbNeDQBrzy9qDgUbiWdc7KA0uZHZ2tJmiw==}
+ '@eslint/object-schema@3.0.5':
+ resolution: {integrity: sha512-vqTaUEgxzm+YDSdElad6PiRoX4t8VGDjCtt05zn4nU810UIx/uNEV7/lZJ6KwFThKZOzOxzXy48da+No7HZaMw==}
+ engines: {node: ^20.19.0 || ^22.13.0 || >=24}
- '@floating-ui/utils@0.2.10':
- resolution: {integrity: sha512-aGTxbpbg8/b5JfU1HXSrbH3wXZuLPJcNEcZQFMxLs3oSzgtVu6nFPkbbGGUvBcUjKV2YyB9Wxxabo+HEH9tcRQ==}
+ '@eslint/plugin-kit@0.7.3':
+ resolution: {integrity: sha512-IkO+/KEUvwbVpiURZg+P7zF74z5Jxe0UgJxVni+RtoHQ6IZieXaO02kmadomap/q+l6bc/jdPGGqTjhuZnuz1Q==}
+ engines: {node: ^20.19.0 || ^22.13.0 || >=24}
'@giscus/vue@3.1.1':
resolution: {integrity: sha512-xgsc93MibRQ0d1glBxN1BrEREHTIf3BPYs/3R+UZHNqawFFoWBV6iJ7uVCXMqoEKZdE2c78B3aKt5gfGqo8I5A==}
peerDependencies:
vue: '>=3.2.0'
- '@humanfs/core@0.19.1':
- resolution: {integrity: sha512-5DyQ4+1JEUzejeK1JGICcideyfUbGixgS9jNgex5nqkW+cY7WZhxBigmieN5Qnw9ZosSNVC9KQKyb+GUaGyKUA==}
+ '@humanfs/core@0.19.2':
+ resolution: {integrity: sha512-UhXNm+CFMWcbChXywFwkmhqjs3PRCmcSa/hfBgLIb7oQ5HNb1wS0icWsGtSAUNgefHeI+eBrA8I1fxmbHsGdvA==}
+ engines: {node: '>=18.18.0'}
+
+ '@humanfs/node@0.16.8':
+ resolution: {integrity: sha512-gE1eQNZ3R++kTzFUpdGlpmy8kDZD/MLyHqDwqjkVQI0JMdI1D51sy1H958PNXYkM2rAac7e5/CnIKZrHtPh3BQ==}
engines: {node: '>=18.18.0'}
- '@humanfs/node@0.16.6':
- resolution: {integrity: sha512-YuI2ZHQL78Q5HbhDiBA1X4LmYdXCKCMQIfw0pw7piHJwyREFebJUvrQN4cMssyES6x+vfUbx1CIpaQUKYdQZOw==}
+ '@humanfs/types@0.15.0':
+ resolution: {integrity: sha512-ZZ1w0aoQkwuUuC7Yf+7sdeaNfqQiiLcSRbfI08oAxqLtpXQr9AIVX7Ay7HLDuiLYAaFPu8oBYNq/QIi9URHJ3Q==}
engines: {node: '>=18.18.0'}
'@humanwhocodes/module-importer@1.0.1':
resolution: {integrity: sha512-bxveV4V8v5Yb4ncFTT3rPSgZBOpCkjfK0y4oVVVJwIuDVBRMDXrPyXRL988i5ap9m9bnyEEjWfm5WkBmtffLfA==}
engines: {node: '>=12.22'}
- '@humanwhocodes/retry@0.3.1':
- resolution: {integrity: sha512-JBxkERygn7Bv/GbN5Rv8Ul6LVknS+5Bp6RgDC/O8gEBU/yeH5Ui5C/OlWrTb6qct7LjjfT6Re2NxB0ln0yYybA==}
- engines: {node: '>=18.18'}
-
'@humanwhocodes/retry@0.4.3':
resolution: {integrity: sha512-bV0Tgo9K4hfPCek+aMAn81RppFKv2ySDQeMoSZuvTASywNTnVJCArCZE2FWqpvIatKu7VMRLWlR1EazvVhDyhQ==}
engines: {node: '>=18.18'}
- '@iconify-json/carbon@1.2.9':
- resolution: {integrity: sha512-RyeSAuFTzhs1GX4yrzVEKEbNQGt95p9zMR4S2F63vbThtNoUr5OKwaWbhO/GbHQCSgdbKuZv2ApAOsY2fLxLbQ==}
-
- '@iconify-json/devicon-plain@1.2.31':
- resolution: {integrity: sha512-c4j4UiGXGflMJ4Ek/SOsix7U1CZG6kJu8xEZIR51vJMUxJeZC0WvZKJ4/kc4skP4l7vSN1quHcUv+zcAQ+V+AA==}
-
- '@iconify-json/devicon@1.2.32':
- resolution: {integrity: sha512-dFBGujAmK7XRAEXSd1rZ9ymv8Vu8F0tvYbgb+IdSA25L7hqXQACPvwKlIfj6/16hAzx3FhfUHvtrbsL62/G6jw==}
+ '@iconify-json/logos@1.2.14':
+ resolution: {integrity: sha512-O36DicXkgAMT6NAsH7MTWlOql8NktHz9fBCItTjz6L/9gyRXw4vQj6qTeVgww5UZWiVugUV1MhVFA/g9HWIkBw==}
- '@iconify-json/logos@1.2.4':
- resolution: {integrity: sha512-XC4If5D/hbaZvUkTV8iaZuGlQCyG6CNOlaAaJaGa13V5QMYwYjgtKk3vPP8wz3wtTVNVEVk3LRx1fOJz+YnSMw==}
+ '@iconify-json/simple-icons@1.2.97':
+ resolution: {integrity: sha512-Z6PmM6jvWVU7rmLzqbxCLJA7SeqCnK6lMHXtjyzHPLZebwuoojBEcHHycppahDzEeN9xujRkrV5J8QpOhMyNrg==}
- '@iconify-json/ri@1.2.5':
- resolution: {integrity: sha512-kWGimOXMZrlYusjBKKXYOWcKhbOHusFsmrmRGmjS7rH0BpML5A9/fy8KHZqFOwZfC4M6amObQYbh8BqO5cMC3w==}
-
- '@iconify-json/simple-icons@1.2.39':
- resolution: {integrity: sha512-XlhW73c4dHvUrwWckVY76HDjnaZ2fWKD6hNZtd5kuv23GC0g3Lu0MXnYscpkIYOeiXO+Gtlw8FM53J7C84mCtA==}
-
- '@iconify-json/vscode-icons@1.2.23':
- resolution: {integrity: sha512-gFTcKecKra2/b5SbGDgHGI/l8CuikHyBPmqGlK+YCmS8AK72dtDQbUekdoACsju/3TYS37QvdPoOQwnyx2LdYg==}
+ '@iconify-json/vscode-icons@1.2.81':
+ resolution: {integrity: sha512-ES/vVycj4IVC7TK8t+9T4Gnca9p/GbuL8A2Va+xWi01HGpyRCrXdRvKAUE8VcQbTkZsfy6Fv0L6TXq9eFj5+Yw==}
'@iconify/types@2.0.0':
resolution: {integrity: sha512-+wluvCrRhXrhyOmRDJ3q8mux9JkKy5SJ/v8ol2tu4FVjyYvtEzkc/3pK15ET6RKg4b4w4BmTk1+gsCUhf21Ykg==}
- '@iconify/utils@2.3.0':
- resolution: {integrity: sha512-GmQ78prtwYW6EtzXRU1rY+KwOKfz32PD7iJh6Iyqw68GiKuoZ2A6pRtzWONz5VQJbp50mEjXh/7NkumtrAgRKA==}
-
- '@intlify/bundle-utils@10.0.1':
- resolution: {integrity: sha512-WkaXfSevtpgtUR4t8K2M6lbR7g03mtOxFeh+vXp5KExvPqS12ppaRj1QxzwRuRI5VUto54A22BjKoBMLyHILWQ==}
- engines: {node: '>= 18'}
- peerDependencies:
- petite-vue-i18n: '*'
- vue-i18n: '*'
- peerDependenciesMeta:
- petite-vue-i18n:
- optional: true
- vue-i18n:
- optional: true
-
- '@intlify/core-base@11.1.10':
- resolution: {integrity: sha512-JhRb40hD93Vk0BgMgDc/xMIFtdXPHoytzeK6VafBNOj6bb6oUZrGamXkBKecMsmGvDQQaPRGG2zpa25VCw8pyw==}
- engines: {node: '>= 16'}
-
- '@intlify/message-compiler@11.1.10':
- resolution: {integrity: sha512-TABl3c8tSLWbcD+jkQTyBhrnW251dzqW39MPgEUCsd69Ua3ceoimsbIzvkcPzzZvt1QDxNkenMht+5//V3JvLQ==}
- engines: {node: '>= 16'}
-
- '@intlify/shared@11.1.10':
- resolution: {integrity: sha512-6ZW/f3Zzjxfa1Wh0tYQI5pLKUtU+SY7l70pEG+0yd0zjcsYcK0EBt6Fz30Dy0tZhEqemziQQy2aNU3GJzyrMUA==}
- engines: {node: '>= 16'}
-
- '@intlify/unplugin-vue-i18n@6.0.8':
- resolution: {integrity: sha512-Vvm3KhjE6TIBVUQAk37rBiaYy2M5OcWH0ZcI1XKEsOTeN1o0bErk+zeuXmcrcMc/73YggfI8RoxOUz9EB/69JQ==}
- engines: {node: '>= 18'}
- peerDependencies:
- petite-vue-i18n: '*'
- vue: ^3.2.25
- vue-i18n: '*'
- peerDependenciesMeta:
- petite-vue-i18n:
- optional: true
- vue-i18n:
- optional: true
-
- '@intlify/vue-i18n-extensions@8.0.0':
- resolution: {integrity: sha512-w0+70CvTmuqbskWfzeYhn0IXxllr6mU+IeM2MU0M+j9OW64jkrvqY+pYFWrUnIIC9bEdij3NICruicwd5EgUuQ==}
- engines: {node: '>= 18'}
- peerDependencies:
- '@intlify/shared': ^9.0.0 || ^10.0.0 || ^11.0.0
- '@vue/compiler-dom': ^3.0.0
- vue: ^3.0.0
- vue-i18n: ^9.0.0 || ^10.0.0 || ^11.0.0
- peerDependenciesMeta:
- '@intlify/shared':
- optional: true
- '@vue/compiler-dom':
- optional: true
- vue:
- optional: true
- vue-i18n:
- optional: true
-
- '@jridgewell/gen-mapping@0.3.12':
- resolution: {integrity: sha512-OuLGC46TjB5BbN1dH8JULVVZY4WTdkF7tV9Ys6wLL1rubZnCMstOhNHueU5bLCrnRuDhKPDM4g6sw4Bel5Gzqg==}
-
- '@jridgewell/resolve-uri@3.1.2':
- resolution: {integrity: sha512-bRISgCIjP20/tbWSPWMEi54QVPRZExkuD9lJL+UIxUKtwVJA8wW1Trb1jMs1RFXo1CBTNZ/5hpC9QvmKWdopKw==}
- engines: {node: '>=6.0.0'}
-
- '@jridgewell/source-map@0.3.10':
- resolution: {integrity: sha512-0pPkgz9dY+bijgistcTTJ5mR+ocqRXLuhXHYdzoMmmoJ2C9S46RCm2GMUbatPEUK9Yjy26IrAy8D/M00lLkv+Q==}
-
- '@jridgewell/sourcemap-codec@1.5.4':
- resolution: {integrity: sha512-VT2+G1VQs/9oz078bLrYbecdZKs912zQlkelYpuf+SXF+QvZDYJlbx/LSx+meSAwdDFnF8FVXW92AVjjkVmgFw==}
-
- '@jridgewell/trace-mapping@0.3.29':
- resolution: {integrity: sha512-uw6guiW/gcAGPDhLmd77/6lW8QLeiV5RUTsAX46Db6oLhGaVj4lhnPwb184s1bkc8kdVg/+h988dro8GRDpmYQ==}
-
- '@kwsites/file-exists@1.1.1':
- resolution: {integrity: sha512-m9/5YGR18lIwxSFDwfE3oA7bWuq9kdau6ugN4H2rJeyhFQZcG9AgSHkQtSD15a8WvTgfz9aikZMrKPHvbpqFiw==}
-
- '@kwsites/promise-deferred@1.1.1':
- resolution: {integrity: sha512-GaHYm+c0O9MjZRu0ongGBRbinu8gVAMd2UZjji6jVmqKtZluZnptXGWhz1E8j8D2HJ3f/yMxKAUC0b+57wncIw==}
-
- '@lit-labs/ssr-dom-shim@1.4.0':
- resolution: {integrity: sha512-ficsEARKnmmW5njugNYKipTm4SFnbik7CXtoencDZzmzo/dQ+2Q0bgkzJuoJP20Aj0F+izzJjOqsnkd6F/o1bw==}
-
- '@lit/reactive-element@2.1.1':
- resolution: {integrity: sha512-N+dm5PAYdQ8e6UlywyyrgI2t++wFGXfHx+dSJ1oBrg6FAxUj40jId++EaRm80MKX5JnlH1sBsyZ5h0bcZKemCg==}
-
- '@mdit-vue/plugin-component@2.1.4':
- resolution: {integrity: sha512-fiLbwcaE6gZE4c8Mkdkc4X38ltXh/EdnuPE1hepFT2dLiW6I4X8ho2Wq7nhYuT8RmV4OKlCFENwCuXlKcpV/sw==}
-
- '@mdit-vue/plugin-frontmatter@2.1.4':
- resolution: {integrity: sha512-mOlavV176njnozIf0UZGFYymmQ2LK5S1rjrbJ1uGz4Df59tu0DQntdE7YZXqmJJA9MiSx7ViCTUQCNPKg7R8Ow==}
-
- '@mdit-vue/types@2.1.4':
- resolution: {integrity: sha512-QiGNZslz+zXUs2X8D11UQhB4KAMZ0DZghvYxa7+1B+VMLcDtz//XHpWbcuexjzE3kBXSxIUTPH3eSQCa0puZHA==}
-
- '@mermaid-js/parser@0.6.2':
- resolution: {integrity: sha512-+PO02uGF6L6Cs0Bw8RpGhikVvMWEysfAyl27qTlroUB8jSWr1lL0Sf6zi78ZxlSnmgSY2AMMKVgghnN9jTtwkQ==}
-
- '@nodelib/fs.scandir@2.1.5':
- resolution: {integrity: sha512-vq24Bq3ym5HEQm2NKCr3yXDwjc7vTsEThRDnkp2DK9p1uqLR+DHurm/NOTo0KG7HYHU7eppKZj3MyqYuMBf62g==}
- engines: {node: '>= 8'}
-
- '@nodelib/fs.stat@2.0.5':
- resolution: {integrity: sha512-RkhPPp2zrqDAQA/2jNhnztcPAlv64XdhIp7a7454A5ovI7Bukxgt7MX7udwAu3zg1DcpPU0rz3VV1SeaqvY4+A==}
- engines: {node: '>= 8'}
-
- '@nodelib/fs.walk@1.2.8':
- resolution: {integrity: sha512-oGB+UxlgWcgQkgwo8GcEGwemoTFt3FIO9ababBmaGwXIoBKZ+GTy0pP185beGg7Llih/NSHSV2XAs1lnznocSg==}
- engines: {node: '>= 8'}
-
- '@octokit/auth-token@5.1.2':
- resolution: {integrity: sha512-JcQDsBdg49Yky2w2ld20IHAlwr8d/d8N6NiOXbtuoPCqzbsiJgF633mVUw3x4mo0H5ypataQIX7SFu3yy44Mpw==}
- engines: {node: '>= 18'}
-
- '@octokit/core@6.1.6':
- resolution: {integrity: sha512-kIU8SLQkYWGp3pVKiYzA5OSaNF5EE03P/R8zEmmrG6XwOg5oBjXyQVVIauQ0dgau4zYhpZEhJrvIYt6oM+zZZA==}
- engines: {node: '>= 18'}
-
- '@octokit/endpoint@10.1.4':
- resolution: {integrity: sha512-OlYOlZIsfEVZm5HCSR8aSg02T2lbUWOsCQoPKfTXJwDzcHQBrVBGdGXb89dv2Kw2ToZaRtudp8O3ZIYoaOjKlA==}
- engines: {node: '>= 18'}
-
- '@octokit/graphql@8.2.2':
- resolution: {integrity: sha512-Yi8hcoqsrXGdt0yObxbebHXFOiUA+2v3n53epuOg1QUgOB6c4XzvisBNVXJSl8RYA5KrDuSL2yq9Qmqe5N0ryA==}
- engines: {node: '>= 18'}
-
- '@octokit/openapi-types@24.2.0':
- resolution: {integrity: sha512-9sIH3nSUttelJSXUrmGzl7QUBFul0/mB8HRYl3fOlgHbIWG+WnYDXU3v/2zMtAvuzZ/ed00Ei6on975FhBfzrg==}
+ '@iconify/utils@3.1.7':
+ resolution: {integrity: sha512-JZHlwdID+dy+lTgbYC8NEC4zeugqeYsc6jewvzb4c58kHauJn+X7rNwQjxz5p2qSjqaEeQoLkCIQ9v/H4PK0/w==}
- '@octokit/openapi-types@25.1.0':
- resolution: {integrity: sha512-idsIggNXUKkk0+BExUn1dQ92sfysJrje03Q0bv0e+KPLrvyqZF8MnBpFz8UNfYDwB3Ie7Z0TByjWfzxt7vseaA==}
+ '@jridgewell/sourcemap-codec@1.6.0':
+ resolution: {integrity: sha512-T7jf+5zgsZHwNJ4lvQ7/aezbyk0nNX+zJVWpmHA7VYsEx7a7qr5Rg5IbtJFqkgze5Y2sruq1RUY8Q837Od7iFw==}
- '@octokit/plugin-paginate-rest@11.6.0':
- resolution: {integrity: sha512-n5KPteiF7pWKgBIBJSk8qzoZWcUkza2O6A0za97pMGVrGfPdltxrfmfF5GucHYvHGZD8BdaZmmHGz5cX/3gdpw==}
+ '@keyv/bigmap@1.3.1':
+ resolution: {integrity: sha512-WbzE9sdmQtKy8vrNPa9BRnwZh5UF4s1KTmSK0KUVLo3eff5BlQNNWDnFOouNpKfPKDnms9xynJjsMYjMaT/aFQ==}
engines: {node: '>= 18'}
peerDependencies:
- '@octokit/core': '>=6'
-
- '@octokit/plugin-request-log@5.3.1':
- resolution: {integrity: sha512-n/lNeCtq+9ofhC15xzmJCNKP2BWTv8Ih2TTy+jatNCCq/gQP/V7rK3fjIfuz0pDWDALO/o/4QY4hyOF6TQQFUw==}
- engines: {node: '>= 18'}
- peerDependencies:
- '@octokit/core': '>=6'
-
- '@octokit/plugin-rest-endpoint-methods@13.5.0':
- resolution: {integrity: sha512-9Pas60Iv9ejO3WlAX3maE1+38c5nqbJXV5GrncEfkndIpZrJ/WPMRd2xYDcPPEt5yzpxcjw9fWNoPhsSGzqKqw==}
- engines: {node: '>= 18'}
- peerDependencies:
- '@octokit/core': '>=6'
-
- '@octokit/request-error@6.1.8':
- resolution: {integrity: sha512-WEi/R0Jmq+IJKydWlKDmryPcmdYSVjL3ekaiEL1L9eo1sUnqMJ+grqmC9cjk7CA7+b2/T397tO5d8YLOH3qYpQ==}
- engines: {node: '>= 18'}
-
- '@octokit/request@9.2.4':
- resolution: {integrity: sha512-q8ybdytBmxa6KogWlNa818r0k1wlqzNC+yNkcQDECHvQo8Vmstrg18JwqJHdJdUiHD2sjlwBgSm9kHkOKe2iyA==}
- engines: {node: '>= 18'}
-
- '@octokit/rest@21.1.1':
- resolution: {integrity: sha512-sTQV7va0IUVZcntzy1q3QqPm/r8rWtDCqpRAmb8eXXnKkjoQEtFe3Nt5GTVsHft+R6jJoHeSiVLcgcvhtue/rg==}
- engines: {node: '>= 18'}
-
- '@octokit/types@13.10.0':
- resolution: {integrity: sha512-ifLaO34EbbPj0Xgro4G5lP5asESjwHracYJvVaPIyXMuiuXLlhic3S47cBdTb+jfODkTE5YtGCLt3Ay3+J97sA==}
-
- '@octokit/types@14.1.0':
- resolution: {integrity: sha512-1y6DgTy8Jomcpu33N+p5w58l6xyt55Ar2I91RPiIA0xCJBXyUAhXCcmZaDWSANiha7R9a6qJJ2CRomGPZ6f46g==}
-
- '@parcel/watcher-android-arm64@2.5.1':
- resolution: {integrity: sha512-KF8+j9nNbUN8vzOFDpRMsaKBHZ/mcjEjMToVMJOhTozkDonQFFrRcfdLWn6yWKCmJKmdVxSgHiYvTCef4/qcBA==}
- engines: {node: '>= 10.0.0'}
- cpu: [arm64]
- os: [android]
-
- '@parcel/watcher-darwin-arm64@2.5.1':
- resolution: {integrity: sha512-eAzPv5osDmZyBhou8PoF4i6RQXAfeKL9tjb3QzYuccXFMQU0ruIc/POh30ePnaOyD1UXdlKguHBmsTs53tVoPw==}
- engines: {node: '>= 10.0.0'}
- cpu: [arm64]
- os: [darwin]
-
- '@parcel/watcher-darwin-x64@2.5.1':
- resolution: {integrity: sha512-1ZXDthrnNmwv10A0/3AJNZ9JGlzrF82i3gNQcWOzd7nJ8aj+ILyW1MTxVk35Db0u91oD5Nlk9MBiujMlwmeXZg==}
- engines: {node: '>= 10.0.0'}
- cpu: [x64]
- os: [darwin]
-
- '@parcel/watcher-freebsd-x64@2.5.1':
- resolution: {integrity: sha512-SI4eljM7Flp9yPuKi8W0ird8TI/JK6CSxju3NojVI6BjHsTyK7zxA9urjVjEKJ5MBYC+bLmMcbAWlZ+rFkLpJQ==}
- engines: {node: '>= 10.0.0'}
- cpu: [x64]
- os: [freebsd]
-
- '@parcel/watcher-linux-arm-glibc@2.5.1':
- resolution: {integrity: sha512-RCdZlEyTs8geyBkkcnPWvtXLY44BCeZKmGYRtSgtwwnHR4dxfHRG3gR99XdMEdQ7KeiDdasJwwvNSF5jKtDwdA==}
- engines: {node: '>= 10.0.0'}
- cpu: [arm]
- os: [linux]
+ keyv: ^5.6.0
- '@parcel/watcher-linux-arm-musl@2.5.1':
- resolution: {integrity: sha512-6E+m/Mm1t1yhB8X412stiKFG3XykmgdIOqhjWj+VL8oHkKABfu/gjFj8DvLrYVHSBNC+/u5PeNrujiSQ1zwd1Q==}
- engines: {node: '>= 10.0.0'}
- cpu: [arm]
- os: [linux]
+ '@keyv/serialize@1.1.1':
+ resolution: {integrity: sha512-dXn3FZhPv0US+7dtJsIi2R+c7qWYiReoEh5zUntWCf4oSpMNib8FDhSoed6m3QyZdx5hK7iLFkYk3rNxwt8vTA==}
- '@parcel/watcher-linux-arm64-glibc@2.5.1':
- resolution: {integrity: sha512-LrGp+f02yU3BN9A+DGuY3v3bmnFUggAITBGriZHUREfNEzZh/GO06FF5u2kx8x+GBEUYfyTGamol4j3m9ANe8w==}
- engines: {node: '>= 10.0.0'}
- cpu: [arm64]
- os: [linux]
+ '@lit-labs/ssr-dom-shim@1.6.0':
+ resolution: {integrity: sha512-VHb0ALPMTlgKjM6yIxxoQNnpKyUKLD04VzeQdsiXkMqkvYlAHxq9glGLmgbb889/1GsohSOAjvQYoiBppXFqrQ==}
- '@parcel/watcher-linux-arm64-musl@2.5.1':
- resolution: {integrity: sha512-cFOjABi92pMYRXS7AcQv9/M1YuKRw8SZniCDw0ssQb/noPkRzA+HBDkwmyOJYp5wXcsTrhxO0zq1U11cK9jsFg==}
- engines: {node: '>= 10.0.0'}
- cpu: [arm64]
- os: [linux]
+ '@lit/reactive-element@2.1.2':
+ resolution: {integrity: sha512-pbCDiVMnne1lYUIaYNN5wrwQXDtHaYtg7YEFPeW+hws6U47WeFvISGUWekPGKWOP1ygrs0ef0o1VJMk1exos5A==}
- '@parcel/watcher-linux-x64-glibc@2.5.1':
- resolution: {integrity: sha512-GcESn8NZySmfwlTsIur+49yDqSny2IhPeZfXunQi48DMugKeZ7uy1FX83pO0X22sHntJ4Ub+9k34XQCX+oHt2A==}
- engines: {node: '>= 10.0.0'}
- cpu: [x64]
- os: [linux]
+ '@mermaid-js/parser@2.0.0':
+ resolution: {integrity: sha512-K8BeapFUfrfxbRAUQAG5oBOCwo1+bNWzaVnPxTCutkfrTBn6T/j91FIhqxWJ32SUeQ9T3iy1zcmPZ5ROZEvDrg==}
+ engines: {node: '>=22.12.0'}
- '@parcel/watcher-linux-x64-musl@2.5.1':
- resolution: {integrity: sha512-n0E2EQbatQ3bXhcH2D1XIAANAcTZkQICBPVaxMeaCVBtOpBZpWJuf7LwyWPSBDITb7In8mqQgJ7gH8CILCURXg==}
- engines: {node: '>= 10.0.0'}
+ '@napi-rs/lzma-linux-x64-gnu@1.5.1':
+ resolution: {integrity: sha512-oTXEIha4SsuXdTA4Iyskj0kpdx2yVXdhd75c2v3xGrHFfVMsbhTPZU/nMPL4sWKo4pBHm3aucLaqGlF696dTyQ==}
+ engines: {node: ^22.20 || ^24.12 || >=25}
cpu: [x64]
os: [linux]
+ libc: [glibc]
- '@parcel/watcher-win32-arm64@2.5.1':
- resolution: {integrity: sha512-RFzklRvmc3PkjKjry3hLF9wD7ppR4AKcWNzH7kXR7GUe0Igb3Nz8fyPwtZCSquGrhU5HhUNDr/mKBqj7tqA2Vw==}
- engines: {node: '>= 10.0.0'}
- cpu: [arm64]
- os: [win32]
-
- '@parcel/watcher-win32-ia32@2.5.1':
- resolution: {integrity: sha512-c2KkcVN+NJmuA7CGlaGD1qJh1cLfDnQsHjE89E60vUEMlqduHGCdCLJCID5geFVM0dOtA3ZiIO8BoEQmzQVfpQ==}
- engines: {node: '>= 10.0.0'}
- cpu: [ia32]
- os: [win32]
-
- '@parcel/watcher-win32-x64@2.5.1':
- resolution: {integrity: sha512-9lHBdJITeNR++EvSQVUcaZoWupyHfXe1jZvGZ06O/5MflPcuPLtEphScIBL+AiCWBO46tDSHzWyD0uDmmZqsgA==}
- engines: {node: '>= 10.0.0'}
- cpu: [x64]
- os: [win32]
-
- '@parcel/watcher@2.5.1':
- resolution: {integrity: sha512-dfUnCxiN9H4ap84DvD2ubjw+3vUNpstxa0TneY/Paat8a3R4uQZDLSvWjmznAY/DoahqTHl9V46HF/Zs3F29pg==}
- engines: {node: '>= 10.0.0'}
-
- '@polka/url@1.0.0-next.29':
- resolution: {integrity: sha512-wwQAWhWSuHaag8c4q/KN/vCoeOJYshAIvMQwD4GpSb3OiZklFfvAgmj0VCBBImRpuF/aFgIRzllXlVX93Jevww==}
-
- '@quansync/fs@0.1.3':
- resolution: {integrity: sha512-G0OnZbMWEs5LhDyqy2UL17vGhSVHkQIfVojMtEWVenvj0V5S84VBgy86kJIuNsGDp2p7sTKlpSIpBUWdC35OKg==}
- engines: {node: '>=20.0.0'}
-
- '@rolldown/pluginutils@1.0.0-beta.19':
- resolution: {integrity: sha512-3FL3mnMbPu0muGOCaKAhhFEYmqv9eTfPSJRJmANrCwtgK8VuxpsZDGK+m0LYAGoyO8+0j5uRe4PeyPDK1yA/hA==}
-
- '@rollup/pluginutils@5.2.0':
- resolution: {integrity: sha512-qWJ2ZTbmumwiLFomfzTyt5Kng4hwPi9rwCYN4SHb6eaRU1KNO4ccxINHr/VhH4GgPlt1XfSTLX2LBTme8ne4Zw==}
- engines: {node: '>=14.0.0'}
- peerDependencies:
- rollup: ^1.20.0||^2.0.0||^3.0.0||^4.0.0
- peerDependenciesMeta:
- rollup:
- optional: true
-
- '@rollup/rollup-android-arm-eabi@4.45.1':
- resolution: {integrity: sha512-NEySIFvMY0ZQO+utJkgoMiCAjMrGvnbDLHvcmlA33UXJpYBCvlBEbMMtV837uCkS+plG2umfhn0T5mMAxGrlRA==}
+ '@rollup/rollup-android-arm-eabi@4.63.5':
+ resolution: {integrity: sha512-J25QJU+B78T4FhhBsNpLJyVWOi31mwtpcMwywHmOKH65Q9IWGA81gPj+dnwlhU8wktVriYE+tFAaQgrnJRzAZg==}
cpu: [arm]
os: [android]
- '@rollup/rollup-android-arm64@4.45.1':
- resolution: {integrity: sha512-ujQ+sMXJkg4LRJaYreaVx7Z/VMgBBd89wGS4qMrdtfUFZ+TSY5Rs9asgjitLwzeIbhwdEhyj29zhst3L1lKsRQ==}
+ '@rollup/rollup-android-arm64@4.63.5':
+ resolution: {integrity: sha512-LDopB3zuZM5Ux9TT2luNEBJW/tYbGU2g1d+VpKk6I+gSKDb+/7sYE6M225gRQt4RbMX6MSwMsVR/phdjVUgRLg==}
cpu: [arm64]
os: [android]
- '@rollup/rollup-darwin-arm64@4.45.1':
- resolution: {integrity: sha512-FSncqHvqTm3lC6Y13xncsdOYfxGSLnP+73k815EfNmpewPs+EyM49haPS105Rh4aF5mJKywk9X0ogzLXZzN9lA==}
+ '@rollup/rollup-darwin-arm64@4.63.5':
+ resolution: {integrity: sha512-wlJEERGfeuHeBavCL2qVnNacOK43NDoZM4sjkeRPymd04OAE9T1zBqDJgmZ+CIsPTYKwdzpUC8vmOw84dwY4Tg==}
cpu: [arm64]
os: [darwin]
- '@rollup/rollup-darwin-x64@4.45.1':
- resolution: {integrity: sha512-2/vVn/husP5XI7Fsf/RlhDaQJ7x9zjvC81anIVbr4b/f0xtSmXQTFcGIQ/B1cXIYM6h2nAhJkdMHTnD7OtQ9Og==}
+ '@rollup/rollup-darwin-x64@4.63.5':
+ resolution: {integrity: sha512-4nJJGg5jbo2wwPP4JP+LfEBA3bvP8rU9CLuhp7jWvq9sxEyhjQFTFdrqi+/dHEin/pd8jpT0vcehIpnZtmEdcQ==}
cpu: [x64]
os: [darwin]
- '@rollup/rollup-freebsd-arm64@4.45.1':
- resolution: {integrity: sha512-4g1kaDxQItZsrkVTdYQ0bxu4ZIQ32cotoQbmsAnW1jAE4XCMbcBPDirX5fyUzdhVCKgPcrwWuucI8yrVRBw2+g==}
+ '@rollup/rollup-freebsd-arm64@4.63.5':
+ resolution: {integrity: sha512-DrZbyCDF1hneuO6jRbvZ2D7+PIBM6yIwYnJpg2vIk58T+wuFpiaGZrfUr59lDWw45bg+IrpTGLPiNi/Fk4w3Cg==}
cpu: [arm64]
os: [freebsd]
- '@rollup/rollup-freebsd-x64@4.45.1':
- resolution: {integrity: sha512-L/6JsfiL74i3uK1Ti2ZFSNsp5NMiM4/kbbGEcOCps99aZx3g8SJMO1/9Y0n/qKlWZfn6sScf98lEOUe2mBvW9A==}
+ '@rollup/rollup-freebsd-x64@4.63.5':
+ resolution: {integrity: sha512-gqfUVMJMB3mehqywxp6hTBFfgtMQykZY19+cfiaYP0toIJLb/1DZRJHVkQQGP13W4TAwfZDWeg1qBcheTRioXQ==}
cpu: [x64]
os: [freebsd]
- '@rollup/rollup-linux-arm-gnueabihf@4.45.1':
- resolution: {integrity: sha512-RkdOTu2jK7brlu+ZwjMIZfdV2sSYHK2qR08FUWcIoqJC2eywHbXr0L8T/pONFwkGukQqERDheaGTeedG+rra6Q==}
+ '@rollup/rollup-linux-arm-gnueabihf@4.63.5':
+ resolution: {integrity: sha512-CFmhpvAwzSaWMlN3VN7UtmoTihlZNzoP0juQib5TQRnYUyDV8dXeWOp29sobWAT6gXl/hQgAClLlEiYozQG3OQ==}
cpu: [arm]
os: [linux]
+ libc: [glibc]
- '@rollup/rollup-linux-arm-musleabihf@4.45.1':
- resolution: {integrity: sha512-3kJ8pgfBt6CIIr1o+HQA7OZ9mp/zDk3ctekGl9qn/pRBgrRgfwiffaUmqioUGN9hv0OHv2gxmvdKOkARCtRb8Q==}
+ '@rollup/rollup-linux-arm-musleabihf@4.63.5':
+ resolution: {integrity: sha512-Uc9H8eXCOayV6JLTH5bXKMId6qbhNHa818/BgYjm4jrlq3vZquC9cqyvHBw17xy5Mnj5f+I3gFK5JcEf3hSqrw==}
cpu: [arm]
os: [linux]
+ libc: [musl]
- '@rollup/rollup-linux-arm64-gnu@4.45.1':
- resolution: {integrity: sha512-k3dOKCfIVixWjG7OXTCOmDfJj3vbdhN0QYEqB+OuGArOChek22hn7Uy5A/gTDNAcCy5v2YcXRJ/Qcnm4/ma1xw==}
+ '@rollup/rollup-linux-arm64-gnu@4.63.5':
+ resolution: {integrity: sha512-VcPr/szv/1BFw112Kt//fxulXt/JPqzzidU84iW68L2DdjnOO8QFUv2zTSYBEPHD6movBD4z+bbr5y60GYM7Jw==}
cpu: [arm64]
os: [linux]
+ libc: [glibc]
- '@rollup/rollup-linux-arm64-musl@4.45.1':
- resolution: {integrity: sha512-PmI1vxQetnM58ZmDFl9/Uk2lpBBby6B6rF4muJc65uZbxCs0EA7hhKCk2PKlmZKuyVSHAyIw3+/SiuMLxKxWog==}
+ '@rollup/rollup-linux-arm64-musl@4.63.5':
+ resolution: {integrity: sha512-BnxtJ5/91BrIHYIkGrmjz/lbMhqEHt1dPFqIxIFR+jPn0xVc/oUSCtIT089zfp5ufwGDlYz2UC+Fe1SRBpYFbQ==}
cpu: [arm64]
os: [linux]
+ libc: [musl]
+
+ '@rollup/rollup-linux-loong64-gnu@4.63.5':
+ resolution: {integrity: sha512-LrYcHZwF+fAMNKHYTOQ5osWM4AZF7YF6D+XtsjDyEvljtt11twc+zHVXBLNEjxVSUnKYsOhvVz4Z213eW02COQ==}
+ cpu: [loong64]
+ os: [linux]
+ libc: [glibc]
- '@rollup/rollup-linux-loongarch64-gnu@4.45.1':
- resolution: {integrity: sha512-9UmI0VzGmNJ28ibHW2GpE2nF0PBQqsyiS4kcJ5vK+wuwGnV5RlqdczVocDSUfGX/Na7/XINRVoUgJyFIgipoRg==}
+ '@rollup/rollup-linux-loong64-musl@4.63.5':
+ resolution: {integrity: sha512-nj7QKQePAAUpCpJHtg0pR0W/b92A9NO17JS3BAQmHDn/yhmkir2p8llrKY9TOhleKIaSzy1JhxS3T9FVld6coA==}
cpu: [loong64]
os: [linux]
+ libc: [musl]
+
+ '@rollup/rollup-linux-ppc64-gnu@4.63.5':
+ resolution: {integrity: sha512-5ylkX6dWMeBKge9nTU+Rxfb+ZfaCIJ9lRqIFaK0eAMcWp7OJbYnLveLgXmm0VrvuLKb8qIK+mHyH0qu88RM+iA==}
+ cpu: [ppc64]
+ os: [linux]
+ libc: [glibc]
- '@rollup/rollup-linux-powerpc64le-gnu@4.45.1':
- resolution: {integrity: sha512-7nR2KY8oEOUTD3pBAxIBBbZr0U7U+R9HDTPNy+5nVVHDXI4ikYniH1oxQz9VoB5PbBU1CZuDGHkLJkd3zLMWsg==}
+ '@rollup/rollup-linux-ppc64-musl@4.63.5':
+ resolution: {integrity: sha512-oHK4ZHYFDKjZviK34I+NwgfbGxgI7ztrNxj2hPTSSNFgeq1a/lEd7dHV2fdGAuTH4Iym3RHJg+vAbWaWG4B7Zg==}
cpu: [ppc64]
os: [linux]
+ libc: [musl]
- '@rollup/rollup-linux-riscv64-gnu@4.45.1':
- resolution: {integrity: sha512-nlcl3jgUultKROfZijKjRQLUu9Ma0PeNv/VFHkZiKbXTBQXhpytS8CIj5/NfBeECZtY2FJQubm6ltIxm/ftxpw==}
+ '@rollup/rollup-linux-riscv64-gnu@4.63.5':
+ resolution: {integrity: sha512-UcetmHZ6XOXuUByiKZyQmb55ZPr0LABr3Ec/HB9wKZn6CEAFWZkE+hsJErJ9hbPBC7nI0dKuELx7CoV6IM7TMg==}
cpu: [riscv64]
os: [linux]
+ libc: [glibc]
- '@rollup/rollup-linux-riscv64-musl@4.45.1':
- resolution: {integrity: sha512-HJV65KLS51rW0VY6rvZkiieiBnurSzpzore1bMKAhunQiECPuxsROvyeaot/tcK3A3aGnI+qTHqisrpSgQrpgA==}
+ '@rollup/rollup-linux-riscv64-musl@4.63.5':
+ resolution: {integrity: sha512-C5CmDPQBtvjVo8cgQsBs+w6WB0JLkiixhgi6hVLV11hERWdn/p0XcPU2OUcZzac9BPOFq7SbaHFa8r3SWEysCQ==}
cpu: [riscv64]
os: [linux]
+ libc: [musl]
- '@rollup/rollup-linux-s390x-gnu@4.45.1':
- resolution: {integrity: sha512-NITBOCv3Qqc6hhwFt7jLV78VEO/il4YcBzoMGGNxznLgRQf43VQDae0aAzKiBeEPIxnDrACiMgbqjuihx08OOw==}
+ '@rollup/rollup-linux-s390x-gnu@4.63.5':
+ resolution: {integrity: sha512-lHVQHJFKsuuxLMi3MQO9XVL8Tje3JR82CzB+QDKC5NWBcsIWuwsn9uIM5e3lBhI+fF1/s63qnyYqsg65+8rV/w==}
cpu: [s390x]
os: [linux]
+ libc: [glibc]
- '@rollup/rollup-linux-x64-gnu@4.45.1':
- resolution: {integrity: sha512-+E/lYl6qu1zqgPEnTrs4WysQtvc/Sh4fC2nByfFExqgYrqkKWp1tWIbe+ELhixnenSpBbLXNi6vbEEJ8M7fiHw==}
+ '@rollup/rollup-linux-x64-gnu@4.63.5':
+ resolution: {integrity: sha512-3W9bTFcQNJn71cSJVM9RKIiZOy8DO/XLDii8Uv/Pm6WKqDRj7JV3ZfuXIEfyuy5LXpIzAbB/1M4Ukp9GKNa7nA==}
cpu: [x64]
os: [linux]
+ libc: [glibc]
- '@rollup/rollup-linux-x64-musl@4.45.1':
- resolution: {integrity: sha512-a6WIAp89p3kpNoYStITT9RbTbTnqarU7D8N8F2CV+4Cl9fwCOZraLVuVFvlpsW0SbIiYtEnhCZBPLoNdRkjQFw==}
+ '@rollup/rollup-linux-x64-musl@4.63.5':
+ resolution: {integrity: sha512-VDC7rRJlee/scpki96GZ27Omf6yU87s1YXwVTpjE5841faVlDYYT565rgfmoR1U0sqL7z5ivQSDjcsF6VRXyBA==}
cpu: [x64]
os: [linux]
+ libc: [musl]
+
+ '@rollup/rollup-openbsd-x64@4.63.5':
+ resolution: {integrity: sha512-z86Ok2p4pTdv5xqCKZsTooO7yBEiaJR/HzU3Wx8RmWsPoLppnMKROhJusQob8B3IE1ghC343kUW9rC2r+Wf3ig==}
+ cpu: [x64]
+ os: [openbsd]
+
+ '@rollup/rollup-openharmony-arm64@4.63.5':
+ resolution: {integrity: sha512-IzQmj+xXwQFGhMAMKMQVXkMwMZN3TqkJgAE0nSsqvVwWWciP4AIPMmWRqOQ2GfX7TUDZr+xqGFcBS36CRPGw0g==}
+ cpu: [arm64]
+ os: [openharmony]
- '@rollup/rollup-win32-arm64-msvc@4.45.1':
- resolution: {integrity: sha512-T5Bi/NS3fQiJeYdGvRpTAP5P02kqSOpqiopwhj0uaXB6nzs5JVi2XMJb18JUSKhCOX8+UE1UKQufyD6Or48dJg==}
+ '@rollup/rollup-win32-arm64-msvc@4.63.5':
+ resolution: {integrity: sha512-F6qpTaPc9bwBH85kjy0/BLmLSW1uv7AoOXCoRIkg2arlgCYlWYcAbiMkvZuAcaWk9TpCRG//okznLAqLGshkMw==}
cpu: [arm64]
os: [win32]
- '@rollup/rollup-win32-ia32-msvc@4.45.1':
- resolution: {integrity: sha512-lxV2Pako3ujjuUe9jiU3/s7KSrDfH6IgTSQOnDWr9aJ92YsFd7EurmClK0ly/t8dzMkDtd04g60WX6yl0sGfdw==}
+ '@rollup/rollup-win32-ia32-msvc@4.63.5':
+ resolution: {integrity: sha512-igoDsTFhhwECBeGbUuLeIk7t8Y1apa+cs6mDWpx2EZ0ch7oEQgzHbFUXN9euoHekCAQzXdXApAGkV6jznS7tWw==}
cpu: [ia32]
os: [win32]
- '@rollup/rollup-win32-x64-msvc@4.45.1':
- resolution: {integrity: sha512-M/fKi4sasCdM8i0aWJjCSFm2qEnYRR8AMLG2kxp6wD13+tMGA4Z1tVAuHkNRjud5SW2EM3naLuK35w9twvf6aA==}
+ '@rollup/rollup-win32-x64-gnu@4.63.5':
+ resolution: {integrity: sha512-U3teMeMbXFmaM5D+OTJpsOXd+wV/qftIeYF9kBKL4v73641qyJmoXFtA28DQLsnmlyayEsTe72xpLHrArq6vHw==}
cpu: [x64]
os: [win32]
- '@sec-ant/readable-stream@0.4.1':
- resolution: {integrity: sha512-831qok9r2t8AlxLko40y2ebgSDhenenCatLVeW/uBtnHPyhHOvG0C7TvfgecV+wHzIm5KUICgzmVpWS+IMEAeg==}
-
- '@selderee/plugin-htmlparser2@0.11.0':
- resolution: {integrity: sha512-P33hHGdldxGabLFjPPpaTxVolMrzrcegejx+0GxjrIb9Zv48D8yAIA/QTDR2dFl7Uz7urX8aX6+5bCZslr+gWQ==}
-
- '@shikijs/core@1.29.2':
- resolution: {integrity: sha512-vju0lY9r27jJfOY4Z7+Rt/nIOjzJpZ3y+nYpqtUZInVoXQ/TJZcfGnNOGnKjFdVZb8qexiCuSlZRKcGfhhTTZQ==}
-
- '@shikijs/core@3.8.1':
- resolution: {integrity: sha512-uTSXzUBQ/IgFcUa6gmGShCHr4tMdR3pxUiiWKDm8pd42UKJdYhkAYsAmHX5mTwybQ5VyGDgTjW4qKSsRvGSang==}
-
- '@shikijs/engine-javascript@1.29.2':
- resolution: {integrity: sha512-iNEZv4IrLYPv64Q6k7EPpOCE/nuvGiKl7zxdq0WFuRPF5PAE9PRo2JGq/d8crLusM59BRemJ4eOqrFrC4wiQ+A==}
-
- '@shikijs/engine-javascript@3.8.1':
- resolution: {integrity: sha512-rZRp3BM1llrHkuBPAdYAzjlF7OqlM0rm/7EWASeCcY7cRYZIrOnGIHE9qsLz5TCjGefxBFnwgIECzBs2vmOyKA==}
-
- '@shikijs/engine-oniguruma@1.29.2':
- resolution: {integrity: sha512-7iiOx3SG8+g1MnlzZVDYiaeHe7Ez2Kf2HrJzdmGwkRisT7r4rak0e655AcM/tF9JG/kg5fMNYlLLKglbN7gBqA==}
-
- '@shikijs/engine-oniguruma@3.8.1':
- resolution: {integrity: sha512-KGQJZHlNY7c656qPFEQpIoqOuC4LrxjyNndRdzk5WKB/Ie87+NJCF1xo9KkOUxwxylk7rT6nhlZyTGTC4fCe1g==}
-
- '@shikijs/langs@1.29.2':
- resolution: {integrity: sha512-FIBA7N3LZ+223U7cJDUYd5shmciFQlYkFXlkKVaHsCPgfVLiO+e12FmQE6Tf9vuyEsFe3dIl8qGWKXgEHL9wmQ==}
+ '@rollup/rollup-win32-x64-msvc@4.63.5':
+ resolution: {integrity: sha512-ypfC34F3RKXvCXBglGqGMsUSMKlgwd1HX9AOAlx9RoZZ6GaI42YHVeKpzg3JG+wpBUJYTG+NNZhqbDWL8tBZkw==}
+ cpu: [x64]
+ os: [win32]
- '@shikijs/langs@3.8.1':
- resolution: {integrity: sha512-TjOFg2Wp1w07oKnXjs0AUMb4kJvujML+fJ1C5cmEj45lhjbUXtziT1x2bPQb9Db6kmPhkG5NI2tgYW1/DzhUuQ==}
+ '@shikijs/core@2.5.0':
+ resolution: {integrity: sha512-uu/8RExTKtavlpH7XqnVYBrfBkUc20ngXiX9NSrBhOVZYv/7XQRKUyhtkeflY5QsxC0GbJThCerruZfsUaSldg==}
- '@shikijs/themes@1.29.2':
- resolution: {integrity: sha512-i9TNZlsq4uoyqSbluIcZkmPL9Bfi3djVxRnofUHwvx/h6SRW3cwgBC5SML7vsDcWyukY0eCzVN980rqP6qNl9g==}
+ '@shikijs/engine-javascript@2.5.0':
+ resolution: {integrity: sha512-VjnOpnQf8WuCEZtNUdjjwGUbtAVKuZkVQ/5cHy/tojVVRIRtlWMYVjyWhxOmIq05AlSOv72z7hRNRGVBgQOl0w==}
- '@shikijs/themes@3.8.1':
- resolution: {integrity: sha512-Vu3t3BBLifc0GB0UPg2Pox1naTemrrvyZv2lkiSw3QayVV60me1ujFQwPZGgUTmwXl1yhCPW8Lieesm0CYruLQ==}
+ '@shikijs/engine-oniguruma@2.5.0':
+ resolution: {integrity: sha512-pGd1wRATzbo/uatrCIILlAdFVKdxImWJGQ5rFiB5VZi2ve5xj3Ax9jny8QvkaV93btQEwR/rSz5ERFpC5mKNIw==}
- '@shikijs/transformers@1.29.2':
- resolution: {integrity: sha512-NHQuA+gM7zGuxGWP9/Ub4vpbwrYCrho9nQCLcCPfOe3Yc7LOYwmSuhElI688oiqIXk9dlZwDiyAG9vPBTuPJMA==}
+ '@shikijs/langs@2.5.0':
+ resolution: {integrity: sha512-Qfrrt5OsNH5R+5tJ/3uYBBZv3SuGmnRPejV9IlIbFH3HTGLDlkqgHymAlzklVmKBjAaVmkPkyikAV/sQ1wSL+w==}
- '@shikijs/transformers@3.8.1':
- resolution: {integrity: sha512-nmTyFfBrhJk6HJi118jes0wuWdfKXeVUq1Nq+hm8h6wbk1KUfvtg+LY/uDfxZD2VDItHO3QoINIs3NtoKBmgxw==}
+ '@shikijs/themes@2.5.0':
+ resolution: {integrity: sha512-wGrk+R8tJnO0VMzmUExHR+QdSaPUl/NKs+a4cQQRWyoc3YFbUzuLEi/KWK1hj+8BfHRKm2jNhhJck1dfstJpiw==}
- '@shikijs/types@1.29.2':
- resolution: {integrity: sha512-VJjK0eIijTZf0QSTODEXCqinjBn0joAHQ+aPSBzrv4O2d/QSbsMw+ZeSRx03kV34Hy7NzUvV/7NqfYGRLrASmw==}
+ '@shikijs/transformers@2.5.0':
+ resolution: {integrity: sha512-SI494W5X60CaUwgi8u4q4m4s3YAFSxln3tzNjOSYqq54wlVgz0/NbbXEb3mdLbqMBztcmS7bVTaEd2w0qMmfeg==}
- '@shikijs/types@3.8.1':
- resolution: {integrity: sha512-5C39Q8/8r1I26suLh+5TPk1DTrbY/kn3IdWA5HdizR0FhlhD05zx5nKCqhzSfDHH3p4S0ZefxWd77DLV+8FhGg==}
+ '@shikijs/types@2.5.0':
+ resolution: {integrity: sha512-ygl5yhxki9ZLNuNpPitBWvcy9fsSKKaRuO4BAlMyagszQidxcpLAr0qiW/q43DtSIDxO6hEbtYLiFZNXO/hdGw==}
'@shikijs/vscode-textmate@10.0.2':
resolution: {integrity: sha512-83yeghZ2xxin3Nj8z1NMd/NCuca+gsYXswywDy5bHvwlWL8tpTQmzGeUuHd9FC3E/SBEMvzJRwWEOz5gGes9Qg==}
- '@sindresorhus/merge-streams@4.0.0':
- resolution: {integrity: sha512-tlqY9xq5ukxTUZBmoOp+m61cqwQD5pHJtFY3Mn8CA8ps6yghLH/Hw8UPdqg4OLmFW3IFlcXnQNmo/dh8HzXYIQ==}
- engines: {node: '>=18'}
-
- '@types/d3-array@3.2.1':
- resolution: {integrity: sha512-Y2Jn2idRrLzUfAKV2LyRImR+y4oa2AntrgID95SHJxuMUrkNXmanDSed71sRNZysveJVt1hLLemQZIady0FpEg==}
+ '@types/d3-array@3.2.2':
+ resolution: {integrity: sha512-hOLWVbm7uRza0BYXpIIW5pxfrKe0W+D5lrFiAEYR+pb6w3N2SwSMaJbXdUfSEv+dT4MfHBLtn5js0LAWaO6otw==}
'@types/d3-axis@3.0.6':
resolution: {integrity: sha512-pYeijfZuBd87T0hGn0FO1vQ/cgLk6E1ALJjfkC0oJ8cbwkZl3TpgS8bVBLZN+2jjGgg38epgxb2zmoGtSfvgMw==}
@@ -1237,8 +805,8 @@ packages:
'@types/d3-delaunay@6.0.4':
resolution: {integrity: sha512-ZMaSKu4THYCU6sV64Lhg6qjf1orxBthaC161plr5KuPHo3CNm8DTHiLw/5Eq2b6TsNP0W0iJrUOFscY6Q450Hw==}
- '@types/d3-dispatch@3.0.6':
- resolution: {integrity: sha512-4fvZhzMeeuBJYZXRXrRIQnvUYfyXwYmLsdiN7XXmVNQKKw1cM8a5WdID0g1hVFZDqT9ZqZEY5pD44p24VS7iZQ==}
+ '@types/d3-dispatch@3.0.7':
+ resolution: {integrity: sha512-5o9OIAdKkhN1QItV2oqaE5KMIiXAvDWBDPrD85e58Qlz1c1kI/J0NcqbEG88CoTwJrYe7ntUCVfeUl2UJKbWgA==}
'@types/d3-drag@3.0.7':
resolution: {integrity: sha512-HE3jVKlzU9AaMazNufooRJ5ZpWmLIoc90A37WU2JMmeq28w1FQqCZswHZ3xR+SuxYftzHq6WU6KJHvqxKzTxxQ==}
@@ -1258,8 +826,8 @@ packages:
'@types/d3-format@3.0.4':
resolution: {integrity: sha512-fALi2aI6shfg7vM5KiR1wNJnZ7r6UuggVqtDA+xiEdPZQwy/trcQaHnwShLuLdta2rTymCNpxYTiMZX/e09F4g==}
- '@types/d3-geo@3.1.0':
- resolution: {integrity: sha512-856sckF0oP/diXtS4jNsiQw/UuK5fQG8l/a9VVLeSouf1/PPbBE1i1W852zVwKwYCBkFJJB7nCFTbk6UMEXBOQ==}
+ '@types/d3-geo@3.1.1':
+ resolution: {integrity: sha512-65Emv9fQiQQqphLlRkuQ5ypPsOmWPhtBGCMv61JDPEPMvsx+gzhGf74yw1a78xFKPj6zw4AgQICJoQv0vK9M2w==}
'@types/d3-hierarchy@3.1.7':
resolution: {integrity: sha512-tJFtNoYBtRtkNysX1Xq4sxtjK8YgoWUNpIiUee0/jHGRwqvzYxkq0hGVbbOGSz+JgFxxRu4K8nb3YpG3CMARtg==}
@@ -1276,8 +844,8 @@ packages:
'@types/d3-quadtree@3.0.6':
resolution: {integrity: sha512-oUzyO1/Zm6rsxKRHA1vH0NEDG58HrT5icx/azi9MF1TWdtttWl0UIUsjEQBBh+SIkrpd21ZjEv7ptxWys1ncsg==}
- '@types/d3-random@3.0.3':
- resolution: {integrity: sha512-Imagg1vJ3y76Y2ea0871wpabqp613+8/r0mCLEBfdtqC7xMSfj9idOnmBYyMoULfHePJyxMAw3nWhJxzc+LFwQ==}
+ '@types/d3-random@3.0.4':
+ resolution: {integrity: sha512-UHYId5WTCx4L4YNel7NU00XUXXgvgpgZOvp10PuvsQENjMDXhh2RyFc0KBjO7B45ne4Ha1yVH7ii0vnzKkuzWA==}
'@types/d3-scale-chromatic@3.1.0':
resolution: {integrity: sha512-iWMJgwkK7yTRmWqRB5plb1kadXyQ5Sj8V/zYlFGMUBbIPKQScw+Dku9cAAMgJG+z5GYDoMjWGLVOvjghDEFnKQ==}
@@ -1285,11 +853,11 @@ packages:
'@types/d3-scale@4.0.9':
resolution: {integrity: sha512-dLmtwB8zkAeO/juAMfnV+sItKjlsw2lKdZVVy6LRr0cBmegxSABiLEpGVmSJJ8O08i4+sGR6qQtb6WtuwJdvVw==}
- '@types/d3-selection@3.0.11':
- resolution: {integrity: sha512-bhAXu23DJWsrI45xafYpkQ4NtcKMwWnAC/vKrd2l+nxMFuvOT3XMYTIj2opv8vq8AO5Yh7Qac/nSeP/3zjTK0w==}
+ '@types/d3-selection@3.0.12':
+ resolution: {integrity: sha512-Qe/KWYhEiIIxGs7HrAAjMfShxKldx19SJtr5zu53f3afPsdZNz7HHtdTLXo/kqeiWNXVycI24kSnfzBYkTzpgw==}
- '@types/d3-shape@3.1.7':
- resolution: {integrity: sha512-VLvUQ33C+3J+8p+Daf+nYSOsjB4GXp19/S/aGo60m9h1v6XaxjiT82lKVWJCfzhtuZ3yD7i/TPeC/fuKLLOSmg==}
+ '@types/d3-shape@3.2.0':
+ resolution: {integrity: sha512-kVd74ta9eof3eJOvbNd1vGKS/XERRyQbT26Og63hIsvDO84cjD5gEOhsXf26w3FSoNlPVz84DOFcKv/oou+fMw==}
'@types/d3-time-format@4.0.3':
resolution: {integrity: sha512-5xg9rC+wWL8kdDj153qZcsJ0FWiFt0J5RB6LYUNZjwSnesfblqrI/bJ1wBdJ8OQfncgbJG5+2F+qfqnqyzYxyg==}
@@ -1309,29 +877,26 @@ packages:
'@types/d3@7.4.3':
resolution: {integrity: sha512-lZXZ9ckh5R8uiFVt8ogUNf+pIrK4EsWrx2Np75WvF/eTpJ0FMHNhjXk8CKEx/+gpHbNQyJWehbFaTvqmHWB3ww==}
- '@types/estree@1.0.8':
- resolution: {integrity: sha512-dWHzHa2WqEXI/O1E9OjrocMTKJl2mSrEolh1Iomrv6U+JuNwaHXsXx9bLu5gG7BUWFIN0skIQJQ/L1rIex4X6w==}
+ '@types/esrecurse@4.3.1':
+ resolution: {integrity: sha512-xJBAbDifo5hpffDBuHl0Y8ywswbiAp/Wi7Y/GtAgSlZyIABppyurxVueOPE8LUQOxdlgi6Zqce7uoEpqNTeiUw==}
+
+ '@types/estree@1.0.9':
+ resolution: {integrity: sha512-GhdPgy1el4/ImP05X05Uw4cw2/M93BCUmnEvWZNStlCzEKME4Fkk+YpoA5OiHNQmoS7Cafb8Xa3Pya8m1Qrzeg==}
'@types/geojson@7946.0.16':
resolution: {integrity: sha512-6C8nqWur3j98U6+lXDfTUWIfgvZU+EumvpHKcYjujKH7woYyLj2sUmff0tRhrqM7BohUw7Pz3ZB1jj2gW9Fvmg==}
- '@types/hast@3.0.4':
- resolution: {integrity: sha512-WPs+bbQw5aCj+x6laNGWLH3wviHtoCv/P3+otBhbOhJgG8qtpdAMlTCxLtsTWA7LH1Oh/bFCHsBn0TPS5m30EQ==}
-
- '@types/http-proxy@1.17.16':
- resolution: {integrity: sha512-sdWoUajOB1cd0A8cRRQ1cfyWNbmFKLAqBB89Y8x5iYyG/mkJHc0YUH8pdWBy2omi9qtCpiIgGjuwO0dQST2l5w==}
+ '@types/hast@3.0.5':
+ resolution: {integrity: sha512-rp/ezSWaD1m44dPKICGhiskI13nVr7qTloFwDa/IYkhhf5nzwP+zIQcIJh3WIFSBOy/H1PzB40jPjMDksN4F+g==}
'@types/json-schema@7.0.15':
resolution: {integrity: sha512-5+fP8P8MFNC+AyZCDxrB2pkZFPGzqQWUzpSeuuVLvm8VMcorNYavBqoFcxK8bQz4Qsbn4oUEEem4wDLfcysGHA==}
- '@types/katex@0.16.7':
- resolution: {integrity: sha512-HMwFiRujE5PjrgwHQ25+bsLJgowjGjm5Z8FVSf0N6PwgJrwxH0QxzHYDcKsTfV3wva0vzrpqMTJS2jXPr5BMEQ==}
-
'@types/linkify-it@5.0.0':
resolution: {integrity: sha512-sVDA58zAw4eWAffKOaQH5/5j3XeayukzDk+ewSsnv3p4yJEZHCCzMDiZM8e0OUrRvmpGZ85jf4yDHkHsgBNr9Q==}
- '@types/markdown-it@14.1.2':
- resolution: {integrity: sha512-promo4eFwuiW+TfGxhi+0x3czqTYJkG8qB17ZUJiVF10Xm7NLVRSLUsfRTU/6h1e24VvRnXCx+hG7li58lkzog==}
+ '@types/markdown-it@14.2.0':
+ resolution: {integrity: sha512-NoQ2yGlLWj4wpxMs+TYmRKk3thDrQ97agr7sFqfLsAlvoS8SNQuTrlObhFqG9iugdTtgOE9jpJ6FNM4ZGsa5xQ==}
'@types/mdast@4.0.4':
resolution: {integrity: sha512-kGaNbPh1k7AFzgpud/gMdvIm5xuECykRR+JnWKQno9TAXVa6WIVCGTPvYGekIDL4uwCZQSYbUxNBSb1aUo79oA==}
@@ -1339,8 +904,8 @@ packages:
'@types/mdurl@2.0.0':
resolution: {integrity: sha512-RGdgjQUZba5p6QEFAVx2OGb8rQDL/cPRG7GiedRzMcJ1tYnUANBncjbSB1NRGwbvjcPeikRABz2nshyPk1bhWg==}
- '@types/node@24.0.15':
- resolution: {integrity: sha512-oaeTSbCef7U/z7rDeJA138xpG3NuKc64/rZ2qmUFkFJmnMsAPaluIifqyWd8hSSMxyP9oie3dLAqYPblag9KgA==}
+ '@types/node@24.19.0':
+ resolution: {integrity: sha512-zY+5tKxXdhGh1PYI0ac+7juvEu4OI6vWtVVoj5i2m42jxAY1U+zHGt6QCyOFwykdP62sM3MJ9stoYYUw5aCWew==}
'@types/trusted-types@2.0.7':
resolution: {integrity: sha512-ScaPdn1dQczgbl0QFTeTOmVHFULt394XJgOQNoyVhZ6r2vLnMLJfBPd53SB52T/3G36VI1/g2MZaX0cwDuXsfw==}
@@ -1348,166 +913,73 @@ packages:
'@types/unist@3.0.3':
resolution: {integrity: sha512-ko/gIFJRv177XgZsZcBwnqJN5x/Gien8qNOn0D5bQU/zAzVf9Zt3BlcUiLqhV9y4ARk0GbT3tnUiPNgnTXzc/Q==}
- '@types/web-bluetooth@0.0.20':
- resolution: {integrity: sha512-g9gZnnXVq7gM7v3tJCWV/qw7w+KeOlSHAhgF9RytFyifW6AF61hdT2ucrYhPq9hLs5JIryeupHV3qGk95dH9ow==}
-
'@types/web-bluetooth@0.0.21':
resolution: {integrity: sha512-oIQLCGWtcFZy2JW77j9k8nHzAOpqMHLQejDA48XXMWH6tjCQHz5RCFz1bzsmROyL6PUm+LLnUiI4BCn221inxA==}
- '@typescript-eslint/project-service@8.37.0':
- resolution: {integrity: sha512-BIUXYsbkl5A1aJDdYJCBAo8rCEbAvdquQ8AnLb6z5Lp1u3x5PNgSSx9A/zqYc++Xnr/0DVpls8iQ2cJs/izTXA==}
+ '@typescript-eslint/eslint-plugin@8.70.1':
+ resolution: {integrity: sha512-nDNrUQ/4ruSNYbu749TRY7cfrzPtoLHEXSNBI8aaNY32LlZCajixqRf3FqcKC4p5Cam4VOHYx/t+i5+nKXvrqA==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
peerDependencies:
- typescript: '>=4.8.4 <5.9.0'
+ '@typescript-eslint/parser': ^8.70.1
+ eslint: ^8.57.0 || ^9.0.0 || ^10.0.0
+ typescript: '>=4.8.4 <6.1.0'
- '@typescript-eslint/scope-manager@8.37.0':
- resolution: {integrity: sha512-0vGq0yiU1gbjKob2q691ybTg9JX6ShiVXAAfm2jGf3q0hdP6/BruaFjL/ManAR/lj05AvYCH+5bbVo0VtzmjOA==}
+ '@typescript-eslint/parser@8.70.1':
+ resolution: {integrity: sha512-nO974WLllwhSFWQXnMLj6nDGa8f0khKEz1JzpPJ1u7Vm/4X1X6ZHajpoknU4bb41vJyMB0HHVyS2GqdhWfIXZw==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
+ peerDependencies:
+ eslint: ^8.57.0 || ^9.0.0 || ^10.0.0
+ typescript: '>=4.8.4 <6.1.0'
- '@typescript-eslint/tsconfig-utils@8.37.0':
- resolution: {integrity: sha512-1/YHvAVTimMM9mmlPvTec9NP4bobA1RkDbMydxG8omqwJJLEW/Iy2C4adsAESIXU3WGLXFHSZUU+C9EoFWl4Zg==}
+ '@typescript-eslint/project-service@8.70.1':
+ resolution: {integrity: sha512-62xOgboPfwc3/IgPSX/W6oQR3ZbF04194FPGUGH8HL8iLFHbt/456/8Ph1wLNUgVF+s94FlHoipBsz+v7+LMnA==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
peerDependencies:
- typescript: '>=4.8.4 <5.9.0'
+ typescript: '>=4.8.4 <6.1.0'
- '@typescript-eslint/types@8.37.0':
- resolution: {integrity: sha512-ax0nv7PUF9NOVPs+lmQ7yIE7IQmAf8LGcXbMvHX5Gm+YJUYNAl340XkGnrimxZ0elXyoQJuN5sbg6C4evKA4SQ==}
+ '@typescript-eslint/scope-manager@8.70.1':
+ resolution: {integrity: sha512-Pa0EeSeAusQc1WbjQMac+YfenewYTBu0KjgYvkUKwhXaHUKbFog23Dm/rp0DX/6tyYOQ3Xl1a+3EcFNZynGHCw==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
- '@typescript-eslint/typescript-estree@8.37.0':
- resolution: {integrity: sha512-zuWDMDuzMRbQOM+bHyU4/slw27bAUEcKSKKs3hcv2aNnc/tvE/h7w60dwVw8vnal2Pub6RT1T7BI8tFZ1fE+yg==}
+ '@typescript-eslint/tsconfig-utils@8.70.1':
+ resolution: {integrity: sha512-jumze1fPI+sDOaM2TWGQdn39PDxTr7TZGeuyLkAbNyx2vtMT3uRnVKChN0hfht5V2TugphJzF6bYXvBcE09qqg==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
peerDependencies:
- typescript: '>=4.8.4 <5.9.0'
+ typescript: '>=4.8.4 <6.1.0'
- '@typescript-eslint/visitor-keys@8.37.0':
- resolution: {integrity: sha512-YzfhzcTnZVPiLfP/oeKtDp2evwvHLMe0LOy7oe+hb9KKIumLNohYS9Hgp1ifwpu42YWxhZE8yieggz6JpqO/1w==}
+ '@typescript-eslint/type-utils@8.70.1':
+ resolution: {integrity: sha512-7zKTnyvaVWqzLZHPFQtX1hVHqgkMC+WebPWakNCSyrQVbIP1AM0L0TlBZtACldIRb6PptI8Odk+jyZ5kP3B1VA==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
-
- '@ungap/structured-clone@1.3.0':
- resolution: {integrity: sha512-WmoN8qaIAo7WTYWbAZuG8PYEhn5fkz7dZrqTBZ7dtt//lL2Gwms1IcnQ5yHqjDfX8Ft5j4YzDM23f87zBfDe9g==}
-
- '@unhead/addons@2.0.12':
- resolution: {integrity: sha512-z/zmWScb5NNTqC3NLY2+rHnMDv2uOWnwbGSOsBLyxT8KvcnV/RdESid8m8zhspHPmCgF79ETLw2XMXBSupDUJw==}
-
- '@unhead/dom@2.0.12':
- resolution: {integrity: sha512-odruHzIYEixtM/lDLQG2t9Lv3iEyNxDW5uuXFGoNUVDFR4NJS/FWbBzCYJ0jszsNUp6BXAAWZevBcwbpgYfB2g==}
- peerDependencies:
- unhead: 2.0.12
-
- '@unhead/schema-org@2.0.12':
- resolution: {integrity: sha512-wsOjcTvNncJwTUouw84vku0dKSfYiWEKxqV9abzpbjOJ6+44woO7XKFGD7MdTcRgsfkjO1J0MLHaG7VEBwJkGg==}
peerDependencies:
- '@unhead/react': 2.0.12
- '@unhead/solid-js': 2.0.12
- '@unhead/svelte': 2.0.12
- '@unhead/vue': 2.0.12
- peerDependenciesMeta:
- '@unhead/react':
- optional: true
- '@unhead/solid-js':
- optional: true
- '@unhead/svelte':
- optional: true
- '@unhead/vue':
- optional: true
+ eslint: ^8.57.0 || ^9.0.0 || ^10.0.0
+ typescript: '>=4.8.4 <6.1.0'
- '@unhead/vue@2.0.12':
- resolution: {integrity: sha512-WFaiCVbBd39FK6Bx3GQskhgT9s45Vjx6dRQegYheVwU1AnF+FAfJVgWbrl21p6fRJcLAFp0xDz6wE18JYBM0eQ==}
- peerDependencies:
- vue: '>=3.5.13'
+ '@typescript-eslint/types@8.70.1':
+ resolution: {integrity: sha512-Dm1ypdhhrGCTyyehxElhgJ6kgk8MVCv5qXdoOVqPr1uqk42jX8KjrZqhROvdShczA8qrDoYiOWn1ykWlx2k81Q==}
+ engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
- '@unocss/astro@66.3.3':
- resolution: {integrity: sha512-q26EfadSMmEXZpWDKsJF9anBCfhYDmWljVpDZ2Wo8K48IbZMUXrWfiAiUc6ijE/A/rADfHk8bp3a3GE01t3I9A==}
+ '@typescript-eslint/typescript-estree@8.70.1':
+ resolution: {integrity: sha512-TU8PwyGN0PQJUcE96mw8eCQ44SmxGdQlJmlWakHaHQ15eIuuvye5yNtmh/i6oS88jzXVQB71xdNkbkB/fMwL0g==}
+ engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
peerDependencies:
- vite: ^2.9.0 || ^3.0.0-0 || ^4.0.0 || ^5.0.0-0 || ^6.0.0-0 || ^7.0.0-0
- peerDependenciesMeta:
- vite:
- optional: true
-
- '@unocss/cli@66.3.3':
- resolution: {integrity: sha512-U0HoDcwi/DetqP5zDT3dfxG94pC3TI0PfxmpdTfPY7xEylIdLbV89fb70CvJVysDSQJIuw6TYwqS1ZlHoYNKTA==}
- engines: {node: '>=14'}
- hasBin: true
-
- '@unocss/config@66.3.3':
- resolution: {integrity: sha512-D/UxnAmkabapqWU4tF85dWWhNfCUyNutWmd4AD2VsQRZOykufJedLV74r3Z3XhoPJn4IGr3BKZm5/rflf5viDg==}
- engines: {node: '>=14'}
+ typescript: '>=4.8.4 <6.1.0'
- '@unocss/core@66.3.3':
- resolution: {integrity: sha512-6WFLd92TJelVQARtCGaF+EgEoHKIVe43gkGXVoWILu0HUDRWdhv+cpcyX0RTJV22Y976AxeneU7/zmhAh+CXNg==}
-
- '@unocss/extractor-arbitrary-variants@66.3.3':
- resolution: {integrity: sha512-TXzjH6FcITQ8V2x7ETHgVOlAHf3ll/ysxL+W4fMROm8jP/o7jvsg36tRfOwU0sDGo/qoCPux82ix9e6/JW0oqQ==}
-
- '@unocss/inspector@66.3.3':
- resolution: {integrity: sha512-NsK1WRWez2Mzk4+ophtBdXel8nGaPkIDa9lYSFMdKLF/1jNW23txeEL8CsD6/CK8K0BsR11rhLKhUrzyrjfBSQ==}
-
- '@unocss/postcss@66.3.3':
- resolution: {integrity: sha512-VKq+BtfPIZbLeAeZFprtKZJAyFBOqA8qpQm+vmWBiBia70JzkwfF2SMNIHiGt022yRo9ZmjnI9uRTxSzqXUsUQ==}
- engines: {node: '>=14'}
+ '@typescript-eslint/utils@8.70.1':
+ resolution: {integrity: sha512-Esgul8MsnKnRLdYU2Eb2cRV9bS5HJYtKj1ByJnOzzG2M58DGdSUQ1jUuILxipqcpB2h9WLrbD5GijIWUjX/Tqw==}
+ engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
peerDependencies:
- postcss: ^8.4.21
-
- '@unocss/preset-attributify@66.3.3':
- resolution: {integrity: sha512-22+0Cqqu09q+xHfZ3Wk8Coxe5m6PmpgWz4U5xrEC8056UfG3Q1KEqoCxy2wySJIq8SqxQ30Nlll7oMa31B8Krw==}
-
- '@unocss/preset-icons@66.3.3':
- resolution: {integrity: sha512-Bmhiev05BN/horlgnyZ8gzQWZKd7oVpUBWD66X7U/dgkLdO6B5GIIsdO5Fi7JLeMDmyXm6vlYk0YQhiTbx8l9w==}
-
- '@unocss/preset-mini@66.3.3':
- resolution: {integrity: sha512-pz8rgvHRYS/6fsZNtG7iArLzwANnLy5GkHY/lbuqkWhO2S2Nf7kpJCbR/uV/XeuFsLnYcZW3NLOmelfvZvJamA==}
-
- '@unocss/preset-tagify@66.3.3':
- resolution: {integrity: sha512-L1Ez7Y4uBaW+wiv1BOQygpfhseSt3EZ53jqkl7fxl1EKVsJy6SuZgJxlXEHUYp9xYdSp6EHq2CfL8UevaR+loA==}
-
- '@unocss/preset-typography@66.3.3':
- resolution: {integrity: sha512-aQXiGCObvWD9grfUpm0d5nzN+Cpvag0rHP39UjUKb0xSTzY09VzwDrua4kWVO5wJLNK6/L70osyhEgmC3qToxA==}
-
- '@unocss/preset-uno@66.3.3':
- resolution: {integrity: sha512-Tiho4LidpuMHrB19GHTU6XrL0A5eFELHk9ebQ/3WeTy+K/9a6Hn5zsHJe5UCtOsEcUdKB33oZx0hXUp93hb/YQ==}
-
- '@unocss/preset-web-fonts@66.3.3':
- resolution: {integrity: sha512-ysKZeC7TXxRiqnNL9GxZFGMKFAHXrcaqozPaEOIJ40dvzbJt8IMLyFndZkcFMcgDCV0pFh/y37mGxxxARO9+pQ==}
-
- '@unocss/preset-wind3@66.3.3':
- resolution: {integrity: sha512-iXmjvPqvmPTo4z7epQDqHxzlGRsbLJEgfETqTrRJeagvFG7Gs+ajS8cQhbf6wL01dSRHjvhVXi3MsIvqfHHXOw==}
-
- '@unocss/preset-wind4@66.3.3':
- resolution: {integrity: sha512-JSJTXVJel6kX+u4Ktt6JGnukYWYhKxmjgORTwclUpokRHgEoD+xsh0Rz4YGJ1fWSnzNslNQhWP9yDRByVPHWwA==}
-
- '@unocss/preset-wind@66.3.3':
- resolution: {integrity: sha512-3Mxl/TDPcv8nNKdFe3WKdlXE6de+lCaaizEH86BILW3ZeyPU9aKzWcZIoxohla0a6zMxDQ2+Gf+7EwaOvpqo7Q==}
-
- '@unocss/reset@66.3.3':
- resolution: {integrity: sha512-VIeR/mIcCL89/1uA1KM1QCYca4aeIGqEHMTJL1nCD4v+7wk6XhNXhsp5gMIHo+V804SUSmATWaeHTiKpiFu7AQ==}
+ eslint: ^8.57.0 || ^9.0.0 || ^10.0.0
+ typescript: '>=4.8.4 <6.1.0'
- '@unocss/rule-utils@66.3.3':
- resolution: {integrity: sha512-QKgVGV5nRRnK44/reUKFLAc5UGyl98vz3hrfk8JI8pVza58vmQWTdAB2rIpNJ5a5j+EkWfDOUlGQaOrIeYGLdg==}
- engines: {node: '>=14'}
-
- '@unocss/transformer-attributify-jsx@66.3.3':
- resolution: {integrity: sha512-ENNYFk5wrI4jlxn0tWGeR9QGxflAfZue3X2ABg0KSVOiYyIOsrHqtdoiLYkuCA9idRlBZPQxePJKcPWt1r/tYA==}
-
- '@unocss/transformer-compile-class@66.3.3':
- resolution: {integrity: sha512-VTEFuwp3iajGWyEFwmO5LRvOjgZM1TK+4rX5Q79xyTAPkLAKgOa03Ne8+kU8oG0TQEa4mXVw6ul9McM7UBJh1w==}
-
- '@unocss/transformer-directives@66.3.3':
- resolution: {integrity: sha512-11T7fmYk/XZcqFDn4qiIvs04mJhUtAoha5Y99bVE+L3byWa6BT4jb5aSAKk+24q5aynwgB++4RgfQxarj69WTw==}
-
- '@unocss/transformer-variant-group@66.3.3':
- resolution: {integrity: sha512-uhK81pbJfXJFYaXxOoIFVEG8/Kx1iaAkTwRB6c+WNUfl9GiKyYQcrI7bETgCPPbg230Z68jVICBgBATeLJ31vQ==}
-
- '@unocss/vite@66.3.3':
- resolution: {integrity: sha512-uu3smeEW6q36ri6vydRx2GiTGF5O/J80Fr4GLmLiwfpt2YnPHraO7XHVR5/mwG2Oz5Kov0uGvxVsdgxZABKRgw==}
- peerDependencies:
- vite: ^2.9.0 || ^3.0.0-0 || ^4.0.0 || ^5.0.0-0 || ^6.0.0-0 || ^7.0.0-0
+ '@typescript-eslint/visitor-keys@8.70.1':
+ resolution: {integrity: sha512-Vwj9lUIW5Xq3wQ9w6gv3R86g1hMK8f2zNOdGTAgeXUMMXFK78G9ruCjjqutHMNJc0+CH7LYRnHeUB9IT8wFmcw==}
+ engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
- '@valaxyjs/devtools@0.25.9':
- resolution: {integrity: sha512-QSZOem1SLbsUGPjXwcyYt+zlVp/eS1CLPtI91C5qHg7pZ1jRaF2LQaXdOXK9DdsqVW92/METMmQ/X02uwVjsXA==}
+ '@ungap/structured-clone@1.4.0':
+ resolution: {integrity: sha512-1mEZtMKPM09vDmQt5y7YvmN2+DFTP7Tg0EWXdic8/C6VRnpb33e4ghisCIE3WZjsE2N8mf+QV1Zqh7ZFYLWInQ==}
- '@valaxyjs/utils@0.25.9':
- resolution: {integrity: sha512-z++/haNEVqgnWsbHtyGhdioQRch5QH294UssBIi5HJRwjiYTbTL/NOU9ZenPYbz0uJMwNR6jlGVHp99H1R3xLw==}
+ '@upsetjs/venn.js@2.0.0':
+ resolution: {integrity: sha512-WbBhLrooyePuQ1VZxrJjtLvTc4NVfpOyKx0sKqioq9bX1C1m7Jgykkn8gLrtwumBioXIqam8DLxp88Adbue6Hw==}
'@vitejs/plugin-vue@5.2.4':
resolution: {integrity: sha512-7Yx/SXSOcQq5HiiV3orevHUFn+pmMB4cgbEkDYgnkUWb0WfeQ/wa2yFv6D5ICiCQOVpjA7vYDXrC7AGO8yjDHA==}
@@ -1516,172 +988,77 @@ packages:
vite: ^5.0.0 || ^6.0.0
vue: ^3.2.25
- '@vitejs/plugin-vue@6.0.0':
- resolution: {integrity: sha512-iAliE72WsdhjzTOp2DtvKThq1VBC4REhwRcaA+zPAAph6I+OQhUXv+Xu2KS7ElxYtb7Zc/3R30Hwv1DxEo7NXQ==}
- engines: {node: ^20.19.0 || >=22.12.0}
- peerDependencies:
- vite: ^5.0.0 || ^6.0.0 || ^7.0.0
- vue: ^3.2.25
-
- '@volar/language-core@2.4.15':
- resolution: {integrity: sha512-3VHw+QZU0ZG9IuQmzT68IyN4hZNd9GchGPhbD9+pa8CVv7rnoOZwo7T8weIbrRmihqy3ATpdfXFnqRrfPVK6CA==}
-
- '@volar/source-map@2.4.15':
- resolution: {integrity: sha512-CPbMWlUN6hVZJYGcU/GSoHu4EnCHiLaXI9n8c9la6RaI9W5JHX+NqG+GSQcB0JdC2FIBLdZJwGsfKyBB71VlTg==}
+ '@volar/language-core@2.4.28':
+ resolution: {integrity: sha512-w4qhIJ8ZSitgLAkVay6AbcnC7gP3glYM3fYwKV3srj8m494E3xtrCv6E+bWviiK/8hs6e6t1ij1s2Endql7vzQ==}
- '@volar/typescript@2.4.15':
- resolution: {integrity: sha512-2aZ8i0cqPGjXb4BhkMsPYDkkuc2ZQ6yOpqwAuNwUoncELqoy5fRgOQtLR9gB0g902iS0NAkvpIzs27geVyVdPg==}
+ '@volar/source-map@2.4.28':
+ resolution: {integrity: sha512-yX2BDBqJkRXfKw8my8VarTyjv48QwxdJtvRgUpNE5erCsgEUdI2DsLbpa+rOQVAJYshY99szEcRDmyHbF10ggQ==}
- '@vue-macros/common@3.0.0-beta.15':
- resolution: {integrity: sha512-DMgq/rIh1H20WYNWU7krIbEfJRYDDhy7ix64GlT4AVUJZZWCZ5pxiYVJR3A3GmWQPkn7Pg7i3oIiGqu4JGC65w==}
- engines: {node: '>=20.18.0'}
+ '@volar/typescript@2.4.28':
+ resolution: {integrity: sha512-Ja6yvWrbis2QtN4ClAKreeUZPVYMARDYZl9LMEv1iQ1QdepB6wn0jTRxA9MftYmYa4DQ4k/DaSZpFPUfxl8giw==}
peerDependencies:
- vue: ^2.7.0 || ^3.2.25
+ typescript: '*'
peerDependenciesMeta:
- vue:
+ typescript:
optional: true
- '@vue/babel-helper-vue-transform-on@1.4.0':
- resolution: {integrity: sha512-mCokbouEQ/ocRce/FpKCRItGo+013tHg7tixg3DUNS+6bmIchPt66012kBMm476vyEIJPafrvOf4E5OYj3shSw==}
+ '@vue/compiler-core@3.5.43':
+ resolution: {integrity: sha512-zdiLhnbe1QQqgDT8xZMpNmyqZ3qlI+/Q/FHQco57Kwl/b05HhCzN6eVGN9QU9rbga4CrS0H5SYY8VGHZCt/1Hg==}
- '@vue/babel-plugin-jsx@1.4.0':
- resolution: {integrity: sha512-9zAHmwgMWlaN6qRKdrg1uKsBKHvnUU+Py+MOCTuYZBoZsopa90Di10QRjB+YPnVss0BZbG/H5XFwJY1fTxJWhA==}
- peerDependencies:
- '@babel/core': ^7.0.0-0
- peerDependenciesMeta:
- '@babel/core':
- optional: true
+ '@vue/compiler-dom@3.5.43':
+ resolution: {integrity: sha512-PEZoAk3NQmsn/ejMzSOCyTYqwGqczrWm70PuhBKjjv1+TCoQAaO/zOqNwjV+honlNstT5ILxtc+8r8UUfj+iEQ==}
- '@vue/babel-plugin-resolve-type@1.4.0':
- resolution: {integrity: sha512-4xqDRRbQQEWHQyjlYSgZsWj44KfiF6D+ktCuXyZ8EnVDYV3pztmXJDf1HveAjUAXxAnR8daCQT51RneWWxtTyQ==}
- peerDependencies:
- '@babel/core': ^7.0.0-0
+ '@vue/compiler-sfc@3.5.43':
+ resolution: {integrity: sha512-FCbrG3XNCRl+js3huuKx4IVHBLTvMkJhVepjbxSPu1gn4yWLaYtGNQdjJGZaMytXB6qb76qQDDmDSLy/vkmleQ==}
- '@vue/compiler-core@3.5.17':
- resolution: {integrity: sha512-Xe+AittLbAyV0pabcN7cP7/BenRBNcteM4aSDCtRvGw0d9OL+HG1u/XHLY/kt1q4fyMeZYXyIYrsHuPSiDPosA==}
+ '@vue/compiler-ssr@3.5.43':
+ resolution: {integrity: sha512-GF62orf7KiJX9RqrHNGrYBudsQGD0OhJ5nDs90O8UiDuS40+YMYomiXu6w6EuvtXuRDc3MSNis3EaaSKAVSWpg==}
- '@vue/compiler-dom@3.5.17':
- resolution: {integrity: sha512-+2UgfLKoaNLhgfhV5Ihnk6wB4ljyW1/7wUIog2puUqajiC29Lp5R/IKDdkebh9jTbTogTbsgB+OY9cEWzG95JQ==}
+ '@vue/devtools-api@7.7.10':
+ resolution: {integrity: sha512-KxtEpUOOpFz/qOGRrAwA36QF7DqIA+FXgCYit9mk9wjbaZt0sXOFz81ElOZtKA4HbWHUdwNjZHBFsFFyp5BZiA==}
- '@vue/compiler-sfc@3.5.17':
- resolution: {integrity: sha512-rQQxbRJMgTqwRugtjw0cnyQv9cP4/4BxWfTdRBkqsTfLOHWykLzbOc3C4GGzAmdMDxhzU/1Ija5bTjMVrddqww==}
+ '@vue/devtools-kit@7.7.10':
+ resolution: {integrity: sha512-3WNi2Kq4tbpVbmhml7RiphmAt0279oh3fKNeWMQIrltfX8Q91b4i5PL8DtyNKdwmcsGrV4fg+erwWOmD05CLIw==}
- '@vue/compiler-ssr@3.5.17':
- resolution: {integrity: sha512-hkDbA0Q20ZzGgpj5uZjb9rBzQtIHLS78mMilwrlpWk2Ep37DYntUz0PonQ6kr113vfOEdM+zTBuJDaceNIW0tQ==}
+ '@vue/devtools-shared@7.7.10':
+ resolution: {integrity: sha512-wOPslzB8vTvpxwdaOcR2qAbwmuSP0L+rhpoC6Cf56V3Jip+HWb7PQQXOUPgBNQARpXsbQX/+mvi8kKucmBGRwQ==}
- '@vue/compiler-vue2@2.7.16':
- resolution: {integrity: sha512-qYC3Psj9S/mfu9uVi5WvNZIzq+xnXMhOwbTFKKDD7b1lhpnn71jXSFdTQ+WsIEk0ONCd7VV2IMm7ONl6tbQ86A==}
+ '@vue/language-core@3.3.11':
+ resolution: {integrity: sha512-QJmpliwAVpC/OxubIByPAhNzsQPRc8/gxlN2qnVzVfIMjMDz/9RnXRFoetjz5yEgXVXyp4LqhXq3V53PjmNzFw==}
- '@vue/devtools-api@6.6.4':
- resolution: {integrity: sha512-sGhTPMuXqZ1rVOk32RylztWkfXTRhuS7vgAKv0zjqk8gbsHkJ7xfFf+jbySxt7tWObEJwyKaHMikV/WGDiQm8g==}
+ '@vue/reactivity@3.5.43':
+ resolution: {integrity: sha512-G/c9GyOZNI2jVaaS6OX1EF1SSFSv7H0ERqNTl4+DTFMlZmB5eVAB53aLQNam/7NL2NPtaDD7RdVrzf8uJzMuOA==}
- '@vue/devtools-api@7.7.2':
- resolution: {integrity: sha512-1syn558KhyN+chO5SjlZIwJ8bV/bQ1nOVTG66t2RbG66ZGekyiYNmRO7X9BJCXQqPsFHlnksqvPhce2qpzxFnA==}
+ '@vue/runtime-core@3.5.43':
+ resolution: {integrity: sha512-hU6U6VnVhBGQDpvlnnDlIB8ZGJBiOcgk2lh/0InltHiz3D8oSkluvuvY+do1G2H3+udeKFsmaBlgVYP7gXQzEw==}
- '@vue/devtools-api@7.7.7':
- resolution: {integrity: sha512-lwOnNBH2e7x1fIIbVT7yF5D+YWhqELm55/4ZKf45R9T8r9dE2AIOy8HKjfqzGsoTHFbWbr337O4E0A0QADnjBg==}
+ '@vue/runtime-dom@3.5.43':
+ resolution: {integrity: sha512-Bb2Jc0YjjJdMt1SJmb9b2L/IWd3I8lIT9x9eS/xvvP9CiVgna0ffua74xKRmt4/uSJ+0r4iN8ex1jrqkhQGWQw==}
- '@vue/devtools-core@7.7.7':
- resolution: {integrity: sha512-9z9TLbfC+AjAi1PQyWX+OErjIaJmdFlbDHcD+cAMYKY6Bh5VlsAtCeGyRMrXwIlMEQPukvnWt3gZBLwTAIMKzQ==}
- peerDependencies:
- vue: ^3.0.0
+ '@vue/server-renderer@3.5.43':
+ resolution: {integrity: sha512-l2Ygjv9NehV94PSBxNWsAHC0j/eIIKbn92mBuWXAPGLnn6HfJ6MH5ubsd+Nk0YoZ5FRuxWI1P2VSoh+dbPQhCQ==}
- '@vue/devtools-kit@7.7.7':
- resolution: {integrity: sha512-wgoZtxcTta65cnZ1Q6MbAfePVFxfM+gq0saaeytoph7nEa7yMXoi6sCPy4ufO111B9msnw0VOWjPEFCXuAKRHA==}
+ '@vue/shared@3.5.43':
+ resolution: {integrity: sha512-uksS7YGMR5NZyr4JNq0Rp+QyLns0ueaz20KwzIPW9R0LH1Vnt4E+XUM29PNseEbf1www2gOuhuDi5AKOIXag9Q==}
- '@vue/devtools-shared@7.7.7':
- resolution: {integrity: sha512-+udSj47aRl5aKb0memBvcUG9koarqnxNM5yjuREvqwK6T3ap4mn3Zqqc17QrBFTqSMjr3HK1cvStEZpMDpfdyw==}
+ '@vueuse/core@12.8.2':
+ resolution: {integrity: sha512-HbvCmZdzAu3VGi/pWYm5Ut+Kd9mn1ZHnn4L5G8kOQTPs/IwIAmJoBrmYk2ckLArgMXZj0AW3n5CAejLUO+PhdQ==}
- '@vue/language-core@2.2.12':
- resolution: {integrity: sha512-IsGljWbKGU1MZpBPN+BvPAdr55YPkj2nB/TBNGNC32Vy2qLG25DYu/NBN2vNtZqdRbTRjaoYrahLrToim2NanA==}
+ '@vueuse/integrations@12.8.2':
+ resolution: {integrity: sha512-fbGYivgK5uBTRt7p5F3zy6VrETlV9RtZjBqd1/HxGdjdckBgBM4ugP8LHpjolqTj14TXTxSK1ZfgPbHYyGuH7g==}
peerDependencies:
- typescript: '*'
- peerDependenciesMeta:
- typescript:
- optional: true
-
- '@vue/reactivity@3.5.17':
- resolution: {integrity: sha512-l/rmw2STIscWi7SNJp708FK4Kofs97zc/5aEPQh4bOsReD/8ICuBcEmS7KGwDj5ODQLYWVN2lNibKJL1z5b+Lw==}
-
- '@vue/runtime-core@3.5.17':
- resolution: {integrity: sha512-QQLXa20dHg1R0ri4bjKeGFKEkJA7MMBxrKo2G+gJikmumRS7PTD4BOU9FKrDQWMKowz7frJJGqBffYMgQYS96Q==}
-
- '@vue/runtime-dom@3.5.17':
- resolution: {integrity: sha512-8El0M60TcwZ1QMz4/os2MdlQECgGoVHPuLnQBU3m9h3gdNRW9xRmI8iLS4t/22OQlOE6aJvNNlBiCzPHur4H9g==}
-
- '@vue/server-renderer@3.5.17':
- resolution: {integrity: sha512-BOHhm8HalujY6lmC3DbqF6uXN/K00uWiEeF22LfEsm9Q93XeJ/plHTepGwf6tqFcF7GA5oGSSAAUock3VvzaCA==}
- peerDependencies:
- vue: 3.5.17
-
- '@vue/shared@3.5.17':
- resolution: {integrity: sha512-CabR+UN630VnsJO/jHWYBC1YVXyMq94KKp6iF5MQgZJs5I8cmjw6oVMO1oDbtBkENSHSSn/UadWlW/OAgdmKrg==}
-
- '@vueuse/core@10.11.1':
- resolution: {integrity: sha512-guoy26JQktXPcz+0n3GukWIy/JDNKti9v6VEMu6kV2sYBsWuGiTU8OWdg+ADfUbHg3/3DlqySDe7JmdHrktiww==}
-
- '@vueuse/core@13.5.0':
- resolution: {integrity: sha512-wV7z0eUpifKmvmN78UBZX8T7lMW53Nrk6JP5+6hbzrB9+cJ3jr//hUlhl9TZO/03bUkMK6gGkQpqOPWoabr72g==}
- peerDependencies:
- vue: ^3.5.0
-
- '@vueuse/integrations@10.11.1':
- resolution: {integrity: sha512-Y5hCGBguN+vuVYTZmdd/IMXLOdfS60zAmDmFYc4BKBcMUPZH1n4tdyDECCPjXm0bNT3ZRUy1xzTLGaUje8Xyaw==}
- peerDependencies:
- async-validator: ^4
- axios: ^1
- change-case: ^4
- drauu: ^0.3
- focus-trap: ^7
- fuse.js: ^6
- idb-keyval: ^6
- jwt-decode: ^3
- nprogress: ^0.2
- qrcode: ^1.5
- sortablejs: ^1
- universal-cookie: ^6
- peerDependenciesMeta:
- async-validator:
- optional: true
- axios:
- optional: true
- change-case:
- optional: true
- drauu:
- optional: true
- focus-trap:
- optional: true
- fuse.js:
- optional: true
- idb-keyval:
- optional: true
- jwt-decode:
- optional: true
- nprogress:
- optional: true
- qrcode:
- optional: true
- sortablejs:
- optional: true
- universal-cookie:
- optional: true
-
- '@vueuse/integrations@13.5.0':
- resolution: {integrity: sha512-7RACJySnlpl0MkSzxbtadioNGSX4TL5/Wl2cUy4nDq/XkeHwPYvVM880HJUSiap/FXhVEup9VKTM9y/n5UspAw==}
- peerDependencies:
- async-validator: ^4
- axios: ^1
- change-case: ^5
- drauu: ^0.4
- focus-trap: ^7
- fuse.js: ^7
- idb-keyval: ^6
- jwt-decode: ^4
- nprogress: ^0.2
- qrcode: ^1.5
- sortablejs: ^1
- universal-cookie: ^7 || ^8
- vue: ^3.5.0
+ async-validator: ^4
+ axios: ^1
+ change-case: ^5
+ drauu: ^0.4
+ focus-trap: ^7
+ fuse.js: ^7
+ idb-keyval: ^6
+ jwt-decode: ^4
+ nprogress: ^0.2
+ qrcode: ^1.5
+ sortablejs: ^1
+ universal-cookie: ^7
peerDependenciesMeta:
async-validator:
optional: true
@@ -1708,272 +1085,67 @@ packages:
universal-cookie:
optional: true
- '@vueuse/metadata@10.11.1':
- resolution: {integrity: sha512-IGa5FXd003Ug1qAZmyE8wF3sJ81xGLSqTqtQ6jaVfkeZ4i5kS2mwQF61yhVqojRnenVew5PldLyRgvdl4YYuSw==}
-
- '@vueuse/metadata@13.5.0':
- resolution: {integrity: sha512-euhItU3b0SqXxSy8u1XHxUCdQ8M++bsRs+TYhOLDU/OykS7KvJnyIFfep0XM5WjIFry9uAPlVSjmVHiqeshmkw==}
+ '@vueuse/metadata@12.8.2':
+ resolution: {integrity: sha512-rAyLGEuoBJ/Il5AmFHiziCPdQzRt88VxR+Y/A/QhJ1EWtWqPBBAxTAFaSkviwEuOEZNtW8pvkPgoCZQ+HxqW1A==}
- '@vueuse/shared@10.11.1':
- resolution: {integrity: sha512-LHpC8711VFZlDaYUXEBbFBCQ7GS3dVU9mjOhhMhXP6txTV4EhYQg/KGnQuvt/sPAtoUKq7VVUnL6mVtFoL42sA==}
-
- '@vueuse/shared@13.5.0':
- resolution: {integrity: sha512-K7GrQIxJ/ANtucxIXbQlUHdB0TPA8c+q5i+zbrjxuhJCnJ9GtBg75sBSnvmLSxHKPg2Yo8w62PWksl9kwH0Q8g==}
- peerDependencies:
- vue: ^3.5.0
+ '@vueuse/shared@12.8.2':
+ resolution: {integrity: sha512-dznP38YzxZoNloI0qpEfpkms8knDtaoQ6Y/sfS0L7Yki4zh40LFHEhur0odJC6xTHG5dxWVPiUWBXn+wCG2s5w==}
acorn-jsx@5.3.2:
resolution: {integrity: sha512-rq9s+JNhf0IChjtDXxllJ7g41oZk5SlXtp0LHwyA5cejwn7vKmKp4pPri6YEePv2PU65sAsegbXtIinmDFDXgQ==}
peerDependencies:
acorn: ^6.0.0 || ^7.0.0 || ^8.0.0
- acorn@8.15.0:
- resolution: {integrity: sha512-NZyJarBfL7nWwIq+FDL6Zp/yHEhePMNnnJ0y3qfieCrmNvYct8uvtiV41UvlSe6apAfk0fY1FbWx+NwfmpvtTg==}
+ acorn@8.18.0:
+ resolution: {integrity: sha512-lGq+9yr1/GuAWaVYIHRjvvySG5/4VfKIvC8EWxStPdcDh/Ka7FG3twP6v4d5BkravUilhIAsG4Qj83t02LWUPQ==}
engines: {node: '>=0.4.0'}
hasBin: true
- agent-base@7.1.4:
- resolution: {integrity: sha512-MnA+YT8fwfJPgBx3m60MNqakm30XOkyIoH1y6huTQvC0PwZG7ki8NacLBcrPbNoo8vEZy7Jpuk7+jMO+CUovTQ==}
- engines: {node: '>= 14'}
-
- ajv@6.12.6:
- resolution: {integrity: sha512-j3fVLgvTo527anyYyJOGTYJbG+vnnQYvE0m5mmkc1TK+nxAppkCLMIL0aZ4dblVCNoGShhm+kzE4ZUykBoMg4g==}
-
- ajv@8.17.1:
- resolution: {integrity: sha512-B/gBuNg5SiMTrPkC+A2+cW0RszwxYmn6VYxB/inlBStS5nx6xHIt/ehKRhIMhqusl7a8LjQoZnjCs5vhwxOQ1g==}
+ ajv@6.15.0:
+ resolution: {integrity: sha512-fgFx7Hfoq60ytK2c7DhnF8jIvzYgOMxfugjLOSMHjLIPgenqa7S7oaagATUq99mV6IYvN2tRmC0wnTYX6iPbMw==}
- algoliasearch@5.34.0:
- resolution: {integrity: sha512-wioVnf/8uuG8Bmywhk5qKIQ3wzCCtmdvicPRb0fa3kKYGGoewfgDqLEaET1MV2NbTc3WGpPv+AgauLVBp1nB9A==}
+ algoliasearch@5.59.0:
+ resolution: {integrity: sha512-wUXzaeI7B526W4y1gFg3lcxgDZ67XSgRJIiellYWOas/pLpO7rOtxm9Gr2E/C8aiSDXIgx1q5TdSsvK67Uakqw==}
engines: {node: '>= 14.0.0'}
- alien-signals@1.0.13:
- resolution: {integrity: sha512-OGj9yyTnJEttvzhTUWuscOvtqxq5vrhF7vL9oS0xJ2mK0ItPYP1/y+vCFebfxoEyAz0++1AIwJ5CMr+Fk3nDmg==}
-
- ansi-escapes@7.0.0:
- resolution: {integrity: sha512-GdYO7a61mR0fOlAsvC9/rIHf7L96sBc6dEWzeOu+KAea5bZyQRPIpojrVoI4AXGJS/ycu/fBTdLrUkA4ODrvjw==}
- engines: {node: '>=18'}
-
- ansi-regex@5.0.1:
- resolution: {integrity: sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==}
- engines: {node: '>=8'}
-
- ansi-regex@6.1.0:
- resolution: {integrity: sha512-7HSX4QQb4CspciLpVFwyRe79O3xsIZDDLER21kERQ71oaPodF8jL725AgJMFAYbooIqolJoRLuM81SpeUkpkvA==}
- engines: {node: '>=12'}
-
- ansi-styles@4.3.0:
- resolution: {integrity: sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==}
- engines: {node: '>=8'}
-
- ansi-styles@6.2.1:
- resolution: {integrity: sha512-bN798gFfQX+viw3R7yrGWRqnrN2oRkEkUjjl4JNn4E8GxxbjtG3FbrEIIY3l8/hrwUwIeCZvi4QuOTP4MErVug==}
- engines: {node: '>=12'}
-
- ansis@4.1.0:
- resolution: {integrity: sha512-BGcItUBWSMRgOCe+SVZJ+S7yTRG0eGt9cXAHev72yuGcY23hnLA7Bky5L/xLyPINoSN95geovfBkqoTlNZYa7w==}
- engines: {node: '>=14'}
-
- anymatch@3.1.3:
- resolution: {integrity: sha512-KMReFUr0B4t+D+OBkjR3KYqvocp2XaSzO55UcB6mgQMd3KbcE+mWTyvVV7D/zsdEbNnV6acZUutkiHQXvTr1Rw==}
- engines: {node: '>= 8'}
+ alien-signals@3.2.1:
+ resolution: {integrity: sha512-I8FjmltrfnDFoZedi5CG8DghVYNhzb/Ijluz7tCSJH0xpd0484Kowhbb1XDYOxfJpU1p5wnM2X54dA+IfGyD1g==}
argparse@1.0.10:
resolution: {integrity: sha512-o5Roy6tNG4SL/FOkCAN6RzjiakZS25RLYFrcMttJqbdd8BWrnA+fGz57iN5Pb06pvBGvl5gQ0B48dJlslXvoTg==}
- argparse@2.0.1:
- resolution: {integrity: sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q==}
-
- ast-kit@2.1.1:
- resolution: {integrity: sha512-mfh6a7gKXE8pDlxTvqIc/syH/P3RkzbOF6LeHdcKztLEzYe6IMsRCL7N8vI7hqTGWNxpkCuuRTpT21xNWqhRtQ==}
- engines: {node: '>=20.18.0'}
-
- ast-walker-scope@0.8.1:
- resolution: {integrity: sha512-72XOdbzQCMKERvFrxAykatn2pu7osPNq/sNUzwcHdWzwPvOsNpPqkawfDXVvQbA2RT+ivtsMNjYdojTUZitt1A==}
- engines: {node: '>=20.18.0'}
+ balanced-match@4.0.4:
+ resolution: {integrity: sha512-BLrgEcRTwX2o6gGxGOCNyMvGSp35YofuYzw9h1IMTRmKqttAZZVU67bdb9Pr2vUHA8+j3i2tJfjO6C6+4myGTA==}
+ engines: {node: 18 || 20 || >=22}
- astral-regex@2.0.0:
- resolution: {integrity: sha512-Z7tMw1ytTXt5jqMcOP+OQteU1VuNK9Y02uuJtKQ1Sv69jXQKKg5cibLwGJow8yzZP+eAc18EmLGPal0bp36rvQ==}
- engines: {node: '>=8'}
-
- async@3.2.6:
- resolution: {integrity: sha512-htCUDlxyyCLMgaM3xXg0C0LW2xqfuQ6p05pCEIsXuyQ+a1koYKTuBMzRNwmybfLgvJDMd0r1LTn4+E0Ti6C2AA==}
-
- asynckit@0.4.0:
- resolution: {integrity: sha512-Oei9OH4tRh0YqU3GxhX79dM/mwVgvbZJaSNaRk+bshkj0S5cfHcgYakreBjrHwatXKbz+IoIdYLxrKim2MjW0Q==}
-
- axios@1.10.0:
- resolution: {integrity: sha512-/1xYAC4MP/HEG+3duIhFr4ZQXR4sQXOIe+o6sdqzeykGLx6Upp/1p8MHqhINOvGeP7xyNHe7tsiJByc4SSVUxw==}
-
- balanced-match@1.0.2:
- resolution: {integrity: sha512-3oSeUO0TMV67hN1AmbXsK4yaqU7tjiHlbxRDZOpH0KW9+CeX4bRAaX0Anxt0tx2MrpRpWwQaPwIlISEJhYU5Pw==}
-
- beasties@0.3.5:
- resolution: {integrity: sha512-NaWu+f4YrJxEttJSm16AzMIFtVldCvaJ68b1L098KpqXmxt9xOLtKoLkKxb8ekhOrLqEJAbvT6n6SEvB/sac7A==}
- engines: {node: '>=14.0.0'}
-
- before-after-hook@3.0.2:
- resolution: {integrity: sha512-Nik3Sc0ncrMK4UUdXQmAnRtzmNQTAAXmXIopizwZ1W1t8QmfJj+zL4OA2I7XPTPW5z5TDqv4hRo/JzouDJnX3A==}
-
- binary-extensions@2.3.0:
- resolution: {integrity: sha512-Ceh+7ox5qe7LJuLHoY0feh3pHuUDHAcRUeyL2VYghZwfpkNIy/+8Ocg0a3UuSoYzavmylwuLWQOf3hl0jjMMIw==}
- engines: {node: '>=8'}
-
- birpc@2.5.0:
- resolution: {integrity: sha512-VSWO/W6nNQdyP520F1mhf+Lc2f8pjGQOtoHHm7Ze8Go1kX7akpVIrtTa0fn+HB0QJEDVacl6aO08YE0PgXfdnQ==}
-
- blueimp-md5@2.19.0:
- resolution: {integrity: sha512-DRQrD6gJyy8FbiE4s+bDoXS9hiW3Vbx5uCdwvcCf3zLHL+Iv7LtGHLpr+GZV8rHG8tK766FGYBwRbu8pELTt+w==}
-
- body-parser@2.2.0:
- resolution: {integrity: sha512-02qvAaxv8tp7fBa/mw1ga98OGm+eCbqzJOKoRt70sLmfEEi+jyBYVTDGfCL/k06/4EMk/z01gCe7HoCH/f2LTg==}
- engines: {node: '>=18'}
+ birpc@2.9.0:
+ resolution: {integrity: sha512-KrayHS5pBi69Xi9JmvoqrIgYGDkD6mcSe/i6YKi3w5kekCLzrX4+nawcXqrj2tIp50Kw/mT/s3p+GVK0A0sKxw==}
boolbase@1.0.0:
resolution: {integrity: sha512-JZOSA7Mo9sNGB8+UjSgzdLtokWAky1zbztM3WRLCbZ70/3cTANmQmOdR7y2g+J0e2WXywy1yS468tY+IruqEww==}
- brace-expansion@1.1.12:
- resolution: {integrity: sha512-9T9UjW3r0UW5c1Q7GTwllptXwhvYmEzFhzMfZ9H7FQWt+uZePjZPjBP/W1ZEyZ1twGWom5/56TF4lPcqjnDHcg==}
-
- brace-expansion@2.0.2:
- resolution: {integrity: sha512-Jt0vHyM+jmUBqojB7E1NIYadt0vI0Qxjxd2TErW94wDz+E2LAm5vKMXXwg6ZZBTHPuUlDgQHKXvjGBdfcF1ZDQ==}
-
- braces@3.0.3:
- resolution: {integrity: sha512-yQbXgO/OSZVD2IsiLlro+7Hf6Q18EJrKSEsdoMzKePKXct3gvD8oLcOQdIzGupr5Fj+EDe8gO/lxc1BzfMpxvA==}
- engines: {node: '>=8'}
-
- browserslist@4.25.1:
- resolution: {integrity: sha512-KGj0KoOMXLpSNkkEI6Z6mShmQy0bc1I+T7K9N81k4WWMrfz+6fQ6es80B/YLAeRoKvjYE1YSHHOW1qe9xIVzHw==}
- engines: {node: ^6 || ^7 || ^8 || ^9 || ^10 || ^11 || ^12 || >=13.7}
- hasBin: true
-
- buffer-from@1.1.2:
- resolution: {integrity: sha512-E+XQCRwSbaaiChtv6k6Dwgc+bx+Bs6vuKJHHl5kox/BaKbhiXzqQOwK4cO22yElGp2OCmjwVhT3HmxgyPGnJfQ==}
-
- bundle-name@4.1.0:
- resolution: {integrity: sha512-tjwM5exMg6BGRI+kNmTntNsvdZS1X8BFYS6tnJ2hdH0kVxM6/eVZ2xy+FqStSWvYmtfFMDLIxurorHwDKfDz5Q==}
- engines: {node: '>=18'}
-
- bytes@3.1.2:
- resolution: {integrity: sha512-/Nf7TyzTx6S3yRJObOAV7956r8cr2+Oj8AC5dt8wSP3BQAoeX58NoHyCU8P8zGkNXStjTSi6fzO6F0pBdcYbEg==}
- engines: {node: '>= 0.8'}
-
- cac@6.7.14:
- resolution: {integrity: sha512-b6Ilus+c3RrdDk+JhLKUAQfzzgLEPy6wcXqS7f/xe1EETvsDP6GORG7SFuOs6cID5YkqchW/LXZbX5bc8j7ZcQ==}
- engines: {node: '>=8'}
-
- call-bind-apply-helpers@1.0.2:
- resolution: {integrity: sha512-Sp1ablJ0ivDkSzjcaJdxEunN5/XvksFJ2sMBFfq6x0ryhQV/2b/KwFe21cMpmHtPOSij8K99/wSfoEuTObmuMQ==}
- engines: {node: '>= 0.4'}
-
- call-bound@1.0.4:
- resolution: {integrity: sha512-+ys997U96po4Kx/ABpBCqhA9EuxJaQWDQg7295H4hBphv3IZg0boBKuwYpt4YXp6MZ5AmZQnU/tyMTlRpaSejg==}
- engines: {node: '>= 0.4'}
-
- callsites@3.1.0:
- resolution: {integrity: sha512-P8BjAsXvZS+VIDUI11hHCQEv74YT67YUi5JJFNWIqL235sBmjX4+qx9Muvls5ivyNENctx46xQLQ3aTuE7ssaQ==}
- engines: {node: '>=6'}
-
- camel-case@4.1.2:
- resolution: {integrity: sha512-gxGWBrTT1JuMx6R+o5PTXMmUnhnVzLQ9SNutD4YqKtI6ap897t3tKECYla6gCWEkplXnlNybEkZg9GEGxKFCgw==}
-
- camelcase@5.3.1:
- resolution: {integrity: sha512-L28STB170nwWS63UjtlEOE3dldQApaJXZkOI1uMFfzf3rRuPegHaHesyee+YxQ+W6SvRDQV6UrdOdRiR153wJg==}
- engines: {node: '>=6'}
-
- camelcase@6.3.0:
- resolution: {integrity: sha512-Gmy6FhYlCY7uOElZUSbxo2UCDH8owEk996gkbrpsgGtrJLM3J7jGxl9Ic7Qwwj4ivOE5AWZWRMecDdF7hqGjFA==}
- engines: {node: '>=10'}
+ brace-expansion@5.0.12:
+ resolution: {integrity: sha512-YovQ3rzhaLMIrDjNDMkNS01tea93qhEhG5xy8f6+R0l+dw3Ki+5sCoIoI942iuLZTHWogWktgwVDhU09iNEimQ==}
+ engines: {node: 20 || >=22}
- caniuse-lite@1.0.30001727:
- resolution: {integrity: sha512-pB68nIHmbN6L/4C6MH1DokyR3bYqFwjaSs/sWDHGj4CTcFtQUQMuJftVwWkXq7mNWOybD3KhUv3oWHoGxgP14Q==}
+ cacheable@2.5.0:
+ resolution: {integrity: sha512-60cyAOytib/OzBw1JNSoSV/boK1AtHryDIjvVBk7XbN4ugfkM3+Sry7fEjNgPMGgOjuaZPAp8ruZ0Cxafwyq9g==}
ccount@2.0.1:
resolution: {integrity: sha512-eyrF0jiFpY+3drT6383f1qhkbGsLSifNAjA61IUjZjmLCWjItY6LB9ft9YhoDgwfmclB2zhu51Lc7+95b8NRAg==}
- chalk@4.1.2:
- resolution: {integrity: sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==}
- engines: {node: '>=10'}
-
- chalk@5.4.1:
- resolution: {integrity: sha512-zgVZuo2WcZgfUEmsn6eO3kINexW8RAE4maiQ8QNs8CtpPCSyMiYsULR3HQYkm3w8FIA3SberyMJMSldGsW+U3w==}
- engines: {node: ^12.17.0 || ^14.13 || >=16.0.0}
-
character-entities-html4@2.1.0:
resolution: {integrity: sha512-1v7fgQRj6hnSwFpq1Eu0ynr/CDEw0rXo2B61qXrLNdHZmPKgb7fqS1a2JwF0rISo9q77jDI8VMEHoApn8qDoZA==}
character-entities-legacy@3.0.0:
resolution: {integrity: sha512-RpPp0asT/6ufRm//AJVwpViZbGM/MkjQFxJccQRHmISF/22NBtsHqAWmL+/pmkPWoIUJdWyeVleTl1wydHATVQ==}
- charenc@0.0.2:
- resolution: {integrity: sha512-yrLQ/yVUFXkzg7EDQsPieE/53+0RlaWTs+wBrvW36cyilJ2SaDWfl4Yj7MtLTXleV9uEKefbAGUPv2/iWSooRA==}
-
- chevrotain-allstar@0.3.1:
- resolution: {integrity: sha512-b7g+y9A0v4mxCW1qUhf3BSVPg+/NvGErk/dOkrDaHA0nQIQGAtrOjlX//9OQtRlSCy+x9rfB5N8yC71lH1nvMw==}
- peerDependencies:
- chevrotain: ^11.0.0
-
- chevrotain@11.0.3:
- resolution: {integrity: sha512-ci2iJH6LeIkvP9eJW6gpueU8cnZhv85ELY8w8WiFtNjMHA5ad6pQLaJo9mEly/9qUyCpvqX8/POVUTf18/HFdw==}
-
- chokidar@3.6.0:
- resolution: {integrity: sha512-7VT13fmjotKpGipCW9JEQAusEPE+Ei8nl6/g4FBAmIm0GOOLMua9NDDo/DWp0ZAxCr3cPq5ZpBqmPAQgDda2Pw==}
- engines: {node: '>= 8.10.0'}
-
- chokidar@4.0.3:
- resolution: {integrity: sha512-Qgzu8kfBvo+cA4962jnP1KkS6Dop5NS6g7R5LFYJr4b8Ub94PPQXUksCw9PvXoeXPRRddRNC5C1JQUR2SMGtnA==}
- engines: {node: '>= 14.16.0'}
-
- clean-css@5.3.3:
- resolution: {integrity: sha512-D5J+kHaVb/wKSFcyyV75uCn8fiY4sV38XJoe4CUyGQ+mOU/fMVYUdH1hJC+CJQ5uY3EnW27SbJYS4X8BiLrAFg==}
- engines: {node: '>= 10.0'}
-
- cli-cursor@5.0.0:
- resolution: {integrity: sha512-aCj4O5wKyszjMmDT4tZj93kxyydN/K5zPWSCe6/0AV/AA1pqe5ZBIw0a2ZfPQV7lL5/yb5HsUreJ6UFAF1tEQw==}
- engines: {node: '>=18'}
-
- cli-spinners@2.9.2:
- resolution: {integrity: sha512-ywqV+5MmyL4E7ybXgKys4DugZbX0FC6LnwrhjuykIjnK9k8OQacQ7axGKnjDXWNhns0xot3bZI5h55H8yo9cJg==}
- engines: {node: '>=6'}
-
- cli-truncate@4.0.0:
- resolution: {integrity: sha512-nPdaFdQ0h/GEigbPClz11D0v/ZJEwxmeVZGeMo3Z5StPtUTkA9o1lD6QwoirYiSDzbcwn2XcjwmCp68W1IS4TA==}
- engines: {node: '>=18'}
-
- cliui@6.0.0:
- resolution: {integrity: sha512-t6wbgtoCXvAzst7QgXxJYqPt0usEfbgQdftEPbLL/cvv6HPE5VgvqCuAIDR0NgU52ds6rFwqrgakNLrHEjCbrQ==}
-
- cliui@9.0.1:
- resolution: {integrity: sha512-k7ndgKhwoQveBL+/1tqGJYNz097I7WOvwbmmU2AR5+magtbjPWQTS1C5vzGkBC8Ym8UWRzfKUzUUqFLypY4Q+w==}
- engines: {node: '>=20'}
-
- color-convert@2.0.1:
- resolution: {integrity: sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==}
- engines: {node: '>=7.0.0'}
-
- color-name@1.1.4:
- resolution: {integrity: sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==}
-
- colorette@2.0.20:
- resolution: {integrity: sha512-IfEDxwoWIjkeXL1eXcDiow4UbKjhLdq6/EuSVR9GMN7KVH3r9gQ83e73hsz1Nd1T3ijd5xv1wcWRYO+D6kCI2w==}
-
- combined-stream@1.0.8:
- resolution: {integrity: sha512-FQN4MRfuJeHf7cBbBMJFXhKSDq+2kAArBlmRBvcvFE5BB1HZKXtSFASDhdlz9zOYwxh8lDdnvmMOe/+5cdoEdg==}
- engines: {node: '>= 0.8'}
+ chevrotain@11.1.2:
+ resolution: {integrity: sha512-opLQzEVriiH1uUQ4Kctsd49bRoFDXGGSC4GUqj7pGyxM3RehRhvTlZJc1FL/Flew2p5uwxa1tUDWKzI4wNM8pg==}
comma-separated-tokens@2.0.3:
resolution: {integrity: sha512-Fu4hJdvzeylCfQPp9SGWidpzrMs7tTrlu6Vb8XGaRGck8QSNZJJp538Wrb60Lax4fPwR64ViY468OIUTbRlGZg==}
- commander@10.0.1:
- resolution: {integrity: sha512-y4Mg2tXshplEbSGzx7amzPwKKOCGuoSRP/CjEdwwk0FOGlUbq6lKuoyDZTNZkmxHdJtp54hdfY/JUrdL7Xfdug==}
- engines: {node: '>=14'}
-
- commander@14.0.0:
- resolution: {integrity: sha512-2uM9rYjPvyq39NwLRqaiLtWHyDC1FvryJDa2ATTVims5YAS4PupsEQsDvP14FqhFr0P49CYDugi59xaxJlTXRA==}
- engines: {node: '>=20'}
-
- commander@2.20.3:
- resolution: {integrity: sha512-GpVkmM8vF2vQUkj2LvZmD35JxeJOLCwJ9cUkugyk2nuhbv3+mJvpLYYt+0+USMxE+oj+ey/lJEnhZw75x/OMcQ==}
-
commander@7.2.0:
resolution: {integrity: sha512-QrWXB+ZQSVPmIWIhtEO9H+gwHaMGYiF5ChvoJ+K9ZGHG/sVsa6yiesAD1GC/x46sET00Xlwo1u49RVVVzvcSkw==}
engines: {node: '>= 10'}
@@ -1982,33 +1154,9 @@ packages:
resolution: {integrity: sha512-OkTL9umf+He2DZkUq8f8J9of7yL6RJKI24dVITBmNfZBmri9zYZQrKkuXiKhyfPSu8tUhnVBB1iKXevvnlR4Ww==}
engines: {node: '>= 12'}
- concat-map@0.0.1:
- resolution: {integrity: sha512-/Srv4dswyQNBfohGpz9o6Yb3Gz3SrUDqBH5rTuhGR7ahtlbYKnVxw2bCFMRljaA7EXHaXZ8wsHdodFvbkhKmqg==}
-
- confbox@0.1.8:
- resolution: {integrity: sha512-RMtmw0iFkeR4YV+fUOSucriAQNb9g8zFR52MWCtl+cCZOFRNL6zeB395vPzFhEjjn4fMxXudmELnl/KF/WrK6w==}
-
- confbox@0.2.2:
- resolution: {integrity: sha512-1NB+BKqhtNipMsov4xI/NnhCKp9XG9NamYp5PVm9klAT0fsrNPjaFICsCFhNhwZJKNh7zB/3q8qXz0E9oaMNtQ==}
-
- consola@3.4.2:
- resolution: {integrity: sha512-5IKcdX0nnYavi6G7TtOhwkYzyjfJlatbjMjuLSfE2kYT5pMDOilZ4OvMhi637CcDICTmz3wARPoyhqyX1Y+XvA==}
- engines: {node: ^14.18.0 || >=16.10.0}
-
- content-type@1.0.5:
- resolution: {integrity: sha512-nTjqfcBFEipKdXCv4YDQWCfmcLZKm81ldF0pAopTvyrFGVbcR6P/VAAd5G7N+0tTr8QqiU0tFadD6FK4NtJwOA==}
- engines: {node: '>= 0.6'}
-
- convert-source-map@2.0.0:
- resolution: {integrity: sha512-Kvp459HrV2FEJ1CAsi1Ku+MY3kasH19TFykTz2xWmMeq6bk2NU3XXvfJ+Q61m0xktWwt+1HSYf3JZsTms3aRJg==}
-
- copy-anything@3.0.5:
- resolution: {integrity: sha512-yCEafptTtb4bk7GLEQoM8KVJpxAfdBJYaXyzQEgQQQgYrZiDp8SJmGKlYza6CYjEDNstAdNdKA3UuoULlEbS6w==}
- engines: {node: '>=12.13'}
-
- cors@2.8.5:
- resolution: {integrity: sha512-KIHbLJqu73RGr/hnbrO9uBeixNGuvSQjul/jdFvS/KFSIH1hWVd1ng7zOHx+YrEfInLG7q4n6GHQ9cDtxv/P6g==}
- engines: {node: '>= 0.10'}
+ copy-anything@4.1.3:
+ resolution: {integrity: sha512-i6UIxTjvO3VPljHh+Kb3OS3idg+B91qNN+POpY07lwLSrFo0583PwbBxmIBBlYT6yvf5Cpjx8pG+GDqTIHCOSg==}
+ engines: {node: '>=18'}
cose-base@1.0.3:
resolution: {integrity: sha512-s9whTXInMSgAp/NVXVNuVxVKzGH2qck3aQlVHxDCdAEPgtMKwc4Wq6/QKhgdEdgbLSi9rBTAcPoRa6JpiG4ksg==}
@@ -2020,29 +1168,13 @@ packages:
resolution: {integrity: sha512-uV2QOWP2nWzsy2aMp8aRibhi9dlzF5Hgh5SHaB9OiTGEyDTiJJyx0uy51QXdyWbtAHNua4XJzUKca3OzKUd3vA==}
engines: {node: '>= 8'}
- crypt@0.0.2:
- resolution: {integrity: sha512-mCxBlsHFYh9C+HVpiEacem8FEBnMXgU9gy4zmNC+SXAZNB/1idgp/aulFJ4FgCi7GPEVbfyng092GqL2k2rmow==}
-
- css-i18n@0.0.5:
- resolution: {integrity: sha512-iIBukKoe2xPzecUUEeIsTp7jr78A55+BKMgM18esXni4i3J4//qadHlAyvkgO6/4VsAa+eLF8uOMqlhvGNSjfg==}
-
- css-select@6.0.0:
- resolution: {integrity: sha512-rZZVSLle8v0+EY8QAkDWrKhpgt6SA5OtHsgBnsj6ZaLb5dmDVOWUDtQitd9ydxxvEjhewNudS6eTVU7uOyzvXw==}
-
- css-tree@3.1.0:
- resolution: {integrity: sha512-0eW44TGN5SQXU1mWSkKwFstI/22X2bG1nYzZTYMAWjylYURhse752YgbE4Cx46AC+bAvI+/dYTPRk1LqSUnu6w==}
- engines: {node: ^10 || ^12.20.0 || ^14.13.0 || >=15.0.0}
-
- css-what@7.0.0:
- resolution: {integrity: sha512-wD5oz5xibMOPHzy13CyGmogB3phdvcDaB5t0W/Nr5Z2O/agcB8YwOz6e2Lsp10pNDzBoDO9nVa3RGs/2BttpHQ==}
- engines: {node: '>= 6'}
-
- cssstyle@4.6.0:
- resolution: {integrity: sha512-2z+rWdzbbSZv6/rhtvzvqeZQHrBaqgogqt85sqFNbabZOuFbCVFb8kPeEtZjiKkbrm395irpNKiYeFeLiQnFPg==}
- engines: {node: '>=18'}
+ cssesc@3.0.0:
+ resolution: {integrity: sha512-/Tb/JcjK111nNScGob5MNtsntNM1aCNUDipB/TkwZFhyDrrE47SOx/18wF2bbjgc3ZzCSKW1T5nt5EbFoAz/Vg==}
+ engines: {node: '>=4'}
+ hasBin: true
- csstype@3.1.3:
- resolution: {integrity: sha512-M1uQkMl8rQK/szD0LNhtqxIPLpimGm8sOBwU7lLnCpSbTyY3yeU1Vc7l4KT5zT4s/yOxHH5O7tIuuLOCnLADRw==}
+ csstype@3.2.3:
+ resolution: {integrity: sha512-z1HGKcYy2xA8AGQfwrn0PAy+PB7X/GSj3UVJW9qKyn43xWa+gl5nXmU4qqLMRzWVLFC8KusUX8T/0kCiOYpAIQ==}
cytoscape-cose-bilkent@4.1.0:
resolution: {integrity: sha512-wgQlVIUJF13Quxiv5e1gstZ08rnZj2XaLHGoFMYXz7SkNfCDOOteKBE6SYRfA9WxxI/iBc3ajfDoc6hb/MRAHQ==}
@@ -2054,8 +1186,8 @@ packages:
peerDependencies:
cytoscape: ^3.2.0
- cytoscape@3.32.1:
- resolution: {integrity: sha512-dbeqFTLYEwlFg7UGtcZhCCG/2WayX72zK3Sq323CEX29CY81tYfVhw1MIdduCtpstB0cTOhJswWlM/OEB3Xp+Q==}
+ cytoscape@3.34.3:
+ resolution: {integrity: sha512-yfYGhRcGAntq6YBD583j4n0Eg3jIxvWmZtz/5uz9UYkeIStSlMxuUja+ec5j3iBD8nv1rwaOAYMW09tBdkSeaQ==}
engines: {node: '>=0.10'}
d3-array@2.12.1:
@@ -2114,8 +1246,8 @@ packages:
resolution: {integrity: sha512-zxV/SsA+U4yte8051P4ECydjD/S+qeYtnaIyAs9tgHCqfguma/aAQDjo85A9Z6EKhBirHRJHXIgJUlffT4wdLg==}
engines: {node: '>=12'}
- d3-format@3.1.0:
- resolution: {integrity: sha512-YyUI6AEuY/Wpt8KWLgZHsIU86atmikuoOmCfommt0LYHiQSPjvX2AcFc38PX0CBpr2RCyZhjex+NS/LPOv6YqA==}
+ d3-format@3.1.2:
+ resolution: {integrity: sha512-AJDdYOdnyRDV5b6ArilzCPPwc1ejkHcoyFarqlPqT7zRYjhavcT3uSrqcMvsgh2CgoPbK3RCwyHaVyxYcP2Arg==}
engines: {node: '>=12'}
d3-geo@3.1.1:
@@ -2197,21 +1329,14 @@ packages:
resolution: {integrity: sha512-e1U46jVP+w7Iut8Jt8ri1YsPOvFpg46k+K8TpCb0P+zjCkjkPnV7WzfDJzMHy1LnA+wj5pLT1wjO901gLXeEhA==}
engines: {node: '>=12'}
- dagre-d3-es@7.0.11:
- resolution: {integrity: sha512-tvlJLyQf834SylNKax8Wkzco/1ias1OPw8DcUMDE7oUIoSEW25riQVuiu/0OWEFqT0cxHT3Pa9/D82Jr47IONw==}
-
- data-urls@5.0.0:
- resolution: {integrity: sha512-ZYP5VBHshaDAiVZxjbRVcFJpc+4xGgT0bK3vzy1HLN8jTO975HEbuYzZJcHoQEY5K1a0z8YayJkyVETa08eNTg==}
- engines: {node: '>=18'}
-
- dayjs@1.11.13:
- resolution: {integrity: sha512-oaMBel6gjolK862uaPQOVTA7q3TZhuSvuMQAAglQDOWYO9A91IrAOUJEyKVlqJlHE0vq5p5UXxzdPfMH/x6xNg==}
+ dagre-d3-es@7.0.14:
+ resolution: {integrity: sha512-P4rFMVq9ESWqmOgK+dlXvOtLwYg0i7u0HBGJER0LZDJT2VHIPAMZ/riPxqJceWMStH5+E61QxFra9kIS3AqdMg==}
- de-indent@1.0.2:
- resolution: {integrity: sha512-e/1zu3xH5MQryN2zdVaF0OrdNLUbvWxzMbi+iNA6Bky7l1RoP8a2fIbRocyHclXt/arDrrR6lL3TqFD9pMQTsg==}
+ dayjs@1.11.23:
+ resolution: {integrity: sha512-QDTCU0M0MxR3hQfnlDJfwekQiaanm1ubOD231u73WBckQ/fsamwRLiE2GBz6D3a/xF1NgfiDLJjXBa1hYOYTtQ==}
- debug@4.4.1:
- resolution: {integrity: sha512-KcKCqiftBJcZr++7ykoDIEwSa3XWowTfNPo92BYxjXiyYEVrUQh2aLyhxBCwww+heortUFxEJYcRzosstTEBYQ==}
+ debug@4.4.3:
+ resolution: {integrity: sha512-RGwwWnwQvkVfavKVt22FGLw+xYSdzARwm0ru6DhTVA3umU5hZc28V3kO4stgYryrTlLpuvgI9GiijltAjNbcqA==}
engines: {node: '>=6.0'}
peerDependencies:
supports-color: '*'
@@ -2219,186 +1344,79 @@ packages:
supports-color:
optional: true
- decamelize@1.2.0:
- resolution: {integrity: sha512-z2S+W9X73hAUUki+N+9Za2lBlun89zigOyGrsax+KUQ6wKW4ZoWpEYBkGhQjwAjjDCkWxhY0VKEhk8wzY7F5cA==}
- engines: {node: '>=0.10.0'}
-
- decimal.js@10.6.0:
- resolution: {integrity: sha512-YpgQiITW3JXGntzdUmyUR1V812Hn8T1YVXhCu+wO3OpS4eU9l4YdD3qjyiKdV6mvV29zapkMeD390UVEf2lkUg==}
-
deep-is@0.1.4:
resolution: {integrity: sha512-oIPzksmTg4/MriiaYGO+okXDT7ztn/w3Eptv/+gSIdMdKsJo0u4CfYNFJPy+4SKMuCqGw2wxnA+URMg3t8a/bQ==}
- deepmerge@4.3.1:
- resolution: {integrity: sha512-3sUqbMEc77XqpdNO7FRyRog+eW3ph+GYCbj+rK+uYyRMuwsVy0rMiVtPn+QJlKFvWP/1PYpapqYn0Me2knFn+A==}
- engines: {node: '>=0.10.0'}
-
- default-browser-id@5.0.0:
- resolution: {integrity: sha512-A6p/pu/6fyBcA1TRz/GqWYPViplrftcW2gZC9q79ngNCKAeR/X3gcEdXQHl4KNXV+3wgIJ1CPkJQ3IHM6lcsyA==}
- engines: {node: '>=18'}
-
- default-browser@5.2.1:
- resolution: {integrity: sha512-WY/3TUME0x3KPYdRRxEJJvXRHV4PyPoUsxtZa78lwItwRQRHhd2U9xOscaT/YTf8uCXIAjeJOFBVEh/7FtD8Xg==}
- engines: {node: '>=18'}
-
- define-lazy-prop@3.0.0:
- resolution: {integrity: sha512-N+MeXYoqr3pOgn8xfyRPREN7gHakLYjhsHhWGT3fWAiL4IkAt0iDw14QiiEm2bE30c5XX5q0FtAA3CK5f9/BUg==}
- engines: {node: '>=12'}
-
- defu@6.1.4:
- resolution: {integrity: sha512-mEQCMmwJu317oSz8CwdIOdwf3xMif1ttiM8LTufzc3g6kR+9Pe236twL8j3IYT1F7GfRgGcW6MWxzZjLIkuHIg==}
-
- delaunator@5.0.1:
- resolution: {integrity: sha512-8nvh+XBe96aCESrGOqMp/84b13H9cdKbG5P2ejQCh4d4sK9RL4371qou9drQjMhvnPmhWl5hnmqbEE0fXr9Xnw==}
-
- delayed-stream@1.0.0:
- resolution: {integrity: sha512-ZySD7Nf91aLB0RxL4KGrKHBXl7Eds1DAmEdcoVawXnLD7SDhpNgtuII2aAkg7a7QS41jxPSZ17p4VdGnMHk3MQ==}
- engines: {node: '>=0.4.0'}
-
- depd@2.0.0:
- resolution: {integrity: sha512-g7nH6P6dyDioJogAAGprGpCtVImJhpPk/roCzdb3fIh61/s/nPsfR6onyMwkCAR/OlC3yBC0lESvUoQEAssIrw==}
- engines: {node: '>= 0.8'}
+ delaunator@5.1.0:
+ resolution: {integrity: sha512-AGrQ4QSgssa1NGmWmLPqN5NY2KajF5MqxetNEO+o0n3ZwZZeTmt7bBnvzHWrmkZFxGgr4HdyFgelzgi06otLuQ==}
dequal@2.0.3:
resolution: {integrity: sha512-0je+qPKHEMohvfRTCEo3CrPG6cAzAYgmzKyxRiYSSDkS6eGJdyVJm7WaYA5ECaAD9wLB2T4EEeymA5aFVcYXCA==}
engines: {node: '>=6'}
- destr@2.0.5:
- resolution: {integrity: sha512-ugFTXCtDZunbzasqBxrK93Ik/DRYsO6S/fedkWEMKqt04xZ4csmnmwGDBAb07QWNaGMAmnTIemsYZCksjATwsA==}
-
- detect-libc@1.0.3:
- resolution: {integrity: sha512-pGjwhsmsp4kL2RTz08wcOlGN83otlqHeD/Z5T8GXZB+/YcpQ/dgo+lbU8ZsGxV0HIvqqxo9l7mqYwyYMD9bKDg==}
- engines: {node: '>=0.10'}
- hasBin: true
-
devlop@1.1.0:
resolution: {integrity: sha512-RWmIqhcFf1lRYBvNmr7qTNuyCt/7/ns2jbpp1+PalgE/rDQcBT0fioSMUpJ93irlUhC5hrg4cYqe6U+0ImW0rA==}
- dijkstrajs@1.0.3:
- resolution: {integrity: sha512-qiSlmBq9+BCdCA/L46dw8Uy93mloxsPSbwnm5yrKn2vMPiy8KyAskTF6zuV/j5BMsmOGZDPs7KjU+mjb670kfA==}
-
- dom-serializer@2.0.0:
- resolution: {integrity: sha512-wIkAryiqt/nV5EQKqQpo3SToSOV9J0DnbJqwK7Wv/Trc92zIAYZ4FlMu+JPFW1DfGFt81ZTCGgDEabffXeLyJg==}
-
- domelementtype@2.3.0:
- resolution: {integrity: sha512-OLETBj6w0OsagBwdXnPdN0cnMfF9opN69co+7ZrbfPGrdpPVNBUj02spi6B1N7wChLQiPn4CSH/zJvXw56gmHw==}
-
- domhandler@5.0.3:
- resolution: {integrity: sha512-cgwlv/1iFQiFnU96XXgROh8xTeetsnJiDsTc7TYCLFd9+/WNkIqPTxiM/8pSd8VIrhXGTf1Ny1q1hquVqDJB5w==}
- engines: {node: '>= 4'}
-
- dompurify@3.2.6:
- resolution: {integrity: sha512-/2GogDQlohXPZe6D6NOgQvXLPSYBqIWMnZ8zzOhn09REE4eyAzb+Hed3jhoM9OkuaJ8P6ZGTTVWQKAi8ieIzfQ==}
-
- domutils@3.2.2:
- resolution: {integrity: sha512-6kZKyUajlDuqlHKVX1w7gyslj9MPIXzIFiz/rGu35uC1wMi+kMhQwGhl4lt9unC9Vb9INnY9Z3/ZA3+FhASLaw==}
-
- dot-case@3.0.4:
- resolution: {integrity: sha512-Kv5nKlh6yRrdrGvxeJ2e5y2eRUpkUosIW4A2AS38zwSz27zu7ufDwQPi5Jhs3XAlGNetl3bmnGhQsMtkKJnj3w==}
-
- dunder-proto@1.0.1:
- resolution: {integrity: sha512-KIN/nDJBQRcXw0MLVhZE9iQHmG68qAVIBg9CqmUYjmQIhgij9U5MFvrqkUL5FbtyyzZuOeOt0zdeRe4UY7ct+A==}
- engines: {node: '>= 0.4'}
-
- duplexer@0.1.2:
- resolution: {integrity: sha512-jtD6YG370ZCIi/9GTaJKQxWTZD045+4R4hTk/x1UyoqadyJ9x9CgSi1RlVDQF8U2sxLLSnFkCaMihqljHIWgMg==}
-
- ee-first@1.1.1:
- resolution: {integrity: sha512-WMwm9LhRUo+WUaRN+vRuETqG89IgZphVSNkdFgeb6sS/E4OrDIN7t48CAewSHXc6C8lefD8KKfr5vY61brQlow==}
-
- ejs@3.1.10:
- resolution: {integrity: sha512-UeJmFfOrAQS8OJWPZ4qtgHyWExa088/MtK5UEyoJGFH67cDEXkZSviOiKRCZ4Xij0zxI3JECgYs3oKx+AizQBA==}
- engines: {node: '>=0.10.0'}
- hasBin: true
-
- electron-to-chromium@1.5.187:
- resolution: {integrity: sha512-cl5Jc9I0KGUoOoSbxvTywTa40uspGJt/BDBoDLoxJRSBpWh4FFXBsjNRHfQrONsV/OoEjDfHUmZQa2d6Ze4YgA==}
+ dompurify@3.4.16:
+ resolution: {integrity: sha512-sqo+pNp3qRhCIpbgRi1y8Tgk27Bo2Ry7w0dC1NBeNTdZChWjz9Xb/KOoZbRP/R6pQZ80Qw8YhXw13hWWBbMRnQ==}
- email-validator@2.0.4:
- resolution: {integrity: sha512-gYCwo7kh5S3IDyZPLZf6hSS0MnZT8QmJFqYvbqlDZSbwdZlY6QZWxJ4i/6UhITOJ4XzyI647Bm2MXKCLqnJ4nQ==}
- engines: {node: '>4.0'}
+ elkjs@0.9.3:
+ resolution: {integrity: sha512-f/ZeWvW/BCXbhGEf1Ujp29EASo/lk1FDnETgNKwJrsVvGZhUWCZyg3xLJjAsxfOmt8KjswHmI5EwCQcPMpOYhQ==}
emoji-regex-xs@1.0.0:
resolution: {integrity: sha512-LRlerrMYoIDrT6jgpeZ2YYl/L8EulRTt5hQcYjy5AInh7HWXKimpqx68aknBFpGL2+/IcogTcaydJEgaTmOpDg==}
- emoji-regex@10.4.0:
- resolution: {integrity: sha512-EC+0oUMY1Rqm4O6LLrgjtYDvcVYTy7chDnM4Q7030tP4Kwj3u/pR6gP9ygnp2CJMK5Gq+9Q2oqmrFJAz01DXjw==}
-
- emoji-regex@8.0.0:
- resolution: {integrity: sha512-MSjYzcWNOA0ewAHpz0MxpYFvwg6yjy1NG3xteoqz644VCo/RPgnr1/GGt+ic3iJTzQ8Eu3TdM14SawnVUmGE6A==}
-
- entities@4.5.0:
- resolution: {integrity: sha512-V0hjH4dGPh9Ao5p0MoRY6BVqtwCjhz6vI5LT8AJ55H+4g9/4vbHx1I54fS0XuclLhDHArPQCiMjDxjaL8fPxhw==}
- engines: {node: '>=0.12'}
-
- entities@6.0.1:
- resolution: {integrity: sha512-aN97NXWF6AWBTahfVOIrB/NShkzi5H7F9r1s9mD3cDj4Ko5f2qhhVoYMibXF7GlLveb/D2ioWay8lxI97Ven3g==}
+ entities@7.0.1:
+ resolution: {integrity: sha512-TWrgLOFUQTH994YUyl1yT4uyavY5nNB5muff+RtWaqNVCAK408b5ZnnbNAUEWLTCpum9w6arT70i1XdQ4UeOPA==}
engines: {node: '>=0.12'}
- environment@1.1.0:
- resolution: {integrity: sha512-xUtoPkMggbz0MPyPiIWr1Kp4aeWJjDZ6SMvURhimjdZgsRuDplF5/s9hcgGhyXMhs+6vpnuoiZ2kFiu3FMnS8Q==}
- engines: {node: '>=18'}
-
- error-stack-parser-es@0.1.5:
- resolution: {integrity: sha512-xHku1X40RO+fO8yJ8Wh2f2rZWVjqyhb1zgq1yZ8aZRQkv6OOKhKWRUaht3eSCUbAOBaKIgM+ykwFLE+QUxgGeg==}
-
- es-define-property@1.0.1:
- resolution: {integrity: sha512-e3nRfgfUZ4rNGL232gUgX06QNyyez04KdjFrF+LTRoOXmrOgFKDg4BCdsjW8EnT69eqdYGmRpJwiPVYNrCaW3g==}
- engines: {node: '>= 0.4'}
-
- es-errors@1.3.0:
- resolution: {integrity: sha512-Zf5H2Kxt2xjTvbJvP2ZWLEICxA6j+hAmMzIlypy4xcBg1vKVnx89Wy0GbS+kf5cwCVFFzdCFh2XSCFNULS6csw==}
- engines: {node: '>= 0.4'}
-
- es-object-atoms@1.1.1:
- resolution: {integrity: sha512-FGgH2h8zKNim9ljj7dankFPcICIK9Cp5bm+c2gQSYePhpaG5+esrLODihIorn+Pe6FGJzWhXQotPv73jTaldXA==}
- engines: {node: '>= 0.4'}
-
- es-set-tostringtag@2.1.0:
- resolution: {integrity: sha512-j6vWzfrGVfyXxge+O0x5sh6cvxAog0a/4Rdd2K36zCMV5eJ+/+tOAngRO8cODMNWbVRdVlmGZQL2YS3yR8bIUA==}
- engines: {node: '>= 0.4'}
+ es-toolkit@1.52.0:
+ resolution: {integrity: sha512-XTNEJQh1tY1ZJVcf6ayP/2n4ZPyaHlW2FWs7xvw5ddPuhUVjLD3olQVQS7kf58JbAB48iL0uL/jerTrjtV3lDA==}
esbuild@0.21.5:
resolution: {integrity: sha512-mg3OPMV4hXywwpoDxu3Qda5xCKQi+vCTZq8S9J/EpkhB2HzKXq4SNFZE3+NK93JYxc8VMSep+lOUSC/RVKaBqw==}
engines: {node: '>=12'}
hasBin: true
- esbuild@0.25.8:
- resolution: {integrity: sha512-vVC0USHGtMi8+R4Kz8rt6JhEWLxsv9Rnu/lGYbPR8u47B+DCBksq9JarW0zOO7bs37hyOK1l2/oqtbciutL5+Q==}
- engines: {node: '>=18'}
- hasBin: true
-
- escalade@3.2.0:
- resolution: {integrity: sha512-WUj2qlxaQtO4g6Pq5c29GTcWGDyd8itL8zTlipgECz3JesAiiOKotd8JU6otB3PACgG6xkJUyVhboMS+bje/jA==}
- engines: {node: '>=6'}
-
- escape-html@1.0.3:
- resolution: {integrity: sha512-NiSupZ4OeuGwr68lGIeym/ksIZMJodUGOSCZ/FSnTxcrekbvqrgdUxlJOMpijaKZVjAJrWrGs/6Jy8OMuyj9ow==}
-
escape-string-regexp@4.0.0:
resolution: {integrity: sha512-TtpcNJ3XAzx3Gq8sWRzJaVajRs0uVxA2YAkdb1jm2YkPz4G6egUFAyA3n5vtEIZefPk5Wa4UXbKuS5fKkJWdgA==}
engines: {node: '>=10'}
- escodegen@2.1.0:
- resolution: {integrity: sha512-2NlIDTwUWJN0mRPQOdtQBzbUHvdGY2P1VXSyU83Q3xKxM7WHX2Ql8dKq782Q9TgQUNOLEzEYu9bzLNj1q88I5w==}
- engines: {node: '>=6.0'}
+ eslint-config-prettier@10.1.8:
+ resolution: {integrity: sha512-82GZUjRS0p/jganf6q1rEO25VSoHH0hKPCTrgillPjdI/3bgBhAE1QzHrHTizjpRvy6pGAvKjDJtk2pF9NDq8w==}
hasBin: true
+ peerDependencies:
+ eslint: '>=7.0.0'
- eslint-scope@8.4.0:
- resolution: {integrity: sha512-sNXOfKCn74rt8RICKMvJS7XKV/Xk9kA7DyJr8mJik3S7Cwgy3qlkkmyS2uQB3jiJg6VNdZd/pDBJu0nvG2NlTg==}
+ eslint-plugin-vue@10.11.1:
+ resolution: {integrity: sha512-pasVXhl7wUmIvhujoqs/m0mJ9r59QW1IR9XXYKGR0FETzSM+Hhlf4qKIYgWiDDP+9YKv4YfbwskD7LqIdVcgQw==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
+ peerDependencies:
+ '@stylistic/eslint-plugin': ^2.0.0 || ^3.0.0 || ^4.0.0 || ^5.0.0
+ '@typescript-eslint/parser': ^7.0.0 || ^8.0.0
+ eslint: ^8.57.0 || ^9.0.0 || ^10.0.0
+ vue-eslint-parser: ^10.3.0
+ peerDependenciesMeta:
+ '@stylistic/eslint-plugin':
+ optional: true
+ '@typescript-eslint/parser':
+ optional: true
+
+ eslint-scope@9.1.2:
+ resolution: {integrity: sha512-xS90H51cKw0jltxmvmHy2Iai1LIqrfbw57b79w/J7MfvDfkIkFZ+kj6zC3BjtUwh150HsSSdxXZcsuv72miDFQ==}
+ engines: {node: ^20.19.0 || ^22.13.0 || >=24}
eslint-visitor-keys@3.4.3:
resolution: {integrity: sha512-wpc+LXeiyiisxPlEkUzU6svyS1frIO3Mgxj1fdy7Pm8Ygzguax2N3Fa/D/ag1WqbOprdI+uY6wMUl8/a2G+iag==}
engines: {node: ^12.22.0 || ^14.17.0 || >=16.0.0}
- eslint-visitor-keys@4.2.1:
- resolution: {integrity: sha512-Uhdk5sfqcee/9H/rCOJikYz67o0a2Tw2hGRPOG2Y1R2dg7brRe1uG0yaNQDHu+TO/uQPF/5eCapvYSmHUjt7JQ==}
- engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
+ eslint-visitor-keys@5.0.1:
+ resolution: {integrity: sha512-tD40eHxA35h0PEIZNeIjkHoDR4YjjJp34biM0mDvplBe//mB+IHCqHDGV7pxF+7MklTvighcCPPZC7ynWyjdTA==}
+ engines: {node: ^20.19.0 || ^22.13.0 || >=24}
- eslint@9.29.0:
- resolution: {integrity: sha512-GsGizj2Y1rCWDu6XoEekL3RLilp0voSePurjZIkxL3wlm5o5EC9VpgaP7lrCvjnkuLvzFBQWB3vWB3K5KQTveQ==}
- engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
+ eslint@10.11.0:
+ resolution: {integrity: sha512-P7a6UEEqb9G95MYAtqkmsTbVXIYyzIfl6NGOIJk162PaahFxFyeGcrlXYFSiagECg4sEm8IseJdZBKR3rx6MsQ==}
+ engines: {node: ^20.19.0 || ^22.13.0 || >=24}
hasBin: true
peerDependencies:
jiti: '*'
@@ -2406,21 +1424,17 @@ packages:
jiti:
optional: true
- espree@10.4.0:
- resolution: {integrity: sha512-j6PAQ2uUr79PZhBjP5C5fhl8e39FmRnOjsD5lGnWrFU8i2G776tBK7+nP8KuQUTTyAZUwfQqXAgrVH5MbH9CYQ==}
- engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
-
- espree@9.6.1:
- resolution: {integrity: sha512-oruZaFkjorTpF32kDSI5/75ViwGeZginGGy2NoOSg3Q9bnwlnmDm4HLnkl0RE3n+njDXR037aY1+x58Z/zFdwQ==}
- engines: {node: ^12.22.0 || ^14.17.0 || >=16.0.0}
+ espree@11.2.0:
+ resolution: {integrity: sha512-7p3DrVEIopW1B1avAGLuCSh1jubc01H2JHc8B4qqGblmg5gI9yumBgACjWo4JlIc04ufug4xJ3SQI8HkS/Rgzw==}
+ engines: {node: ^20.19.0 || ^22.13.0 || >=24}
esprima@4.0.1:
resolution: {integrity: sha512-eGuFFw7Upda+g4p+QHvnW0RyTX/SVeJBDM/gCtMARO0cLuT2HcEKnTPvhjV6aGeqrCB/sbNop0Kszm0jsaWU4A==}
engines: {node: '>=4'}
hasBin: true
- esquery@1.6.0:
- resolution: {integrity: sha512-ca9pw9fomFcKPvFLXhBKUK90ZvGibiGOvRJNbjljY7s7uq/5YO4BOzcYtJqExdx99rF6aAcnRxHmcUHcz6sQsg==}
+ esquery@1.7.0:
+ resolution: {integrity: sha512-Ap6G0WQwcU/LHsvLwON1fAQX9Zp0A2Y6Y/cJBl9r/JbW90Zyg4/zbG6zzKa2OTALELarYHmKu0GhpM5EO+7T0g==}
engines: {node: '>=0.10'}
esrecurse@4.3.0:
@@ -2434,224 +1448,74 @@ packages:
estree-walker@2.0.2:
resolution: {integrity: sha512-Rfkk/Mp/DL7JVje3u18FxFujQlTNR2q6QfMSMB7AvCBx91NGj/ba3kCfza0f6dVDbw7YlRf/nDrn7pQrCCyQ/w==}
- estree-walker@3.0.3:
- resolution: {integrity: sha512-7RUKfXgSMMkzt6ZuXmqapOurLGPPfgj6l9uRZ7lRGolvk0y2yocc35LdcxKC5PQZdn2DMqioAQ2NoWcrTKmm6g==}
-
esutils@2.0.3:
resolution: {integrity: sha512-kVscqXk4OCp68SZ0dkgEKVi6/8ij300KBWTJq32P/dYeWTSwK41WyTxalN1eRmA5Z9UU/LX9D7FWSmV9SAYx6g==}
engines: {node: '>=0.10.0'}
- eventemitter3@4.0.7:
- resolution: {integrity: sha512-8guHBZCwKnFhYdHr2ysuRWErTwhoN2X8XELRlrRwpmfeY2jjuUN4taQMsULKUVo1K4DvZl+0pgfyoysHxvmvEw==}
-
- eventemitter3@5.0.1:
- resolution: {integrity: sha512-GWkBvjiSZK87ELrYOSESUYeVIc9mvLLf/nXalMOS5dYrgZq9o5OVkbZAVM06CVxYsCwH9BDZFPlQTlPA1j4ahA==}
-
- execa@9.6.0:
- resolution: {integrity: sha512-jpWzZ1ZhwUmeWRhS7Qv3mhpOhLfwI+uAX4e5fOcXqwMR7EcJ0pj2kV1CVzHVMX/LphnKWD3LObjZCoJ71lKpHw==}
- engines: {node: ^18.19.0 || >=20.5.0}
-
- exsolve@1.0.7:
- resolution: {integrity: sha512-VO5fQUzZtI6C+vx4w/4BWJpg3s/5l+6pRQEHzFRM8WFi4XffSP1Z+4qi7GbjWbvRQEbdIco5mIMq+zX4rPuLrw==}
-
extend-shallow@2.0.1:
resolution: {integrity: sha512-zCnTtlxNoAiDc3gqY2aYAWFx7XWWiasuF2K8Me5WbN8otHKTUKBwjPtNpRs/rbUZm7KxWAaNj7P1a/p52GbVug==}
engines: {node: '>=0.10.0'}
- fast-content-type-parse@2.0.1:
- resolution: {integrity: sha512-nGqtvLrj5w0naR6tDPfB4cUmYCqouzyQiz6C5y/LtcDllJdrcc6WaWW6iXyIIOErTa/XRybj28aasdn4LkVk6Q==}
-
fast-deep-equal@3.1.3:
resolution: {integrity: sha512-f3qQ9oQy9j2AhBe/H9VC91wLmKBCCU/gDOnKNAYG5hswO7BLKj09Hc5HYNz9cGI++xlpDCIgDaitVs03ATR84Q==}
- fast-glob@3.3.3:
- resolution: {integrity: sha512-7MptL8U0cqcFdzIzwOTHoilX9x5BrNqye7Z/LuC7kCMRio1EMSyqRK3BEAUD7sXRq4iT4AzTVuZdhgQ2TCvYLg==}
- engines: {node: '>=8.6.0'}
-
fast-json-stable-stringify@2.1.0:
resolution: {integrity: sha512-lhd/wF+Lk98HZoTCtlVraHtfh5XYijIjalXck7saUtuanSDyLMxnHhSXEDJqHxD7msR8D0uCmqlkwjCV8xvwHw==}
fast-levenshtein@2.0.6:
resolution: {integrity: sha512-DCXu6Ifhqcks7TZKY3Hxp3y6qphY5SJZmrWMDrKcERSOXWQdMhU9Ig/PYrzyw/ul9jOIyh0N4M0tbC5hodg8dw==}
- fast-uri@3.0.6:
- resolution: {integrity: sha512-Atfo14OibSv5wAp4VWNsFYE1AchQRTv9cBGWET4pZWHzYshFSS9NQI6I57rdKn9croWVMbYFbLhJ+yJvmZIIHw==}
-
- fastq@1.19.1:
- resolution: {integrity: sha512-GwLTyxkCXjXbxqIhTsMI2Nui8huMPtnxg7krajPJAjnEG/iiOS7i+zCtWGZR9G0NBKbXKh6X9m9UIsYX/N6vvQ==}
-
- fdir@6.4.6:
- resolution: {integrity: sha512-hiFoqpyZcfNm1yc4u8oWCf9A2c4D3QjCrks3zmoVKVxpQRzmPNar1hUJcBG2RQHvEVGDN+Jm81ZheVLAQMK6+w==}
+ fdir@6.5.0:
+ resolution: {integrity: sha512-tIbYtZbucOs0BRGqPJkshJUYdL+SDH7dVM8gjy+ERp3WAUjLEFJE+02kanyHtwjWOnwrKYBiwAmM0p4kLJAnXg==}
+ engines: {node: '>=12.0.0'}
peerDependencies:
picomatch: ^3 || ^4
peerDependenciesMeta:
picomatch:
optional: true
- feed@5.1.0:
- resolution: {integrity: sha512-qGNhgYygnefSkAHHrNHqC7p3R8J0/xQDS/cYUud8er/qD9EFGWyCdUDfULHTJQN1d3H3WprzVwMc9MfB4J50Wg==}
- engines: {node: '>=20', pnpm: '>=10'}
-
- figures@6.1.0:
- resolution: {integrity: sha512-d+l3qxjSesT4V7v2fh+QnmFnUWv9lSpjarhShNTgBOfA0ttejbQUAlHLitbjkoRiDulW0OPoQPYIGhIC8ohejg==}
- engines: {node: '>=18'}
-
- file-entry-cache@8.0.0:
- resolution: {integrity: sha512-XXTUwCvisa5oacNGRP9SfNtYBNAMi+RPwBFmblZEF7N7swHYQS6/Zfk7SRwx4D5j3CH211YNRco1DEMNVfZCnQ==}
- engines: {node: '>=16.0.0'}
-
- filelist@1.0.4:
- resolution: {integrity: sha512-w1cEuf3S+DrLCQL7ET6kz+gmlJdbq9J7yXCSjK/OZCPA+qEN1WyF4ZAf0YYJa4/shHJra2t/d/r8SV4Ji+x+8Q==}
-
- fill-range@7.1.1:
- resolution: {integrity: sha512-YsGpe3WHLK8ZYi4tWDg2Jy3ebRz2rXowDxnld4bkQB00cc/1Zw9AWnC0i9ztDJitivtQvaI9KaLyKrc+hBW0yg==}
- engines: {node: '>=8'}
-
- find-up@4.1.0:
- resolution: {integrity: sha512-PpOwAdQ/YlXQ2vj8a3h8IipDuYRi3wceVQQGYWxNINccq40Anw7BlsEXCMbt1Zt+OLA6Fq9suIpIWD0OsnISlw==}
- engines: {node: '>=8'}
+ file-entry-cache@11.1.5:
+ resolution: {integrity: sha512-+PFTHITI08JIGhnNpGNI8T8inUpgZfk3GNEqfT9R2zZV2iFXg3CvqzSl/uEhs7TSGujYRELEANyDvS8Fj7+S7Q==}
find-up@5.0.0:
resolution: {integrity: sha512-78/PXT1wlLLDgTzDs7sjq9hzz0vXD+zn+7wypEe4fXQxCmdmqfGsEPQxmiCSQI3ajFV91bVSsvNtrJRiW6nGng==}
engines: {node: '>=10'}
- flat-cache@4.0.1:
- resolution: {integrity: sha512-f7ccFPK3SXFHpx15UIGyRJ/FJQctuKZ0zVuN3frBo4HnK3cay9VEW0R6yPYFHC0AgqhukPzKjq22t5DmAyqGyw==}
- engines: {node: '>=16'}
-
- flatted@3.3.3:
- resolution: {integrity: sha512-GX+ysw4PBCz0PzosHDepZGANEuFCMLrnRTiEy9McGjmkCQYwRq4A/X786G/fjM/+OjsWSU1ZrY5qyARZmO/uwg==}
-
- floating-vue@5.2.2:
- resolution: {integrity: sha512-afW+h2CFafo+7Y9Lvw/xsqjaQlKLdJV7h1fCHfcYQ1C4SVMlu7OAekqWgu5d4SgvkBVU0pVpLlVsrSTBURFRkg==}
- peerDependencies:
- '@nuxt/kit': ^3.2.0
- vue: ^3.2.0
- peerDependenciesMeta:
- '@nuxt/kit':
- optional: true
-
- focus-trap@7.6.5:
- resolution: {integrity: sha512-7Ke1jyybbbPZyZXFxEftUtxFGLMpE2n6A+z//m4CRDlj0hW+o3iYSmh8nFlYMurOiJVDmJRilUQtJr08KfIxlg==}
-
- follow-redirects@1.15.9:
- resolution: {integrity: sha512-gew4GsXizNgdoRyqmyfMHyAmXsZDk6mHkSxZFCzW9gwlbtOW44CDtYavM+y+72qD/Vq2l550kMF52DT8fOLJqQ==}
- engines: {node: '>=4.0'}
- peerDependencies:
- debug: '*'
- peerDependenciesMeta:
- debug:
- optional: true
+ flat-cache@6.1.23:
+ resolution: {integrity: sha512-f++BY9pTk+983xK1FLzlLpmM0i0z+jHmx3QESGkURMXujQZz1k5wzwX6hjnQ8goaD0B+sYnDK1yZ6MTyZfUaqA==}
- form-data@4.0.4:
- resolution: {integrity: sha512-KrGhL9Q4zjj0kiUt5OO4Mr/A/jlI2jDYs5eHBpYHPcBEVSiipAvn2Ko2HnPe20rmcuuvMHNdZFp+4IlGTMF0Ow==}
- engines: {node: '>= 6'}
+ flatted@3.4.4:
+ resolution: {integrity: sha512-5+ybhBZANEJxaH3X5evAFatUxLfEHSr7n6kYJ+1Qd0mUqr4eu9gIf6GDbWHf8RJijHrjjO8G+la14SlL2SeS1Q==}
- fs-extra@11.3.0:
- resolution: {integrity: sha512-Z4XaCL6dUDHfP/jT25jJKMmtxvuwbkrD1vNSMFlo9lNLY2c5FHYSQgHPRZUjAB26TpDEoW9HCOgplrdbaPV/ew==}
- engines: {node: '>=14.14'}
+ focus-trap@7.8.0:
+ resolution: {integrity: sha512-/yNdlIkpWbM0ptxno3ONTuf+2g318kh2ez3KSeZN5dZ8YC6AAmgeWz+GasYYiBJPFaYcSAPeu4GfhUaChzIJXA==}
fsevents@2.3.3:
resolution: {integrity: sha512-5xoDfX+fL7faATnagmWPpbFtwh/R77WmMMqqHGS65C3vvB0YHrgF+B1YmZ3441tMj5n63k0212XNoJwzlhffQw==}
engines: {node: ^8.16.0 || ^10.6.0 || >=11.0.0}
os: [darwin]
- function-bind@1.1.2:
- resolution: {integrity: sha512-7XHNxH7qX9xG5mIwxkhumTox/MIRNcOgDrxWsMt2pAr23WHp6MrRlN7FBSFpCpr+oVO0F744iUgR82nJMfG2SA==}
-
- fuse.js@7.1.0:
- resolution: {integrity: sha512-trLf4SzuuUxfusZADLINj+dE8clK1frKdmqiJNb1Es75fmI5oY6X2mxLVUciLLjxqw/xr72Dhy+lER6dGd02FQ==}
- engines: {node: '>=10'}
-
- gensync@1.0.0-beta.2:
- resolution: {integrity: sha512-3hN7NaskYvMDLQY55gnW3NQ+mesEAepTqlg+VEbj7zzqEMBVNhzcGYYeqFo/TlYz6eQiFcp1HcsCZO+nGgS8zg==}
- engines: {node: '>=6.9.0'}
-
- get-caller-file@2.0.5:
- resolution: {integrity: sha512-DyFP3BM/3YHTQOCUL/w0OZHR0lpKeGrxotcHWcqNEdnltqFwXVfhEBQ94eIo34AfQpo0rGki4cyIiftY06h2Fg==}
- engines: {node: 6.* || 8.* || >= 10.*}
-
- get-east-asian-width@1.3.0:
- resolution: {integrity: sha512-vpeMIQKxczTD/0s2CdEWHcb0eeJe6TFjxb+J5xgX7hScxqrGuyjmv4c1D4A/gelKfyox0gJJwIHF+fLjeaM8kQ==}
- engines: {node: '>=18'}
-
- get-intrinsic@1.3.0:
- resolution: {integrity: sha512-9fSjSaos/fRIVIp+xSJlE6lfwhES7LNtKaCBIamHsjr2na1BiABJPo0mOjjz8GJDURarmCPGqaiVg5mfjb98CQ==}
- engines: {node: '>= 0.4'}
-
- get-proto@1.0.1:
- resolution: {integrity: sha512-sTSfBjoXBp89JvIKIefqw7U2CCebsc74kiY6awiGogKtoSGbgjYE/G/+l9sF3MWFPNc9IcoOC4ODfKHfxFmp0g==}
- engines: {node: '>= 0.4'}
-
- get-stream@9.0.1:
- resolution: {integrity: sha512-kVCxPF3vQM/N0B1PmoqVUqgHP+EeVjmZSQn+1oCRPxd2P21P2F19lIgbR3HBosbB1PUhOAoctJnfEn2GbN2eZA==}
- engines: {node: '>=18'}
-
- giscus@1.6.0:
- resolution: {integrity: sha512-Zrsi8r4t1LVW950keaWcsURuZUQwUaMKjvJgTCY125vkW6OiEBkatE7ScJDbpqKHdZwb///7FVC21SE3iFK3PQ==}
-
- glob-parent@5.1.2:
- resolution: {integrity: sha512-AOIgSQCepiJYwP3ARnGx+5VnTu2HBYdzbGP45eLw1vr3zB3vZLeyed1sC9hnbcOc9/SrMyM5RPQrkGz4aS9Zow==}
- engines: {node: '>= 6'}
+ giscus@1.6.0:
+ resolution: {integrity: sha512-Zrsi8r4t1LVW950keaWcsURuZUQwUaMKjvJgTCY125vkW6OiEBkatE7ScJDbpqKHdZwb///7FVC21SE3iFK3PQ==}
glob-parent@6.0.2:
resolution: {integrity: sha512-XxwI8EOhVQgWp6iDL+3b0r86f4d6AX6zSU55HfB4ydCEuXLXc5FcYeOu+nnGftS4TEju/11rt4KJPTMgbfmv4A==}
engines: {node: '>=10.13.0'}
- global-directory@4.0.1:
- resolution: {integrity: sha512-wHTUcDUoZ1H5/0iVqEudYW4/kAlN5cZ3j/bXn0Dpbizl9iaUVeWSHqiOjsgk6OW2bkLclbBjzewBz6weQ1zA2Q==}
- engines: {node: '>=18'}
-
- globals@14.0.0:
- resolution: {integrity: sha512-oahGvuMGQlPw/ivIYBjVSrWAfWLBeku5tpPE2fOPLi+WHffIWbuh2tCjhyQhTBPMf5E9jDEH4FOmTYgYwbKwtQ==}
- engines: {node: '>=18'}
-
- globals@15.15.0:
- resolution: {integrity: sha512-7ACyT3wmyp3I61S4fG682L0VA2RGD9otkqGJIwNUMF1SWUombIIk+af1unuDYgMm082aHYwD+mzJvv9Iu8dsgg==}
+ globals@17.12.0:
+ resolution: {integrity: sha512-cezEd/DTyyht9cvSSURyygXPfy04GtWO/5e6ZPvH7fCtjKz9PYOmuawphw1Ctd1f6C+5JypXfGD7ahNMXvevBA==}
engines: {node: '>=18'}
- gopd@1.2.0:
- resolution: {integrity: sha512-ZUKRh6/kUFoAiTAtTYPZJ3hw9wNxx+BIBOijnlG9PnrJsCcSjs1wyyD6vJpaYtgnzDrKYRSqf3OO6Rfa93xsRg==}
- engines: {node: '>= 0.4'}
-
- graceful-fs@4.2.11:
- resolution: {integrity: sha512-RbJ5/jmFcNNCcDV5o9eTnBLJ/HszWV0P73bc+Ff4nS/rJj+YaS6IGyiOL0VoBYX+l1Wrl3k63h/KrH+nhJ0XvQ==}
-
- gravatar@1.8.2:
- resolution: {integrity: sha512-GdRwLM3oYpFQKy47MKuluw9hZ2gaCtiKPbDGdcDEuYDKlc8eNnW27KYL9LVbIDzEsx88WtDWQm2ClBcsgBnj6w==}
- engines: {node: '>=10'}
- hasBin: true
-
gray-matter@4.0.3:
resolution: {integrity: sha512-5v6yZd4JK3eMI3FqqCouswVqwugaA9r4dNZB1wwcmrD02QkV5H0y7XBQW8QwQqEaZY1pM9aqORSORhJRdNK44Q==}
engines: {node: '>=6.0'}
- gzip-size@6.0.0:
- resolution: {integrity: sha512-ax7ZYomf6jqPTQ4+XCpUGyXKHk5WweS+e05MBO4/y3WJ5RkmPXNKvX+bx1behVILVwr6JSQvZAku021CHPXG3Q==}
- engines: {node: '>=10'}
-
hachure-fill@0.5.2:
resolution: {integrity: sha512-3GKBOn+m2LX9iq+JC1064cSFprJY4jL1jCXTcpnfER5HYE2l/4EfWSGzkPa/ZDBmYI0ZOEj5VHV/eKnPGkHuOg==}
- has-flag@3.0.0:
- resolution: {integrity: sha512-sKJf1+ceQBr4SMkvQnBDNDtf4TXpVhVGateu0t918bl30FnbE2m4vNLX+VWe/dpjlb+HugGYzW7uQXH98HPEYw==}
- engines: {node: '>=4'}
-
- has-flag@4.0.0:
- resolution: {integrity: sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==}
- engines: {node: '>=8'}
-
- has-symbols@1.1.0:
- resolution: {integrity: sha512-1cDNdwJ2Jaohmb3sg4OmKaMBwuC48sYni5HUw2DvsC8LjGTLK9h+eb1X6RyuOHe4hT0ULCW68iomhjUoKUqlPQ==}
- engines: {node: '>= 0.4'}
-
- has-tostringtag@1.0.2:
- resolution: {integrity: sha512-NqADB8VjPFLM2V0VvHUewwwsw0ZWBaIdgo+ieHtK3hasLz4qeCRjYcqfB6AQrBggRKppKF8L52/VqdVsO47Dlw==}
- engines: {node: '>= 0.4'}
-
- hasown@2.0.2:
- resolution: {integrity: sha512-0hJU9SCPvmMzIBdZFqNPXWa6dqh7WdH0cII9y+CyS8rG3nL48Bclra9HmKhVVUHyPWNH5Y7xDwAB7bfgSjkUMQ==}
- engines: {node: '>= 0.4'}
+ hashery@1.5.1:
+ resolution: {integrity: sha512-iZyKG96/JwPz1N55vj2Ie2vXbhu440zfUfJvSwEqEbeLluk7NnapfGqa7LH0mOsnDxTF85Mx8/dyR6HfqcbmbQ==}
+ engines: {node: '>=20'}
hast-util-to-html@9.0.5:
resolution: {integrity: sha512-OguPdidb+fbHQSU4Q4ZiLKnzWo8Wwsf5bZfbvu7//a9oTYoqD/fWpe96NuHkoS9h0ccGOTe0C4NGXdtS0iObOw==}
@@ -2659,62 +1523,18 @@ packages:
hast-util-whitespace@3.0.0:
resolution: {integrity: sha512-88JUN06ipLwsnv+dVn+OIYOvAuvBMy/Qoi6O7mQHxdPXpjy+Cd6xRkWwux7DKO+4sYILtLBRIKgsdpS2gQc7qw==}
- he@1.2.0:
- resolution: {integrity: sha512-F/1DnUGPopORZi0ni+CvrCgHQ5FyEAHRLSApuYWMmrbSwoN2Mn/7k+Gl38gJnR7yyDZk6WLXwiGod1JOWNDKGw==}
- hasBin: true
-
hookable@5.5.3:
resolution: {integrity: sha512-Yc+BQe8SvoXH1643Qez1zqLRmbA5rCL+sSmk6TVos0LWVfNIB7PGncdlId77WzLGSIB5KaWgTaNTs2lNVEI6VQ==}
- html-encoding-sniffer@4.0.0:
- resolution: {integrity: sha512-Y22oTqIU4uuPgEemfz7NDJz6OeKf12Lsu+QC+s3BVpda64lTiMYCyGwg5ki4vFxkMwQdeZDl2adZoqUgdFuTgQ==}
- engines: {node: '>=18'}
-
- html-minifier-terser@7.2.0:
- resolution: {integrity: sha512-tXgn3QfqPIpGl9o+K5tpcj3/MN4SfLtsx2GWwBC3SSd0tXQGyF3gsSqad8loJgKZGM3ZxbYDd5yhiBIdWpmvLA==}
- engines: {node: ^14.13.1 || >=16.0.0}
- hasBin: true
+ hookified@1.15.1:
+ resolution: {integrity: sha512-MvG/clsADq1GPM2KGo2nyfaWVyn9naPiXrqIe4jYjXNZQt238kWyOGrsyc/DmRAQ+Re6yeo6yX/yoNCG5KAEVg==}
- html-to-text@9.0.5:
- resolution: {integrity: sha512-qY60FjREgVZL03vJU6IfMV4GDjGBIoOyvuFdpBDIX9yTlDw0TjxVBQp+P8NvpdIXNJvfWBTNul7fsAQJq2FNpg==}
- engines: {node: '>=14'}
+ hookified@2.2.0:
+ resolution: {integrity: sha512-p/LgFzRN5FeoD3DLS6bkUapeye6E4SI6yJs6KetENd18S+FBthqYq2amJUWpt5z0EQwwHemidjY5OqJGEKm5uA==}
html-void-elements@3.0.0:
resolution: {integrity: sha512-bEqo66MRXsUGxWHV5IP0PUiAWwoEjba4VCzg0LjFJBpchPaTfyfCKTG6bc5F8ucKec3q5y6qOdGyYTSBEvhCrg==}
- html5parser@2.0.2:
- resolution: {integrity: sha512-L0y+IdTVxHsovmye8MBtFgBvWZnq1C9WnI/SmJszxoQjmUH1psX2uzDk21O5k5et6udxdGjwxkbmT9eVRoG05w==}
-
- htmlparser2@10.0.0:
- resolution: {integrity: sha512-TwAZM+zE5Tq3lrEHvOlvwgj1XLWQCtaaibSN11Q+gGBAS7Y1uZSWwXXRe4iF6OXnaq1riyQAPFOBtYc77Mxq0g==}
-
- htmlparser2@8.0.2:
- resolution: {integrity: sha512-GYdjWKDkbRLkZ5geuHs5NY1puJ+PXwP7+fHPRz06Eirsb9ugf6d8kkXav6ADhcODhFFPMIXyxkxSuMf3D6NCFA==}
-
- http-errors@2.0.0:
- resolution: {integrity: sha512-FtwrG/euBzaEjYeRqOgly7G0qviiXoJWnvEH2Z1plBdXgbyjv34pHTSb9zoeHMyDy33+DWy5Wt9Wo+TURtOYSQ==}
- engines: {node: '>= 0.8'}
-
- http-proxy-agent@7.0.2:
- resolution: {integrity: sha512-T1gkAiYYDWYx3V5Bmyu7HcfcvL7mUrTWiM6yOfa3PIphViJ/gFPbvidQ+veqSOHci/PxBcDabeUNCzpOODJZig==}
- engines: {node: '>= 14'}
-
- http-proxy-middleware@3.0.5:
- resolution: {integrity: sha512-GLZZm1X38BPY4lkXA01jhwxvDoOkkXqjgVyUzVxiEK4iuRu03PZoYHhHRwxnfhQMDuaxi3vVri0YgSro/1oWqg==}
- engines: {node: ^14.15.0 || ^16.10.0 || >=18.0.0}
-
- http-proxy@1.18.1:
- resolution: {integrity: sha512-7mz/721AbnJwIVbnaSv1Cz3Am0ZLT/UBwkC92VlxhXv/k/BBQfM2fXElQNC27BVGr0uwUpplYPQM9LnaBMR5NQ==}
- engines: {node: '>=8.0.0'}
-
- https-proxy-agent@7.0.6:
- resolution: {integrity: sha512-vK9P5/iUfdl95AI+JVyUuIcVtd4ofvtrOr3HNtM2yxC9bnMbEdp3x01OhQNnjb8IJYi38VlTE3mBXwcfvywuSw==}
- engines: {node: '>= 14'}
-
- human-signals@8.0.1:
- resolution: {integrity: sha512-eKCa6bwnJhvxj14kZk5NCPc6Hb6BdsU9DZcOnmQKSnO1VKrfV0zCvtttPZUsBvjmNDn8rpcJfpwSYnHBjc95MQ==}
- engines: {node: '>=18.18.0'}
-
husky@9.1.7:
resolution: {integrity: sha512-5gs5ytaNjBrh5Ow3zrvdUUY+0VxIuWVL4i9irt6friV+BqdCfmV11CQTWMiBYWHbXhco+J1kHfTOUkePhCDvMA==}
engines: {node: '>=18'}
@@ -2724,31 +1544,21 @@ packages:
resolution: {integrity: sha512-4fCk79wshMdzMp2rH06qWrJE4iolqLhCUH+OiuIgU++RB0+94NlDL81atO7GX55uUKueo0txHNtvEyI6D7WdMw==}
engines: {node: '>=0.10.0'}
- ignore-by-default@1.0.1:
- resolution: {integrity: sha512-Ius2VYcGNk7T90CppJqcIkS5ooHUZyIQK+ClZfMfMNFEF9VSE73Fq+906u/CWu92x4gzZMWOwfFYckPObzdEbA==}
-
ignore@5.3.2:
resolution: {integrity: sha512-hsBTNUqQTDwkWtcdYI2i06Y/nUBEsNEDJKjWdigLvegy8kDuJAS8uRlpkkcQpyEXL0Z/pjDy5HBmMjRCJ2gq+g==}
engines: {node: '>= 4'}
- immutable@5.1.3:
- resolution: {integrity: sha512-+chQdDfvscSF1SJqv2gn4SRO2ZyS3xL3r7IW/wWEEzrzLisnOlKiQu5ytC/BVNcS15C39WT2Hg/bjKjDMcu+zg==}
+ ignore@7.0.10:
+ resolution: {integrity: sha512-HpbUakT7xp5miBUywCHf36ZEuAJNklBJDDsGpUIjMzOSmM8ELSfA9Sa/QDPeNeqeoN31u+UTCkL4klCOVvRm4Q==}
+ engines: {node: '>= 4'}
- import-fresh@3.3.1:
- resolution: {integrity: sha512-TR3KfrTZTYLPB6jUjfx6MF9WcWrHL9su5TObK4ZkYgBdWKPOFoSoQIdEuTuR82pmtxH2spWG9h6etwfr1pLBqQ==}
- engines: {node: '>=6'}
+ import-meta-resolve@4.2.0:
+ resolution: {integrity: sha512-Iqv2fzaTQN28s/FwZAoFq0ZSs/7hMAHJVX+w8PZl3cY19Pxk6jFFalxQoIfW2826i/fDLXv8IiEZRIT0lDuWcg==}
imurmurhash@0.1.4:
resolution: {integrity: sha512-JmXMZ6wuvDmLiHEml9ykzqO6lwFbof0GG4IkcGaENdCRDDmMVnny7s5HsIgHCbaq0w2MyPhDqkhTUgS2LU2PHA==}
engines: {node: '>=0.8.19'}
- inherits@2.0.4:
- resolution: {integrity: sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ==}
-
- ini@4.1.1:
- resolution: {integrity: sha512-QQnnxNyfvmHFIsj7gkPcYymR8Jdw/o7mp5ZFihxn6h8Ci6fh3Dx4E1gPjpQEpIuPo9XVNY/ZUwh4BPMjGyL01g==}
- engines: {node: ^14.17.0 || ^16.13.0 || >=18.0.0}
-
internmap@1.0.1:
resolution: {integrity: sha512-lDB5YccMydFBtasVtxnZ3MRBHuaoE8GKsppq+EchKL2U4nK/DmEpPHNH8MZe5HkMtpSiTSOZwfN0tzYjO/lJEw==}
@@ -2756,18 +1566,6 @@ packages:
resolution: {integrity: sha512-5Hh7Y1wQbvY5ooGgPbDaL5iYLAPzMTUrjMulskHLH6wnv/A+1q5rgEaiuqEjB+oxGXIVZs1FF+R/KPN3ZSQYYg==}
engines: {node: '>=12'}
- is-binary-path@2.1.0:
- resolution: {integrity: sha512-ZMERYes6pDydyuGidse7OsHxtbI7WVeUEozgR/g7rd0xUimYNlvZRE/K2MgZTjWy725IfelLeVcEM97mmtRGXw==}
- engines: {node: '>=8'}
-
- is-buffer@1.1.6:
- resolution: {integrity: sha512-NcdALwpXkTm5Zvvbk7owOUSvVvBKDgKP5/ewfXEznmQFfs4ZRmanOeKBTjRVjka3QFoN6XJ+9F3USqfHqTaU5w==}
-
- is-docker@3.0.0:
- resolution: {integrity: sha512-eljcgEDlEns/7AXFosB5K/2nCM4P7FQPkGc/DWLy5rmFEWvZayGrik1d9/QIY5nJ4f9YsVvBkA6kJpHn9rISdQ==}
- engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
- hasBin: true
-
is-extendable@0.1.1:
resolution: {integrity: sha512-5BMULNob1vgFX6EjQw5izWDxrecWK9AM72rugNr0TFldMOi0fj6Jk+zeKIt0xGj4cEfQIJth4w3OKWOJ4f+AFw==}
engines: {node: '>=0.10.0'}
@@ -2776,136 +1574,29 @@ packages:
resolution: {integrity: sha512-SbKbANkN603Vi4jEZv49LeVJMn4yGwsbzZworEoyEiutsN3nJYdbO36zfhGJ6QEDpOZIFkDtnq5JRxmvl3jsoQ==}
engines: {node: '>=0.10.0'}
- is-fullwidth-code-point@3.0.0:
- resolution: {integrity: sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg==}
- engines: {node: '>=8'}
-
- is-fullwidth-code-point@4.0.0:
- resolution: {integrity: sha512-O4L094N2/dZ7xqVdrXhh9r1KODPJpFms8B5sGdJLPy664AgvXsreZUyCQQNItZRDlYug4xStLjNp/sz3HvBowQ==}
- engines: {node: '>=12'}
-
- is-fullwidth-code-point@5.0.0:
- resolution: {integrity: sha512-OVa3u9kkBbw7b8Xw5F9P+D/T9X+Z4+JruYVNapTjPYZYUznQ5YfWeFkOj606XYYW8yugTfC8Pj0hYqvi4ryAhA==}
- engines: {node: '>=18'}
-
is-glob@4.0.3:
resolution: {integrity: sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg==}
engines: {node: '>=0.10.0'}
- is-inside-container@1.0.0:
- resolution: {integrity: sha512-KIYLCCJghfHZxqjYBE7rEy0OBuTd5xCHS7tHVgvCLkx7StIoaxwNW3hCALgEUjFfeRk+MG/Qxmp/vtETEF3tRA==}
- engines: {node: '>=14.16'}
- hasBin: true
-
- is-interactive@2.0.0:
- resolution: {integrity: sha512-qP1vozQRI+BMOPcjFzrjXuQvdak2pHNUMZoeG2eRbiSqyvbEf/wQtEOTOX1guk6E3t36RkaqiSt8A/6YElNxLQ==}
- engines: {node: '>=12'}
-
- is-number@7.0.0:
- resolution: {integrity: sha512-41Cifkg6e8TylSpdtTpeLVMqvSBEVzTttHvERD741+pnZ8ANv0004MRL43QKPDlK9cGvNp6NZWZUBlbGXYxxng==}
- engines: {node: '>=0.12.0'}
-
- is-plain-obj@4.1.0:
- resolution: {integrity: sha512-+Pgi+vMuUNkJyExiMBt5IlFoMyKnr5zhJ4Uspz58WOhBF5QoIZkFyNHIbBAtHwzVAgk5RtndVNsDRN61/mmDqg==}
- engines: {node: '>=12'}
-
- is-plain-object@5.0.0:
- resolution: {integrity: sha512-VRSzKkbMm5jMDoKLbltAkFQ5Qr7VDiTFGXxYFXXowVj387GeGNOCsOH6Msy00SGZ3Fp84b1Naa1psqgcCIEP5Q==}
- engines: {node: '>=0.10.0'}
-
- is-potential-custom-element-name@1.0.1:
- resolution: {integrity: sha512-bCYeRA2rVibKZd+s2625gGnGF/t7DSqDs4dP7CrLA1m7jKWz6pps0LpYLJN8Q64HtmPKJ1hrN3nzPNKFEKOUiQ==}
-
- is-stream@4.0.1:
- resolution: {integrity: sha512-Dnz92NInDqYckGEUJv689RbRiTSEHCQ7wOVeALbkOz999YpqT46yMRIGtSNl2iCL1waAZSx40+h59NV/EwzV/A==}
- engines: {node: '>=18'}
-
- is-unicode-supported@1.3.0:
- resolution: {integrity: sha512-43r2mRvz+8JRIKnWJ+3j8JtjRKZ6GmjzfaE/qiBJnikNnYv/6bagRJ1kUhNk8R5EX/GkobD+r+sfxCPJsiKBLQ==}
- engines: {node: '>=12'}
-
- is-unicode-supported@2.1.0:
- resolution: {integrity: sha512-mE00Gnza5EEB3Ds0HfMyllZzbBrmLOX3vfWoj9A9PEnTfratQ/BcaJOuMhnkhjXvb2+FkY3VuHqtAGpTPmglFQ==}
- engines: {node: '>=18'}
-
- is-what@4.1.16:
- resolution: {integrity: sha512-ZhMwEosbFJkA0YhFnNDgTM4ZxDRsS6HqTo7qsZM08fehyRYIYa0yHu5R6mgo1n/8MgaPBXiPimPD77baVFYg+A==}
- engines: {node: '>=12.13'}
-
- is-wsl@3.1.0:
- resolution: {integrity: sha512-UcVfVfaK4Sc4m7X3dUSoHoozQGBEFeDC+zVo06t98xe8CzHSZZBekNXH+tu0NalHolcJ/QAGqS46Hef7QXBIMw==}
- engines: {node: '>=16'}
-
isexe@2.0.0:
resolution: {integrity: sha512-RHxMLp9lnKHGHRng9QFhRCMbYAcVpn69smSGcq3f36xjgVVWThj4qqLbTLlq7Ssj8B+fIQ1EuCEGI2lKsyQeIw==}
- jake@10.9.2:
- resolution: {integrity: sha512-2P4SQ0HrLQ+fw6llpLnOaGAvN2Zu6778SJMrCUwns4fOoG9ayrTiZk3VV8sCPkVZF8ab0zksVpS8FDY5pRCNBA==}
- engines: {node: '>=10'}
- hasBin: true
-
- jiti@2.4.2:
- resolution: {integrity: sha512-rg9zJN+G4n2nfJl5MW3BMygZX56zKPNVEYYqq7adpmMh4Jn2QNEwhvQlFy6jPVdcod7txZtKHWnyZiA3a0zP7A==}
- hasBin: true
-
- js-base64@3.7.7:
- resolution: {integrity: sha512-7rCnleh0z2CkXhH67J8K1Ytz0b2Y+yxTPL+/KOJoa20hfnVQ/3/T6W/KflYI4bRHRagNeXeU2bkNGI3v1oS/lw==}
-
- js-tokens@4.0.0:
- resolution: {integrity: sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ==}
-
- js-yaml@3.14.1:
- resolution: {integrity: sha512-okMH7OXXJ7YrN9Ok3/SXrnu4iX9yOk+25nqX4imS2npuvTYDmo/QEZoqwZkYaIDk3jVvBOTOIEgEhaLOynBS9g==}
- hasBin: true
-
- js-yaml@4.1.0:
- resolution: {integrity: sha512-wpxZs9NoxZaJESJGIZTyDEaYpl0FKSA+FB9aJiyemKhMwkxQg63h4T1KJgUGHpTqPDNRcmmYLugrRjJlBtWvRA==}
- hasBin: true
-
- jsdom@26.1.0:
- resolution: {integrity: sha512-Cvc9WUhxSMEo4McES3P7oK3QaXldCfNWp7pl2NNeiIFlCoLr3kfq9kb1fxftiwk1FLV7CvpvDfonxtzUDeSOPg==}
- engines: {node: '>=18'}
- peerDependencies:
- canvas: ^3.0.0
- peerDependenciesMeta:
- canvas:
- optional: true
-
- jsesc@3.1.0:
- resolution: {integrity: sha512-/sM3dO2FOzXjKQhJuo0Q173wf2KOo8t4I8vHy6lF9poUp7bKT0/NHE8fPX23PwfhnykfqnC2xRxOnVw5XuGIaA==}
- engines: {node: '>=6'}
+ js-yaml@3.15.2:
+ resolution: {integrity: sha512-6EuL879VkRA+1Cz578mKMiKvjPNEuk6+r1JaFzoSWejZmtf7xWbIyw1e3KkxlkzTIt9Taw6JBhEppG7utc1P+w==}
hasBin: true
- json-buffer@3.0.1:
- resolution: {integrity: sha512-4bV5BfR2mqfQTJm+V5tPPdf+ZpuhiIvTuAB5g8kcrXOZpTT/QwwVRWBywX1ozr6lEuPdbHxwaJlm9G6mI2sfSQ==}
-
json-schema-traverse@0.4.1:
resolution: {integrity: sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg==}
- json-schema-traverse@1.0.0:
- resolution: {integrity: sha512-NM8/P9n3XjXhIZn1lLhkFaACTOURQXjWhV4BA/RnOv8xvgqtqpAX9IO4mRQxSx1Rlo4tqzeqb0sOlruaOy3dug==}
-
json-stable-stringify-without-jsonify@1.0.1:
resolution: {integrity: sha512-Bdboy+l7tA3OGW6FjyFHWkP5LuByj1Tk33Ljyq0axyzdk9//JSi2u3fP1QSmd1KNwq6VOKYGlAu87CisVir6Pw==}
- json5@2.2.3:
- resolution: {integrity: sha512-XmOWe7eyHYH14cLdVPoyg+GOH3rYX++KpzrylJwSW98t3Nk+U8XOl8FWKOgwtzdb8lXGf6zYwDUzeHMWfxasyg==}
- engines: {node: '>=6'}
- hasBin: true
-
- jsonc-eslint-parser@2.4.0:
- resolution: {integrity: sha512-WYDyuc/uFcGp6YtM2H0uKmUwieOuzeE/5YocFJLnLfclZ4inf3mRn8ZVy1s7Hxji7Jxm6Ss8gqpexD/GlKoGgg==}
- engines: {node: ^12.22.0 || ^14.17.0 || >=16.0.0}
-
- jsonfile@6.1.0:
- resolution: {integrity: sha512-5dgndWOriYSm5cnYaJNhalLNDKOqFwyDB/rr1E9ZsGciGvKPs8R2xYGCacuf3z6K1YKDz182fd+fY3cn3pMqXQ==}
-
- katex@0.16.22:
- resolution: {integrity: sha512-XCHRdUw4lf3SKBaJe4EvgqIuWwkPSo9XoeO8GjQW94Bp7TWv9hNhzZjZ+OH9yf1UmLygb7DIT5GSFQiyt16zYg==}
+ katex@0.16.47:
+ resolution: {integrity: sha512-Eeo8Ys1doU1z+x8AZsPpQu+p/QcZBI5PeOo7QGQdy2x2m0MU/hYagBbGOmXwr5KVbEfVuWv9LpnQWeehogurjg==}
hasBin: true
- keyv@4.5.4:
- resolution: {integrity: sha512-oxVHkHR/EJf2CNXnWxRLW6mg7JyCCUcG0DtEGmL2ctUo1PNTin1PUil+r/+4r5MpVgC/fn1kjsx7mjSujKqIpw==}
+ keyv@5.6.0:
+ resolution: {integrity: sha512-CYDD3SOtsHtyXeEORYRx2qBtpDJFjRTGXUtmNEMGyzYOKj1TE3tycdlho7kA1Ufx9OYWZzg52QFBGALTirzDSw==}
khroma@2.1.0:
resolution: {integrity: sha512-Ls993zuzfayK269Svk9hzpeGUKob/sIgZzyHYdjQoAdQetRKpOLj+k/QQQ/6Qi0Yz65mlROrfd+Ev+1+7dz9Kw==}
@@ -2914,182 +1605,60 @@ packages:
resolution: {integrity: sha512-dcS1ul+9tmeD95T+x28/ehLgd9mENa3LsvDTtzm3vyBEO7RPptvAD+t44WVXaUjTBRcrpFeFlC8WCruUR456hw==}
engines: {node: '>=0.10.0'}
- kolorist@1.8.0:
- resolution: {integrity: sha512-Y+60/zizpJ3HRH8DCss+q95yr6145JXZo46OTpFvDZWLfRCE4qChOyk1b26nMaNpfHHgxagk9dXT5OP0Tfe+dQ==}
-
- langium@3.3.1:
- resolution: {integrity: sha512-QJv/h939gDpvT+9SiLVlY7tZC3xB2qK57v0J04Sh9wpMb6MP1q8gB21L3WIo8T5P1MSMg3Ep14L7KkDCFG3y4w==}
- engines: {node: '>=16.0.0'}
-
layout-base@1.0.2:
resolution: {integrity: sha512-8h2oVEZNktL4BH2JCOI90iD1yXwL6iNW7KcCKT2QZgQJR2vbqDsldCTPRU9NifTCqHZci57XvQQ15YTu+sTYPg==}
layout-base@2.0.1:
resolution: {integrity: sha512-dp3s92+uNI1hWIpPGH3jK2kxE2lMjdXdr+DH8ynZHpd6PUlH6x6cbuXnoMmiNumznqaNO31xu9e79F0uuZ0JFg==}
- leac@0.6.0:
- resolution: {integrity: sha512-y+SqErxb8h7nE/fiEX07jsbuhrpO9lL8eca7/Y1nuWV2moNlXhyd59iDGcRf6moVyDMbmTNzL40SUyrFU/yDpg==}
-
levn@0.4.1:
resolution: {integrity: sha512-+bT2uH4E5LGE7h/n3evcS/sQlJXCpIp6ym8OWJ5eV6+67Dsql/LaaT7qJBAt2rzfoa/5QBGBhxDix1dMt2kQKQ==}
engines: {node: '>= 0.8.0'}
- lilconfig@3.1.3:
- resolution: {integrity: sha512-/vlFKAoH5Cgt3Ie+JLhRbwOsCQePABiU3tJ1egGvyQ+33R/vcwM2Zl2QR/LzjsBeItPt3oSVXapn+m4nQDvpzw==}
- engines: {node: '>=14'}
-
- linkify-it@5.0.0:
- resolution: {integrity: sha512-5aHCbzQRADcdP+ATqnDuhhJ/MRIqDkZX5pyjFHRRysS8vZ5AbqGEoFIb6pYHPZ+L/OC2Lc+xT8uHVVR5CAK/wQ==}
-
- lint-staged@16.1.2:
- resolution: {integrity: sha512-sQKw2Si2g9KUZNY3XNvRuDq4UJqpHwF0/FQzZR2M7I5MvtpWvibikCjUVJzZdGE0ByurEl3KQNvsGetd1ty1/Q==}
- engines: {node: '>=20.17'}
+ lint-staged@17.6.0:
+ resolution: {integrity: sha512-nOhBfYkZEwkFtNzD5pK9s9LkcWoxJ+whLzEnhqi9nl7zTB5n7tg8+9iYgMGx2Wm3VlLu8cbNj0RACzY+nWi5iQ==}
+ engines: {node: '>=22.22.1'}
hasBin: true
- listr2@8.3.3:
- resolution: {integrity: sha512-LWzX2KsqcB1wqQ4AHgYb4RsDXauQiqhjLk+6hjbaeHG4zpjjVAB6wC/gz6X0l+Du1cN3pUB5ZlrvTbhGSNnUQQ==}
- engines: {node: '>=18.0.0'}
+ lit-element@4.2.2:
+ resolution: {integrity: sha512-aFKhNToWxoyhkNDmWZwEva2SlQia+jfG0fjIWV//YeTaWrVnOxD89dPKfigCUspXFmjzOEUQpOkejH5Ly6sG0w==}
- lit-element@4.2.1:
- resolution: {integrity: sha512-WGAWRGzirAgyphK2urmYOV72tlvnxw7YfyLDgQ+OZnM9vQQBQnumQ7jUJe6unEzwGU3ahFOjuz1iz1jjrpCPuw==}
+ lit-html@3.3.3:
+ resolution: {integrity: sha512-el8M6jK2o3RXBnrSHX3ZKrsN8zEV63pSExTO1wYJz7QndGYZ8353e2a5PPX+qHe2aGayfnchQmkAojaWAREOIA==}
- lit-html@3.3.1:
- resolution: {integrity: sha512-S9hbyDu/vs1qNrithiNyeyv64c9yqiW9l+DBgI18fL+MTvOtWoFR0FWiyq1TxaYef5wNlpEmzlXoBlZEO+WjoA==}
-
- lit@3.3.1:
- resolution: {integrity: sha512-Ksr/8L3PTapbdXJCk+EJVB78jDodUMaP54gD24W186zGRARvwrsPfS60wae/SSCTCNZVPd1chXqio1qHQmu4NA==}
-
- local-pkg@0.5.1:
- resolution: {integrity: sha512-9rrA30MRRP3gBD3HTGnC6cDFpaE1kVDWxWgqWJUN0RvDNAo+Nz/9GxB+nHOH0ifbVFy0hSA1V6vFDvnx54lTEQ==}
- engines: {node: '>=14'}
-
- local-pkg@1.1.1:
- resolution: {integrity: sha512-WunYko2W1NcdfAFpuLUoucsgULmgDBRkdxHxWQ7mK0cQqwPiy8E1enjuRBrhLtZkB5iScJ1XIPdhVEFK8aOLSg==}
- engines: {node: '>=14'}
-
- locate-path@5.0.0:
- resolution: {integrity: sha512-t7hw9pI+WvuwNJXwk5zVHpyhIqzg2qTlklJOf0mVxGSbe3Fp2VieZcduNYjaLDoy6p9uGpQEGWG87WpMKlNq8g==}
- engines: {node: '>=8'}
+ lit@3.3.3:
+ resolution: {integrity: sha512-fycuvZg/hkpozL00lm1pEJH5nN/lr9ZXd6mJI2HSN4+Bzc+LDNdEApJ6HFbPkdFNHLvOplIIuJvxkS4XUxqirw==}
locate-path@6.0.0:
resolution: {integrity: sha512-iPZK6eYjbxRu3uB4/WZ3EsEIMJFMqAoopl3R+zuq0UjcAm/MO6KCweDgPfP3elTztoKP3KtnVHxTn2NHBSDVUw==}
engines: {node: '>=10'}
- lodash-es@4.17.21:
- resolution: {integrity: sha512-mKnC+QJ9pWVzv+C4/U3rRsHapFfHvQFoFB92e52xeyGMcX6/OlIl78je1u8vePzYZSkkogMPJ2yjxxsb89cxyw==}
-
- lodash.merge@4.6.2:
- resolution: {integrity: sha512-0KpjqXRVvrYyCsX1swR/XTK0va6VQkQM6MNo7PqW77ByjAhoARA8EfrP1N4+KlKj8YS0ZUCtRT/YUuhyYDujIQ==}
-
- lodash.truncate@4.4.2:
- resolution: {integrity: sha512-jttmRe7bRse52OsWIMDLaXxWqRAmtIUccAQ3garviCqJjafXOfNMO0yMfNpdD6zbGaTU0P5Nz7e7gAT6cKmJRw==}
-
- log-symbols@6.0.0:
- resolution: {integrity: sha512-i24m8rpwhmPIS4zscNzK6MSEhk0DUWa/8iYQWxhffV8jkI4Phvs3F+quL5xvS0gdQR0FyTCMMH33Y78dDTzzIw==}
- engines: {node: '>=18'}
-
- log-update@6.1.0:
- resolution: {integrity: sha512-9ie8ItPR6tjY5uYJh8K/Zrv/RMZ5VOlOWvtZdEHYSTFKZfIBPQa9tOAEeAWhd+AnIneLJ22w5fjOYtoutpWq5w==}
- engines: {node: '>=18'}
-
- lower-case@2.0.2:
- resolution: {integrity: sha512-7fm3l3NAF9WfN6W3JOmf5drwpVqX78JtoGJ3A6W0a6ZnldM41w2fV5D490psKFTpMds8TJse/eHLFFsNHHjHgg==}
-
- lru-cache@10.4.3:
- resolution: {integrity: sha512-JNAzZcXrCt42VGLuYz0zfAzDfAvJWW6AfYlDBQyDV5DClI2m5sAmK+OIO7s59XfsRsWHp02jAJrRadPRGTt6SQ==}
-
- lru-cache@11.1.0:
- resolution: {integrity: sha512-QIXZUBJUx+2zHUdQujWejBkcD9+cs94tLn0+YL8UrCh+D5sCXZ4c7LaEH48pNwRY3MLDgqUFyhlCyjJPf1WP0A==}
- engines: {node: 20 || >=22}
-
- lru-cache@5.1.1:
- resolution: {integrity: sha512-KpNARQA3Iwv+jTA0utUVVbrh+Jlrr1Fv0e56GGzAFOXN7dk/FviaDW8LHmK52DlcH4WP2n6gI8vN1aesBFgo9w==}
+ lodash-es@4.17.23:
+ resolution: {integrity: sha512-kVI48u3PZr38HdYz98UmfPnXl2DXrpdctLrFLCd3kOx1xUkOmpFPx7gCWWM5MPkL/fD8zb+Ph0QzjGFs4+hHWg==}
- magic-string-ast@1.0.0:
- resolution: {integrity: sha512-8rbuNizut2gW94kv7pqgt0dvk+AHLPVIm0iJtpSgQJ9dx21eWx5SBel8z3jp1xtC0j6/iyK3AWGhAR1H61s7LA==}
- engines: {node: '>=20.18.0'}
+ lodash-es@4.18.1:
+ resolution: {integrity: sha512-J8xewKD/Gk22OZbhpOVSwcs60zhd95ESDwezOFuA3/099925PdHJ7OFHNTGtajL3AlZkykD32HykiMo+BIBI8A==}
- magic-string@0.30.17:
- resolution: {integrity: sha512-sNPKHvyjVf7gyjwS4xGTaW/mCnF8wnjtifKBEhxfZ7E/S8tQ0rssrwGNn6q8JH/ohItJfSQp9mBtQYuTlH5QnA==}
+ magic-string@0.30.21:
+ resolution: {integrity: sha512-vd2F4YUyEXKGcLHoq+TEyCjxueSeHnFxyyjNp80yg0XV4vUhnDer/lvvlqM/arB5bXQN5K2/3oinyCRyx8T2CQ==}
mark.js@8.11.1:
resolution: {integrity: sha512-1I+1qpDt4idfgLQG+BNWmrqku+7/2bi5nLf4YwF8y8zXvmfiTBY3PV3ZibfrjBueCByROpuBjLLFCajqkgYoLQ==}
- markdown-it-anchor@9.2.0:
- resolution: {integrity: sha512-sa2ErMQ6kKOA4l31gLGYliFQrMKkqSO0ZJgGhDHKijPf0pNFM9vghjAh3gn26pS4JDRs7Iwa9S36gxm3vgZTzg==}
- peerDependencies:
- '@types/markdown-it': '*'
- markdown-it: '*'
-
- markdown-it-async@2.2.0:
- resolution: {integrity: sha512-sITME+kf799vMeO/ww/CjH6q+c05f6TLpn6VOmmWCGNqPJzSh+uFgZoMB9s0plNtW6afy63qglNAC3MhrhP/gg==}
-
- markdown-it-attrs@4.3.1:
- resolution: {integrity: sha512-/ko6cba+H6gdZ0DOw7BbNMZtfuJTRp9g/IrGIuz8lYc/EfnmWRpaR3CFPnNbVz0LDvF8Gf1hFGPqrQqq7De0rg==}
- engines: {node: '>=6'}
- peerDependencies:
- markdown-it: '>= 9.0.0'
-
- markdown-it-container@4.0.0:
- resolution: {integrity: sha512-HaNccxUH0l7BNGYbFbjmGpf5aLHAMTinqRZQAEQbMr2cdD3z91Q6kIo1oUn1CQndkT03jat6ckrdRYuwwqLlQw==}
-
- markdown-it-emoji@3.0.0:
- resolution: {integrity: sha512-+rUD93bXHubA4arpEZO3q80so0qgoFJEKRkRbjKX8RTdca89v2kfyF+xR3i2sQTwql9tpPZPOQN5B+PunspXRg==}
-
- markdown-it-footnote@4.0.0:
- resolution: {integrity: sha512-WYJ7urf+khJYl3DqofQpYfEYkZKbmXmwxQV8c8mO/hGIhgZ1wOe7R4HLFNwqx7TjILbnC98fuyeSsin19JdFcQ==}
-
- markdown-it-image-figures@2.1.1:
- resolution: {integrity: sha512-mwXSQ2nPeVUzCMIE3HlLvjRioopiqyJLNph0pyx38yf9mpqFDhNGnMpAXF9/A2Xv0oiF2cVyg9xwfF0HNAz05g==}
- engines: {node: '>=12.0.0'}
- peerDependencies:
- markdown-it: '*'
-
- markdown-it-table-of-contents@0.9.0:
- resolution: {integrity: sha512-PKtgvLweW/PXj8Pg2EfJM9qANbYqchxOiZy+70kLKFfCL4IkdlMzc53Z4Yj2ABw45MEzrXUSHh+4Cs2tDjwEig==}
- engines: {node: '>6.4.0'}
-
- markdown-it-task-lists@2.1.1:
- resolution: {integrity: sha512-TxFAc76Jnhb2OUu+n3yz9RMu4CwGfaT788br6HhEDlvWfdeJcLUsxk1Hgw2yJio0OXsxv7pyIPmvECY7bMbluA==}
-
- markdown-it@14.1.0:
- resolution: {integrity: sha512-a54IwgWPaeBCAAsv13YgmALOF1elABB08FxO9i+r4VFk5Vl4pKokRPeX8u5TCgSsPi6ec1otfLjdOpVcgbpshg==}
- hasBin: true
-
- marked@16.1.1:
- resolution: {integrity: sha512-ij/2lXfCRT71L6u0M29tJPhP0bM5shLL3u5BePhFwPELj2blMJ6GDtD7PfJhRLhJ/c2UwrK17ySVcDzy2YHjHQ==}
+ marked@16.4.2:
+ resolution: {integrity: sha512-TI3V8YYWvkVf3KJe1dRkpnjs68JUPyEa5vjKrp1XEEJUAOaQc+Qj+L1qWbPd0SJuAdQkFU0h73sXXqwDYxsiDA==}
engines: {node: '>= 20'}
hasBin: true
- math-intrinsics@1.1.0:
- resolution: {integrity: sha512-/IXtbwEk5HTPyEwyKX6hGkYXxM9nbj64B+ilVJnC/R6B0pH5G4V3b0pVbL7DBj4tkhBAppbQUlf6F6Xl9LHu1g==}
- engines: {node: '>= 0.4'}
-
- md5@2.3.0:
- resolution: {integrity: sha512-T1GITYmFaKuO91vxyoQMFETst+O71VUPEU3ze5GNzDm0OWdP8v1ziTaAEPUr/3kLsY3Sftgz242A1SetQiDL7g==}
-
- mdast-util-to-hast@13.2.0:
- resolution: {integrity: sha512-QGYKEuUsYT9ykKBCMOEDLsU5JRObWQusAolFMeko/tYPufNkRffBAQjIE+99jbA87xv6FgmjLtwjh9wBWajwAA==}
-
- mdn-data@2.12.2:
- resolution: {integrity: sha512-IEn+pegP1aManZuckezWCO+XZQDplx1366JoVhTpMpBB1sPey/SbveZQUosKiKiGYjg1wH4pMlNgXbCiYgihQA==}
-
- mdurl@2.0.0:
- resolution: {integrity: sha512-Lf+9+2r+Tdp5wXDXC4PcIBjTDtq4UKjCPMQhKIuzpJNW0b96kVqSwW0bT7FhRSfmAiFYgP+SCRvdrDozfh0U5w==}
-
- media-typer@1.1.0:
- resolution: {integrity: sha512-aisnrDP4GNe06UcKFnV5bfMNPBUw4jsLGaWwWfnH3v02GnBuXX2MCVn5RbrWo0j3pczUilYblq7fQ7Nw2t5XKw==}
- engines: {node: '>= 0.8'}
+ mdast-util-to-hast@13.2.1:
+ resolution: {integrity: sha512-cctsq2wp5vTsLIcaymblUriiTcZd0CwWtCbLvrOzYCDZoWyMNV8sZ7krj09FSnsiJi3WVsHLM4k6Dq/yaPyCXA==}
medium-zoom@1.1.0:
resolution: {integrity: sha512-ewyDsp7k4InCUp3jRmwHBRFGyjBimKps/AJLjRSox+2q/2H4p/PNpQf+pwONWlJiOudkBXtbdmVbFjqyybfTmQ==}
- merge2@1.4.1:
- resolution: {integrity: sha512-8q7VEgMJW4J8tcfVPy8g09NcQwZdbwFEqhe/WZkoIzjn/3TGDwtOCYtXGxA3O8tPzpczCCDgv+P2P5y00ZJOOg==}
- engines: {node: '>= 8'}
-
- mermaid@11.9.0:
- resolution: {integrity: sha512-YdPXn9slEwO0omQfQIsW6vS84weVQftIyyTGAZCwM//MGhPzL1+l6vO6bkf0wnP4tHigH1alZ5Ooy3HXI2gOag==}
+ mermaid@12.0.0:
+ resolution: {integrity: sha512-/wQXC9iBxoGV8p3erbvaXs9h77VyLDBH6GdayVjj3hEcSQhFU4N1WUhUppotCEqlIxI2pRMwjwBSwTB1MfZBgQ==}
+ engines: {node: '>=22.12.0'}
micromark-util-character@2.1.1:
resolution: {integrity: sha512-wv8tdUTJ3thSFFFJKtpYKOYiGP2+v96Hvk4Tu8KpCAsTMs6yi+nVmGh1syvSCsaxz45J6Jbw+9DD6g97+NV67Q==}
@@ -3106,200 +1675,50 @@ packages:
micromark-util-types@2.0.2:
resolution: {integrity: sha512-Yw0ECSpJoViF1qTU4DC6NwtC4aWGt1EkzaQB8KPPyCRR8z9TWeV0HbEFGTO+ZY1wB22zmxnJqhPyTpOVCpeHTA==}
- micromatch@4.0.8:
- resolution: {integrity: sha512-PXwfBhYu0hBCPw8Dn0E+WDYb7af3dSLVWKi3HGv84IdF4TyFoC0ysxFd0Goxw7nSv4T/PzEJQxsYsEiFCKo2BA==}
- engines: {node: '>=8.6'}
-
- mime-db@1.52.0:
- resolution: {integrity: sha512-sPU4uV7dYlvtWJxwwxHD0PuihVNiE7TyAbQ5SWxDCB9mUYvOgroQOwYQQOKPJ8CIbE+1ETVlOoK1UC2nU3gYvg==}
- engines: {node: '>= 0.6'}
-
- mime-db@1.54.0:
- resolution: {integrity: sha512-aU5EJuIN2WDemCcAp2vFBfp/m4EAhWJnUNSSw0ixs7/kXbd6Pg64EmwJkNdFhB8aWt1sH2CTXrLxo/iAGV3oPQ==}
- engines: {node: '>= 0.6'}
-
- mime-types@2.1.35:
- resolution: {integrity: sha512-ZDY+bPm5zTTF+YpCrAU9nK0UgICYPT0QtT1NZWFv4s++TNkcgVaT0g6+4R2uI4MjQjzysHB1zxuWL50hzaeXiw==}
- engines: {node: '>= 0.6'}
-
- mime-types@3.0.1:
- resolution: {integrity: sha512-xRc4oEhT6eaBpU1XF7AjpOFD+xQmXNB5OVKwp4tqCuBpHLS/ZbBDrc07mYTDqVMg6PfxUjjNp85O6Cd2Z/5HWA==}
- engines: {node: '>= 0.6'}
-
- mimic-function@5.0.1:
- resolution: {integrity: sha512-VP79XUPxV2CigYP3jWwAUFSku2aKqBH7uTAapFWCBqutsbmDo96KY5o8uh6U+/YSIn5OxJnXp73beVkpqMIGhA==}
- engines: {node: '>=18'}
-
- minimatch@3.1.2:
- resolution: {integrity: sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==}
+ minimatch@10.2.6:
+ resolution: {integrity: sha512-vpLQEs+VLCr1nU0BXS07maYoFwlDAH0gngQuuttxIwutDFEMHq2blX+8vpgxDdK3J1PwjCJiep77OitTZ4Ll1A==}
+ engines: {node: 18 || 20 || >=22}
- minimatch@5.1.6:
- resolution: {integrity: sha512-lKwV/1brpG6mBUFHtb7NUmtABCb2WZZmm2wNiOA5hAb8VdCS4B3dtMWyvcoViccwAW/COERjXLt0zP1zXUN26g==}
- engines: {node: '>=10'}
-
- minimatch@9.0.5:
- resolution: {integrity: sha512-G6T0ZX48xgozx7587koeX9Ys2NYy6Gmv//P89sEte9V9whIapMNF4idKxnW2QtCcLiTWlb/wfCabAtAFWhhBow==}
- engines: {node: '>=16 || 14 >=14.17'}
-
- minisearch@6.3.0:
- resolution: {integrity: sha512-ihFnidEeU8iXzcVHy74dhkxh/dn8Dc08ERl0xwoMMGqp4+LvRSCgicb+zGqWthVokQKvCSxITlh3P08OzdTYCQ==}
+ minisearch@7.2.0:
+ resolution: {integrity: sha512-dqT2XBYUOZOiC5t2HRnwADjhNS2cecp9u+TJRiJ1Qp/f5qjkeT5APcGPjHw+bz89Ms8Jp+cG4AlE+QZ/QnDglg==}
mitt@3.0.1:
resolution: {integrity: sha512-vKivATfr97l2/QBCYAkXYDbrIWPM2IIKEl7YPhjCvKlG3kE2gm+uBo6nEXK3M5/Ffh/FLpKExzOQ3JJoJGFKBw==}
- mlly@1.7.4:
- resolution: {integrity: sha512-qmdSIPC4bDJXgZTCR7XosJiNKySV7O215tsPtDN9iEO/7q/76b/ijtgRu/+epFXSJhijtTCCGp3DWS549P3xKw==}
-
- mrmime@2.0.1:
- resolution: {integrity: sha512-Y3wQdFg2Va6etvQ5I82yUhGdsKrcYox6p7FfL1LbK2J4V01F9TGlepTIhnK24t7koZibmg82KGglhA1XK5IsLQ==}
- engines: {node: '>=10'}
-
ms@2.1.3:
resolution: {integrity: sha512-6FlzubTLZG3J2a/NVCAleEhjzq5oxgHyaCU9yYXvcLsvoVaHJq/s5xXI6/XXP6tz7R9xAOtHnSO/tXtF3WRTlA==}
muggle-string@0.4.1:
resolution: {integrity: sha512-VNTrAak/KhO2i8dqqnqnAHOa3cYBwXEZe9h+D5h/1ZqFSTEFHdM65lR7RoIqq3tBBYavsOXV84NoHXZ0AkPyqQ==}
- nano-spawn@1.0.2:
- resolution: {integrity: sha512-21t+ozMQDAL/UGgQVBbZ/xXvNO10++ZPuTmKRO8k9V3AClVRht49ahtDjfY8l1q6nSHOrE5ASfthzH3ol6R/hg==}
- engines: {node: '>=20.17'}
-
- nanoid@3.3.11:
- resolution: {integrity: sha512-N8SpfPUnUp1bK+PMYW8qSWdl9U+wwNWI4QKxOYDy9JAro3WMX7p2OeVRF9v+347pnakNevPmiHhNmZ2HbFA76w==}
+ nanoid@3.3.19:
+ resolution: {integrity: sha512-Y2tUNy4ouw6tq5oDSKeQYGOyhkUBhNOcGV/02KC+6kd9eDGqdZd++mjMiIDilrBYvjEnCYvVtsuHCuP+okSfug==}
engines: {node: ^10 || ^12 || ^13.7 || ^14 || >=15.0.1}
hasBin: true
- nanoid@5.1.5:
- resolution: {integrity: sha512-Ir/+ZpE9fDsNH0hQ3C68uyThDXzYcim2EqcZ8zn8Chtt1iylPT9xXJB0kPCnqzgcEGikO9RxSrh63MsmVCU7Fw==}
- engines: {node: ^18 || >=20}
- hasBin: true
-
natural-compare@1.4.0:
resolution: {integrity: sha512-OWND8ei3VtNC9h7V60qff3SVobHr996CTwgxubgyQYEpg290h9J0buyECNNJexkFm5sOajh5G116RYA1c8ZMSw==}
- no-case@3.0.4:
- resolution: {integrity: sha512-fgAN3jGAh+RoxUGZHTSOLJIqUc2wmoBwGR4tbpNAKmmovFoWq0OdRkb0VkldReO2a2iBT/OEulG9XSUc10r3zg==}
-
- node-addon-api@7.1.1:
- resolution: {integrity: sha512-5m3bsyrjFWE1xf7nz7YXdN4udnVtXK6/Yfgn5qnahL6bCkf2yKt4k3nuTKAtT4r3IG8JNR2ncsIMdZuAzJjHQQ==}
-
- node-fetch-native@1.6.6:
- resolution: {integrity: sha512-8Mc2HhqPdlIfedsuZoc3yioPuzp6b+L5jRCRY1QzuWZh2EGJVQrGppC6V6cF0bLdbW0+O2YpqCA25aF/1lvipQ==}
-
- node-releases@2.0.19:
- resolution: {integrity: sha512-xxOWJsBKtzAq7DY0J+DTzuz58K8e7sJbdgwkbMWQe8UYB6ekmsQ45q0M/tJDsGaZmbC+l7n57UV8Hl5tHxO9uw==}
-
- nodemon@3.1.10:
- resolution: {integrity: sha512-WDjw3pJ0/0jMFmyNDp3gvY2YizjLmmOUQo6DEBY+JgdvW/yQ9mEeSw6H5ythl5Ny2ytb7f9C2nIbjSxMNzbJXw==}
- engines: {node: '>=10'}
- hasBin: true
-
- normalize-path@3.0.0:
- resolution: {integrity: sha512-6eZs5Ls3WtCisHWp9S2GUy8dqkpGi4BVSz3GaqiE6ezub0512ESztXUwUB6C6IKbQkY2Pnb/mD4WYojCRwcwLA==}
- engines: {node: '>=0.10.0'}
-
- npm-run-path@6.0.0:
- resolution: {integrity: sha512-9qny7Z9DsQU8Ou39ERsPU4OZQlSTP47ShQzuKZ6PRXpYLtIFgl/DEBYEXKlvcEa+9tHVcK8CF81Y2V72qaZhWA==}
- engines: {node: '>=18'}
-
- nprogress@0.2.0:
- resolution: {integrity: sha512-I19aIingLgR1fmhftnbWWO3dXc0hSxqHQHQb3H8m+K3TnEn/iSeTZZOyvKXWqQESMwuUVnatlCnZdLBZZt2VSA==}
-
nth-check@2.1.1:
resolution: {integrity: sha512-lqjrjmaOoAnWfMmBPL+XNnynZh2+swxiX3WUE0s4yEHI6m+AwrK2UZOimIRl3X/4QctVqS8AiZjFqyOGrMXb/w==}
- nwsapi@2.2.20:
- resolution: {integrity: sha512-/ieB+mDe4MrrKMT8z+mQL8klXydZWGR5Dowt4RAGKbJ3kIGEx3X4ljUo+6V73IXtUPWgfOlU5B9MlGxFO5T+cA==}
-
- object-assign@4.1.1:
- resolution: {integrity: sha512-rJgTQnkUnH1sFw8yT6VSU3zD3sWmu6sZhIseY8VX+GRu3P6F7Fu+JNDoXfklElbLJSnc3FUQHVe4cU5hj+BcUg==}
- engines: {node: '>=0.10.0'}
-
- object-inspect@1.13.4:
- resolution: {integrity: sha512-W67iLl4J2EXEGTbfeHCffrjDfitvLANg0UlX3wFUUSTx92KXRFegMHUVgSqE+wvhAbi4WqjGg9czysTV2Epbew==}
- engines: {node: '>= 0.4'}
-
- ofetch@1.4.1:
- resolution: {integrity: sha512-QZj2DfGplQAr2oj9KzceK9Hwz6Whxazmn85yYeVuS3u9XTMOGMRx0kO95MQ+vLsj/S/NwBDMMLU5hpxvI6Tklw==}
-
- ohash@2.0.11:
- resolution: {integrity: sha512-RdR9FQrFwNBNXAr4GixM8YaRZRJ5PUWbKYbE5eOsrwAjJW0q2REGcf79oYPsLyskQCZG1PLN+S/K1V00joZAoQ==}
-
- on-finished@2.4.1:
- resolution: {integrity: sha512-oVlzkg3ENAhCk2zdv7IJwd/QUD4z2RxRwpkcGY8psCVcCYZNq4wYnVWALHM+brtuJjePWiYF/ClmuDr8Ch5+kg==}
- engines: {node: '>= 0.8'}
-
- onetime@7.0.0:
- resolution: {integrity: sha512-VXJjc87FScF88uafS3JllDgvAm+c/Slfz06lorj2uAY34rlUu0Nt+v8wreiImcrgAjjIHp1rXpTDlLOGw29WwQ==}
- engines: {node: '>=18'}
-
- oniguruma-parser@0.12.1:
- resolution: {integrity: sha512-8Unqkvk1RYc6yq2WBYRj4hdnsAxVze8i7iPfQr8e4uSP3tRv0rpZcbGUDvxfQQcdwHt/e9PrMvGCsa8OqG9X3w==}
-
- oniguruma-to-es@2.3.0:
- resolution: {integrity: sha512-bwALDxriqfKGfUufKGGepCzu9x7nJQuoRoAFp4AnwehhC2crqrDIAP/uN2qdlsAvSMpeRC3+Yzhqc7hLmle5+g==}
-
- oniguruma-to-es@4.3.3:
- resolution: {integrity: sha512-rPiZhzC3wXwE59YQMRDodUwwT9FZ9nNBwQQfsd1wfdtlKEyCdRV0avrTcSZ5xlIvGRVPd/cx6ZN45ECmS39xvg==}
-
- open@10.1.0:
- resolution: {integrity: sha512-mnkeQ1qP5Ue2wd+aivTD3NHd/lZ96Lu0jgf0pwktLPtx6cTZiH7tyeGRRHs0zX0rbrahXPnXlUnbeXyaBBuIaw==}
- engines: {node: '>=18'}
+ oniguruma-to-es@3.1.1:
+ resolution: {integrity: sha512-bUH8SDvPkH3ho3dvwJwfonjlQ4R80vjyvrU8YpxuROddv55vAEJrTuCuCVUhhsHbtlD9tGGbaNApGQckXhS8iQ==}
optionator@0.9.4:
resolution: {integrity: sha512-6IpQ7mKUxRcZNLIObR0hz7lxsapSSIYNZJwXPGeF0mTVqGKFIXj1DQcMoT22S3ROcLyY/rz0PWaWZ9ayWmad9g==}
engines: {node: '>= 0.8.0'}
- ora@8.2.0:
- resolution: {integrity: sha512-weP+BZ8MVNnlCm8c0Qdc1WSWq4Qn7I+9CJGm7Qali6g44e/PUzbjNqJX5NJ9ljlNMosfJvg1fKEGILklK9cwnw==}
- engines: {node: '>=18'}
-
- p-limit@2.3.0:
- resolution: {integrity: sha512-//88mFWSJx8lxCzwdAABTJL2MyWB12+eIY7MDL2SqLmAkeKU9qxRvWuSyTjm3FUmpBEMuFfckAIqEaVGUDxb6w==}
- engines: {node: '>=6'}
-
p-limit@3.1.0:
resolution: {integrity: sha512-TYOanM3wGwNGsZN2cVTYPArw454xnXj5qmWF1bEoAc4+cU/ol7GVh7odevjp1FNHduHc3KZMcFduxU5Xc6uJRQ==}
engines: {node: '>=10'}
- p-locate@4.1.0:
- resolution: {integrity: sha512-R79ZZ/0wAxKGu3oYMlz8jy/kbhsNrS7SKZ7PxEHBgJ5+F2mtFW2fK2cOtBh1cHYkQsbzFV7I+EoRKe6Yt0oK7A==}
- engines: {node: '>=8'}
-
p-locate@5.0.0:
resolution: {integrity: sha512-LaNjtRWUBY++zB5nE/NwcaoMylSPk+S+ZHNB1TzdbMJMny6dynpAGt7X/tl/QYq3TIeE6nxHppbo2LGymrG5Pw==}
engines: {node: '>=10'}
- p-try@2.2.0:
- resolution: {integrity: sha512-R4nPAVTAU0B9D35/Gk3uJf/7XYbQcyohSKdvAxIRSNghFl4e71hVoGnBNQz9cWaXxO2I10KTC+3jMdvvoKw6dQ==}
- engines: {node: '>=6'}
-
- package-manager-detector@1.3.0:
- resolution: {integrity: sha512-ZsEbbZORsyHuO00lY1kV3/t72yp6Ysay6Pd17ZAlNGuGwmWDLCJxFpRs0IzfXfj1o4icJOkUEioexFHzyPurSQ==}
-
- param-case@3.0.4:
- resolution: {integrity: sha512-RXlj7zCYokReqWpOPH9oYivUzLYZ5vAPIfEmCTNViosC78F8F0H9y7T7gG2M39ymgutxF5gcFEsyZQSph9Bp3A==}
-
- parent-module@1.0.1:
- resolution: {integrity: sha512-GQ2EWRpQV8/o+Aw8YqtfZZPfNRWZYkbidE9k5rpl/hC3vtHHBfGm2Ifi6qWV+coDGkrUKZAxE3Lot5kcsRlh+g==}
- engines: {node: '>=6'}
-
- parse-ms@4.0.0:
- resolution: {integrity: sha512-TXfryirbmq34y8QBwgqCVLi+8oA3oWx2eAnSn62ITyEhEYaWRlVZ2DvMM9eZbMs/RfxPu/PK/aBLyGj4IrqMHw==}
- engines: {node: '>=18'}
-
- parse5@7.3.0:
- resolution: {integrity: sha512-IInvU7fabl34qmi9gY8XOVxhYyMyuH2xUNpb2q8/Y+7552KlejkRvqvD19nMoUW/uQGGbqNpA6Tufu5FL5BZgw==}
-
- parseley@0.12.1:
- resolution: {integrity: sha512-e6qHKe3a9HWr0oMRVDTRhKce+bRO8VGQR3NyVwcjwrbhMmFCX9KszEV35+rn4AdilFAq9VPxP/Fe1wC9Qjd2lw==}
-
- pascal-case@3.1.2:
- resolution: {integrity: sha512-uWlGT3YSnK9x3BQJaOdcZwrnV6hPpd8jFH1/ucpiLRPh/2zCVJKS19E4GvYHvaCcACn3foXZ0cLB9Wrx1KGe5g==}
-
- pascalcase@2.0.0:
- resolution: {integrity: sha512-DHpENy5Qm/FaX+x3iBLoMLG/XHNCTgL+yErm1TwuVaj6u4fiOSkYkf60vGtITk7hrKHOO4uCl9vRrD4hqjNKjg==}
- engines: {node: '>=14'}
+ package-manager-detector@1.8.0:
+ resolution: {integrity: sha512-yQA4H19AmPEoMUeavPMDIe1higySl/gH/yaQrkT/s07Qp+7pp2hYz30N3z2l5BkjVkF9Ow6o0wjJamm2y7Sn0A==}
path-browserify@1.0.1:
resolution: {integrity: sha512-b7uo2UCUOYZcnF/3ID0lulOJi/bafxa1xPe7ZPsammBSpjSWQkjNxlt635YGS2MiR9GjvuXCtz2emr3jbsz98g==}
@@ -3315,137 +1734,57 @@ packages:
resolution: {integrity: sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q==}
engines: {node: '>=8'}
- path-key@4.0.0:
- resolution: {integrity: sha512-haREypq7xkM7ErfgIyA0z+Bj4AGKlMSdlQE2jvJo6huWD1EdkKYV+G/T4nq0YEF2vgTT8kqMFKo1uHn950r4SQ==}
- engines: {node: '>=12'}
-
- pathe@1.1.2:
- resolution: {integrity: sha512-whLdWMYL2TwI08hn8/ZqAbrVemu0LNaNNJZX73O6qaIdCTfXutsLhMkjdENX0qhsQ9uIimo4/aQOmXkoon2nDQ==}
-
- pathe@2.0.3:
- resolution: {integrity: sha512-WUjGcAqP1gQacoQe+OBJsFA7Ld4DyXuUIjZ5cc75cLHvJ7dtNsTugphxIADwspS+AraAUePCKrSVtPLFj/F88w==}
-
- peberminta@0.9.0:
- resolution: {integrity: sha512-XIxfHpEuSJbITd1H3EeQwpcZbTLHc+VVr8ANI9t5sit565tsI4/xK3KWTUFE2e6QiangUkh3B0jihzmGnNrRsQ==}
-
perfect-debounce@1.0.0:
resolution: {integrity: sha512-xCy9V055GLEqoFaHoC1SoLIaLmWctgCUaBaWxDZ7/Zx4CTyX7cJQLJOok/orfjZAh9kEYpjJa4d0KcJmCbctZA==}
picocolors@1.1.1:
resolution: {integrity: sha512-xceH2snhtb5M9liqDsmEw56le376mTZkEX/jEb/RxNFyegNul7eNslCXP9FDj/Lcu0X8KEyMceP2ntpaHrDEVA==}
- picomatch@2.3.1:
- resolution: {integrity: sha512-JU3teHTNjmE2VCGFzuY8EXzCDVwEqB2a8fsIvwaStHhAWJEeVd1o1QD80CU6+ZdEXXSLbSsuLwJjkCBWqRQUVA==}
- engines: {node: '>=8.6'}
-
- picomatch@4.0.3:
- resolution: {integrity: sha512-5gTmgEY/sqK6gFXLIsQNH19lWb4ebPDLA4SdLP7dsWkIXHWlG66oPuVvXSGFPppYZz8ZDZq0dYYrbHfBCVUb1Q==}
+ picomatch@4.0.7:
+ resolution: {integrity: sha512-qcJu88Q2IWqJsDD529JKMdwGm/dvInW4HvQnRwiH9JtihJvzGOscDtHE3x1pBKeUOTysQ8kVmLnJ2kJu7yhcGA==}
engines: {node: '>=12'}
- pidtree@0.6.0:
- resolution: {integrity: sha512-eG2dWTVw5bzqGRztnHExczNxt5VGsE6OwTeCG3fdUf9KBsZzO3R5OIIIzWR+iZA0NtZ+RDVdaoE2dK1cn6jH4g==}
- engines: {node: '>=0.10'}
- hasBin: true
-
- pinia@3.0.3:
- resolution: {integrity: sha512-ttXO/InUULUXkMHpTdp9Fj4hLpD/2AoJdmAbAeW2yu1iy1k+pkFekQXw5VpC0/5p51IOR/jDaDRfRWRnMMsGOA==}
- peerDependencies:
- typescript: '>=4.4.4'
- vue: ^2.7.0 || ^3.5.11
- peerDependenciesMeta:
- typescript:
- optional: true
-
- pkg-types@1.3.1:
- resolution: {integrity: sha512-/Jm5M4RvtBFVkKWRu2BLUTNP8/M2a+UwuAX+ae4770q1qVGtfjG+WTCupoZixokjmHiry8uI+dlY8KXYV5HVVQ==}
-
- pkg-types@2.2.0:
- resolution: {integrity: sha512-2SM/GZGAEkPp3KWORxQZns4M+WSeXbC2HEvmOIJe3Cmiv6ieAJvdVhDldtHqM5J1Y7MrR1XhkBT/rMlhh9FdqQ==}
-
- pngjs@5.0.0:
- resolution: {integrity: sha512-40QW5YalBNfQo5yRYmiw7Yz6TKKVr3h6970B2YE+3fQpsWcrbj1PzJgxeJ19DRQjhMbKPIuMY8rFaXc8moolVw==}
- engines: {node: '>=10.13.0'}
-
points-on-curve@0.2.0:
resolution: {integrity: sha512-0mYKnYYe9ZcqMCWhUjItv/oHjvgEsfKvnUTg8sAtnHr3GVy7rGkXCb6d5cSyqrWqL4k81b9CPg3urd+T7aop3A==}
points-on-path@0.2.1:
resolution: {integrity: sha512-25ClnWWuw7JbWZcgqY/gJ4FQWadKxGWk+3kR/7kD0tCaDtPPMj7oHu2ToLaVhfpnHrZzYby2w6tUA0eOIuUg8g==}
- postcss-media-query-parser@0.2.3:
- resolution: {integrity: sha512-3sOlxmbKcSHMjlUXQZKQ06jOswE7oVkXPxmZdoB1r5l0q6gTFTQSHxNxOrCccElbW7dxNytifNEo8qidX2Vsig==}
+ postcss-selector-parser@7.1.6:
+ resolution: {integrity: sha512-7qASPzhKF2l2KLboRZux8CCTRMdGiV08vWmyKzPz22qZ7ZjQBOeY7rNzNoCLSUiftJ7HUq0GERHmxw/t0dCdMw==}
+ engines: {node: '>=4'}
- postcss@8.5.6:
- resolution: {integrity: sha512-3Ybi1tAuwAP9s0r1UQ2J4n5Y0G05bJkpUIO0/bI9MhwmD70S5aTWbXGBwxHrelT+XM1k6dM0pk+SwNkpTRN7Pg==}
+ postcss@8.5.28:
+ resolution: {integrity: sha512-RRuzqDtt5Y9h3quz5hWhK+TPnsmVs6WwSU6LkJMeY4HstUEDuYTG8UJSdawMRzmzAtV+KEoG8N3Qg2qLy5vM/A==}
engines: {node: ^10 || ^12 || >=14}
- preact@10.26.9:
- resolution: {integrity: sha512-SSjF9vcnF27mJK1XyFMNJzFd5u3pQiATFqoaDy03XuN00u4ziveVVEGt5RKJrDR8MHE/wJo9Nnad56RLzS2RMA==}
+ preact@10.29.8:
+ resolution: {integrity: sha512-ej2aVZ+vZ8WO7tvlQWRM9N63A0KzF9q4mWJfDUHgYaIofWY9hu74QdnQrjoPMmZi2/nZ5gN0bJCQF49xQqx09Q==}
+ peerDependencies:
+ preact-render-to-string: '>=5'
+ peerDependenciesMeta:
+ preact-render-to-string:
+ optional: true
prelude-ls@1.2.1:
resolution: {integrity: sha512-vkcDPrRZo1QZLbn5RLGPpg/WmIQ65qoWWhcGKf/b5eplkkarX0m9z8ppCat4mlOqUsWpyNuYgO3VRyrYHSzX5g==}
engines: {node: '>= 0.8.0'}
- prettier@3.6.2:
- resolution: {integrity: sha512-I7AIg5boAr5R0FFtJ6rCfD+LFsWHp81dolrFD8S79U9tb8Az2nGrJncnMSnys+bpQJfRUzqs9hnA81OAA3hCuQ==}
+ prettier@3.9.9:
+ resolution: {integrity: sha512-Z/CJHIkdujO/OtN7nXUii0Rf3VT5SRuhjBA82Xvu2XhBUgX3nhP67T0LHceBdQLex7OOFGTox+Q5Yg8Jk2Qivg==}
engines: {node: '>=14'}
hasBin: true
- pretty-ms@9.2.0:
- resolution: {integrity: sha512-4yf0QO/sllf/1zbZWYnvWw3NxCQwLXKzIj0G849LSufP15BXKM0rbD2Z3wVnkMfjdn/CB0Dpp444gYAACdsplg==}
- engines: {node: '>=18'}
-
- property-information@7.1.0:
- resolution: {integrity: sha512-TwEZ+X+yCJmYfL7TPUOcvBZ4QfoT5YenQiJuX//0th53DE6w0xxLEtfK3iyryQFddXuvkIk51EEgrJQ0WJkOmQ==}
-
- proxy-from-env@1.1.0:
- resolution: {integrity: sha512-D+zkORCbA9f1tdWRK0RaCR3GPv50cMxcrz4X8k5LTSUD1Dkw47mKJEZQNunItRTkWwgtaUSo1RVFRIG9ZXiFYg==}
-
- pstree.remy@1.1.8:
- resolution: {integrity: sha512-77DZwxQmxKnu3aR542U+X8FypNzbfJ+C5XQDk3uWjWxn6151aIMGthWYRXTqT1E5oJvg+ljaa2OJi+VfvCOQ8w==}
-
- punycode.js@2.3.1:
- resolution: {integrity: sha512-uxFIHU0YlHYhDQtV4R9J6a52SLx28BCjT+4ieh7IGbgwVJWO+km431c4yRlREUAsAmt/uMjQUyQHNEPf0M39CA==}
- engines: {node: '>=6'}
+ property-information@7.2.0:
+ resolution: {integrity: sha512-IAtzIB6sUiWaJYrX9smp3V46pBGbBeLFRGdh25kg1334VcBlD8HzhPeNIWQH9zhGmo2itIe25EHt9dQP7G5hmg==}
punycode@2.3.1:
resolution: {integrity: sha512-vYt7UD1U9Wg6138shLtLOvdAu+8DsC/ilFtEVHcH+wydcSpNE20AfSOduf6MkRFahL5FY7X1oU7nKVZFtfq8Fg==}
engines: {node: '>=6'}
- qrcode@1.5.4:
- resolution: {integrity: sha512-1ca71Zgiu6ORjHqFBDpnSMTR2ReToX4l1Au1VFLyVeBTFavzQnv5JxMFr3ukHVKpSrSA2MCk0lNJSykjUfz7Zg==}
- engines: {node: '>=10.13.0'}
- hasBin: true
-
- qs@6.14.0:
- resolution: {integrity: sha512-YWWTjgABSKcvs/nWBi9PycY/JiPJqOD4JA6o9Sej2AtvSGarXxKC3OQSk4pAarbdQlKAh5D4FCQkJNkW+GAn3w==}
- engines: {node: '>=0.6'}
-
- quansync@0.2.10:
- resolution: {integrity: sha512-t41VRkMYbkHyCYmOvx/6URnN80H7k4X0lLdBMGsz+maAwrJQYB1djpV6vHrQIBE0WBSGqhtEHrK9U3DWWH8v7A==}
-
- querystring@0.2.0:
- resolution: {integrity: sha512-X/xY82scca2tau62i9mDyU9K+I+djTMUsvwf7xnUX5GLvVzgJybOJf4Y6o9Zx3oJK/LSXg5tTZBjwzqVPaPO2g==}
- engines: {node: '>=0.4.x'}
- deprecated: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
-
- queue-microtask@1.2.3:
- resolution: {integrity: sha512-NuaNSa6flKT5JaSYQzJok04JzTL1CA6aGhv5rfLW3PgqA+M2ChpZQnAC8h8i4ZFkBS8X5RqkDBHA7r4hej3K9A==}
-
- raw-body@3.0.0:
- resolution: {integrity: sha512-RmkhL8CAyCRPXCE28MMH0z2PNWQBNk2Q09ZdxM9IOOXwxwZbN+qbWaatPkdkWIKL2ZVDImrN/pK5HTRz2PcS4g==}
- engines: {node: '>= 0.8'}
-
- readdirp@3.6.0:
- resolution: {integrity: sha512-hOS089on8RduqdbhvQ5Z37A0ESjsqz6qnRcffsMU3495FuTdqSm+7bhJ29JvIOsBDEEnan5DPu9t3To9VRlMzA==}
- engines: {node: '>=8.10.0'}
-
- readdirp@4.1.2:
- resolution: {integrity: sha512-GDhwkLfywWL2s6vEjyhri+eXmfH6j1L7JE27WhqLeYzoh/A3DBaYGEj2H/HFZCn/kMfim73FXxEJTw06WtxQwg==}
- engines: {node: '>= 14.18.0'}
-
- regex-recursion@5.1.1:
- resolution: {integrity: sha512-ae7SBCbzVNrIjgSbh7wMznPcQel1DNlDtzensnFxpiNpXt1U2ju/bHugH422r+4LAVS1FpW1YCwilmnNsjum9w==}
+ qified@0.10.1:
+ resolution: {integrity: sha512-+Owyggi9IxT1ePKGafcI87ubSmxol6smwJ+RAHDQlx9+9cPwFWDiKFFCPuWhr9ignlGpZ9vDQLw67N4dcTVFEA==}
+ engines: {node: '>=20'}
regex-recursion@6.0.2:
resolution: {integrity: sha512-0YCaSCq2VRIebiaUviZNs0cBz1kg5kVS2UKUfNIx8YVs1cN3AV7NTctO5FOKBA+UT2BPJIWZauYHPqJODG50cg==}
@@ -3453,91 +1792,29 @@ packages:
regex-utilities@2.3.0:
resolution: {integrity: sha512-8VhliFJAWRaUiVvREIiW2NXXTmHs4vMNnSzuJVhscgmGav3g9VDxLrQndI3dZZVVdp0ZO/5v0xmX516/7M9cng==}
- regex@5.1.1:
- resolution: {integrity: sha512-dN5I359AVGPnwzJm2jN1k0W9LPZ+ePvoOeVMMfqIMFz53sSwXkxaJoxr50ptnsC771lK95BnTrVSZxq0b9yCGw==}
+ regex@6.1.0:
+ resolution: {integrity: sha512-6VwtthbV4o/7+OaAF9I5L5V3llLEsoPyq9P1JVXkedTP33c7MfCG0/5NOPcSJn0TzXcG9YUrR0gQSWioew3LDg==}
- regex@6.0.1:
- resolution: {integrity: sha512-uorlqlzAKjKQZ5P+kTJr3eeJGSVroLKoHmquUj4zHWuR+hEyNqlXsSKlYYF5F4NI6nl7tWCs0apKJ0lmfsXAPA==}
+ rfdc@1.4.1:
+ resolution: {integrity: sha512-q1b3N5QkRUWUl7iyylaaj3kOpIT0N2i9MqIEQXP73GVsN9cw3fdx8X63cEmWhJGi2PPCF23Ijp7ktmd39rawIA==}
- relateurl@0.2.7:
- resolution: {integrity: sha512-G08Dxvm4iDN3MLM0EsP62EDV9IuhXPR6blNz6Utcp7zyV3tr4HVNINt6MpaRWbxoOHT3Q7YN2P+jaHX8vUbgog==}
- engines: {node: '>= 0.10'}
+ robust-predicates@3.0.3:
+ resolution: {integrity: sha512-NS3levdsRIUOmiJ8FZWCP7LG3QpJyrs/TE0Zpf1yvZu8cAJJ6QMW92H1c7kWpdIHo8RvmLxN/o2JXTKHp74lUA==}
- require-directory@2.1.1:
- resolution: {integrity: sha512-fGxEI7+wsG9xrvdjsrlmL22OMTTiHRwAMroiEeMgq8gzoLC/PQr7RsRDSTLUg/bZAZtF+TVIkHc6/4RIKrui+Q==}
- engines: {node: '>=0.10.0'}
-
- require-from-string@2.0.2:
- resolution: {integrity: sha512-Xf0nWe6RseziFMu+Ap9biiUbmplq6S9/p+7w7YXP/JBHhrUDDUhwa+vANyubuqfZWTveU//DYVGsDG7RKL/vEw==}
- engines: {node: '>=0.10.0'}
-
- require-main-filename@2.0.0:
- resolution: {integrity: sha512-NKN5kMDylKuldxYLSUfrbo5Tuzh4hd+2E8NPPX02mZtn1VuREQToYe/ZdlJy+J3uCpfaiGF05e7B8W0iXbQHmg==}
-
- requires-port@1.0.0:
- resolution: {integrity: sha512-KigOCHcocU3XODJxsu8i/j8T9tzT4adHiecwORRQ0ZZFcp7ahwXuRU1m+yuO90C5ZUyGeGfocHDI14M3L3yDAQ==}
-
- resolve-from@4.0.0:
- resolution: {integrity: sha512-pb/MYmXstAkysRFx8piNI1tGFNQIFA3vkE3Gq4EuA1dF6gHp/+vgZqsCGJapvy8N3Q+4o7FwvquPJcnZ7RYy4g==}
- engines: {node: '>=4'}
-
- resolve-global@2.0.0:
- resolution: {integrity: sha512-gnAQ0Q/KkupGkuiMyX4L0GaBV8iFwlmoXsMtOz+DFTaKmHhOO/dSlP1RMKhpvHv/dh6K/IQkowGJBqUG0NfBUw==}
- engines: {node: '>=18'}
-
- restore-cursor@5.1.0:
- resolution: {integrity: sha512-oMA2dcrw6u0YfxJQXm342bFKX/E4sG9rbTzO9ptUcR/e8A33cHuvStiYOwH7fszkZlZ1z/ta9AAoPk2F4qIOHA==}
- engines: {node: '>=18'}
-
- reusify@1.1.0:
- resolution: {integrity: sha512-g6QUff04oZpHs0eG5p83rFLhHeV00ug/Yf9nZM6fLeUrPguBTkTQOdpAWWspMh55TZfVQDPaN3NQJfbVRAxdIw==}
- engines: {iojs: '>=1.0.0', node: '>=0.10.0'}
-
- rfdc@1.4.1:
- resolution: {integrity: sha512-q1b3N5QkRUWUl7iyylaaj3kOpIT0N2i9MqIEQXP73GVsN9cw3fdx8X63cEmWhJGi2PPCF23Ijp7ktmd39rawIA==}
-
- robust-predicates@3.0.2:
- resolution: {integrity: sha512-IXgzBWvWQwE6PrDI05OvmXUIruQTcoMDzRsOd5CDvHCVLcLHMTSYvOK5Cm46kWqlV3yAbuSpBZdJ5oP5OUoStg==}
-
- rollup@4.45.1:
- resolution: {integrity: sha512-4iya7Jb76fVpQyLoiVpzUrsjQ12r3dM7fIVz+4NwoYvZOShknRmiv+iu9CClZml5ZLGb0XMcYLutK6w9tgxHDw==}
- engines: {node: '>=18.0.0', npm: '>=8.0.0'}
- hasBin: true
+ rollup@4.63.5:
+ resolution: {integrity: sha512-KRWwmNLlPw5M7HcdYfm15oBv9n9LPtjzpzCIxS/phwqvPyxHSoKX6Y2YU3pxSPfy0CLquVgsx/j/hBi6OvH1Nw==}
+ engines: {node: '>=18.0.0', npm: '>=8.0.0'}
+ hasBin: true
roughjs@4.6.6:
resolution: {integrity: sha512-ZUz/69+SYpFN/g/lUlo2FXcIjRkSu3nDarreVdGGndHEBJ6cXPdKguS8JGxwj5HA5xIbVKSmLgr5b3AWxtRfvQ==}
- rrweb-cssom@0.8.0:
- resolution: {integrity: sha512-guoltQEx+9aMf2gDZ0s62EcV8lsXR+0w8915TC3ITdn2YueuNjdAYh/levpU9nFaoChh9RUS5ZdQMrKfVEN9tw==}
-
- run-applescript@7.0.0:
- resolution: {integrity: sha512-9by4Ij99JUr/MCFBUkDKLWK3G9HVXmabKz9U5MlIAIuvuzkiOicRYs8XJLxX+xahD+mLiiCYDqF9dKAgtzKP1A==}
- engines: {node: '>=18'}
-
- run-parallel@1.2.0:
- resolution: {integrity: sha512-5l4VyZR86LZ/lDxZTR6jqL8AFE2S0IFLMP26AbjsLVADxHdhB/c0GUsH+y39UfCi3dzz8OlQuPmnaJOMoDHQBA==}
-
rw@1.3.3:
resolution: {integrity: sha512-PdhdWy89SiZogBLaw42zdeqtRJ//zFd2PgQavcICDUgJT5oW10QCRKbJ6bg4r0/UY2M6BWd5tkxuGFRvCkgfHQ==}
safer-buffer@2.1.2:
resolution: {integrity: sha512-YZo3K82SD7Riyi0E1EQPojLz7kpepnSQI9IyPbHHg1XXXevb5dJI7tpyN2ADxGcQbHG7vcyRHk0cbwqcQriUtg==}
- sass@1.89.2:
- resolution: {integrity: sha512-xCmtksBKd/jdJ9Bt9p7nPKiuqrlBMBuuGkQlkhZjjQk3Ty48lv93k5Dq6OPkKt4XwxDJ7tvlfrTa1MPA9bf+QA==}
- engines: {node: '>=14.0.0'}
- hasBin: true
-
- sax@1.4.1:
- resolution: {integrity: sha512-+aWOz7yVScEGoKNd4PA10LZ8sk0A/z5+nXQG5giUO5rprX9jgYsTdov9qCchZiPIZezbZH+jRut8nPodFAX4Jg==}
-
- saxes@6.0.0:
- resolution: {integrity: sha512-xAg7SOnEhrm5zI3puOOKyy1OMcMlIJZYNJY7xLBwSze0UjhPLnWfj2GF2EpT0jmzaJKIWKHLsaSSajf35bcYnA==}
- engines: {node: '>=v12.22.7'}
-
- scule@1.3.0:
- resolution: {integrity: sha512-6FtHJEvt+pVMIB9IBY+IcCJ6Z5f1iQnytgyfKMhDKgmzYG+TeH/wx1y3l27rshSbLiSanrR9ffZDrEsmjlQF2g==}
-
search-insights@2.17.3:
resolution: {integrity: sha512-RQPdCYTa8A68uM2jwxoY842xDhvx3E5LFL1LxvxCNMev4o5mLuokczhzjAgGwUZBAmOKZknArSxLKmXtIi2AxQ==}
@@ -3545,24 +1822,11 @@ packages:
resolution: {integrity: sha512-vfD3pmTzGpufjScBh50YHKzEu2lxBWhVEHsNGoEXmCmn2hKGfeNLYMzCJpe8cD7gqX7TJluOVpBkAequ6dgMmA==}
engines: {node: '>=4'}
- selderee@0.11.0:
- resolution: {integrity: sha512-5TF+l7p4+OsnP8BCCvSyZiSPc4x4//p5uPwK8TCnVPJYRmU2aYKMpOXvw8zM5a5JvuuCGN1jmsMwuU2W02ukfA==}
-
- semver@6.3.1:
- resolution: {integrity: sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==}
- hasBin: true
-
- semver@7.7.2:
- resolution: {integrity: sha512-RF0Fw+rO5AMf9MAyaRXI4AV0Ulj5lMHqVxxdSgiVbixSCXoEmmX/jk0CuJw4+3SqroYO9VoUh+HcuJivvtJemA==}
+ semver@7.8.5:
+ resolution: {integrity: sha512-Y7/KDsb8LjooZpwaqGyulO6DQlksgCncchHGk+sZIY4SBvUocMBEFH5Ur1fI4dV+Jvl0w6cjvucaIi40puRioA==}
engines: {node: '>=10'}
hasBin: true
- set-blocking@2.0.0:
- resolution: {integrity: sha512-KiKBS8AnWGEyLzofFfmvKwpdPzqiy16LvQfK3yv/fVH7Bj13/wl3JSR1J+rfgRE9q7xUJK4qvgS8raSOeLUehw==}
-
- setprototypeof@1.2.0:
- resolution: {integrity: sha512-E5LDX7Wrp85Kil5bhZv46j8jOeboKq5JMmYM3gVGdGH8xFpPWXUMsNrlODCrkoxMEeNi/XZIwuRvY4XNwYMJpw==}
-
shebang-command@2.0.0:
resolution: {integrity: sha512-kHxr2zZpYtdmrN1qDjrrX/Z1rR1kG8Dx+gkpK1G4eXmvXswmcE1hTWBWYUzlraYw1/yZp6YuDY77YtvbN0dmDA==}
engines: {node: '>=8'}
@@ -3571,69 +1835,13 @@ packages:
resolution: {integrity: sha512-7++dFhtcx3353uBaq8DDR4NuxBetBzC7ZQOhmTQInHEd6bSrXdiEyzCvG07Z44UYdLShWUyXt5M/yhz8ekcb1A==}
engines: {node: '>=8'}
- shiki@1.29.2:
- resolution: {integrity: sha512-njXuliz/cP+67jU2hukkxCNuH1yUi4QfdZZY+sMr5PPrIyXSu5iTb/qYC4BiWWB0vZ+7TbdvYUCeL23zpwCfbg==}
-
- shiki@3.8.1:
- resolution: {integrity: sha512-+MYIyjwGPCaegbpBeFN9+oOifI8CKiKG3awI/6h3JeT85c//H2wDW/xCJEGuQ5jPqtbboKNqNy+JyX9PYpGwNg==}
-
- side-channel-list@1.0.0:
- resolution: {integrity: sha512-FCLHtRD/gnpCiCHEiJLOwdmFP+wzCmDEkc9y7NsYxeF4u7Btsn1ZuwgwJGxImImHicJArLP4R0yX4c2KCrMrTA==}
- engines: {node: '>= 0.4'}
-
- side-channel-map@1.0.1:
- resolution: {integrity: sha512-VCjCNfgMsby3tTdo02nbjtM/ewra6jPHmpThenkTYh8pG9ucZ/1P8So4u4FGBek/BjpOVsDCMoLA/iuBKIFXRA==}
- engines: {node: '>= 0.4'}
-
- side-channel-weakmap@1.0.2:
- resolution: {integrity: sha512-WPS/HvHQTYnHisLo9McqBHOJk2FkHO/tlpvldyrnem4aeQp4hai3gythswg6p01oSoTl58rcpiFAjF2br2Ak2A==}
- engines: {node: '>= 0.4'}
-
- side-channel@1.1.0:
- resolution: {integrity: sha512-ZX99e6tRweoUXqR+VBrslhda51Nh5MTQwou5tnUDgbtyM0dBgmhEDtWGP/xbKn6hqfPRHujUNwz5fy/wbbhnpw==}
- engines: {node: '>= 0.4'}
-
- signal-exit@4.1.0:
- resolution: {integrity: sha512-bzyZ1e88w9O1iNJbKnOlvYTrWPDl46O1bG0D3XInv+9tkPrxrN8jUUTiFlDkkmKWgn1M6CfIA13SuGqOa9Korw==}
- engines: {node: '>=14'}
-
- simple-git@3.28.0:
- resolution: {integrity: sha512-Rs/vQRwsn1ILH1oBUy8NucJlXmnnLeLCfcvbSehkPzbv3wwoFWIdtfd6Ndo6ZPhlPsCZ60CPI4rxurnwAa+a2w==}
-
- simple-update-notifier@2.0.0:
- resolution: {integrity: sha512-a2B9Y0KlNXl9u/vsW6sTIu9vGEpfKu2wRV6l1H3XEas/0gUIzGzBoP/IouTcUQbm9JWZLH3COxyn03TYlFax6w==}
- engines: {node: '>=10'}
-
- sirv@3.0.1:
- resolution: {integrity: sha512-FoqMu0NCGBLCcAkS1qA+XJIQTR6/JHfQXl+uGteNCQ76T91DMUjPa9xfmeqMY3z80nLSg9yQmNjK0Px6RWsH/A==}
- engines: {node: '>=18'}
-
- sisteransi@1.0.5:
- resolution: {integrity: sha512-bLGGlR1QxBcynn2d5YmDX4MGjlZvy2MRBDRNHLJ8VI6l6+9FUiyTFNJ0IveOSP0bcXgVDPRcfGqA0pjaqUpfVg==}
-
- slice-ansi@4.0.0:
- resolution: {integrity: sha512-qMCMfhY040cVHT43K9BFygqYbUPFZKHOg7K73mtTWJRb8pyP3fzf4Ixd5SzdEJQ6MRUg/WBnOLxghZtKKurENQ==}
- engines: {node: '>=10'}
-
- slice-ansi@5.0.0:
- resolution: {integrity: sha512-FC+lgizVPfie0kkhqUScwRu1O/lF6NOgJmlCgK+/LYxDCTk8sGelYaHDhFcDN+Sn3Cv+3VSa4Byeo+IMCzpMgQ==}
- engines: {node: '>=12'}
-
- slice-ansi@7.1.0:
- resolution: {integrity: sha512-bSiSngZ/jWeX93BqeIAbImyTbEihizcwNjFoRUIY/T1wWQsfsm2Vw1agPKylXvQTU7iASGdHhyqRlqQzfz+Htg==}
- engines: {node: '>=18'}
+ shiki@2.5.0:
+ resolution: {integrity: sha512-mI//trrsaiCIPsja5CNfsyNOqgAZUb6VpJA+340toL42UpzQlXpwRV9nch69X6gaUxrr9kaOOa6e3y3uAkGFxQ==}
source-map-js@1.2.1:
resolution: {integrity: sha512-UXWMKhLOwVKb728IUtQPXxfYU+usdybtUrK/8uGE8CQMvrhOpwvzDBwj0QhSL7MQc7vIsISBG8VQ8+IDQxpfQA==}
engines: {node: '>=0.10.0'}
- source-map-support@0.5.21:
- resolution: {integrity: sha512-uBHU3L3czsIyYXKX88fdrGovxdSCoTGDRZ6SYXtSRxLZUzHg5P/66Ht6uoUlHu9EZod+inXhKo3qQgwXUT/y1w==}
-
- source-map@0.6.1:
- resolution: {integrity: sha512-UjgapumWlbMhkBgzT7Ykc5YXUT46F0iKu8SGXq0bcwP5dz/h0Plj6enJqjz1Zbq2l5WaqYnrVbwWOWMyF3F47g==}
- engines: {node: '>=0.10.0'}
-
space-separated-tokens@2.0.2:
resolution: {integrity: sha512-PEGlAwrG8yXGXRjW32fGbg66JAlOAwbObuqVoJpv/mRgoWDQfgH1wDPvtzWyUSNAXBGSk8h755YDbbcEy3SH2Q==}
@@ -3644,173 +1852,69 @@ packages:
sprintf-js@1.0.3:
resolution: {integrity: sha512-D9cPgkvLlV3t3IzL0D0YLvGA9Ahk4PcvVwUbN0dSGr1aP0Nrt4AEnTUbuGvquEC0mA64Gqt1fzirlRs5ibXx8g==}
- star-markdown-css@0.5.3:
- resolution: {integrity: sha512-ewlx4ge1i6B2jopgOJbhgTbshNFI8HEH5vD2itxDh3qKYz+a9+H2EJC1pyPapDeJEOm0DRpHiAvBOSB/H1RMvA==}
-
- statuses@2.0.1:
- resolution: {integrity: sha512-RwNA9Z/7PrK06rYLIzFMlaF+l73iwpzsqRIFgbMLbTcLD6cOao82TaWefPXQvB2fOC4AjuYSEndS7N/mTCbkdQ==}
- engines: {node: '>= 0.8'}
-
- stdin-discarder@0.2.2:
- resolution: {integrity: sha512-UhDfHmA92YAlNnCfhmq0VeNL5bDbiZGg7sZ2IvPsXubGkiNa9EC+tUTsjBRsYUAz87btI6/1wf4XoVvQ3uRnmQ==}
- engines: {node: '>=18'}
-
string-argv@0.3.2:
resolution: {integrity: sha512-aqD2Q0144Z+/RqG52NeHEkZauTAUWJO8c6yTftGJKO3Tja5tUgIfmIl6kExvhtxSDP7fXB6DvzkfMpCd/F3G+Q==}
engines: {node: '>=0.6.19'}
- string-width@4.2.3:
- resolution: {integrity: sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==}
- engines: {node: '>=8'}
-
- string-width@7.2.0:
- resolution: {integrity: sha512-tsaTIkKW9b4N+AEj+SVA+WhJzV7/zMhcSu78mLKWSk7cXMOSHsBKFWUs0fWwq8QyK3MgJBQRX6Gbi4kYbdvGkQ==}
- engines: {node: '>=18'}
-
stringify-entities@4.0.4:
resolution: {integrity: sha512-IwfBptatlO+QCJUo19AqvrPNqlVMpW9YEL2LIVY+Rpv2qsjCGxaDLNRgeGsQWJhfItebuJhsGSLjaBbNSQ+ieg==}
- strip-ansi@6.0.1:
- resolution: {integrity: sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==}
- engines: {node: '>=8'}
-
- strip-ansi@7.1.0:
- resolution: {integrity: sha512-iq6eVVI64nQQTRYq2KtEg2d2uU7LElhTJwsH4YzIHZshxlgZms/wIc4VoDQTlG/IvVIrBKG06CrZnp0qv7hkcQ==}
- engines: {node: '>=12'}
-
strip-bom-string@1.0.0:
resolution: {integrity: sha512-uCC2VHvQRYu+lMh4My/sFNmF2klFymLX1wHJeXnbEJERpV/ZsVuonzerjfrGpIGF7LBVa1O7i9kjiWvJiFck8g==}
engines: {node: '>=0.10.0'}
- strip-final-newline@4.0.0:
- resolution: {integrity: sha512-aulFJcD6YK8V1G7iRB5tigAP4TsHBZZrOV8pjV++zdUwmeV8uzbY7yn6h9MswN62adStNZFuCIx4haBnRuMDaw==}
- engines: {node: '>=18'}
-
- strip-json-comments@3.1.1:
- resolution: {integrity: sha512-6fPc+R4ihwqP6N/aIv2f1gMH8lOVtWQHoqC4yK6oSDVVocumAsfCqjkXnqiYMhmMwS/mEHLp7Vehlt3ql6lEig==}
- engines: {node: '>=8'}
-
- stylis@4.3.6:
- resolution: {integrity: sha512-yQ3rwFWRfwNUY7H5vpU0wfdkNSnvnJinhF9830Swlaxl03zsOjCfmX0ugac+3LtK0lYSgwL/KXc8oYL3mG4YFQ==}
+ stylis@4.4.0:
+ resolution: {integrity: sha512-5Z9ZpRzfuH6l/UAvCPAPUo3665Nk2wLaZU3x+TLHKVzIz33+sbJqbtrYoC3KD4/uVOr2Zp+L0LySezP9OHV9yA==}
- superjson@2.2.2:
- resolution: {integrity: sha512-5JRxVqC8I8NuOUjzBbvVJAKNM8qoVuH0O77h4WInc/qC2q5IreqKxYwgkga3PfA22OayK2ikceb/B26dztPl+Q==}
+ superjson@2.2.6:
+ resolution: {integrity: sha512-H+ue8Zo4vJmV2nRjpx86P35lzwDT3nItnIsocgumgr0hHMQ+ZGq5vrERg9kJBo5AWGmxZDhzDo+WVIJqkB0cGA==}
engines: {node: '>=16'}
- supports-color@5.5.0:
- resolution: {integrity: sha512-QjVjwdXIt408MIiAqCX4oUKsgU2EqAGzs2Ppkm4aQYbjm+ZEWEcW4SfFNTr4uMNZma0ey4f5lgLrkB0aX0QMow==}
- engines: {node: '>=4'}
-
- supports-color@7.2.0:
- resolution: {integrity: sha512-qpCAvRl9stuOHveKsn7HncJRvv501qIacKzQlO/+Lwxc9+0q2wLyv4Dfvt80/DPn2pqOBsJdDiogXGR9+OvwRw==}
- engines: {node: '>=8'}
-
- symbol-tree@3.2.4:
- resolution: {integrity: sha512-9QNk5KwDF+Bvz+PyObkmSYjI5ksVUYtjW7AU22r2NKcfLJcXp96hkDWU3+XndOsUb+AQ9QhfzfCT2O+CNWT5Tw==}
-
- tabbable@6.2.0:
- resolution: {integrity: sha512-Cat63mxsVJlzYvN51JmVXIgNoUokrIaT2zLclCXjRd8boZ0004U4KCs/sToJ75C6sdlByWxpYnb5Boif1VSFew==}
-
- table@6.9.0:
- resolution: {integrity: sha512-9kY+CygyYM6j02t5YFHbNz2FN5QmYGv9zAjVp4lCDjlCw7amdckXlEt/bjMhUIfj4ThGRE4gCUH5+yGnNuPo5A==}
- engines: {node: '>=10.0.0'}
+ tabbable@6.5.0:
+ resolution: {integrity: sha512-wieBHXygIm7OyQOu5hQlkk62/WyCFYGlWg7L6/ZCUZwx0o398Zkn4pVmMyfYhfMG8kGrj/Krt8eIk6UKC6VzwA==}
- terser@5.43.1:
- resolution: {integrity: sha512-+6erLbBm0+LROX2sPXlUYx/ux5PyE9K/a92Wrt6oA+WDAoFTdpHE5tCYCI5PNzq2y8df4rA+QgHLJuR4jNymsg==}
- engines: {node: '>=10'}
- hasBin: true
-
- tinyexec@1.0.1:
- resolution: {integrity: sha512-5uC6DDlmeqiOwCPmK9jMSdOuZTh8bU39Ys6yidB+UTt5hfZUPGAypSgFRiEp+jbi9qH40BLDvy85jIU88wKSqw==}
+ tinyexec@1.3.1:
+ resolution: {integrity: sha512-GCvB3aoys96IuDFBMcTB46JOR6mdMtAToqwiW8JlWhsoh1mhHi/xn9ss/Dg7N555GiJyEt2qzoG/NHCwM6h1EA==}
+ engines: {node: '>=18'}
- tinyglobby@0.2.14:
- resolution: {integrity: sha512-tX5e7OM1HnYr2+a2C/4V0htOcSQcoSTH9KgJnVvNm5zm/cyEWKJ7j7YutsH9CxMdtOkkLFy2AHrMci9IM8IPZQ==}
+ tinyglobby@0.2.17:
+ resolution: {integrity: sha512-wXR/dYpcqKmfWpEdZjiKJOwCNFndD0DMnrW/cYjVGttEkBfVgcLFHoNrlj47mjOVic9yyNu65alsgF4NQyTa2g==}
engines: {node: '>=12.0.0'}
- tldts-core@6.1.86:
- resolution: {integrity: sha512-Je6p7pkk+KMzMv2XXKmAE3McmolOQFdxkKw0R8EYNr7sELW46JqnNeTX8ybPiQgvg1ymCoF8LXs5fzFaZvJPTA==}
-
- tldts@6.1.86:
- resolution: {integrity: sha512-WMi/OQ2axVTf/ykqCQgXiIct+mSQDFdH2fkwhPwgEwvJ1kSzZRiinb0zF2Xb8u4+OqPChmyI6MEu4EezNJz+FQ==}
- hasBin: true
-
- to-regex-range@5.0.1:
- resolution: {integrity: sha512-65P7iz6X5yEr1cwcgvQxbbIw7Uk3gOy5dIdtZ4rDveLqhrdJP+Li/Hx6tyK0NEb+2GCyneCMJiGqrADCSNk8sQ==}
- engines: {node: '>=8.0'}
-
- toidentifier@1.0.1:
- resolution: {integrity: sha512-o5sSPKEkg/DIQNmH43V0/uerLrpzVedkUh8tGNvaeXpfpuwjKenlSox/2O/BTlZUtEe+JG7s5YhEz608PlAHRA==}
- engines: {node: '>=0.6'}
-
- totalist@3.0.1:
- resolution: {integrity: sha512-sf4i37nQ2LBx4m3wB74y+ubopq6W/dIzXg0FDGjsYnZHVa1Da8FH853wlL2gtUhg+xJXjfk3kUZS3BRoQeoQBQ==}
- engines: {node: '>=6'}
-
- touch@3.1.1:
- resolution: {integrity: sha512-r0eojU4bI8MnHr8c5bNo7lJDdI2qXlWWJk6a9EAFG7vbhTjElYhBVS3/miuE0uOuoLdb8Mc/rVfsmm6eo5o9GA==}
- hasBin: true
-
- tough-cookie@5.1.2:
- resolution: {integrity: sha512-FVDYdxtnj0G6Qm/DhNPSb8Ju59ULcup3tuJxkFb5K8Bv2pUXILbf0xZWU8PX8Ov19OXljbUyveOFwRMwkXzO+A==}
- engines: {node: '>=16'}
-
- tr46@5.1.1:
- resolution: {integrity: sha512-hdF5ZgjTqgAntKkklYw0R03MG2x/bSzTtkxmIRw/sTNV8YXsCJ1tfLAX23lhxhHJlEf3CRCOCGGWw3vI3GaSPw==}
- engines: {node: '>=18'}
-
trim-lines@3.0.1:
resolution: {integrity: sha512-kRj8B+YHZCc9kQYdWfJB2/oUl9rA99qbowYYBtr4ui4mZyAQ2JpvVBd/6U2YloATfqBhBTSMhTpgBHtU0Mf3Rg==}
- ts-api-utils@2.1.0:
- resolution: {integrity: sha512-CUgTZL1irw8u29bzrOD/nH85jqyc74D6SshFgujOIA7osm2Rz7dYH77agkx7H4FBNxDq7Cjf+IjaX/8zwFW+ZQ==}
+ ts-api-utils@2.5.0:
+ resolution: {integrity: sha512-OJ/ibxhPlqrMM0UiNHJ/0CKQkoKF243/AEmplt3qpRgkW8VG7IfOS41h7V8TjITqdByHzrjcS/2si+y4lIh8NA==}
engines: {node: '>=18.12'}
peerDependencies:
typescript: '>=4.8.4'
- ts-dedent@2.2.0:
- resolution: {integrity: sha512-q5W7tVM71e2xjHZTlgfTDoPF/SmqKG5hddq9SzR49CH2hayqRKJtQ4mtRlSxKaJlR/+9rEM+mnBHf7I2/BQcpQ==}
+ ts-dedent@2.3.0:
+ resolution: {integrity: sha512-JfJeIHke7y2egdGGgRAvpCwYFUsHlM2gPcrVOxFkznt/4uzQ7HFmvE63iFHVLBJNDuyDOQgijDK/tXH/f6Msjg==}
engines: {node: '>=6.10'}
- tslib@2.8.1:
- resolution: {integrity: sha512-oJFu94HQb+KVduSUQL7wnpmqnfmLsOA/nAh6b6EH0wCEoK0/mPeXU6c3wKDV83MkOuHPRHtSXKKU99IBazS/2w==}
-
type-check@0.4.0:
resolution: {integrity: sha512-XleUoc9uwGXqjWwXaUTZAmzMcFZ5858QA2vvx1Ur5xIcixXIP+8LnFDgRplU30us6teqdlskFfu+ae4K79Ooew==}
engines: {node: '>= 0.8.0'}
- type-is@2.0.1:
- resolution: {integrity: sha512-OZs6gsjF4vMp32qrCbiVSkrFmXtG/AZhY3t0iAMrMBiAZyV9oALtXO8hsrHbMXF9x6L3grlFuwW2oAz7cav+Gw==}
- engines: {node: '>= 0.6'}
+ typescript-eslint@8.70.1:
+ resolution: {integrity: sha512-AcWG7KDjZ2THNXsgwttMaGmzVi0VFRlFYfqFHYQRbDpF3owuYbuiL8c7UUrd2k8s3PoSfIQrWfrGXfcElrWLYA==}
+ engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
+ peerDependencies:
+ eslint: ^8.57.0 || ^9.0.0 || ^10.0.0
+ typescript: '>=4.8.4 <6.1.0'
- typescript@5.8.3:
- resolution: {integrity: sha512-p1diW6TqL9L07nNxvRMM7hMMw4c5XOo/1ibL4aAIGmSAt9slTE1Xgw5KWuof2uTOvCg9BY7ZRi+GaF+7sfgPeQ==}
+ typescript@6.0.3:
+ resolution: {integrity: sha512-y2TvuxSZPDyQakkFRPZHKFm+KKVqIisdg9/CZwm9ftvKXLP8NRWj38/ODjNbr43SsoXqNuAisEf1GdCxqWcdBw==}
engines: {node: '>=14.17'}
hasBin: true
- uc.micro@2.1.0:
- resolution: {integrity: sha512-ARDJmphmdvUk6Glw7y9DQ2bFkKBHwQHLi2lsaH6PPmz/Ka9sFOBsBluozhDltWmnv9u/cF6Rt87znRTPV+yp/A==}
+ undici-types@7.24.6:
+ resolution: {integrity: sha512-WRNW+sJgj5OBN4/0JpHFqtqzhpbnV0GuB+OozA9gCL7a993SmU+1JBZCzLNxYsbMfIeDL+lTsphD5jN5N+n0zg==}
- ufo@1.6.1:
- resolution: {integrity: sha512-9a4/uxlTWJ4+a5i0ooc1rU7C7YOw3wT+UGqdeNNHWnOF9qcMBgLRS+4IYUqbczewFx4mLEig6gawh7X6mFlEkA==}
-
- unconfig@7.3.2:
- resolution: {integrity: sha512-nqG5NNL2wFVGZ0NA/aCFw0oJ2pxSf1lwg4Z5ill8wd7K4KX/rQbHlwbh+bjctXL5Ly1xtzHenHGOK0b+lG6JVg==}
-
- undefsafe@2.0.5:
- resolution: {integrity: sha512-WxONCrssBM8TSPRqN5EmsjVrsv4A8X12J4ArBiiayv3DyyG3ZlIg6yysuuSYdZsVz3TKcTg2fd//Ujd4CHV1iA==}
-
- undici-types@7.8.0:
- resolution: {integrity: sha512-9UJ2xGDvQ43tYyVMpuHlsgApydB8ZKfVYTsLDhXkFL/6gfkp+U8xTGdh8pMJv1SpZna0zxG1DwsKZsreLbXBxw==}
-
- unhead@2.0.12:
- resolution: {integrity: sha512-5oo0lwz81XDXCmrHGzgmbaNOxM8R9MZ3FkEs2ROHeW8e16xsrv7qXykENlISrcxr3RLPHQEsD1b6js9P2Oj/Ow==}
-
- unicorn-magic@0.3.0:
- resolution: {integrity: sha512-+QBBXBCvifc56fsbuxZQ6Sic3wqqc3WWaqxs58gvJrcOuN83HGTCwz3oS5phzU9LthRNE9VrJCFCLUgHeeFnfA==}
- engines: {node: '>=18'}
-
- unist-util-is@6.0.0:
- resolution: {integrity: sha512-2qCTHimwdxLfz+YzdGfkqNlH0tLi9xjTnHddPmJwtIG9MGsdbutfTc4P+haPD7l7Cjxf/WZj+we5qfVPvvxfYw==}
+ unist-util-is@6.0.1:
+ resolution: {integrity: sha512-LsiILbtBETkDz8I9p1dQ0uyRUWuaQzd/cuEeS1hoRSyW5E5XGmTzlwY1OrNzzakGowI9Dr/I8HVaw4hTtnxy8g==}
unist-util-position@5.0.0:
resolution: {integrity: sha512-fucsC7HjXvkB5R3kTCO7kUjRdrS0BJt3M/FPxmHMBOm8JQi2BsHAHFsy27E0EolP8rp0NzXsJ+jNPyDWvOJZPA==}
@@ -3818,187 +1922,30 @@ packages:
unist-util-stringify-position@4.0.0:
resolution: {integrity: sha512-0ASV06AAoKCDkS2+xw5RXJywruurpbC4JZSm7nr7MOt1ojAzvyyaO+UxZf18j8FCF6kmzCZKcAgN/yu2gm2XgQ==}
- unist-util-visit-parents@6.0.1:
- resolution: {integrity: sha512-L/PqWzfTP9lzzEa6CKs0k2nARxTdZduw3zyh8d2NVBnsyvHjSX4TWse388YrrQKbvI8w20fGjGlhgT96WwKykw==}
-
- unist-util-visit@5.0.0:
- resolution: {integrity: sha512-MR04uvD+07cwl/yhVuVWAtw+3GOR/knlL55Nd/wAdblk27GCVt3lqpTivy/tkJcZoNPzTwS1Y+KMojlLDhoTzg==}
-
- universal-user-agent@7.0.3:
- resolution: {integrity: sha512-TmnEAEAsBJVZM/AADELsK76llnwcf9vMKuPz8JflO1frO8Lchitr0fNaN9d+Ap0BjKtqWqd/J17qeDnXh8CL2A==}
-
- universalify@2.0.1:
- resolution: {integrity: sha512-gptHNQghINnc/vTGIk0SOFGFNXw7JVrlRUtConJRlvaw6DuX0wO5Jeko9sWrMBhh+PsYAZ7oXAiOnf/UKogyiw==}
- engines: {node: '>= 10.0.0'}
-
- unocss@66.3.3:
- resolution: {integrity: sha512-HSB+K4/EbouwYmxpPU52cg0exua7PUr2IAJZBV3iai6tPdMcJ0c8jXaw7G+2L+ffruVFTcS0e2kE4OrR8BKDLg==}
- engines: {node: '>=14'}
- peerDependencies:
- '@unocss/webpack': 66.3.3
- vite: ^2.9.0 || ^3.0.0-0 || ^4.0.0 || ^5.0.0-0 || ^6.0.0-0 || ^7.0.0-0
- peerDependenciesMeta:
- '@unocss/webpack':
- optional: true
- vite:
- optional: true
-
- unpipe@1.0.0:
- resolution: {integrity: sha512-pjy2bYhSsufwWlKwPc+l3cN7+wuJlK6uz0YdJEOlQDbl6jo/YlPi4mb8agUkVC8BF7V8NuzeyPNqRksA3hztKQ==}
- engines: {node: '>= 0.8'}
-
- unplugin-ast@0.15.1:
- resolution: {integrity: sha512-7nhKrf61dXPU7vqzu3yxHs0YaUToIYB32FlnNLxdAOjF+bI+16LpDygGtdRuhJKgwPCpz0tNaAEamxaGB/SQOQ==}
- engines: {node: '>=20.18.0'}
-
- unplugin-utils@0.2.4:
- resolution: {integrity: sha512-8U/MtpkPkkk3Atewj1+RcKIjb5WBimZ/WSLhhR3w6SsIj8XJuKTacSP8g+2JhfSGw0Cb125Y+2zA/IzJZDVbhA==}
- engines: {node: '>=18.12.0'}
-
- unplugin-vue-components@28.0.0:
- resolution: {integrity: sha512-vYe0wSyqTVhyNFIad1iiGyQGhG++tDOMgohqenMDOAooMJP9vvzCdXTqCVx20A0rCQXFNjgoRbSeDAioLPH36Q==}
- engines: {node: '>=14'}
- peerDependencies:
- '@babel/parser': ^7.15.8
- '@nuxt/kit': ^3.2.2
- vue: 2 || 3
- peerDependenciesMeta:
- '@babel/parser':
- optional: true
- '@nuxt/kit':
- optional: true
-
- unplugin-vue-markdown@29.1.0:
- resolution: {integrity: sha512-BvDFrhsiXzVvzfq1y68jtZwHg1NYJBteSXmUK4zMdX1HT2QtKw8yimjUbDwuI1K9TW/1/L6QYiRQSl1OkHcxWg==}
- engines: {node: '>=20'}
- peerDependencies:
- vite: ^2.0.0 || ^3.0.0-0 || ^4.0.0-0 || ^5.0.0-0 || ^6.0.0 || ^7.0.0
-
- unplugin-vue-router@0.14.0:
- resolution: {integrity: sha512-ipjunvS5e2aFHBAUFuLbHl2aHKbXXXBhTxGT9wZx66fNVPdEQzVVitF8nODr1plANhTTa3UZ+DQu9uyLngMzoQ==}
- peerDependencies:
- '@vue/compiler-sfc': ^3.5.17
- vue-router: ^4.5.1
- peerDependenciesMeta:
- vue-router:
- optional: true
-
- unplugin@1.16.1:
- resolution: {integrity: sha512-4/u/j4FrCKdi17jaxuJA0jClGxB1AvU2hw/IuayPc4ay1XGaJs/rbb4v5WKwAjNifjmXK9PIFyuPiaK8azyR9w==}
- engines: {node: '>=14.0.0'}
+ unist-util-visit-parents@6.0.2:
+ resolution: {integrity: sha512-goh1s1TBrqSqukSc8wrjwWhL0hiJxgA8m4kFxGlQ+8FYQ3C/m11FcTs4YYem7V664AhHVvgoQLk890Ssdsr2IQ==}
- unplugin@2.3.5:
- resolution: {integrity: sha512-RyWSb5AHmGtjjNQ6gIlA67sHOsWpsbWpwDokLwTcejVdOjEkJZh7QKu14J00gDDVSh8kGH4KYC/TNBceXFZhtw==}
- engines: {node: '>=18.12.0'}
-
- update-browserslist-db@1.1.3:
- resolution: {integrity: sha512-UxhIZQ+QInVdunkDAaiazvvT/+fXL5Osr0JZlJulepYu6Jd7qJtDZjlur0emRlT71EN3ScPoE7gvsuIKKNavKw==}
- hasBin: true
- peerDependencies:
- browserslist: '>= 4.21.0'
+ unist-util-visit@5.1.0:
+ resolution: {integrity: sha512-m+vIdyeCOpdr/QeQCu2EzxX/ohgS8KbnPDgFni4dQsfSCtpz8UqDyY5GjRru8PDKuYn7Fq19j1CQ+nJSsGKOzg==}
uri-js@4.4.1:
resolution: {integrity: sha512-7rKUyy33Q1yc98pQ1DAmLtwX109F7TIfWlW1Ydo8Wl1ii1SeHieeh0HHfPeL2fMXK6z0s8ecKs9frCuLJvndBg==}
- uuid@11.1.0:
- resolution: {integrity: sha512-0/A9rDy9P7cJ+8w1c9WD9V//9Wj15Ce2MPz8Ri6032usz+NfePxx5AcN3bN+r6ZL6jEo066/yNYB3tn4pQEx+A==}
- hasBin: true
-
- valaxy-addon-algolia@0.2.0:
- resolution: {integrity: sha512-7Swjt3nrljjJ+1U80lZw3zN8cMj/7z8V71CJBRWhHKtGYDlNNv5g2EkvRJbI6O3Bpvvnb9iOC0K5ST6oRn7ReQ==}
- peerDependencies:
- valaxy: '>=0.22'
-
- valaxy-addon-components@0.1.0:
- resolution: {integrity: sha512-7uCJgUgc2JHISmz/UDQlhBqGSNW4QKmkiRlcwj5WhjhScC/KktK8JtADeKh6FCaAJHbjShovHB/9UPVtnTwORg==}
-
- valaxy-addon-git-log@0.3.2:
- resolution: {integrity: sha512-2gJPX6+gXYvyMtoboLORuFrsE9Bh+jz5cy8zjXfW2kDJdxmyJI8rqpP8WBHepssbU2DRUauK3cS+O+Xhnchs3A==}
- peerDependencies:
- valaxy: '>=0.22'
-
- valaxy-theme-press@0.25.9:
- resolution: {integrity: sha512-m3/ELaJGpMStqDc5JFcB+3U6VTc4wGsDN1sfwdvajh1T7RRryVsZHKBbD0kMA9JXtNkn3GGpAs0wU1eIuJ6Oaw==}
+ util-deprecate@1.0.2:
+ resolution: {integrity: sha512-EPD5q1uXyFxJpCrLnCc1nHnq3gOa6DZBocAIiI2TaSCA7VCJ1UJDMagCzIkXNsUYfD1daK//LTEQ8xiIbrHtcw==}
- valaxy@0.25.9:
- resolution: {integrity: sha512-FmfVaQdpfMls4hWu8Z8G8An8RaKNK8kX6FnZ1jC+acPRtfyDNAqhdBBCIqktSZXXcmYosWIrPsJqzXo/r5TCgg==}
- engines: {node: ^14.18.0 || >=16.0.0}
+ uuid@14.0.2:
+ resolution: {integrity: sha512-xZe/16rV4aa+HGSOCiY2YeLT1OybRLrrkL/Rqaq7p7GMVXjFh+6wN4oMYgjFmnSnhY8t6Xpdl2l9qmnHYuMHwQ==}
hasBin: true
- vanilla-lazyload@19.1.3:
- resolution: {integrity: sha512-bBMERPu2AFJc35krS+8BOhq++c6dRfL6q368lJPnkS5U92fRQagTR3FsNta69/GukfZzDwDEjD5M3U7VuSiCDw==}
-
- vary@1.1.2:
- resolution: {integrity: sha512-BNGbWLfd0eUPabhkXUVm0j8uuvREyTh5ovRa/dyow/BqAbZJyC+5fU+IzQOzmAKzYqYRAISoRhdQr3eIZ/PXqg==}
- engines: {node: '>= 0.8'}
-
- vfile-message@4.0.2:
- resolution: {integrity: sha512-jRDZ1IMLttGj41KcZvlrYAaI3CfqpLpfpf+Mfig13viT6NKvRzWZ+lXz0Y5D60w6uJIBAOGq9mSHf0gktF0duw==}
+ vfile-message@4.0.3:
+ resolution: {integrity: sha512-QTHzsGd1EhbZs4AsQ20JX1rC3cOlt/IWJruk893DfLRr57lcnOeMaWG4K0JrRta4mIJZKth2Au3mM3u03/JWKw==}
vfile@6.0.3:
resolution: {integrity: sha512-KzIbH/9tXat2u30jf+smMwFCsno4wHVdNmzFyL+T/L3UGqqk6JKfVqOFOZEpZSHADH1k40ab6NUIXZq422ov3Q==}
- vite-dev-rpc@1.1.0:
- resolution: {integrity: sha512-pKXZlgoXGoE8sEKiKJSng4hI1sQ4wi5YT24FCrwrLt6opmkjlqPPVmiPWWJn8M8byMxRGzp1CrFuqQs4M/Z39A==}
- peerDependencies:
- vite: ^2.9.0 || ^3.0.0-0 || ^4.0.0-0 || ^5.0.0-0 || ^6.0.1 || ^7.0.0-0
-
- vite-hot-client@2.1.0:
- resolution: {integrity: sha512-7SpgZmU7R+dDnSmvXE1mfDtnHLHQSisdySVR7lO8ceAXvM0otZeuQQ6C8LrS5d/aYyP/QZ0hI0L+dIPrm4YlFQ==}
- peerDependencies:
- vite: ^2.6.0 || ^3.0.0 || ^4.0.0 || ^5.0.0-0 || ^6.0.0-0 || ^7.0.0-0
-
- vite-plugin-inspect@0.8.9:
- resolution: {integrity: sha512-22/8qn+LYonzibb1VeFZmISdVao5kC22jmEKm24vfFE8siEn47EpVcCLYMv6iKOYMJfjSvSJfueOwcFCkUnV3A==}
- engines: {node: '>=14'}
- peerDependencies:
- '@nuxt/kit': '*'
- vite: ^3.1.0 || ^4.0.0 || ^5.0.0-0 || ^6.0.1
- peerDependenciesMeta:
- '@nuxt/kit':
- optional: true
-
- vite-plugin-vue-devtools@7.7.7:
- resolution: {integrity: sha512-d0fIh3wRcgSlr4Vz7bAk4va1MkdqhQgj9ANE/rBhsAjOnRfTLs2ocjFMvSUOsv6SRRXU9G+VM7yMgqDb6yI4iQ==}
- engines: {node: '>=v14.21.3'}
- peerDependencies:
- vite: ^3.1.0 || ^4.0.0-0 || ^5.0.0-0 || ^6.0.0-0 || ^7.0.0-0
-
- vite-plugin-vue-inspector@5.3.2:
- resolution: {integrity: sha512-YvEKooQcSiBTAs0DoYLfefNja9bLgkFM7NI2b07bE2SruuvX0MEa9cMaxjKVMkeCp5Nz9FRIdcN1rOdFVBeL6Q==}
- peerDependencies:
- vite: ^3.0.0-0 || ^4.0.0-0 || ^5.0.0-0 || ^6.0.0-0 || ^7.0.0-0
-
- vite-plugin-vue-layouts@0.11.0:
- resolution: {integrity: sha512-uh6NW7lt+aOXujK4eHfiNbeo55K9OTuB7fnv+5RVc4OBn/cZull6ThXdYH03JzKanUfgt6QZ37NbbtJ0og59qw==}
- peerDependencies:
- vite: ^4.0.0 || ^5.0.0
- vue: ^3.2.4
- vue-router: ^4.0.11
-
- vite-ssg-sitemap@0.9.0:
- resolution: {integrity: sha512-C5XCa+oPET2w/re92L9o7je4LMsKJDOC/TI6klo0xAi72nlgQKa7rt9cOYMZxgAsAJUhk+c6RYPTRc73xvn1vw==}
-
- vite-ssg@28.0.0:
- resolution: {integrity: sha512-idYdFXRi1XdiE4fd1g6n/NIpGn6KzMX4Lzrq2Ynr+j2FTd0UMuBlMJh6Z4kB6ux4lBonTOU2tTV2hhL/ubQ/1w==}
- engines: {node: '>=20.0.0'}
- hasBin: true
- peerDependencies:
- beasties: ^0.2.0
- prettier: ^3.3.0
- vite: ^2.0.0 || ^3.0.0 || ^4.0.0 || ^5.0.0-0 || ^6.0.0 || ^7.0.0-0
- vue: ^3.2.10
- vue-router: ^4.0.1
- peerDependenciesMeta:
- beasties:
- optional: true
- prettier:
- optional: true
- vue-router:
- optional: true
-
- vite@5.4.19:
- resolution: {integrity: sha512-qO3aKv3HoQC8QKiNSTuUM1l9o/XX3+c+VTgLHbJWHZGeTPVAg2XwazI9UWzoxjIJCGCV2zU60uqMzjeLZuULqA==}
+ vite@5.4.21:
+ resolution: {integrity: sha512-o5a9xKjbtuhY6Bi5S3+HvbRERmouabWbyUcpXXUA1u+GNUKoROi9byOJ8M0nHbHYHkYICiMlqxkg1KkYmm25Sw==}
engines: {node: ^18.0.0 || >=20.0.0}
hasBin: true
peerDependencies:
@@ -4028,94 +1975,16 @@ packages:
terser:
optional: true
- vite@6.3.5:
- resolution: {integrity: sha512-cZn6NDFE7wdTpINgs++ZJ4N49W2vRp8LCKrn3Ob1kYNtOo21vfDoaV5GzBfLU4MovSAB8uNRm4jgzVQZ+mBzPQ==}
- engines: {node: ^18.0.0 || ^20.0.0 || >=22.0.0}
- hasBin: true
- peerDependencies:
- '@types/node': ^18.0.0 || ^20.0.0 || >=22.0.0
- jiti: '>=1.21.0'
- less: '*'
- lightningcss: ^1.21.0
- sass: '*'
- sass-embedded: '*'
- stylus: '*'
- sugarss: '*'
- terser: ^5.16.0
- tsx: ^4.8.1
- yaml: ^2.4.2
- peerDependenciesMeta:
- '@types/node':
- optional: true
- jiti:
- optional: true
- less:
- optional: true
- lightningcss:
- optional: true
- sass:
- optional: true
- sass-embedded:
- optional: true
- stylus:
- optional: true
- sugarss:
- optional: true
- terser:
- optional: true
- tsx:
- optional: true
- yaml:
- optional: true
-
- vite@7.0.5:
- resolution: {integrity: sha512-1mncVwJxy2C9ThLwz0+2GKZyEXuC3MyWtAAlNftlZZXZDP3AJt5FmwcMit/IGGaNZ8ZOB2BNO/HFUB+CpN0NQw==}
- engines: {node: ^20.19.0 || >=22.12.0}
- hasBin: true
+ vitepress-plugin-group-icons@1.7.6:
+ resolution: {integrity: sha512-fXSpQAYHpFpEsZLKWQAwbRx/+0uRSHmY58YNAQcz0AVirGsM6w22jtSmQhOGLEj8ZKyeRtTJrpx6otUI6wvoaQ==}
peerDependencies:
- '@types/node': ^20.19.0 || >=22.12.0
- jiti: '>=1.21.0'
- less: ^4.0.0
- lightningcss: ^1.21.0
- sass: ^1.70.0
- sass-embedded: ^1.70.0
- stylus: '>=0.54.8'
- sugarss: ^5.0.0
- terser: ^5.16.0
- tsx: ^4.8.1
- yaml: ^2.4.2
+ vite: '>=3'
peerDependenciesMeta:
- '@types/node':
- optional: true
- jiti:
- optional: true
- less:
- optional: true
- lightningcss:
- optional: true
- sass:
- optional: true
- sass-embedded:
- optional: true
- stylus:
- optional: true
- sugarss:
- optional: true
- terser:
- optional: true
- tsx:
- optional: true
- yaml:
+ vite:
optional: true
- vitepress-plugin-group-icons@1.6.1:
- resolution: {integrity: sha512-eoFlFAhAy/yTZDbaIgA/nMbjVYXkf8pz8rr75MN2VCw7yH60I3cw6bW5EuwddAeafZtBqbo8OsEGU7TIWFiAjg==}
- peerDependencies:
- markdown-it: '>=14'
- vite: '>=3'
-
- vitepress@1.1.4:
- resolution: {integrity: sha512-bWIzFZXpPB6NIDBuWnS20aMADH+FcFKDfQNYFvbOWij03PR29eImTceQHIzCKordjXYBhM/TjE5VKFTUJ3EheA==}
+ vitepress@1.6.4:
+ resolution: {integrity: sha512-+2ym1/+0VVrbhNyRoFFesVvBvHAVMZMK0rw60E3X/5349M1GuVdKeazuksqopEdvkKwKGs21Q729jX81/bkBJg==}
hasBin: true
peerDependencies:
markdown-it-mathjax3: ^4
@@ -4126,101 +1995,29 @@ packages:
postcss:
optional: true
- vscode-jsonrpc@8.2.0:
- resolution: {integrity: sha512-C+r0eKJUIfiDIfwJhria30+TYWPtuHJXHtI7J0YlOmKAo7ogxP20T0zxB7HZQIFhIyvoBPwWskjxrvAtfjyZfA==}
- engines: {node: '>=14.0.0'}
-
- vscode-languageserver-protocol@3.17.5:
- resolution: {integrity: sha512-mb1bvRJN8SVznADSGWM9u/b07H7Ecg0I3OgXDuLdn307rl/J3A9YD6/eYOssqhecL27hK1IPZAsaqh00i/Jljg==}
-
- vscode-languageserver-textdocument@1.0.12:
- resolution: {integrity: sha512-cxWNPesCnQCcMPeenjKKsOCKQZ/L6Tv19DTRIGuLWe32lyzWhihGVJ/rcckZXJxfdKCFvRLS3fpBIsV/ZGX4zA==}
-
- vscode-languageserver-types@3.17.5:
- resolution: {integrity: sha512-Ld1VelNuX9pdF39h2Hgaeb5hEZM2Z3jUrrMgWQAu82jMtZp7p3vJT3BzToKtZI7NgQssZje5o0zryOrhQvzQAg==}
-
- vscode-languageserver@9.0.1:
- resolution: {integrity: sha512-woByF3PDpkHFUreUa7Hos7+pUWdeWMXRd26+ZX2A8cFx6v/JPTtd4/uN0/jB6XQHYaOlHbio03NTHCqrgG5n7g==}
- hasBin: true
-
- vscode-uri@3.0.8:
- resolution: {integrity: sha512-AyFQ0EVmsOZOlAnxoFOGOq1SQDWAB7C6aqMGS23svWAllfOaxbuFvcT8D1i8z3Gyn8fraVeZNNmN6e9bxxXkKw==}
-
- vscode-uri@3.1.0:
- resolution: {integrity: sha512-/BpdSx+yCQGnCvecbyXdxHDkuk55/G3xwnC0GqY4gmQ3j+A+g8kzzgB4Nk/SINjqn6+waqw3EgbVF2QKExkRxQ==}
-
- vue-demi@0.14.10:
- resolution: {integrity: sha512-nMZBOwuzabUO0nLgIcc6rycZEebF6eeUfaiQx9+WSk8e29IbLvPU9feI6tqW4kTo3hvoYAJkMh8n8D0fuISphg==}
- engines: {node: '>=12'}
- hasBin: true
- peerDependencies:
- '@vue/composition-api': ^1.0.0-rc.1
- vue: ^3.0.0-0 || ^2.6.0
- peerDependenciesMeta:
- '@vue/composition-api':
- optional: true
-
- vue-flow-layout@0.1.1:
- resolution: {integrity: sha512-JdgRRUVrN0Y2GosA0M68DEbKlXMqJ7FQgsK8CjQD2vxvNSqAU6PZEpi4cfcTVtfM2GVOMjHo7GKKLbXxOBqDqA==}
- peerDependencies:
- vue: ^3.4.37
-
- vue-i18n@11.1.10:
- resolution: {integrity: sha512-C+IwnSg8QDSOAox0gdFYP5tsKLx5jNWxiawNoiNB/Tw4CReXmM1VJMXbduhbrEzAFLhreqzfDocuSVjGbxQrag==}
- engines: {node: '>= 16'}
- peerDependencies:
- vue: ^3.0.0
-
- vue-resize@2.0.0-alpha.1:
- resolution: {integrity: sha512-7+iqOueLU7uc9NrMfrzbG8hwMqchfVfSzpVlCMeJQe4pyibqyoifDNbKTZvwxZKDvGkB+PdFeKvnGZMoEb8esg==}
- peerDependencies:
- vue: ^3.0.0
+ vscode-uri@3.2.0:
+ resolution: {integrity: sha512-m2gXo3bn0G1kT9InzMf07fTbqMbGtyckj3bH5ktLO+1Ssv+yiATZ4dhwaQv9UZWxJh6E9IFGnQyjgWVDWVBDrg==}
- vue-router@4.5.1:
- resolution: {integrity: sha512-ogAF3P97NPm8fJsE4by9dwSYtDwXIY1nFY9T6DyQnGHd1E2Da94w9JIolpe42LJGIl0DwOHBi8TcRPlPGwbTtw==}
+ vue-eslint-parser@10.4.1:
+ resolution: {integrity: sha512-Gk6gRDj0n/fkRa3C3l0bBheoBckUq/Rs0F/TvMWIS6nzzx67amAViMe9CkNgsP2tXyQONvGiHQESHwFtZ3aYDA==}
+ engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
peerDependencies:
- vue: ^3.2.0
+ eslint: ^8.57.0 || ^9.0.0 || ^10.0.0
- vue-tsc@2.2.12:
- resolution: {integrity: sha512-P7OP77b2h/Pmk+lZdJ0YWs+5tJ6J2+uOQPo7tlBnY44QqQSPYvS0qVT4wqDJgwrZaLe47etJLLQRFia71GYITw==}
+ vue-tsc@3.3.11:
+ resolution: {integrity: sha512-gOb0B9rtU2+f1dszwPqSH5kAieIF9ReeLhD3kSRNHv5WZZUQz/JdVXW0RTdqhNTMlQkqKzrTTviqKr/4FYZraQ==}
hasBin: true
peerDependencies:
typescript: '>=5.0.0'
- vue@3.5.17:
- resolution: {integrity: sha512-LbHV3xPN9BeljML+Xctq4lbz2lVHCR6DtbpTf5XIO6gugpXUN49j2QQPcMj086r9+AkJ0FfUT8xjulKKBkkr9g==}
+ vue@3.5.43:
+ resolution: {integrity: sha512-o5qZoksdnjIKvW1srZ3ab7pcDNYAerBjRe54D0LBLfRdCYFrSgBHVXokMas35czQc0//lmx4/tuY4ZNQ+Rf2Ng==}
peerDependencies:
typescript: '*'
peerDependenciesMeta:
typescript:
optional: true
- w3c-xmlserializer@5.0.0:
- resolution: {integrity: sha512-o8qghlI8NZHU1lLPrpi2+Uq7abh4GGPpYANlalzWxyWteJOCsr/P+oPBA49TOLu5FTZO4d3F9MnWJfiMo4BkmA==}
- engines: {node: '>=18'}
-
- webidl-conversions@7.0.0:
- resolution: {integrity: sha512-VwddBukDzu71offAQR975unBIGqfKZpM+8ZX6ySk8nYhVoo5CYaZyzt3YBvYtRtO+aoGlqxPg/B87NGVZ/fu6g==}
- engines: {node: '>=12'}
-
- webpack-virtual-modules@0.6.2:
- resolution: {integrity: sha512-66/V2i5hQanC51vBQKPH4aI8NMAcBW59FVBs+rC7eGHupMyfn34q7rZIE+ETlJ+XTevqfUhVVBgSUNSW2flEUQ==}
-
- whatwg-encoding@3.1.1:
- resolution: {integrity: sha512-6qN4hJdMwfYBtE3YBTTHhoeuUrDBPZmbQaxWAqSALV/MeEnR5z1xd8UKud2RAkFoPkmB+hli1TZSnyi84xz1vQ==}
- engines: {node: '>=18'}
-
- whatwg-mimetype@4.0.0:
- resolution: {integrity: sha512-QaKxh0eNIi2mE9p2vEdzfagOKHCcj1pJ56EEHGQOVxp8r9/iszLUUV7v89x9O1p/T+NlTM5W7jW6+cz4Fq1YVg==}
- engines: {node: '>=18'}
-
- whatwg-url@14.2.0:
- resolution: {integrity: sha512-De72GdQZzNTUBBChsXueQUnPKDkg/5A5zp7pFDuQAj5UFoENpiACU0wlCvzpAGnTkj++ihpKwKyYewn/XNUbKw==}
- engines: {node: '>=18'}
-
- which-module@2.0.1:
- resolution: {integrity: sha512-iBdZ57RDvnOR9AGBhML2vFZf7h8vmBjhoaZqODJBFWHVtKkDmKuHai3cx5PgVMrX5YDNp27AofYbAwctSS+vhQ==}
-
which@2.0.2:
resolution: {integrity: sha512-BLI3Tl1TW3Pvl70l3yq3Y64i+awpwXqsGBYWkkqMtnbXgrMD+yj7rhW0kuEDxzJaYXGjEW5ogapKNMEKNMjibA==}
engines: {node: '>= 8'}
@@ -4230,474 +2027,205 @@ packages:
resolution: {integrity: sha512-BN22B5eaMMI9UMtjrGd5g5eCYPpCPDUy0FJXbYsaT5zYxjFOckS53SQDE3pWkVoWpHXVb3BrYcEN4Twa55B5cA==}
engines: {node: '>=0.10.0'}
- wrap-ansi@6.2.0:
- resolution: {integrity: sha512-r6lPcBGxZXlIcymEu7InxDMhdW0KDxpLgoFLcguasxCaJ/SOIZwINatK9KY/tf+ZrlywOKU0UDj3ATXUBfxJXA==}
- engines: {node: '>=8'}
-
- wrap-ansi@9.0.0:
- resolution: {integrity: sha512-G8ura3S+3Z2G+mkgNRq8dqaFZAuxfsxpBB8OCTGRTCtp+l/v9nbFNmCUP1BZMts3G1142MsZfn6eeUKrr4PD1Q==}
- engines: {node: '>=18'}
-
- ws@8.18.3:
- resolution: {integrity: sha512-PEIGCY5tSlUt50cqyMXfCzX+oOPqN0vuGqWzbcJ2xvnkzkq46oOpz7dQaTDBdfICb4N14+GARUDw2XV2N4tvzg==}
- engines: {node: '>=10.0.0'}
- peerDependencies:
- bufferutil: ^4.0.1
- utf-8-validate: '>=5.0.2'
- peerDependenciesMeta:
- bufferutil:
- optional: true
- utf-8-validate:
- optional: true
-
- xml-js@1.6.11:
- resolution: {integrity: sha512-7rVi2KMfwfWFl+GpPg6m80IVMWXLRjO+PxTq7V2CDhoGak0wzYzFgUY2m4XJ47OGdXd8eLE8EmwfAmdjw7lC1g==}
- hasBin: true
-
xml-name-validator@5.0.0:
resolution: {integrity: sha512-EvGK8EJ3DhaHfbRlETOWAS5pO9MZITeauHKJyb8wyajUfQUenkIg2MvLDTZ4T/TgIcm3HU0TFBgWWboAZ30UHg==}
engines: {node: '>=18'}
- xmlchars@2.2.0:
- resolution: {integrity: sha512-JZnDKK8B0RCDw84FNdDAIpZK+JuJw+s7Lz8nksI7SIuU3UXJJslUthsi+uWBUYOwPFwW7W7PRLRfUKpxjtjFCw==}
-
- y18n@4.0.3:
- resolution: {integrity: sha512-JKhqTOwSrqNA1NY5lSztJ1GrBiUodLMmIZuLiDaMRJ+itFd+ABVE8XBjOvIWL+rSqNDC74LCSFmlb/U4UZ4hJQ==}
-
- y18n@5.0.8:
- resolution: {integrity: sha512-0pfFzegeDWJHJIAmTLRP2DwHjdF5s7jo9tuztdQxAhINCdvS+3nGINqPd00AphqJR/0LhANUS6/+7SCb98YOfA==}
- engines: {node: '>=10'}
-
- yallist@3.1.1:
- resolution: {integrity: sha512-a4UGQaWPH59mOXUYnAG2ewncQS4i4F43Tv3JoAM+s2VDAmS9NsK8GpDMLrCHPksFT7h3K6TOoUNn2pb7RoXx4g==}
-
- yaml-eslint-parser@1.3.0:
- resolution: {integrity: sha512-E/+VitOorXSLiAqtTd7Yqax0/pAS3xaYMP+AUUJGOK1OZG3rhcj9fcJOM5HJ2VrP1FrStVCWr1muTfQCdj4tAA==}
- engines: {node: ^14.17.0 || >=16.0.0}
-
- yaml@2.8.0:
- resolution: {integrity: sha512-4lLa/EcQCB0cJkyts+FpIRx5G/llPxfP6VQU5KByHEhLxY3IJCH0f0Hy1MHI8sClTvsIb8qwRJ6R/ZdlDJ/leQ==}
+ yaml@2.9.1:
+ resolution: {integrity: sha512-3NxN8+78OdzbT7C/WjGsyfPAtJaN3FNDsWxv7Y7mcDsT/oOmgW8BpyQQFFBnvZE3j9Y2Sdz1ULFLezL7Eb2yFw==}
engines: {node: '>= 14.6'}
hasBin: true
- yargs-parser@18.1.3:
- resolution: {integrity: sha512-o50j0JeToy/4K6OZcaQmW6lyXXKhq7csREXcDwk2omFPJEwUNOVtJKvmDr9EI1fAJZUyZcRF7kxGBWmRXudrCQ==}
- engines: {node: '>=6'}
-
- yargs-parser@22.0.0:
- resolution: {integrity: sha512-rwu/ClNdSMpkSrUb+d6BRsSkLUq1fmfsY6TOpYzTwvwkg1/NRG85KBy3kq++A8LKQwX6lsu+aWad+2khvuXrqw==}
- engines: {node: ^20.19.0 || ^22.12.0 || >=23}
-
- yargs@15.4.1:
- resolution: {integrity: sha512-aePbxDmcYW++PaqBsJ+HYUFwCdv4LVvdnhBy78E57PIor8/OVvhMrADFFEDh8DHDFRv/O9i3lPhsENjO7QX0+A==}
- engines: {node: '>=8'}
-
- yargs@18.0.0:
- resolution: {integrity: sha512-4UEqdc2RYGHZc7Doyqkrqiln3p9X2DZVxaGbwhn2pi7MrRagKaOcIKe8L3OxYcbhXLgLFUS3zAYuQjKBQgmuNg==}
- engines: {node: ^20.19.0 || ^22.12.0 || >=23}
-
yocto-queue@0.1.0:
resolution: {integrity: sha512-rVksvsnNCdJ/ohGc6xgPwyN8eheCxsiLM8mxuE/t/mOVqJewPuO1miLpTHQiRgTKCLexL4MeAFVagts7HmNZ2Q==}
engines: {node: '>=10'}
- yoctocolors@2.1.1:
- resolution: {integrity: sha512-GQHQqAopRhwU8Kt1DDM8NjibDXHC8eoh1erhGAJPEyveY9qqVeXvVikNKrDz69sHowPMorbPUrH/mx8c50eiBQ==}
- engines: {node: '>=18'}
-
zwitch@2.0.4:
resolution: {integrity: sha512-bXE4cR/kVZhKZX/RjPEflHaKVhUVl85noU3v6b8apfQEc1x4A+zBxjZ4lN8LqGd6WZ3dl98pY4o717VFmoPp+A==}
snapshots:
- '@algolia/autocomplete-core@1.17.9(@algolia/client-search@5.34.0)(algoliasearch@5.34.0)(search-insights@2.17.3)':
+ '@algolia/abtesting@1.25.0':
+ dependencies:
+ '@algolia/client-common': 5.59.0
+ '@algolia/requester-browser-xhr': 5.59.0
+ '@algolia/requester-fetch': 5.59.0
+ '@algolia/requester-node-http': 5.59.0
+
+ '@algolia/autocomplete-core@1.17.7(@algolia/client-search@5.59.0)(algoliasearch@5.59.0)(search-insights@2.17.3)':
dependencies:
- '@algolia/autocomplete-plugin-algolia-insights': 1.17.9(@algolia/client-search@5.34.0)(algoliasearch@5.34.0)(search-insights@2.17.3)
- '@algolia/autocomplete-shared': 1.17.9(@algolia/client-search@5.34.0)(algoliasearch@5.34.0)
+ '@algolia/autocomplete-plugin-algolia-insights': 1.17.7(@algolia/client-search@5.59.0)(algoliasearch@5.59.0)(search-insights@2.17.3)
+ '@algolia/autocomplete-shared': 1.17.7(@algolia/client-search@5.59.0)(algoliasearch@5.59.0)
transitivePeerDependencies:
- '@algolia/client-search'
- algoliasearch
- search-insights
- '@algolia/autocomplete-plugin-algolia-insights@1.17.9(@algolia/client-search@5.34.0)(algoliasearch@5.34.0)(search-insights@2.17.3)':
+ '@algolia/autocomplete-plugin-algolia-insights@1.17.7(@algolia/client-search@5.59.0)(algoliasearch@5.59.0)(search-insights@2.17.3)':
dependencies:
- '@algolia/autocomplete-shared': 1.17.9(@algolia/client-search@5.34.0)(algoliasearch@5.34.0)
+ '@algolia/autocomplete-shared': 1.17.7(@algolia/client-search@5.59.0)(algoliasearch@5.59.0)
search-insights: 2.17.3
transitivePeerDependencies:
- '@algolia/client-search'
- algoliasearch
- '@algolia/autocomplete-preset-algolia@1.17.9(@algolia/client-search@5.34.0)(algoliasearch@5.34.0)':
- dependencies:
- '@algolia/autocomplete-shared': 1.17.9(@algolia/client-search@5.34.0)(algoliasearch@5.34.0)
- '@algolia/client-search': 5.34.0
- algoliasearch: 5.34.0
-
- '@algolia/autocomplete-shared@1.17.9(@algolia/client-search@5.34.0)(algoliasearch@5.34.0)':
- dependencies:
- '@algolia/client-search': 5.34.0
- algoliasearch: 5.34.0
-
- '@algolia/client-abtesting@5.34.0':
- dependencies:
- '@algolia/client-common': 5.34.0
- '@algolia/requester-browser-xhr': 5.34.0
- '@algolia/requester-fetch': 5.34.0
- '@algolia/requester-node-http': 5.34.0
-
- '@algolia/client-analytics@5.34.0':
- dependencies:
- '@algolia/client-common': 5.34.0
- '@algolia/requester-browser-xhr': 5.34.0
- '@algolia/requester-fetch': 5.34.0
- '@algolia/requester-node-http': 5.34.0
-
- '@algolia/client-common@5.34.0': {}
-
- '@algolia/client-insights@5.34.0':
- dependencies:
- '@algolia/client-common': 5.34.0
- '@algolia/requester-browser-xhr': 5.34.0
- '@algolia/requester-fetch': 5.34.0
- '@algolia/requester-node-http': 5.34.0
-
- '@algolia/client-personalization@5.34.0':
- dependencies:
- '@algolia/client-common': 5.34.0
- '@algolia/requester-browser-xhr': 5.34.0
- '@algolia/requester-fetch': 5.34.0
- '@algolia/requester-node-http': 5.34.0
-
- '@algolia/client-query-suggestions@5.34.0':
- dependencies:
- '@algolia/client-common': 5.34.0
- '@algolia/requester-browser-xhr': 5.34.0
- '@algolia/requester-fetch': 5.34.0
- '@algolia/requester-node-http': 5.34.0
-
- '@algolia/client-search@5.34.0':
- dependencies:
- '@algolia/client-common': 5.34.0
- '@algolia/requester-browser-xhr': 5.34.0
- '@algolia/requester-fetch': 5.34.0
- '@algolia/requester-node-http': 5.34.0
-
- '@algolia/ingestion@1.34.0':
- dependencies:
- '@algolia/client-common': 5.34.0
- '@algolia/requester-browser-xhr': 5.34.0
- '@algolia/requester-fetch': 5.34.0
- '@algolia/requester-node-http': 5.34.0
-
- '@algolia/monitoring@1.34.0':
- dependencies:
- '@algolia/client-common': 5.34.0
- '@algolia/requester-browser-xhr': 5.34.0
- '@algolia/requester-fetch': 5.34.0
- '@algolia/requester-node-http': 5.34.0
-
- '@algolia/recommend@5.34.0':
- dependencies:
- '@algolia/client-common': 5.34.0
- '@algolia/requester-browser-xhr': 5.34.0
- '@algolia/requester-fetch': 5.34.0
- '@algolia/requester-node-http': 5.34.0
-
- '@algolia/requester-browser-xhr@5.34.0':
- dependencies:
- '@algolia/client-common': 5.34.0
-
- '@algolia/requester-fetch@5.34.0':
- dependencies:
- '@algolia/client-common': 5.34.0
-
- '@algolia/requester-node-http@5.34.0':
- dependencies:
- '@algolia/client-common': 5.34.0
-
- '@ampproject/remapping@2.3.0':
- dependencies:
- '@jridgewell/gen-mapping': 0.3.12
- '@jridgewell/trace-mapping': 0.3.29
-
- '@antfu/install-pkg@1.1.0':
- dependencies:
- package-manager-detector: 1.3.0
- tinyexec: 1.0.1
-
- '@antfu/utils@0.7.10': {}
-
- '@antfu/utils@8.1.1': {}
-
- '@antfu/utils@9.2.0': {}
-
- '@asamuzakjp/css-color@3.2.0':
- dependencies:
- '@csstools/css-calc': 2.1.4(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
- '@csstools/css-color-parser': 3.0.10(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
- '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
- '@csstools/css-tokenizer': 3.0.4
- lru-cache: 10.4.3
-
- '@babel/code-frame@7.27.1':
- dependencies:
- '@babel/helper-validator-identifier': 7.27.1
- js-tokens: 4.0.0
- picocolors: 1.1.1
-
- '@babel/compat-data@7.28.0': {}
-
- '@babel/core@7.28.0':
- dependencies:
- '@ampproject/remapping': 2.3.0
- '@babel/code-frame': 7.27.1
- '@babel/generator': 7.28.0
- '@babel/helper-compilation-targets': 7.27.2
- '@babel/helper-module-transforms': 7.27.3(@babel/core@7.28.0)
- '@babel/helpers': 7.27.6
- '@babel/parser': 7.28.0
- '@babel/template': 7.27.2
- '@babel/traverse': 7.28.0
- '@babel/types': 7.28.1
- convert-source-map: 2.0.0
- debug: 4.4.1(supports-color@5.5.0)
- gensync: 1.0.0-beta.2
- json5: 2.2.3
- semver: 6.3.1
- transitivePeerDependencies:
- - supports-color
-
- '@babel/generator@7.28.0':
- dependencies:
- '@babel/parser': 7.28.0
- '@babel/types': 7.28.1
- '@jridgewell/gen-mapping': 0.3.12
- '@jridgewell/trace-mapping': 0.3.29
- jsesc: 3.1.0
-
- '@babel/helper-annotate-as-pure@7.27.3':
- dependencies:
- '@babel/types': 7.28.1
-
- '@babel/helper-compilation-targets@7.27.2':
+ '@algolia/autocomplete-preset-algolia@1.17.7(@algolia/client-search@5.59.0)(algoliasearch@5.59.0)':
dependencies:
- '@babel/compat-data': 7.28.0
- '@babel/helper-validator-option': 7.27.1
- browserslist: 4.25.1
- lru-cache: 5.1.1
- semver: 6.3.1
+ '@algolia/autocomplete-shared': 1.17.7(@algolia/client-search@5.59.0)(algoliasearch@5.59.0)
+ '@algolia/client-search': 5.59.0
+ algoliasearch: 5.59.0
- '@babel/helper-create-class-features-plugin@7.27.1(@babel/core@7.28.0)':
+ '@algolia/autocomplete-shared@1.17.7(@algolia/client-search@5.59.0)(algoliasearch@5.59.0)':
dependencies:
- '@babel/core': 7.28.0
- '@babel/helper-annotate-as-pure': 7.27.3
- '@babel/helper-member-expression-to-functions': 7.27.1
- '@babel/helper-optimise-call-expression': 7.27.1
- '@babel/helper-replace-supers': 7.27.1(@babel/core@7.28.0)
- '@babel/helper-skip-transparent-expression-wrappers': 7.27.1
- '@babel/traverse': 7.28.0
- semver: 6.3.1
- transitivePeerDependencies:
- - supports-color
-
- '@babel/helper-globals@7.28.0': {}
+ '@algolia/client-search': 5.59.0
+ algoliasearch: 5.59.0
- '@babel/helper-member-expression-to-functions@7.27.1':
+ '@algolia/client-abtesting@5.59.0':
dependencies:
- '@babel/traverse': 7.28.0
- '@babel/types': 7.28.1
- transitivePeerDependencies:
- - supports-color
+ '@algolia/client-common': 5.59.0
+ '@algolia/requester-browser-xhr': 5.59.0
+ '@algolia/requester-fetch': 5.59.0
+ '@algolia/requester-node-http': 5.59.0
- '@babel/helper-module-imports@7.27.1':
+ '@algolia/client-analytics@5.59.0':
dependencies:
- '@babel/traverse': 7.28.0
- '@babel/types': 7.28.1
- transitivePeerDependencies:
- - supports-color
+ '@algolia/client-common': 5.59.0
+ '@algolia/requester-browser-xhr': 5.59.0
+ '@algolia/requester-fetch': 5.59.0
+ '@algolia/requester-node-http': 5.59.0
- '@babel/helper-module-transforms@7.27.3(@babel/core@7.28.0)':
- dependencies:
- '@babel/core': 7.28.0
- '@babel/helper-module-imports': 7.27.1
- '@babel/helper-validator-identifier': 7.27.1
- '@babel/traverse': 7.28.0
- transitivePeerDependencies:
- - supports-color
+ '@algolia/client-common@5.59.0': {}
- '@babel/helper-optimise-call-expression@7.27.1':
+ '@algolia/client-insights@5.59.0':
dependencies:
- '@babel/types': 7.28.1
-
- '@babel/helper-plugin-utils@7.27.1': {}
+ '@algolia/client-common': 5.59.0
+ '@algolia/requester-browser-xhr': 5.59.0
+ '@algolia/requester-fetch': 5.59.0
+ '@algolia/requester-node-http': 5.59.0
- '@babel/helper-replace-supers@7.27.1(@babel/core@7.28.0)':
+ '@algolia/client-personalization@5.59.0':
dependencies:
- '@babel/core': 7.28.0
- '@babel/helper-member-expression-to-functions': 7.27.1
- '@babel/helper-optimise-call-expression': 7.27.1
- '@babel/traverse': 7.28.0
- transitivePeerDependencies:
- - supports-color
+ '@algolia/client-common': 5.59.0
+ '@algolia/requester-browser-xhr': 5.59.0
+ '@algolia/requester-fetch': 5.59.0
+ '@algolia/requester-node-http': 5.59.0
- '@babel/helper-skip-transparent-expression-wrappers@7.27.1':
+ '@algolia/client-query-suggestions@5.59.0':
dependencies:
- '@babel/traverse': 7.28.0
- '@babel/types': 7.28.1
- transitivePeerDependencies:
- - supports-color
+ '@algolia/client-common': 5.59.0
+ '@algolia/requester-browser-xhr': 5.59.0
+ '@algolia/requester-fetch': 5.59.0
+ '@algolia/requester-node-http': 5.59.0
- '@babel/helper-string-parser@7.27.1': {}
-
- '@babel/helper-validator-identifier@7.27.1': {}
-
- '@babel/helper-validator-option@7.27.1': {}
-
- '@babel/helpers@7.27.6':
+ '@algolia/client-search@5.59.0':
dependencies:
- '@babel/template': 7.27.2
- '@babel/types': 7.28.1
+ '@algolia/client-common': 5.59.0
+ '@algolia/requester-browser-xhr': 5.59.0
+ '@algolia/requester-fetch': 5.59.0
+ '@algolia/requester-node-http': 5.59.0
- '@babel/parser@7.28.0':
+ '@algolia/ingestion@1.59.0':
dependencies:
- '@babel/types': 7.28.1
+ '@algolia/client-common': 5.59.0
+ '@algolia/requester-browser-xhr': 5.59.0
+ '@algolia/requester-fetch': 5.59.0
+ '@algolia/requester-node-http': 5.59.0
- '@babel/plugin-proposal-decorators@7.28.0(@babel/core@7.28.0)':
+ '@algolia/monitoring@1.59.0':
dependencies:
- '@babel/core': 7.28.0
- '@babel/helper-create-class-features-plugin': 7.27.1(@babel/core@7.28.0)
- '@babel/helper-plugin-utils': 7.27.1
- '@babel/plugin-syntax-decorators': 7.27.1(@babel/core@7.28.0)
- transitivePeerDependencies:
- - supports-color
+ '@algolia/client-common': 5.59.0
+ '@algolia/requester-browser-xhr': 5.59.0
+ '@algolia/requester-fetch': 5.59.0
+ '@algolia/requester-node-http': 5.59.0
- '@babel/plugin-syntax-decorators@7.27.1(@babel/core@7.28.0)':
+ '@algolia/recommend@5.59.0':
dependencies:
- '@babel/core': 7.28.0
- '@babel/helper-plugin-utils': 7.27.1
+ '@algolia/client-common': 5.59.0
+ '@algolia/requester-browser-xhr': 5.59.0
+ '@algolia/requester-fetch': 5.59.0
+ '@algolia/requester-node-http': 5.59.0
- '@babel/plugin-syntax-import-attributes@7.27.1(@babel/core@7.28.0)':
+ '@algolia/requester-browser-xhr@5.59.0':
dependencies:
- '@babel/core': 7.28.0
- '@babel/helper-plugin-utils': 7.27.1
+ '@algolia/client-common': 5.59.0
- '@babel/plugin-syntax-import-meta@7.10.4(@babel/core@7.28.0)':
+ '@algolia/requester-fetch@5.59.0':
dependencies:
- '@babel/core': 7.28.0
- '@babel/helper-plugin-utils': 7.27.1
+ '@algolia/client-common': 5.59.0
- '@babel/plugin-syntax-jsx@7.27.1(@babel/core@7.28.0)':
+ '@algolia/requester-node-http@5.59.0':
dependencies:
- '@babel/core': 7.28.0
- '@babel/helper-plugin-utils': 7.27.1
+ '@algolia/client-common': 5.59.0
- '@babel/plugin-syntax-typescript@7.27.1(@babel/core@7.28.0)':
+ '@antfu/install-pkg@2.1.0':
dependencies:
- '@babel/core': 7.28.0
- '@babel/helper-plugin-utils': 7.27.1
+ package-manager-detector: 1.8.0
+ tinyexec: 1.3.1
- '@babel/plugin-transform-typescript@7.28.0(@babel/core@7.28.0)':
- dependencies:
- '@babel/core': 7.28.0
- '@babel/helper-annotate-as-pure': 7.27.3
- '@babel/helper-create-class-features-plugin': 7.27.1(@babel/core@7.28.0)
- '@babel/helper-plugin-utils': 7.27.1
- '@babel/helper-skip-transparent-expression-wrappers': 7.27.1
- '@babel/plugin-syntax-typescript': 7.27.1(@babel/core@7.28.0)
- transitivePeerDependencies:
- - supports-color
+ '@babel/helper-string-parser@7.29.7': {}
- '@babel/template@7.27.2':
- dependencies:
- '@babel/code-frame': 7.27.1
- '@babel/parser': 7.28.0
- '@babel/types': 7.28.1
+ '@babel/helper-validator-identifier@7.29.7': {}
- '@babel/traverse@7.28.0':
+ '@babel/parser@7.29.9':
dependencies:
- '@babel/code-frame': 7.27.1
- '@babel/generator': 7.28.0
- '@babel/helper-globals': 7.28.0
- '@babel/parser': 7.28.0
- '@babel/template': 7.27.2
- '@babel/types': 7.28.1
- debug: 4.4.1(supports-color@5.5.0)
- transitivePeerDependencies:
- - supports-color
+ '@babel/types': 7.29.8
- '@babel/types@7.28.1':
+ '@babel/types@7.29.8':
dependencies:
- '@babel/helper-string-parser': 7.27.1
- '@babel/helper-validator-identifier': 7.27.1
-
- '@braintree/sanitize-url@7.1.1': {}
+ '@babel/helper-string-parser': 7.29.7
+ '@babel/helper-validator-identifier': 7.29.7
- '@chevrotain/cst-dts-gen@11.0.3':
- dependencies:
- '@chevrotain/gast': 11.0.3
- '@chevrotain/types': 11.0.3
- lodash-es: 4.17.21
+ '@braintree/sanitize-url@7.1.2': {}
- '@chevrotain/gast@11.0.3':
+ '@cacheable/memory@2.2.0':
dependencies:
- '@chevrotain/types': 11.0.3
- lodash-es: 4.17.21
-
- '@chevrotain/regexp-to-ast@11.0.3': {}
-
- '@chevrotain/types@11.0.3': {}
-
- '@chevrotain/utils@11.0.3': {}
+ '@cacheable/utils': 2.5.0
+ '@keyv/bigmap': 1.3.1(keyv@5.6.0)
+ hookified: 1.15.1
+ keyv: 5.6.0
- '@clack/core@0.5.0':
+ '@cacheable/utils@2.5.0':
dependencies:
- picocolors: 1.1.1
- sisteransi: 1.0.5
+ hashery: 1.5.1
+ keyv: 5.6.0
- '@clack/prompts@0.11.0':
+ '@chevrotain/cst-dts-gen@11.1.2':
dependencies:
- '@clack/core': 0.5.0
- picocolors: 1.1.1
- sisteransi: 1.0.5
+ '@chevrotain/gast': 11.1.2
+ '@chevrotain/types': 11.1.2
+ lodash-es: 4.17.23
- '@csstools/color-helpers@5.0.2': {}
-
- '@csstools/css-calc@2.1.4(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)':
+ '@chevrotain/gast@11.1.2':
dependencies:
- '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
- '@csstools/css-tokenizer': 3.0.4
+ '@chevrotain/types': 11.1.2
+ lodash-es: 4.17.23
- '@csstools/css-color-parser@3.0.10(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)':
- dependencies:
- '@csstools/color-helpers': 5.0.2
- '@csstools/css-calc': 2.1.4(@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4))(@csstools/css-tokenizer@3.0.4)
- '@csstools/css-parser-algorithms': 3.0.5(@csstools/css-tokenizer@3.0.4)
- '@csstools/css-tokenizer': 3.0.4
+ '@chevrotain/regexp-to-ast@11.1.2': {}
- '@csstools/css-parser-algorithms@3.0.5(@csstools/css-tokenizer@3.0.4)':
- dependencies:
- '@csstools/css-tokenizer': 3.0.4
+ '@chevrotain/types@11.1.2': {}
- '@csstools/css-tokenizer@3.0.4': {}
+ '@chevrotain/utils@11.1.2': {}
- '@docsearch/css@3.9.0': {}
+ '@docsearch/css@3.8.2': {}
- '@docsearch/js@3.9.0(@algolia/client-search@5.34.0)(search-insights@2.17.3)':
+ '@docsearch/js@3.8.2(@algolia/client-search@5.59.0)(search-insights@2.17.3)':
dependencies:
- '@docsearch/react': 3.9.0(@algolia/client-search@5.34.0)(search-insights@2.17.3)
- preact: 10.26.9
+ '@docsearch/react': 3.8.2(@algolia/client-search@5.59.0)(search-insights@2.17.3)
+ preact: 10.29.8
transitivePeerDependencies:
- '@algolia/client-search'
- '@types/react'
+ - preact-render-to-string
- react
- react-dom
- search-insights
- '@docsearch/react@3.9.0(@algolia/client-search@5.34.0)(search-insights@2.17.3)':
+ '@docsearch/react@3.8.2(@algolia/client-search@5.59.0)(search-insights@2.17.3)':
dependencies:
- '@algolia/autocomplete-core': 1.17.9(@algolia/client-search@5.34.0)(algoliasearch@5.34.0)(search-insights@2.17.3)
- '@algolia/autocomplete-preset-algolia': 1.17.9(@algolia/client-search@5.34.0)(algoliasearch@5.34.0)
- '@docsearch/css': 3.9.0
- algoliasearch: 5.34.0
+ '@algolia/autocomplete-core': 1.17.7(@algolia/client-search@5.59.0)(algoliasearch@5.59.0)(search-insights@2.17.3)
+ '@algolia/autocomplete-preset-algolia': 1.17.7(@algolia/client-search@5.59.0)(algoliasearch@5.59.0)
+ '@docsearch/css': 3.8.2
+ algoliasearch: 5.59.0
optionalDependencies:
search-insights: 2.17.3
transitivePeerDependencies:
@@ -4706,693 +2234,294 @@ snapshots:
'@esbuild/aix-ppc64@0.21.5':
optional: true
- '@esbuild/aix-ppc64@0.25.8':
- optional: true
-
'@esbuild/android-arm64@0.21.5':
optional: true
- '@esbuild/android-arm64@0.25.8':
- optional: true
-
'@esbuild/android-arm@0.21.5':
optional: true
- '@esbuild/android-arm@0.25.8':
- optional: true
-
'@esbuild/android-x64@0.21.5':
optional: true
- '@esbuild/android-x64@0.25.8':
- optional: true
-
'@esbuild/darwin-arm64@0.21.5':
optional: true
- '@esbuild/darwin-arm64@0.25.8':
- optional: true
-
'@esbuild/darwin-x64@0.21.5':
optional: true
- '@esbuild/darwin-x64@0.25.8':
- optional: true
-
'@esbuild/freebsd-arm64@0.21.5':
optional: true
- '@esbuild/freebsd-arm64@0.25.8':
- optional: true
-
'@esbuild/freebsd-x64@0.21.5':
optional: true
- '@esbuild/freebsd-x64@0.25.8':
- optional: true
-
'@esbuild/linux-arm64@0.21.5':
optional: true
- '@esbuild/linux-arm64@0.25.8':
- optional: true
-
'@esbuild/linux-arm@0.21.5':
optional: true
- '@esbuild/linux-arm@0.25.8':
- optional: true
-
'@esbuild/linux-ia32@0.21.5':
optional: true
- '@esbuild/linux-ia32@0.25.8':
- optional: true
-
'@esbuild/linux-loong64@0.21.5':
optional: true
- '@esbuild/linux-loong64@0.25.8':
- optional: true
-
'@esbuild/linux-mips64el@0.21.5':
optional: true
- '@esbuild/linux-mips64el@0.25.8':
- optional: true
-
'@esbuild/linux-ppc64@0.21.5':
optional: true
- '@esbuild/linux-ppc64@0.25.8':
- optional: true
-
'@esbuild/linux-riscv64@0.21.5':
optional: true
- '@esbuild/linux-riscv64@0.25.8':
- optional: true
-
'@esbuild/linux-s390x@0.21.5':
optional: true
- '@esbuild/linux-s390x@0.25.8':
- optional: true
-
'@esbuild/linux-x64@0.21.5':
optional: true
- '@esbuild/linux-x64@0.25.8':
- optional: true
-
- '@esbuild/netbsd-arm64@0.25.8':
- optional: true
-
'@esbuild/netbsd-x64@0.21.5':
optional: true
- '@esbuild/netbsd-x64@0.25.8':
- optional: true
-
- '@esbuild/openbsd-arm64@0.25.8':
- optional: true
-
'@esbuild/openbsd-x64@0.21.5':
optional: true
- '@esbuild/openbsd-x64@0.25.8':
- optional: true
-
- '@esbuild/openharmony-arm64@0.25.8':
- optional: true
-
'@esbuild/sunos-x64@0.21.5':
optional: true
- '@esbuild/sunos-x64@0.25.8':
- optional: true
-
'@esbuild/win32-arm64@0.21.5':
optional: true
- '@esbuild/win32-arm64@0.25.8':
- optional: true
-
'@esbuild/win32-ia32@0.21.5':
optional: true
- '@esbuild/win32-ia32@0.25.8':
- optional: true
-
'@esbuild/win32-x64@0.21.5':
optional: true
- '@esbuild/win32-x64@0.25.8':
- optional: true
-
- '@eslint-community/eslint-utils@4.7.0(eslint@9.29.0(jiti@2.4.2))':
+ '@eslint-community/eslint-utils@4.10.1(eslint@10.11.0)':
dependencies:
- eslint: 9.29.0(jiti@2.4.2)
+ eslint: 10.11.0
eslint-visitor-keys: 3.4.3
- '@eslint-community/regexpp@4.12.1': {}
+ '@eslint-community/regexpp@4.12.2': {}
- '@eslint/config-array@0.20.1':
+ '@eslint/config-array@0.23.5':
dependencies:
- '@eslint/object-schema': 2.1.6
- debug: 4.4.1(supports-color@5.5.0)
- minimatch: 3.1.2
+ '@eslint/object-schema': 3.0.5
+ debug: 4.4.3
+ minimatch: 10.2.6
transitivePeerDependencies:
- supports-color
- '@eslint/config-helpers@0.2.3': {}
-
- '@eslint/core@0.14.0':
+ '@eslint/config-helpers@0.7.0':
dependencies:
- '@types/json-schema': 7.0.15
+ '@eslint/core': 1.2.1
- '@eslint/core@0.15.1':
+ '@eslint/core@1.2.1':
dependencies:
'@types/json-schema': 7.0.15
- '@eslint/eslintrc@3.3.1':
- dependencies:
- ajv: 6.12.6
- debug: 4.4.1(supports-color@5.5.0)
- espree: 10.4.0
- globals: 14.0.0
- ignore: 5.3.2
- import-fresh: 3.3.1
- js-yaml: 4.1.0
- minimatch: 3.1.2
- strip-json-comments: 3.1.1
- transitivePeerDependencies:
- - supports-color
-
- '@eslint/js@9.29.0': {}
+ '@eslint/js@10.0.1(eslint@10.11.0)':
+ optionalDependencies:
+ eslint: 10.11.0
- '@eslint/object-schema@2.1.6': {}
+ '@eslint/object-schema@3.0.5': {}
- '@eslint/plugin-kit@0.3.3':
+ '@eslint/plugin-kit@0.7.3':
dependencies:
- '@eslint/core': 0.15.1
+ '@eslint/core': 1.2.1
levn: 0.4.1
- '@floating-ui/core@1.7.2':
+ '@giscus/vue@3.1.1(vue@3.5.43(typescript@6.0.3))':
dependencies:
- '@floating-ui/utils': 0.2.10
+ giscus: 1.6.0
+ vue: 3.5.43(typescript@6.0.3)
- '@floating-ui/dom@1.1.1':
+ '@humanfs/core@0.19.2':
dependencies:
- '@floating-ui/core': 1.7.2
+ '@humanfs/types': 0.15.0
- '@floating-ui/utils@0.2.10': {}
-
- '@giscus/vue@3.1.1(vue@3.5.17(typescript@5.8.3))':
+ '@humanfs/node@0.16.8':
dependencies:
- giscus: 1.6.0
- vue: 3.5.17(typescript@5.8.3)
-
- '@humanfs/core@0.19.1': {}
+ '@humanfs/core': 0.19.2
+ '@humanfs/types': 0.15.0
+ '@humanwhocodes/retry': 0.4.3
- '@humanfs/node@0.16.6':
- dependencies:
- '@humanfs/core': 0.19.1
- '@humanwhocodes/retry': 0.3.1
+ '@humanfs/types@0.15.0': {}
'@humanwhocodes/module-importer@1.0.1': {}
- '@humanwhocodes/retry@0.3.1': {}
-
'@humanwhocodes/retry@0.4.3': {}
- '@iconify-json/carbon@1.2.9':
+ '@iconify-json/logos@1.2.14':
dependencies:
'@iconify/types': 2.0.0
- '@iconify-json/devicon-plain@1.2.31':
+ '@iconify-json/simple-icons@1.2.97':
dependencies:
'@iconify/types': 2.0.0
- '@iconify-json/devicon@1.2.32':
+ '@iconify-json/vscode-icons@1.2.81':
dependencies:
'@iconify/types': 2.0.0
- '@iconify-json/logos@1.2.4':
- dependencies:
- '@iconify/types': 2.0.0
+ '@iconify/types@2.0.0': {}
- '@iconify-json/ri@1.2.5':
+ '@iconify/utils@3.1.7':
dependencies:
+ '@antfu/install-pkg': 2.1.0
'@iconify/types': 2.0.0
+ import-meta-resolve: 4.2.0
- '@iconify-json/simple-icons@1.2.39':
- dependencies:
- '@iconify/types': 2.0.0
+ '@jridgewell/sourcemap-codec@1.6.0': {}
- '@iconify-json/vscode-icons@1.2.23':
+ '@keyv/bigmap@1.3.1(keyv@5.6.0)':
dependencies:
- '@iconify/types': 2.0.0
+ hashery: 1.5.1
+ hookified: 1.15.1
+ keyv: 5.6.0
- '@iconify/types@2.0.0': {}
+ '@keyv/serialize@1.1.1': {}
- '@iconify/utils@2.3.0':
- dependencies:
- '@antfu/install-pkg': 1.1.0
- '@antfu/utils': 8.1.1
- '@iconify/types': 2.0.0
- debug: 4.4.1(supports-color@5.5.0)
- globals: 15.15.0
- kolorist: 1.8.0
- local-pkg: 1.1.1
- mlly: 1.7.4
- transitivePeerDependencies:
- - supports-color
+ '@lit-labs/ssr-dom-shim@1.6.0': {}
- '@intlify/bundle-utils@10.0.1(vue-i18n@11.1.10(vue@3.5.17(typescript@5.8.3)))':
+ '@lit/reactive-element@2.1.2':
dependencies:
- '@intlify/message-compiler': 11.1.10
- '@intlify/shared': 11.1.10
- acorn: 8.15.0
- escodegen: 2.1.0
- estree-walker: 2.0.2
- jsonc-eslint-parser: 2.4.0
- mlly: 1.7.4
- source-map-js: 1.2.1
- yaml-eslint-parser: 1.3.0
- optionalDependencies:
- vue-i18n: 11.1.10(vue@3.5.17(typescript@5.8.3))
+ '@lit-labs/ssr-dom-shim': 1.6.0
- '@intlify/core-base@11.1.10':
+ '@mermaid-js/parser@2.0.0':
dependencies:
- '@intlify/message-compiler': 11.1.10
- '@intlify/shared': 11.1.10
+ '@chevrotain/types': 11.1.2
- '@intlify/message-compiler@11.1.10':
- dependencies:
- '@intlify/shared': 11.1.10
- source-map-js: 1.2.1
+ '@napi-rs/lzma-linux-x64-gnu@1.5.1':
+ optional: true
- '@intlify/shared@11.1.10': {}
-
- '@intlify/unplugin-vue-i18n@6.0.8(@vue/compiler-dom@3.5.17)(eslint@9.29.0(jiti@2.4.2))(rollup@4.45.1)(typescript@5.8.3)(vue-i18n@11.1.10(vue@3.5.17(typescript@5.8.3)))(vue@3.5.17(typescript@5.8.3))':
- dependencies:
- '@eslint-community/eslint-utils': 4.7.0(eslint@9.29.0(jiti@2.4.2))
- '@intlify/bundle-utils': 10.0.1(vue-i18n@11.1.10(vue@3.5.17(typescript@5.8.3)))
- '@intlify/shared': 11.1.10
- '@intlify/vue-i18n-extensions': 8.0.0(@intlify/shared@11.1.10)(@vue/compiler-dom@3.5.17)(vue-i18n@11.1.10(vue@3.5.17(typescript@5.8.3)))(vue@3.5.17(typescript@5.8.3))
- '@rollup/pluginutils': 5.2.0(rollup@4.45.1)
- '@typescript-eslint/scope-manager': 8.37.0
- '@typescript-eslint/typescript-estree': 8.37.0(typescript@5.8.3)
- debug: 4.4.1(supports-color@5.5.0)
- fast-glob: 3.3.3
- js-yaml: 4.1.0
- json5: 2.2.3
- pathe: 1.1.2
- picocolors: 1.1.1
- source-map-js: 1.2.1
- unplugin: 1.16.1
- vue: 3.5.17(typescript@5.8.3)
- optionalDependencies:
- vue-i18n: 11.1.10(vue@3.5.17(typescript@5.8.3))
- transitivePeerDependencies:
- - '@vue/compiler-dom'
- - eslint
- - rollup
- - supports-color
- - typescript
+ '@rollup/rollup-android-arm-eabi@4.63.5':
+ optional: true
- '@intlify/vue-i18n-extensions@8.0.0(@intlify/shared@11.1.10)(@vue/compiler-dom@3.5.17)(vue-i18n@11.1.10(vue@3.5.17(typescript@5.8.3)))(vue@3.5.17(typescript@5.8.3))':
- dependencies:
- '@babel/parser': 7.28.0
- optionalDependencies:
- '@intlify/shared': 11.1.10
- '@vue/compiler-dom': 3.5.17
- vue: 3.5.17(typescript@5.8.3)
- vue-i18n: 11.1.10(vue@3.5.17(typescript@5.8.3))
+ '@rollup/rollup-android-arm64@4.63.5':
+ optional: true
- '@jridgewell/gen-mapping@0.3.12':
- dependencies:
- '@jridgewell/sourcemap-codec': 1.5.4
- '@jridgewell/trace-mapping': 0.3.29
+ '@rollup/rollup-darwin-arm64@4.63.5':
+ optional: true
- '@jridgewell/resolve-uri@3.1.2': {}
+ '@rollup/rollup-darwin-x64@4.63.5':
+ optional: true
- '@jridgewell/source-map@0.3.10':
- dependencies:
- '@jridgewell/gen-mapping': 0.3.12
- '@jridgewell/trace-mapping': 0.3.29
+ '@rollup/rollup-freebsd-arm64@4.63.5':
+ optional: true
- '@jridgewell/sourcemap-codec@1.5.4': {}
+ '@rollup/rollup-freebsd-x64@4.63.5':
+ optional: true
- '@jridgewell/trace-mapping@0.3.29':
- dependencies:
- '@jridgewell/resolve-uri': 3.1.2
- '@jridgewell/sourcemap-codec': 1.5.4
+ '@rollup/rollup-linux-arm-gnueabihf@4.63.5':
+ optional: true
- '@kwsites/file-exists@1.1.1':
- dependencies:
- debug: 4.4.1(supports-color@5.5.0)
- transitivePeerDependencies:
- - supports-color
+ '@rollup/rollup-linux-arm-musleabihf@4.63.5':
+ optional: true
- '@kwsites/promise-deferred@1.1.1': {}
+ '@rollup/rollup-linux-arm64-gnu@4.63.5':
+ optional: true
- '@lit-labs/ssr-dom-shim@1.4.0': {}
+ '@rollup/rollup-linux-arm64-musl@4.63.5':
+ optional: true
- '@lit/reactive-element@2.1.1':
- dependencies:
- '@lit-labs/ssr-dom-shim': 1.4.0
+ '@rollup/rollup-linux-loong64-gnu@4.63.5':
+ optional: true
- '@mdit-vue/plugin-component@2.1.4':
- dependencies:
- '@types/markdown-it': 14.1.2
- markdown-it: 14.1.0
+ '@rollup/rollup-linux-loong64-musl@4.63.5':
+ optional: true
- '@mdit-vue/plugin-frontmatter@2.1.4':
- dependencies:
- '@mdit-vue/types': 2.1.4
- '@types/markdown-it': 14.1.2
- gray-matter: 4.0.3
- markdown-it: 14.1.0
+ '@rollup/rollup-linux-ppc64-gnu@4.63.5':
+ optional: true
- '@mdit-vue/types@2.1.4': {}
+ '@rollup/rollup-linux-ppc64-musl@4.63.5':
+ optional: true
- '@mermaid-js/parser@0.6.2':
- dependencies:
- langium: 3.3.1
+ '@rollup/rollup-linux-riscv64-gnu@4.63.5':
+ optional: true
- '@nodelib/fs.scandir@2.1.5':
- dependencies:
- '@nodelib/fs.stat': 2.0.5
- run-parallel: 1.2.0
+ '@rollup/rollup-linux-riscv64-musl@4.63.5':
+ optional: true
- '@nodelib/fs.stat@2.0.5': {}
+ '@rollup/rollup-linux-s390x-gnu@4.63.5':
+ optional: true
- '@nodelib/fs.walk@1.2.8':
- dependencies:
- '@nodelib/fs.scandir': 2.1.5
- fastq: 1.19.1
+ '@rollup/rollup-linux-x64-gnu@4.63.5':
+ optional: true
- '@octokit/auth-token@5.1.2': {}
+ '@rollup/rollup-linux-x64-musl@4.63.5':
+ optional: true
- '@octokit/core@6.1.6':
- dependencies:
- '@octokit/auth-token': 5.1.2
- '@octokit/graphql': 8.2.2
- '@octokit/request': 9.2.4
- '@octokit/request-error': 6.1.8
- '@octokit/types': 14.1.0
- before-after-hook: 3.0.2
- universal-user-agent: 7.0.3
+ '@rollup/rollup-openbsd-x64@4.63.5':
+ optional: true
- '@octokit/endpoint@10.1.4':
- dependencies:
- '@octokit/types': 14.1.0
- universal-user-agent: 7.0.3
+ '@rollup/rollup-openharmony-arm64@4.63.5':
+ optional: true
- '@octokit/graphql@8.2.2':
- dependencies:
- '@octokit/request': 9.2.4
- '@octokit/types': 14.1.0
- universal-user-agent: 7.0.3
+ '@rollup/rollup-win32-arm64-msvc@4.63.5':
+ optional: true
- '@octokit/openapi-types@24.2.0': {}
+ '@rollup/rollup-win32-ia32-msvc@4.63.5':
+ optional: true
- '@octokit/openapi-types@25.1.0': {}
+ '@rollup/rollup-win32-x64-gnu@4.63.5':
+ optional: true
- '@octokit/plugin-paginate-rest@11.6.0(@octokit/core@6.1.6)':
- dependencies:
- '@octokit/core': 6.1.6
- '@octokit/types': 13.10.0
+ '@rollup/rollup-win32-x64-msvc@4.63.5':
+ optional: true
- '@octokit/plugin-request-log@5.3.1(@octokit/core@6.1.6)':
+ '@shikijs/core@2.5.0':
dependencies:
- '@octokit/core': 6.1.6
+ '@shikijs/engine-javascript': 2.5.0
+ '@shikijs/engine-oniguruma': 2.5.0
+ '@shikijs/types': 2.5.0
+ '@shikijs/vscode-textmate': 10.0.2
+ '@types/hast': 3.0.5
+ hast-util-to-html: 9.0.5
- '@octokit/plugin-rest-endpoint-methods@13.5.0(@octokit/core@6.1.6)':
+ '@shikijs/engine-javascript@2.5.0':
dependencies:
- '@octokit/core': 6.1.6
- '@octokit/types': 13.10.0
+ '@shikijs/types': 2.5.0
+ '@shikijs/vscode-textmate': 10.0.2
+ oniguruma-to-es: 3.1.1
- '@octokit/request-error@6.1.8':
+ '@shikijs/engine-oniguruma@2.5.0':
dependencies:
- '@octokit/types': 14.1.0
+ '@shikijs/types': 2.5.0
+ '@shikijs/vscode-textmate': 10.0.2
- '@octokit/request@9.2.4':
+ '@shikijs/langs@2.5.0':
dependencies:
- '@octokit/endpoint': 10.1.4
- '@octokit/request-error': 6.1.8
- '@octokit/types': 14.1.0
- fast-content-type-parse: 2.0.1
- universal-user-agent: 7.0.3
+ '@shikijs/types': 2.5.0
- '@octokit/rest@21.1.1':
+ '@shikijs/themes@2.5.0':
dependencies:
- '@octokit/core': 6.1.6
- '@octokit/plugin-paginate-rest': 11.6.0(@octokit/core@6.1.6)
- '@octokit/plugin-request-log': 5.3.1(@octokit/core@6.1.6)
- '@octokit/plugin-rest-endpoint-methods': 13.5.0(@octokit/core@6.1.6)
+ '@shikijs/types': 2.5.0
- '@octokit/types@13.10.0':
+ '@shikijs/transformers@2.5.0':
dependencies:
- '@octokit/openapi-types': 24.2.0
+ '@shikijs/core': 2.5.0
+ '@shikijs/types': 2.5.0
- '@octokit/types@14.1.0':
+ '@shikijs/types@2.5.0':
dependencies:
- '@octokit/openapi-types': 25.1.0
+ '@shikijs/vscode-textmate': 10.0.2
+ '@types/hast': 3.0.5
- '@parcel/watcher-android-arm64@2.5.1':
- optional: true
+ '@shikijs/vscode-textmate@10.0.2': {}
- '@parcel/watcher-darwin-arm64@2.5.1':
- optional: true
+ '@types/d3-array@3.2.2': {}
- '@parcel/watcher-darwin-x64@2.5.1':
- optional: true
+ '@types/d3-axis@3.0.6':
+ dependencies:
+ '@types/d3-selection': 3.0.12
- '@parcel/watcher-freebsd-x64@2.5.1':
- optional: true
-
- '@parcel/watcher-linux-arm-glibc@2.5.1':
- optional: true
-
- '@parcel/watcher-linux-arm-musl@2.5.1':
- optional: true
-
- '@parcel/watcher-linux-arm64-glibc@2.5.1':
- optional: true
-
- '@parcel/watcher-linux-arm64-musl@2.5.1':
- optional: true
-
- '@parcel/watcher-linux-x64-glibc@2.5.1':
- optional: true
-
- '@parcel/watcher-linux-x64-musl@2.5.1':
- optional: true
-
- '@parcel/watcher-win32-arm64@2.5.1':
- optional: true
-
- '@parcel/watcher-win32-ia32@2.5.1':
- optional: true
-
- '@parcel/watcher-win32-x64@2.5.1':
- optional: true
-
- '@parcel/watcher@2.5.1':
- dependencies:
- detect-libc: 1.0.3
- is-glob: 4.0.3
- micromatch: 4.0.8
- node-addon-api: 7.1.1
- optionalDependencies:
- '@parcel/watcher-android-arm64': 2.5.1
- '@parcel/watcher-darwin-arm64': 2.5.1
- '@parcel/watcher-darwin-x64': 2.5.1
- '@parcel/watcher-freebsd-x64': 2.5.1
- '@parcel/watcher-linux-arm-glibc': 2.5.1
- '@parcel/watcher-linux-arm-musl': 2.5.1
- '@parcel/watcher-linux-arm64-glibc': 2.5.1
- '@parcel/watcher-linux-arm64-musl': 2.5.1
- '@parcel/watcher-linux-x64-glibc': 2.5.1
- '@parcel/watcher-linux-x64-musl': 2.5.1
- '@parcel/watcher-win32-arm64': 2.5.1
- '@parcel/watcher-win32-ia32': 2.5.1
- '@parcel/watcher-win32-x64': 2.5.1
- optional: true
-
- '@polka/url@1.0.0-next.29': {}
-
- '@quansync/fs@0.1.3':
- dependencies:
- quansync: 0.2.10
-
- '@rolldown/pluginutils@1.0.0-beta.19': {}
-
- '@rollup/pluginutils@5.2.0(rollup@4.45.1)':
- dependencies:
- '@types/estree': 1.0.8
- estree-walker: 2.0.2
- picomatch: 4.0.3
- optionalDependencies:
- rollup: 4.45.1
-
- '@rollup/rollup-android-arm-eabi@4.45.1':
- optional: true
-
- '@rollup/rollup-android-arm64@4.45.1':
- optional: true
-
- '@rollup/rollup-darwin-arm64@4.45.1':
- optional: true
-
- '@rollup/rollup-darwin-x64@4.45.1':
- optional: true
-
- '@rollup/rollup-freebsd-arm64@4.45.1':
- optional: true
-
- '@rollup/rollup-freebsd-x64@4.45.1':
- optional: true
-
- '@rollup/rollup-linux-arm-gnueabihf@4.45.1':
- optional: true
-
- '@rollup/rollup-linux-arm-musleabihf@4.45.1':
- optional: true
-
- '@rollup/rollup-linux-arm64-gnu@4.45.1':
- optional: true
-
- '@rollup/rollup-linux-arm64-musl@4.45.1':
- optional: true
-
- '@rollup/rollup-linux-loongarch64-gnu@4.45.1':
- optional: true
-
- '@rollup/rollup-linux-powerpc64le-gnu@4.45.1':
- optional: true
-
- '@rollup/rollup-linux-riscv64-gnu@4.45.1':
- optional: true
-
- '@rollup/rollup-linux-riscv64-musl@4.45.1':
- optional: true
-
- '@rollup/rollup-linux-s390x-gnu@4.45.1':
- optional: true
-
- '@rollup/rollup-linux-x64-gnu@4.45.1':
- optional: true
-
- '@rollup/rollup-linux-x64-musl@4.45.1':
- optional: true
-
- '@rollup/rollup-win32-arm64-msvc@4.45.1':
- optional: true
-
- '@rollup/rollup-win32-ia32-msvc@4.45.1':
- optional: true
-
- '@rollup/rollup-win32-x64-msvc@4.45.1':
- optional: true
-
- '@sec-ant/readable-stream@0.4.1': {}
-
- '@selderee/plugin-htmlparser2@0.11.0':
- dependencies:
- domhandler: 5.0.3
- selderee: 0.11.0
-
- '@shikijs/core@1.29.2':
- dependencies:
- '@shikijs/engine-javascript': 1.29.2
- '@shikijs/engine-oniguruma': 1.29.2
- '@shikijs/types': 1.29.2
- '@shikijs/vscode-textmate': 10.0.2
- '@types/hast': 3.0.4
- hast-util-to-html: 9.0.5
-
- '@shikijs/core@3.8.1':
- dependencies:
- '@shikijs/types': 3.8.1
- '@shikijs/vscode-textmate': 10.0.2
- '@types/hast': 3.0.4
- hast-util-to-html: 9.0.5
-
- '@shikijs/engine-javascript@1.29.2':
- dependencies:
- '@shikijs/types': 1.29.2
- '@shikijs/vscode-textmate': 10.0.2
- oniguruma-to-es: 2.3.0
-
- '@shikijs/engine-javascript@3.8.1':
- dependencies:
- '@shikijs/types': 3.8.1
- '@shikijs/vscode-textmate': 10.0.2
- oniguruma-to-es: 4.3.3
-
- '@shikijs/engine-oniguruma@1.29.2':
- dependencies:
- '@shikijs/types': 1.29.2
- '@shikijs/vscode-textmate': 10.0.2
-
- '@shikijs/engine-oniguruma@3.8.1':
- dependencies:
- '@shikijs/types': 3.8.1
- '@shikijs/vscode-textmate': 10.0.2
-
- '@shikijs/langs@1.29.2':
- dependencies:
- '@shikijs/types': 1.29.2
-
- '@shikijs/langs@3.8.1':
- dependencies:
- '@shikijs/types': 3.8.1
-
- '@shikijs/themes@1.29.2':
- dependencies:
- '@shikijs/types': 1.29.2
-
- '@shikijs/themes@3.8.1':
- dependencies:
- '@shikijs/types': 3.8.1
-
- '@shikijs/transformers@1.29.2':
- dependencies:
- '@shikijs/core': 1.29.2
- '@shikijs/types': 1.29.2
-
- '@shikijs/transformers@3.8.1':
- dependencies:
- '@shikijs/core': 3.8.1
- '@shikijs/types': 3.8.1
-
- '@shikijs/types@1.29.2':
- dependencies:
- '@shikijs/vscode-textmate': 10.0.2
- '@types/hast': 3.0.4
-
- '@shikijs/types@3.8.1':
- dependencies:
- '@shikijs/vscode-textmate': 10.0.2
- '@types/hast': 3.0.4
-
- '@shikijs/vscode-textmate@10.0.2': {}
-
- '@sindresorhus/merge-streams@4.0.0': {}
-
- '@types/d3-array@3.2.1': {}
-
- '@types/d3-axis@3.0.6':
- dependencies:
- '@types/d3-selection': 3.0.11
-
- '@types/d3-brush@3.0.6':
- dependencies:
- '@types/d3-selection': 3.0.11
+ '@types/d3-brush@3.0.6':
+ dependencies:
+ '@types/d3-selection': 3.0.12
'@types/d3-chord@3.0.6': {}
@@ -5400,16 +2529,16 @@ snapshots:
'@types/d3-contour@3.0.6':
dependencies:
- '@types/d3-array': 3.2.1
+ '@types/d3-array': 3.2.2
'@types/geojson': 7946.0.16
'@types/d3-delaunay@6.0.4': {}
- '@types/d3-dispatch@3.0.6': {}
+ '@types/d3-dispatch@3.0.7': {}
'@types/d3-drag@3.0.7':
dependencies:
- '@types/d3-selection': 3.0.11
+ '@types/d3-selection': 3.0.12
'@types/d3-dsv@3.0.7': {}
@@ -5423,7 +2552,7 @@ snapshots:
'@types/d3-format@3.0.4': {}
- '@types/d3-geo@3.1.0':
+ '@types/d3-geo@3.1.1':
dependencies:
'@types/geojson': 7946.0.16
@@ -5439,7 +2568,7 @@ snapshots:
'@types/d3-quadtree@3.0.6': {}
- '@types/d3-random@3.0.3': {}
+ '@types/d3-random@3.0.4': {}
'@types/d3-scale-chromatic@3.1.0': {}
@@ -5447,9 +2576,9 @@ snapshots:
dependencies:
'@types/d3-time': 3.0.4
- '@types/d3-selection@3.0.11': {}
+ '@types/d3-selection@3.0.12': {}
- '@types/d3-shape@3.1.7':
+ '@types/d3-shape@3.2.0':
dependencies:
'@types/d3-path': 3.1.1
@@ -5461,65 +2590,61 @@ snapshots:
'@types/d3-transition@3.0.9':
dependencies:
- '@types/d3-selection': 3.0.11
+ '@types/d3-selection': 3.0.12
'@types/d3-zoom@3.0.8':
dependencies:
'@types/d3-interpolate': 3.0.4
- '@types/d3-selection': 3.0.11
+ '@types/d3-selection': 3.0.12
'@types/d3@7.4.3':
dependencies:
- '@types/d3-array': 3.2.1
+ '@types/d3-array': 3.2.2
'@types/d3-axis': 3.0.6
'@types/d3-brush': 3.0.6
'@types/d3-chord': 3.0.6
'@types/d3-color': 3.1.3
'@types/d3-contour': 3.0.6
'@types/d3-delaunay': 6.0.4
- '@types/d3-dispatch': 3.0.6
+ '@types/d3-dispatch': 3.0.7
'@types/d3-drag': 3.0.7
'@types/d3-dsv': 3.0.7
'@types/d3-ease': 3.0.2
'@types/d3-fetch': 3.0.7
'@types/d3-force': 3.0.10
'@types/d3-format': 3.0.4
- '@types/d3-geo': 3.1.0
+ '@types/d3-geo': 3.1.1
'@types/d3-hierarchy': 3.1.7
'@types/d3-interpolate': 3.0.4
'@types/d3-path': 3.1.1
'@types/d3-polygon': 3.0.2
'@types/d3-quadtree': 3.0.6
- '@types/d3-random': 3.0.3
+ '@types/d3-random': 3.0.4
'@types/d3-scale': 4.0.9
'@types/d3-scale-chromatic': 3.1.0
- '@types/d3-selection': 3.0.11
- '@types/d3-shape': 3.1.7
+ '@types/d3-selection': 3.0.12
+ '@types/d3-shape': 3.2.0
'@types/d3-time': 3.0.4
'@types/d3-time-format': 4.0.3
'@types/d3-timer': 3.0.2
'@types/d3-transition': 3.0.9
'@types/d3-zoom': 3.0.8
- '@types/estree@1.0.8': {}
+ '@types/esrecurse@4.3.1': {}
+
+ '@types/estree@1.0.9': {}
'@types/geojson@7946.0.16': {}
- '@types/hast@3.0.4':
+ '@types/hast@3.0.5':
dependencies:
'@types/unist': 3.0.3
- '@types/http-proxy@1.17.16':
- dependencies:
- '@types/node': 24.0.15
-
'@types/json-schema@7.0.15': {}
- '@types/katex@0.16.7': {}
-
'@types/linkify-it@5.0.0': {}
- '@types/markdown-it@14.1.2':
+ '@types/markdown-it@14.2.0':
dependencies:
'@types/linkify-it': 5.0.0
'@types/mdurl': 2.0.0
@@ -5530,841 +2655,348 @@ snapshots:
'@types/mdurl@2.0.0': {}
- '@types/node@24.0.15':
+ '@types/node@24.19.0':
dependencies:
- undici-types: 7.8.0
+ undici-types: 7.24.6
'@types/trusted-types@2.0.7': {}
'@types/unist@3.0.3': {}
- '@types/web-bluetooth@0.0.20': {}
-
'@types/web-bluetooth@0.0.21': {}
- '@typescript-eslint/project-service@8.37.0(typescript@5.8.3)':
+ '@typescript-eslint/eslint-plugin@8.70.1(@typescript-eslint/parser@8.70.1(eslint@10.11.0)(typescript@6.0.3))(eslint@10.11.0)(typescript@6.0.3)':
dependencies:
- '@typescript-eslint/tsconfig-utils': 8.37.0(typescript@5.8.3)
- '@typescript-eslint/types': 8.37.0
- debug: 4.4.1(supports-color@5.5.0)
- typescript: 5.8.3
+ '@eslint-community/regexpp': 4.12.2
+ '@typescript-eslint/parser': 8.70.1(eslint@10.11.0)(typescript@6.0.3)
+ '@typescript-eslint/scope-manager': 8.70.1
+ '@typescript-eslint/type-utils': 8.70.1(eslint@10.11.0)(typescript@6.0.3)
+ '@typescript-eslint/utils': 8.70.1(eslint@10.11.0)(typescript@6.0.3)
+ '@typescript-eslint/visitor-keys': 8.70.1
+ eslint: 10.11.0
+ ignore: 7.0.10
+ natural-compare: 1.4.0
+ ts-api-utils: 2.5.0(typescript@6.0.3)
+ typescript: 6.0.3
transitivePeerDependencies:
- supports-color
- '@typescript-eslint/scope-manager@8.37.0':
+ '@typescript-eslint/parser@8.70.1(eslint@10.11.0)(typescript@6.0.3)':
dependencies:
- '@typescript-eslint/types': 8.37.0
- '@typescript-eslint/visitor-keys': 8.37.0
-
- '@typescript-eslint/tsconfig-utils@8.37.0(typescript@5.8.3)':
- dependencies:
- typescript: 5.8.3
-
- '@typescript-eslint/types@8.37.0': {}
-
- '@typescript-eslint/typescript-estree@8.37.0(typescript@5.8.3)':
- dependencies:
- '@typescript-eslint/project-service': 8.37.0(typescript@5.8.3)
- '@typescript-eslint/tsconfig-utils': 8.37.0(typescript@5.8.3)
- '@typescript-eslint/types': 8.37.0
- '@typescript-eslint/visitor-keys': 8.37.0
- debug: 4.4.1(supports-color@5.5.0)
- fast-glob: 3.3.3
- is-glob: 4.0.3
- minimatch: 9.0.5
- semver: 7.7.2
- ts-api-utils: 2.1.0(typescript@5.8.3)
- typescript: 5.8.3
+ '@typescript-eslint/scope-manager': 8.70.1
+ '@typescript-eslint/types': 8.70.1
+ '@typescript-eslint/typescript-estree': 8.70.1(typescript@6.0.3)
+ '@typescript-eslint/visitor-keys': 8.70.1
+ debug: 4.4.3
+ eslint: 10.11.0
+ typescript: 6.0.3
transitivePeerDependencies:
- supports-color
- '@typescript-eslint/visitor-keys@8.37.0':
- dependencies:
- '@typescript-eslint/types': 8.37.0
- eslint-visitor-keys: 4.2.1
-
- '@ungap/structured-clone@1.3.0': {}
-
- '@unhead/addons@2.0.12(rollup@4.45.1)':
- dependencies:
- '@rollup/pluginutils': 5.2.0(rollup@4.45.1)
- estree-walker: 3.0.3
- magic-string: 0.30.17
- mlly: 1.7.4
- ufo: 1.6.1
- unplugin: 2.3.5
- unplugin-ast: 0.15.1
- transitivePeerDependencies:
- - rollup
-
- '@unhead/dom@2.0.12(unhead@2.0.12)':
- dependencies:
- unhead: 2.0.12
-
- '@unhead/schema-org@2.0.12(@unhead/vue@2.0.12(vue@3.5.17(typescript@5.8.3)))':
- dependencies:
- defu: 6.1.4
- ohash: 2.0.11
- ufo: 1.6.1
- unhead: 2.0.12
- optionalDependencies:
- '@unhead/vue': 2.0.12(vue@3.5.17(typescript@5.8.3))
-
- '@unhead/vue@2.0.12(vue@3.5.17(typescript@5.8.3))':
- dependencies:
- hookable: 5.5.3
- unhead: 2.0.12
- vue: 3.5.17(typescript@5.8.3)
-
- '@unocss/astro@66.3.3(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))(vue@3.5.17(typescript@5.8.3))':
+ '@typescript-eslint/project-service@8.70.1(typescript@6.0.3)':
dependencies:
- '@unocss/core': 66.3.3
- '@unocss/reset': 66.3.3
- '@unocss/vite': 66.3.3(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))(vue@3.5.17(typescript@5.8.3))
- optionalDependencies:
- vite: 7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0)
+ '@typescript-eslint/tsconfig-utils': 8.70.1(typescript@6.0.3)
+ '@typescript-eslint/types': 8.70.1
+ debug: 4.4.3
+ typescript: 6.0.3
transitivePeerDependencies:
- - vue
-
- '@unocss/cli@66.3.3':
- dependencies:
- '@ampproject/remapping': 2.3.0
- '@unocss/config': 66.3.3
- '@unocss/core': 66.3.3
- '@unocss/preset-uno': 66.3.3
- cac: 6.7.14
- chokidar: 3.6.0
- colorette: 2.0.20
- consola: 3.4.2
- magic-string: 0.30.17
- pathe: 2.0.3
- perfect-debounce: 1.0.0
- tinyglobby: 0.2.14
- unplugin-utils: 0.2.4
+ - supports-color
- '@unocss/config@66.3.3':
+ '@typescript-eslint/scope-manager@8.70.1':
dependencies:
- '@unocss/core': 66.3.3
- unconfig: 7.3.2
-
- '@unocss/core@66.3.3': {}
+ '@typescript-eslint/types': 8.70.1
+ '@typescript-eslint/visitor-keys': 8.70.1
- '@unocss/extractor-arbitrary-variants@66.3.3':
+ '@typescript-eslint/tsconfig-utils@8.70.1(typescript@6.0.3)':
dependencies:
- '@unocss/core': 66.3.3
+ typescript: 6.0.3
- '@unocss/inspector@66.3.3(vue@3.5.17(typescript@5.8.3))':
+ '@typescript-eslint/type-utils@8.70.1(eslint@10.11.0)(typescript@6.0.3)':
dependencies:
- '@unocss/core': 66.3.3
- '@unocss/rule-utils': 66.3.3
- colorette: 2.0.20
- gzip-size: 6.0.0
- sirv: 3.0.1
- vue-flow-layout: 0.1.1(vue@3.5.17(typescript@5.8.3))
+ '@typescript-eslint/types': 8.70.1
+ '@typescript-eslint/typescript-estree': 8.70.1(typescript@6.0.3)
+ '@typescript-eslint/utils': 8.70.1(eslint@10.11.0)(typescript@6.0.3)
+ debug: 4.4.3
+ eslint: 10.11.0
+ ts-api-utils: 2.5.0(typescript@6.0.3)
+ typescript: 6.0.3
transitivePeerDependencies:
- - vue
-
- '@unocss/postcss@66.3.3(postcss@8.5.6)':
- dependencies:
- '@unocss/config': 66.3.3
- '@unocss/core': 66.3.3
- '@unocss/rule-utils': 66.3.3
- css-tree: 3.1.0
- postcss: 8.5.6
- tinyglobby: 0.2.14
+ - supports-color
- '@unocss/preset-attributify@66.3.3':
- dependencies:
- '@unocss/core': 66.3.3
+ '@typescript-eslint/types@8.70.1': {}
- '@unocss/preset-icons@66.3.3':
+ '@typescript-eslint/typescript-estree@8.70.1(typescript@6.0.3)':
dependencies:
- '@iconify/utils': 2.3.0
- '@unocss/core': 66.3.3
- ofetch: 1.4.1
+ '@typescript-eslint/project-service': 8.70.1(typescript@6.0.3)
+ '@typescript-eslint/tsconfig-utils': 8.70.1(typescript@6.0.3)
+ '@typescript-eslint/types': 8.70.1
+ '@typescript-eslint/visitor-keys': 8.70.1
+ debug: 4.4.3
+ minimatch: 10.2.6
+ semver: 7.8.5
+ tinyglobby: 0.2.17
+ ts-api-utils: 2.5.0(typescript@6.0.3)
+ typescript: 6.0.3
transitivePeerDependencies:
- supports-color
- '@unocss/preset-mini@66.3.3':
- dependencies:
- '@unocss/core': 66.3.3
- '@unocss/extractor-arbitrary-variants': 66.3.3
- '@unocss/rule-utils': 66.3.3
-
- '@unocss/preset-tagify@66.3.3':
- dependencies:
- '@unocss/core': 66.3.3
-
- '@unocss/preset-typography@66.3.3':
+ '@typescript-eslint/utils@8.70.1(eslint@10.11.0)(typescript@6.0.3)':
dependencies:
- '@unocss/core': 66.3.3
- '@unocss/preset-mini': 66.3.3
- '@unocss/rule-utils': 66.3.3
-
- '@unocss/preset-uno@66.3.3':
- dependencies:
- '@unocss/core': 66.3.3
- '@unocss/preset-wind3': 66.3.3
-
- '@unocss/preset-web-fonts@66.3.3':
- dependencies:
- '@unocss/core': 66.3.3
- ofetch: 1.4.1
-
- '@unocss/preset-wind3@66.3.3':
- dependencies:
- '@unocss/core': 66.3.3
- '@unocss/preset-mini': 66.3.3
- '@unocss/rule-utils': 66.3.3
-
- '@unocss/preset-wind4@66.3.3':
- dependencies:
- '@unocss/core': 66.3.3
- '@unocss/extractor-arbitrary-variants': 66.3.3
- '@unocss/rule-utils': 66.3.3
-
- '@unocss/preset-wind@66.3.3':
- dependencies:
- '@unocss/core': 66.3.3
- '@unocss/preset-wind3': 66.3.3
-
- '@unocss/reset@66.3.3': {}
-
- '@unocss/rule-utils@66.3.3':
- dependencies:
- '@unocss/core': 66.3.3
- magic-string: 0.30.17
-
- '@unocss/transformer-attributify-jsx@66.3.3':
- dependencies:
- '@unocss/core': 66.3.3
-
- '@unocss/transformer-compile-class@66.3.3':
- dependencies:
- '@unocss/core': 66.3.3
-
- '@unocss/transformer-directives@66.3.3':
- dependencies:
- '@unocss/core': 66.3.3
- '@unocss/rule-utils': 66.3.3
- css-tree: 3.1.0
-
- '@unocss/transformer-variant-group@66.3.3':
- dependencies:
- '@unocss/core': 66.3.3
-
- '@unocss/vite@66.3.3(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))(vue@3.5.17(typescript@5.8.3))':
- dependencies:
- '@ampproject/remapping': 2.3.0
- '@unocss/config': 66.3.3
- '@unocss/core': 66.3.3
- '@unocss/inspector': 66.3.3(vue@3.5.17(typescript@5.8.3))
- chokidar: 3.6.0
- magic-string: 0.30.17
- pathe: 2.0.3
- tinyglobby: 0.2.14
- unplugin-utils: 0.2.4
- vite: 7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0)
- transitivePeerDependencies:
- - vue
-
- '@valaxyjs/devtools@0.25.9(debug@4.4.1)(rollup@4.45.1)(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))':
- dependencies:
- '@rollup/pluginutils': 5.2.0(rollup@4.45.1)
- axios: 1.10.0(debug@4.4.1)
- body-parser: 2.2.0
- cors: 2.8.5
- http-proxy-middleware: 3.0.5
- js-yaml: 4.1.0
- pathe: 2.0.3
- sirv: 3.0.1
- vite-dev-rpc: 1.1.0(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))
+ '@eslint-community/eslint-utils': 4.10.1(eslint@10.11.0)
+ '@typescript-eslint/scope-manager': 8.70.1
+ '@typescript-eslint/types': 8.70.1
+ '@typescript-eslint/typescript-estree': 8.70.1(typescript@6.0.3)
+ eslint: 10.11.0
+ typescript: 6.0.3
transitivePeerDependencies:
- - debug
- - rollup
- supports-color
- - vite
- '@valaxyjs/utils@0.25.9': {}
-
- '@vitejs/plugin-vue@5.2.4(vite@5.4.19(@types/node@24.0.15)(sass@1.89.2)(terser@5.43.1))(vue@3.5.17(typescript@5.8.3))':
- dependencies:
- vite: 5.4.19(@types/node@24.0.15)(sass@1.89.2)(terser@5.43.1)
- vue: 3.5.17(typescript@5.8.3)
-
- '@vitejs/plugin-vue@6.0.0(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))(vue@3.5.17(typescript@5.8.3))':
+ '@typescript-eslint/visitor-keys@8.70.1':
dependencies:
- '@rolldown/pluginutils': 1.0.0-beta.19
- vite: 7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0)
- vue: 3.5.17(typescript@5.8.3)
+ '@typescript-eslint/types': 8.70.1
+ eslint-visitor-keys: 5.0.1
- '@volar/language-core@2.4.15':
- dependencies:
- '@volar/source-map': 2.4.15
+ '@ungap/structured-clone@1.4.0': {}
- '@volar/source-map@2.4.15': {}
+ '@upsetjs/venn.js@2.0.0':
+ optionalDependencies:
+ d3-selection: 3.0.0
+ d3-transition: 3.0.1(d3-selection@3.0.0)
- '@volar/typescript@2.4.15':
+ '@vitejs/plugin-vue@5.2.4(vite@5.4.21(@types/node@24.19.0))(vue@3.5.43(typescript@6.0.3))':
dependencies:
- '@volar/language-core': 2.4.15
- path-browserify: 1.0.1
- vscode-uri: 3.1.0
+ vite: 5.4.21(@types/node@24.19.0)
+ vue: 3.5.43(typescript@6.0.3)
- '@vue-macros/common@3.0.0-beta.15(vue@3.5.17(typescript@5.8.3))':
+ '@volar/language-core@2.4.28':
dependencies:
- '@vue/compiler-sfc': 3.5.17
- ast-kit: 2.1.1
- local-pkg: 1.1.1
- magic-string-ast: 1.0.0
- unplugin-utils: 0.2.4
- optionalDependencies:
- vue: 3.5.17(typescript@5.8.3)
+ '@volar/source-map': 2.4.28
- '@vue/babel-helper-vue-transform-on@1.4.0': {}
+ '@volar/source-map@2.4.28': {}
- '@vue/babel-plugin-jsx@1.4.0(@babel/core@7.28.0)':
+ '@volar/typescript@2.4.28(typescript@6.0.3)':
dependencies:
- '@babel/helper-module-imports': 7.27.1
- '@babel/helper-plugin-utils': 7.27.1
- '@babel/plugin-syntax-jsx': 7.27.1(@babel/core@7.28.0)
- '@babel/template': 7.27.2
- '@babel/traverse': 7.28.0
- '@babel/types': 7.28.1
- '@vue/babel-helper-vue-transform-on': 1.4.0
- '@vue/babel-plugin-resolve-type': 1.4.0(@babel/core@7.28.0)
- '@vue/shared': 3.5.17
+ '@volar/language-core': 2.4.28
+ path-browserify: 1.0.1
+ vscode-uri: 3.2.0
optionalDependencies:
- '@babel/core': 7.28.0
- transitivePeerDependencies:
- - supports-color
-
- '@vue/babel-plugin-resolve-type@1.4.0(@babel/core@7.28.0)':
- dependencies:
- '@babel/code-frame': 7.27.1
- '@babel/core': 7.28.0
- '@babel/helper-module-imports': 7.27.1
- '@babel/helper-plugin-utils': 7.27.1
- '@babel/parser': 7.28.0
- '@vue/compiler-sfc': 3.5.17
- transitivePeerDependencies:
- - supports-color
+ typescript: 6.0.3
- '@vue/compiler-core@3.5.17':
+ '@vue/compiler-core@3.5.43':
dependencies:
- '@babel/parser': 7.28.0
- '@vue/shared': 3.5.17
- entities: 4.5.0
+ '@babel/parser': 7.29.9
+ '@vue/shared': 3.5.43
+ entities: 7.0.1
estree-walker: 2.0.2
source-map-js: 1.2.1
- '@vue/compiler-dom@3.5.17':
+ '@vue/compiler-dom@3.5.43':
dependencies:
- '@vue/compiler-core': 3.5.17
- '@vue/shared': 3.5.17
+ '@vue/compiler-core': 3.5.43
+ '@vue/shared': 3.5.43
- '@vue/compiler-sfc@3.5.17':
+ '@vue/compiler-sfc@3.5.43':
dependencies:
- '@babel/parser': 7.28.0
- '@vue/compiler-core': 3.5.17
- '@vue/compiler-dom': 3.5.17
- '@vue/compiler-ssr': 3.5.17
- '@vue/shared': 3.5.17
+ '@babel/parser': 7.29.9
+ '@vue/compiler-core': 3.5.43
+ '@vue/compiler-dom': 3.5.43
+ '@vue/compiler-ssr': 3.5.43
+ '@vue/shared': 3.5.43
estree-walker: 2.0.2
- magic-string: 0.30.17
- postcss: 8.5.6
+ magic-string: 0.30.21
+ postcss: 8.5.28
source-map-js: 1.2.1
- '@vue/compiler-ssr@3.5.17':
+ '@vue/compiler-ssr@3.5.43':
dependencies:
- '@vue/compiler-dom': 3.5.17
- '@vue/shared': 3.5.17
+ '@vue/compiler-dom': 3.5.43
+ '@vue/shared': 3.5.43
- '@vue/compiler-vue2@2.7.16':
+ '@vue/devtools-api@7.7.10':
dependencies:
- de-indent: 1.0.2
- he: 1.2.0
-
- '@vue/devtools-api@6.6.4': {}
-
- '@vue/devtools-api@7.7.2':
- dependencies:
- '@vue/devtools-kit': 7.7.7
-
- '@vue/devtools-api@7.7.7':
- dependencies:
- '@vue/devtools-kit': 7.7.7
-
- '@vue/devtools-core@7.7.7(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))(vue@3.5.17(typescript@5.8.3))':
- dependencies:
- '@vue/devtools-kit': 7.7.7
- '@vue/devtools-shared': 7.7.7
- mitt: 3.0.1
- nanoid: 5.1.5
- pathe: 2.0.3
- vite-hot-client: 2.1.0(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))
- vue: 3.5.17(typescript@5.8.3)
- transitivePeerDependencies:
- - vite
+ '@vue/devtools-kit': 7.7.10
- '@vue/devtools-kit@7.7.7':
+ '@vue/devtools-kit@7.7.10':
dependencies:
- '@vue/devtools-shared': 7.7.7
- birpc: 2.5.0
+ '@vue/devtools-shared': 7.7.10
+ birpc: 2.9.0
hookable: 5.5.3
mitt: 3.0.1
perfect-debounce: 1.0.0
speakingurl: 14.0.1
- superjson: 2.2.2
+ superjson: 2.2.6
- '@vue/devtools-shared@7.7.7':
+ '@vue/devtools-shared@7.7.10':
dependencies:
rfdc: 1.4.1
- '@vue/language-core@2.2.12(typescript@5.8.3)':
+ '@vue/language-core@3.3.11':
dependencies:
- '@volar/language-core': 2.4.15
- '@vue/compiler-dom': 3.5.17
- '@vue/compiler-vue2': 2.7.16
- '@vue/shared': 3.5.17
- alien-signals: 1.0.13
- minimatch: 9.0.5
+ '@volar/language-core': 2.4.28
+ '@vue/compiler-dom': 3.5.43
+ '@vue/shared': 3.5.43
+ alien-signals: 3.2.1
muggle-string: 0.4.1
path-browserify: 1.0.1
- optionalDependencies:
- typescript: 5.8.3
+ picomatch: 4.0.7
- '@vue/reactivity@3.5.17':
+ '@vue/reactivity@3.5.43':
dependencies:
- '@vue/shared': 3.5.17
+ '@vue/shared': 3.5.43
- '@vue/runtime-core@3.5.17':
+ '@vue/runtime-core@3.5.43':
dependencies:
- '@vue/reactivity': 3.5.17
- '@vue/shared': 3.5.17
+ '@vue/reactivity': 3.5.43
+ '@vue/shared': 3.5.43
- '@vue/runtime-dom@3.5.17':
+ '@vue/runtime-dom@3.5.43':
dependencies:
- '@vue/reactivity': 3.5.17
- '@vue/runtime-core': 3.5.17
- '@vue/shared': 3.5.17
- csstype: 3.1.3
+ '@vue/reactivity': 3.5.43
+ '@vue/runtime-core': 3.5.43
+ '@vue/shared': 3.5.43
+ csstype: 3.2.3
- '@vue/server-renderer@3.5.17(vue@3.5.17(typescript@5.8.3))':
+ '@vue/server-renderer@3.5.43':
dependencies:
- '@vue/compiler-ssr': 3.5.17
- '@vue/shared': 3.5.17
- vue: 3.5.17(typescript@5.8.3)
+ '@vue/compiler-ssr': 3.5.43
+ '@vue/runtime-dom': 3.5.43
+ '@vue/shared': 3.5.43
- '@vue/shared@3.5.17': {}
-
- '@vueuse/core@10.11.1(vue@3.5.17(typescript@5.8.3))':
- dependencies:
- '@types/web-bluetooth': 0.0.20
- '@vueuse/metadata': 10.11.1
- '@vueuse/shared': 10.11.1(vue@3.5.17(typescript@5.8.3))
- vue-demi: 0.14.10(vue@3.5.17(typescript@5.8.3))
- transitivePeerDependencies:
- - '@vue/composition-api'
- - vue
+ '@vue/shared@3.5.43': {}
- '@vueuse/core@13.5.0(vue@3.5.17(typescript@5.8.3))':
+ '@vueuse/core@12.8.2(typescript@6.0.3)':
dependencies:
'@types/web-bluetooth': 0.0.21
- '@vueuse/metadata': 13.5.0
- '@vueuse/shared': 13.5.0(vue@3.5.17(typescript@5.8.3))
- vue: 3.5.17(typescript@5.8.3)
-
- '@vueuse/integrations@10.11.1(axios@1.10.0)(focus-trap@7.6.5)(fuse.js@7.1.0)(nprogress@0.2.0)(qrcode@1.5.4)(vue@3.5.17(typescript@5.8.3))':
- dependencies:
- '@vueuse/core': 10.11.1(vue@3.5.17(typescript@5.8.3))
- '@vueuse/shared': 10.11.1(vue@3.5.17(typescript@5.8.3))
- vue-demi: 0.14.10(vue@3.5.17(typescript@5.8.3))
- optionalDependencies:
- axios: 1.10.0(debug@4.4.1)
- focus-trap: 7.6.5
- fuse.js: 7.1.0
- nprogress: 0.2.0
- qrcode: 1.5.4
+ '@vueuse/metadata': 12.8.2
+ '@vueuse/shared': 12.8.2(typescript@6.0.3)
+ vue: 3.5.43(typescript@6.0.3)
transitivePeerDependencies:
- - '@vue/composition-api'
- - vue
+ - typescript
- '@vueuse/integrations@13.5.0(axios@1.10.0)(focus-trap@7.6.5)(fuse.js@7.1.0)(nprogress@0.2.0)(qrcode@1.5.4)(vue@3.5.17(typescript@5.8.3))':
+ '@vueuse/integrations@12.8.2(focus-trap@7.8.0)(typescript@6.0.3)':
dependencies:
- '@vueuse/core': 13.5.0(vue@3.5.17(typescript@5.8.3))
- '@vueuse/shared': 13.5.0(vue@3.5.17(typescript@5.8.3))
- vue: 3.5.17(typescript@5.8.3)
+ '@vueuse/core': 12.8.2(typescript@6.0.3)
+ '@vueuse/shared': 12.8.2(typescript@6.0.3)
+ vue: 3.5.43(typescript@6.0.3)
optionalDependencies:
- axios: 1.10.0(debug@4.4.1)
- focus-trap: 7.6.5
- fuse.js: 7.1.0
- nprogress: 0.2.0
- qrcode: 1.5.4
-
- '@vueuse/metadata@10.11.1': {}
+ focus-trap: 7.8.0
+ transitivePeerDependencies:
+ - typescript
- '@vueuse/metadata@13.5.0': {}
+ '@vueuse/metadata@12.8.2': {}
- '@vueuse/shared@10.11.1(vue@3.5.17(typescript@5.8.3))':
+ '@vueuse/shared@12.8.2(typescript@6.0.3)':
dependencies:
- vue-demi: 0.14.10(vue@3.5.17(typescript@5.8.3))
+ vue: 3.5.43(typescript@6.0.3)
transitivePeerDependencies:
- - '@vue/composition-api'
- - vue
-
- '@vueuse/shared@13.5.0(vue@3.5.17(typescript@5.8.3))':
- dependencies:
- vue: 3.5.17(typescript@5.8.3)
+ - typescript
- acorn-jsx@5.3.2(acorn@8.15.0):
+ acorn-jsx@5.3.2(acorn@8.18.0):
dependencies:
- acorn: 8.15.0
-
- acorn@8.15.0: {}
+ acorn: 8.18.0
- agent-base@7.1.4: {}
+ acorn@8.18.0: {}
- ajv@6.12.6:
+ ajv@6.15.0:
dependencies:
fast-deep-equal: 3.1.3
fast-json-stable-stringify: 2.1.0
json-schema-traverse: 0.4.1
uri-js: 4.4.1
- ajv@8.17.1:
- dependencies:
- fast-deep-equal: 3.1.3
- fast-uri: 3.0.6
- json-schema-traverse: 1.0.0
- require-from-string: 2.0.2
+ algoliasearch@5.59.0:
+ dependencies:
+ '@algolia/abtesting': 1.25.0
+ '@algolia/client-abtesting': 5.59.0
+ '@algolia/client-analytics': 5.59.0
+ '@algolia/client-common': 5.59.0
+ '@algolia/client-insights': 5.59.0
+ '@algolia/client-personalization': 5.59.0
+ '@algolia/client-query-suggestions': 5.59.0
+ '@algolia/client-search': 5.59.0
+ '@algolia/ingestion': 1.59.0
+ '@algolia/monitoring': 1.59.0
+ '@algolia/recommend': 5.59.0
+ '@algolia/requester-browser-xhr': 5.59.0
+ '@algolia/requester-fetch': 5.59.0
+ '@algolia/requester-node-http': 5.59.0
+
+ alien-signals@3.2.1: {}
- algoliasearch@5.34.0:
+ argparse@1.0.10:
dependencies:
- '@algolia/client-abtesting': 5.34.0
- '@algolia/client-analytics': 5.34.0
- '@algolia/client-common': 5.34.0
- '@algolia/client-insights': 5.34.0
- '@algolia/client-personalization': 5.34.0
- '@algolia/client-query-suggestions': 5.34.0
- '@algolia/client-search': 5.34.0
- '@algolia/ingestion': 1.34.0
- '@algolia/monitoring': 1.34.0
- '@algolia/recommend': 5.34.0
- '@algolia/requester-browser-xhr': 5.34.0
- '@algolia/requester-fetch': 5.34.0
- '@algolia/requester-node-http': 5.34.0
-
- alien-signals@1.0.13: {}
+ sprintf-js: 1.0.3
- ansi-escapes@7.0.0:
- dependencies:
- environment: 1.1.0
+ balanced-match@4.0.4: {}
- ansi-regex@5.0.1: {}
+ birpc@2.9.0: {}
- ansi-regex@6.1.0: {}
+ boolbase@1.0.0: {}
- ansi-styles@4.3.0:
+ brace-expansion@5.0.12:
dependencies:
- color-convert: 2.0.1
-
- ansi-styles@6.2.1: {}
+ balanced-match: 4.0.4
- ansis@4.1.0: {}
-
- anymatch@3.1.3:
+ cacheable@2.5.0:
dependencies:
- normalize-path: 3.0.0
- picomatch: 2.3.1
+ '@cacheable/memory': 2.2.0
+ '@cacheable/utils': 2.5.0
+ hookified: 1.15.1
+ keyv: 5.6.0
+ qified: 0.10.1
- argparse@1.0.10:
- dependencies:
- sprintf-js: 1.0.3
+ ccount@2.0.1: {}
- argparse@2.0.1: {}
+ character-entities-html4@2.1.0: {}
- ast-kit@2.1.1:
- dependencies:
- '@babel/parser': 7.28.0
- pathe: 2.0.3
+ character-entities-legacy@3.0.0: {}
- ast-walker-scope@0.8.1:
+ chevrotain@11.1.2:
dependencies:
- '@babel/parser': 7.28.0
- ast-kit: 2.1.1
+ '@chevrotain/cst-dts-gen': 11.1.2
+ '@chevrotain/gast': 11.1.2
+ '@chevrotain/regexp-to-ast': 11.1.2
+ '@chevrotain/types': 11.1.2
+ '@chevrotain/utils': 11.1.2
+ lodash-es: 4.17.23
- astral-regex@2.0.0: {}
+ comma-separated-tokens@2.0.3: {}
- async@3.2.6: {}
+ commander@7.2.0: {}
- asynckit@0.4.0: {}
+ commander@8.3.0: {}
- axios@1.10.0(debug@4.4.1):
- dependencies:
- follow-redirects: 1.15.9(debug@4.4.1)
- form-data: 4.0.4
- proxy-from-env: 1.1.0
- transitivePeerDependencies:
- - debug
+ copy-anything@4.1.3: {}
- balanced-match@1.0.2: {}
+ cose-base@1.0.3:
+ dependencies:
+ layout-base: 1.0.2
- beasties@0.3.5:
+ cose-base@2.2.0:
dependencies:
- css-select: 6.0.0
- css-what: 7.0.0
- dom-serializer: 2.0.0
- domhandler: 5.0.3
- htmlparser2: 10.0.0
- picocolors: 1.1.1
- postcss: 8.5.6
- postcss-media-query-parser: 0.2.3
+ layout-base: 2.0.1
- before-after-hook@3.0.2: {}
+ cross-spawn@7.0.6:
+ dependencies:
+ path-key: 3.1.1
+ shebang-command: 2.0.0
+ which: 2.0.2
- binary-extensions@2.3.0: {}
+ cssesc@3.0.0: {}
- birpc@2.5.0: {}
+ csstype@3.2.3: {}
- blueimp-md5@2.19.0: {}
-
- body-parser@2.2.0:
- dependencies:
- bytes: 3.1.2
- content-type: 1.0.5
- debug: 4.4.1(supports-color@5.5.0)
- http-errors: 2.0.0
- iconv-lite: 0.6.3
- on-finished: 2.4.1
- qs: 6.14.0
- raw-body: 3.0.0
- type-is: 2.0.1
- transitivePeerDependencies:
- - supports-color
-
- boolbase@1.0.0: {}
-
- brace-expansion@1.1.12:
- dependencies:
- balanced-match: 1.0.2
- concat-map: 0.0.1
-
- brace-expansion@2.0.2:
- dependencies:
- balanced-match: 1.0.2
-
- braces@3.0.3:
- dependencies:
- fill-range: 7.1.1
-
- browserslist@4.25.1:
- dependencies:
- caniuse-lite: 1.0.30001727
- electron-to-chromium: 1.5.187
- node-releases: 2.0.19
- update-browserslist-db: 1.1.3(browserslist@4.25.1)
-
- buffer-from@1.1.2: {}
-
- bundle-name@4.1.0:
- dependencies:
- run-applescript: 7.0.0
-
- bytes@3.1.2: {}
-
- cac@6.7.14: {}
-
- call-bind-apply-helpers@1.0.2:
- dependencies:
- es-errors: 1.3.0
- function-bind: 1.1.2
-
- call-bound@1.0.4:
- dependencies:
- call-bind-apply-helpers: 1.0.2
- get-intrinsic: 1.3.0
-
- callsites@3.1.0: {}
-
- camel-case@4.1.2:
- dependencies:
- pascal-case: 3.1.2
- tslib: 2.8.1
-
- camelcase@5.3.1: {}
-
- camelcase@6.3.0: {}
-
- caniuse-lite@1.0.30001727: {}
-
- ccount@2.0.1: {}
-
- chalk@4.1.2:
- dependencies:
- ansi-styles: 4.3.0
- supports-color: 7.2.0
-
- chalk@5.4.1: {}
-
- character-entities-html4@2.1.0: {}
-
- character-entities-legacy@3.0.0: {}
-
- charenc@0.0.2: {}
-
- chevrotain-allstar@0.3.1(chevrotain@11.0.3):
- dependencies:
- chevrotain: 11.0.3
- lodash-es: 4.17.21
-
- chevrotain@11.0.3:
- dependencies:
- '@chevrotain/cst-dts-gen': 11.0.3
- '@chevrotain/gast': 11.0.3
- '@chevrotain/regexp-to-ast': 11.0.3
- '@chevrotain/types': 11.0.3
- '@chevrotain/utils': 11.0.3
- lodash-es: 4.17.21
-
- chokidar@3.6.0:
- dependencies:
- anymatch: 3.1.3
- braces: 3.0.3
- glob-parent: 5.1.2
- is-binary-path: 2.1.0
- is-glob: 4.0.3
- normalize-path: 3.0.0
- readdirp: 3.6.0
- optionalDependencies:
- fsevents: 2.3.3
-
- chokidar@4.0.3:
- dependencies:
- readdirp: 4.1.2
-
- clean-css@5.3.3:
- dependencies:
- source-map: 0.6.1
-
- cli-cursor@5.0.0:
- dependencies:
- restore-cursor: 5.1.0
-
- cli-spinners@2.9.2: {}
-
- cli-truncate@4.0.0:
- dependencies:
- slice-ansi: 5.0.0
- string-width: 7.2.0
-
- cliui@6.0.0:
- dependencies:
- string-width: 4.2.3
- strip-ansi: 6.0.1
- wrap-ansi: 6.2.0
-
- cliui@9.0.1:
- dependencies:
- string-width: 7.2.0
- strip-ansi: 7.1.0
- wrap-ansi: 9.0.0
-
- color-convert@2.0.1:
- dependencies:
- color-name: 1.1.4
-
- color-name@1.1.4: {}
-
- colorette@2.0.20: {}
-
- combined-stream@1.0.8:
- dependencies:
- delayed-stream: 1.0.0
-
- comma-separated-tokens@2.0.3: {}
-
- commander@10.0.1: {}
-
- commander@14.0.0: {}
-
- commander@2.20.3: {}
-
- commander@7.2.0: {}
-
- commander@8.3.0: {}
-
- concat-map@0.0.1: {}
-
- confbox@0.1.8: {}
-
- confbox@0.2.2: {}
-
- consola@3.4.2: {}
-
- content-type@1.0.5: {}
-
- convert-source-map@2.0.0: {}
-
- copy-anything@3.0.5:
- dependencies:
- is-what: 4.1.16
-
- cors@2.8.5:
- dependencies:
- object-assign: 4.1.1
- vary: 1.1.2
-
- cose-base@1.0.3:
- dependencies:
- layout-base: 1.0.2
-
- cose-base@2.2.0:
- dependencies:
- layout-base: 2.0.1
-
- cross-spawn@7.0.6:
- dependencies:
- path-key: 3.1.1
- shebang-command: 2.0.0
- which: 2.0.2
-
- crypt@0.0.2: {}
-
- css-i18n@0.0.5: {}
-
- css-select@6.0.0:
- dependencies:
- boolbase: 1.0.0
- css-what: 7.0.0
- domhandler: 5.0.3
- domutils: 3.2.2
- nth-check: 2.1.1
-
- css-tree@3.1.0:
- dependencies:
- mdn-data: 2.12.2
- source-map-js: 1.2.1
-
- css-what@7.0.0: {}
-
- cssstyle@4.6.0:
- dependencies:
- '@asamuzakjp/css-color': 3.2.0
- rrweb-cssom: 0.8.0
-
- csstype@3.1.3: {}
-
- cytoscape-cose-bilkent@4.1.0(cytoscape@3.32.1):
+ cytoscape-cose-bilkent@4.1.0(cytoscape@3.34.3):
dependencies:
cose-base: 1.0.3
- cytoscape: 3.32.1
+ cytoscape: 3.34.3
- cytoscape-fcose@2.2.0(cytoscape@3.32.1):
+ cytoscape-fcose@2.2.0(cytoscape@3.34.3):
dependencies:
cose-base: 2.2.0
- cytoscape: 3.32.1
+ cytoscape: 3.34.3
- cytoscape@3.32.1: {}
+ cytoscape@3.34.3: {}
d3-array@2.12.1:
dependencies:
@@ -6396,7 +3028,7 @@ snapshots:
d3-delaunay@6.0.4:
dependencies:
- delaunator: 5.0.1
+ delaunator: 5.1.0
d3-dispatch@3.0.1: {}
@@ -6423,7 +3055,7 @@ snapshots:
d3-quadtree: 3.0.1
d3-timer: 3.0.1
- d3-format@3.1.0: {}
+ d3-format@3.1.2: {}
d3-geo@3.1.1:
dependencies:
@@ -6458,7 +3090,7 @@ snapshots:
d3-scale@4.0.2:
dependencies:
d3-array: 3.2.4
- d3-format: 3.1.0
+ d3-format: 3.1.2
d3-interpolate: 3.0.1
d3-time: 3.1.0
d3-time-format: 4.1.0
@@ -6515,7 +3147,7 @@ snapshots:
d3-ease: 3.0.1
d3-fetch: 3.0.1
d3-force: 3.0.0
- d3-format: 3.1.0
+ d3-format: 3.1.2
d3-geo: 3.1.1
d3-hierarchy: 3.1.2
d3-interpolate: 3.0.1
@@ -6533,139 +3165,40 @@ snapshots:
d3-transition: 3.0.1(d3-selection@3.0.0)
d3-zoom: 3.0.0
- dagre-d3-es@7.0.11:
+ dagre-d3-es@7.0.14:
dependencies:
d3: 7.9.0
- lodash-es: 4.17.21
-
- data-urls@5.0.0:
- dependencies:
- whatwg-mimetype: 4.0.0
- whatwg-url: 14.2.0
-
- dayjs@1.11.13: {}
+ lodash-es: 4.18.1
- de-indent@1.0.2: {}
+ dayjs@1.11.23: {}
- debug@4.4.1(supports-color@5.5.0):
+ debug@4.4.3:
dependencies:
ms: 2.1.3
- optionalDependencies:
- supports-color: 5.5.0
-
- decamelize@1.2.0: {}
-
- decimal.js@10.6.0: {}
deep-is@0.1.4: {}
- deepmerge@4.3.1: {}
-
- default-browser-id@5.0.0: {}
-
- default-browser@5.2.1:
- dependencies:
- bundle-name: 4.1.0
- default-browser-id: 5.0.0
-
- define-lazy-prop@3.0.0: {}
-
- defu@6.1.4: {}
-
- delaunator@5.0.1:
+ delaunator@5.1.0:
dependencies:
- robust-predicates: 3.0.2
-
- delayed-stream@1.0.0: {}
-
- depd@2.0.0: {}
+ robust-predicates: 3.0.3
dequal@2.0.3: {}
- destr@2.0.5: {}
-
- detect-libc@1.0.3:
- optional: true
-
devlop@1.1.0:
dependencies:
dequal: 2.0.3
- dijkstrajs@1.0.3: {}
-
- dom-serializer@2.0.0:
- dependencies:
- domelementtype: 2.3.0
- domhandler: 5.0.3
- entities: 4.5.0
-
- domelementtype@2.3.0: {}
-
- domhandler@5.0.3:
- dependencies:
- domelementtype: 2.3.0
-
- dompurify@3.2.6:
+ dompurify@3.4.16:
optionalDependencies:
'@types/trusted-types': 2.0.7
- domutils@3.2.2:
- dependencies:
- dom-serializer: 2.0.0
- domelementtype: 2.3.0
- domhandler: 5.0.3
-
- dot-case@3.0.4:
- dependencies:
- no-case: 3.0.4
- tslib: 2.8.1
-
- dunder-proto@1.0.1:
- dependencies:
- call-bind-apply-helpers: 1.0.2
- es-errors: 1.3.0
- gopd: 1.2.0
-
- duplexer@0.1.2: {}
-
- ee-first@1.1.1: {}
-
- ejs@3.1.10:
- dependencies:
- jake: 10.9.2
-
- electron-to-chromium@1.5.187: {}
-
- email-validator@2.0.4: {}
+ elkjs@0.9.3: {}
emoji-regex-xs@1.0.0: {}
- emoji-regex@10.4.0: {}
-
- emoji-regex@8.0.0: {}
-
- entities@4.5.0: {}
-
- entities@6.0.1: {}
+ entities@7.0.1: {}
- environment@1.1.0: {}
-
- error-stack-parser-es@0.1.5: {}
-
- es-define-property@1.0.1: {}
-
- es-errors@1.3.0: {}
-
- es-object-atoms@1.1.1:
- dependencies:
- es-errors: 1.3.0
-
- es-set-tostringtag@2.1.0:
- dependencies:
- es-errors: 1.3.0
- get-intrinsic: 1.3.0
- has-tostringtag: 1.0.2
- hasown: 2.0.2
+ es-toolkit@1.52.0: {}
esbuild@0.21.5:
optionalDependencies:
@@ -6693,115 +3226,80 @@ snapshots:
'@esbuild/win32-ia32': 0.21.5
'@esbuild/win32-x64': 0.21.5
- esbuild@0.25.8:
- optionalDependencies:
- '@esbuild/aix-ppc64': 0.25.8
- '@esbuild/android-arm': 0.25.8
- '@esbuild/android-arm64': 0.25.8
- '@esbuild/android-x64': 0.25.8
- '@esbuild/darwin-arm64': 0.25.8
- '@esbuild/darwin-x64': 0.25.8
- '@esbuild/freebsd-arm64': 0.25.8
- '@esbuild/freebsd-x64': 0.25.8
- '@esbuild/linux-arm': 0.25.8
- '@esbuild/linux-arm64': 0.25.8
- '@esbuild/linux-ia32': 0.25.8
- '@esbuild/linux-loong64': 0.25.8
- '@esbuild/linux-mips64el': 0.25.8
- '@esbuild/linux-ppc64': 0.25.8
- '@esbuild/linux-riscv64': 0.25.8
- '@esbuild/linux-s390x': 0.25.8
- '@esbuild/linux-x64': 0.25.8
- '@esbuild/netbsd-arm64': 0.25.8
- '@esbuild/netbsd-x64': 0.25.8
- '@esbuild/openbsd-arm64': 0.25.8
- '@esbuild/openbsd-x64': 0.25.8
- '@esbuild/openharmony-arm64': 0.25.8
- '@esbuild/sunos-x64': 0.25.8
- '@esbuild/win32-arm64': 0.25.8
- '@esbuild/win32-ia32': 0.25.8
- '@esbuild/win32-x64': 0.25.8
-
- escalade@3.2.0: {}
-
- escape-html@1.0.3: {}
-
escape-string-regexp@4.0.0: {}
- escodegen@2.1.0:
+ eslint-config-prettier@10.1.8(eslint@10.11.0):
dependencies:
- esprima: 4.0.1
- estraverse: 5.3.0
- esutils: 2.0.3
+ eslint: 10.11.0
+
+ eslint-plugin-vue@10.11.1(@typescript-eslint/parser@8.70.1(eslint@10.11.0)(typescript@6.0.3))(eslint@10.11.0)(vue-eslint-parser@10.4.1(eslint@10.11.0)):
+ dependencies:
+ '@eslint-community/eslint-utils': 4.10.1(eslint@10.11.0)
+ eslint: 10.11.0
+ natural-compare: 1.4.0
+ nth-check: 2.1.1
+ postcss-selector-parser: 7.1.6
+ semver: 7.8.5
+ vue-eslint-parser: 10.4.1(eslint@10.11.0)
+ xml-name-validator: 5.0.0
optionalDependencies:
- source-map: 0.6.1
+ '@typescript-eslint/parser': 8.70.1(eslint@10.11.0)(typescript@6.0.3)
- eslint-scope@8.4.0:
+ eslint-scope@9.1.2:
dependencies:
+ '@types/esrecurse': 4.3.1
+ '@types/estree': 1.0.9
esrecurse: 4.3.0
estraverse: 5.3.0
eslint-visitor-keys@3.4.3: {}
- eslint-visitor-keys@4.2.1: {}
+ eslint-visitor-keys@5.0.1: {}
- eslint@9.29.0(jiti@2.4.2):
+ eslint@10.11.0:
dependencies:
- '@eslint-community/eslint-utils': 4.7.0(eslint@9.29.0(jiti@2.4.2))
- '@eslint-community/regexpp': 4.12.1
- '@eslint/config-array': 0.20.1
- '@eslint/config-helpers': 0.2.3
- '@eslint/core': 0.14.0
- '@eslint/eslintrc': 3.3.1
- '@eslint/js': 9.29.0
- '@eslint/plugin-kit': 0.3.3
- '@humanfs/node': 0.16.6
+ '@eslint-community/eslint-utils': 4.10.1(eslint@10.11.0)
+ '@eslint-community/regexpp': 4.12.2
+ '@eslint/config-array': 0.23.5
+ '@eslint/config-helpers': 0.7.0
+ '@eslint/core': 1.2.1
+ '@eslint/plugin-kit': 0.7.3
+ '@humanfs/node': 0.16.8
'@humanwhocodes/module-importer': 1.0.1
'@humanwhocodes/retry': 0.4.3
- '@types/estree': 1.0.8
- '@types/json-schema': 7.0.15
- ajv: 6.12.6
- chalk: 4.1.2
+ '@types/estree': 1.0.9
+ ajv: 6.15.0
cross-spawn: 7.0.6
- debug: 4.4.1(supports-color@5.5.0)
+ debug: 4.4.3
escape-string-regexp: 4.0.0
- eslint-scope: 8.4.0
- eslint-visitor-keys: 4.2.1
- espree: 10.4.0
- esquery: 1.6.0
+ eslint-scope: 9.1.2
+ eslint-visitor-keys: 5.0.1
+ espree: 11.2.0
+ esquery: 1.7.0
esutils: 2.0.3
fast-deep-equal: 3.1.3
- file-entry-cache: 8.0.0
+ file-entry-cache: 11.1.5
find-up: 5.0.0
glob-parent: 6.0.2
ignore: 5.3.2
imurmurhash: 0.1.4
is-glob: 4.0.3
json-stable-stringify-without-jsonify: 1.0.1
- lodash.merge: 4.6.2
- minimatch: 3.1.2
+ minimatch: 10.2.6
natural-compare: 1.4.0
optionator: 0.9.4
- optionalDependencies:
- jiti: 2.4.2
transitivePeerDependencies:
- supports-color
- espree@10.4.0:
- dependencies:
- acorn: 8.15.0
- acorn-jsx: 5.3.2(acorn@8.15.0)
- eslint-visitor-keys: 4.2.1
-
- espree@9.6.1:
+ espree@11.2.0:
dependencies:
- acorn: 8.15.0
- acorn-jsx: 5.3.2(acorn@8.15.0)
- eslint-visitor-keys: 3.4.3
+ acorn: 8.18.0
+ acorn-jsx: 5.3.2(acorn@8.18.0)
+ eslint-visitor-keys: 5.0.1
esprima@4.0.1: {}
- esquery@1.6.0:
+ esquery@1.7.0:
dependencies:
estraverse: 5.3.0
@@ -6813,1925 +3311,567 @@ snapshots:
estree-walker@2.0.2: {}
- estree-walker@3.0.3:
- dependencies:
- '@types/estree': 1.0.8
-
esutils@2.0.3: {}
- eventemitter3@4.0.7: {}
-
- eventemitter3@5.0.1: {}
-
- execa@9.6.0:
- dependencies:
- '@sindresorhus/merge-streams': 4.0.0
- cross-spawn: 7.0.6
- figures: 6.1.0
- get-stream: 9.0.1
- human-signals: 8.0.1
- is-plain-obj: 4.1.0
- is-stream: 4.0.1
- npm-run-path: 6.0.0
- pretty-ms: 9.2.0
- signal-exit: 4.1.0
- strip-final-newline: 4.0.0
- yoctocolors: 2.1.1
-
- exsolve@1.0.7: {}
-
extend-shallow@2.0.1:
dependencies:
is-extendable: 0.1.1
- fast-content-type-parse@2.0.1: {}
-
fast-deep-equal@3.1.3: {}
- fast-glob@3.3.3:
- dependencies:
- '@nodelib/fs.stat': 2.0.5
- '@nodelib/fs.walk': 1.2.8
- glob-parent: 5.1.2
- merge2: 1.4.1
- micromatch: 4.0.8
-
fast-json-stable-stringify@2.1.0: {}
fast-levenshtein@2.0.6: {}
- fast-uri@3.0.6: {}
-
- fastq@1.19.1:
- dependencies:
- reusify: 1.1.0
-
- fdir@6.4.6(picomatch@4.0.3):
+ fdir@6.5.0(picomatch@4.0.7):
optionalDependencies:
- picomatch: 4.0.3
-
- feed@5.1.0:
- dependencies:
- xml-js: 1.6.11
-
- figures@6.1.0:
- dependencies:
- is-unicode-supported: 2.1.0
-
- file-entry-cache@8.0.0:
- dependencies:
- flat-cache: 4.0.1
-
- filelist@1.0.4:
- dependencies:
- minimatch: 5.1.6
-
- fill-range@7.1.1:
- dependencies:
- to-regex-range: 5.0.1
+ picomatch: 4.0.7
- find-up@4.1.0:
+ file-entry-cache@11.1.5:
dependencies:
- locate-path: 5.0.0
- path-exists: 4.0.0
+ flat-cache: 6.1.23
find-up@5.0.0:
dependencies:
locate-path: 6.0.0
path-exists: 4.0.0
- flat-cache@4.0.1:
- dependencies:
- flatted: 3.3.3
- keyv: 4.5.4
-
- flatted@3.3.3: {}
-
- floating-vue@5.2.2(vue@3.5.17(typescript@5.8.3)):
- dependencies:
- '@floating-ui/dom': 1.1.1
- vue: 3.5.17(typescript@5.8.3)
- vue-resize: 2.0.0-alpha.1(vue@3.5.17(typescript@5.8.3))
-
- focus-trap@7.6.5:
+ flat-cache@6.1.23:
dependencies:
- tabbable: 6.2.0
-
- follow-redirects@1.15.9(debug@4.4.1):
- optionalDependencies:
- debug: 4.4.1(supports-color@5.5.0)
+ cacheable: 2.5.0
+ flatted: 3.4.4
+ hookified: 1.15.1
- form-data@4.0.4:
- dependencies:
- asynckit: 0.4.0
- combined-stream: 1.0.8
- es-set-tostringtag: 2.1.0
- hasown: 2.0.2
- mime-types: 2.1.35
+ flatted@3.4.4: {}
- fs-extra@11.3.0:
+ focus-trap@7.8.0:
dependencies:
- graceful-fs: 4.2.11
- jsonfile: 6.1.0
- universalify: 2.0.1
+ tabbable: 6.5.0
fsevents@2.3.3:
optional: true
- function-bind@1.1.2: {}
-
- fuse.js@7.1.0: {}
-
- gensync@1.0.0-beta.2: {}
-
- get-caller-file@2.0.5: {}
-
- get-east-asian-width@1.3.0: {}
-
- get-intrinsic@1.3.0:
- dependencies:
- call-bind-apply-helpers: 1.0.2
- es-define-property: 1.0.1
- es-errors: 1.3.0
- es-object-atoms: 1.1.1
- function-bind: 1.1.2
- get-proto: 1.0.1
- gopd: 1.2.0
- has-symbols: 1.1.0
- hasown: 2.0.2
- math-intrinsics: 1.1.0
-
- get-proto@1.0.1:
- dependencies:
- dunder-proto: 1.0.1
- es-object-atoms: 1.1.1
-
- get-stream@9.0.1:
- dependencies:
- '@sec-ant/readable-stream': 0.4.1
- is-stream: 4.0.1
-
giscus@1.6.0:
dependencies:
- lit: 3.3.1
-
- glob-parent@5.1.2:
- dependencies:
- is-glob: 4.0.3
+ lit: 3.3.3
glob-parent@6.0.2:
dependencies:
is-glob: 4.0.3
- global-directory@4.0.1:
- dependencies:
- ini: 4.1.1
-
- globals@14.0.0: {}
-
- globals@15.15.0: {}
-
- gopd@1.2.0: {}
-
- graceful-fs@4.2.11: {}
-
- gravatar@1.8.2:
- dependencies:
- blueimp-md5: 2.19.0
- email-validator: 2.0.4
- querystring: 0.2.0
- yargs: 15.4.1
+ globals@17.12.0: {}
gray-matter@4.0.3:
dependencies:
- js-yaml: 3.14.1
+ js-yaml: 3.15.2
kind-of: 6.0.3
section-matter: 1.0.0
strip-bom-string: 1.0.0
- gzip-size@6.0.0:
- dependencies:
- duplexer: 0.1.2
-
hachure-fill@0.5.2: {}
- has-flag@3.0.0: {}
-
- has-flag@4.0.0: {}
-
- has-symbols@1.1.0: {}
-
- has-tostringtag@1.0.2:
+ hashery@1.5.1:
dependencies:
- has-symbols: 1.1.0
-
- hasown@2.0.2:
- dependencies:
- function-bind: 1.1.2
+ hookified: 1.15.1
hast-util-to-html@9.0.5:
dependencies:
- '@types/hast': 3.0.4
+ '@types/hast': 3.0.5
'@types/unist': 3.0.3
ccount: 2.0.1
comma-separated-tokens: 2.0.3
hast-util-whitespace: 3.0.0
html-void-elements: 3.0.0
- mdast-util-to-hast: 13.2.0
- property-information: 7.1.0
+ mdast-util-to-hast: 13.2.1
+ property-information: 7.2.0
space-separated-tokens: 2.0.2
stringify-entities: 4.0.4
zwitch: 2.0.4
hast-util-whitespace@3.0.0:
dependencies:
- '@types/hast': 3.0.4
-
- he@1.2.0: {}
+ '@types/hast': 3.0.5
hookable@5.5.3: {}
- html-encoding-sniffer@4.0.0:
- dependencies:
- whatwg-encoding: 3.1.1
-
- html-minifier-terser@7.2.0:
- dependencies:
- camel-case: 4.1.2
- clean-css: 5.3.3
- commander: 10.0.1
- entities: 4.5.0
- param-case: 3.0.4
- relateurl: 0.2.7
- terser: 5.43.1
+ hookified@1.15.1: {}
- html-to-text@9.0.5:
- dependencies:
- '@selderee/plugin-htmlparser2': 0.11.0
- deepmerge: 4.3.1
- dom-serializer: 2.0.0
- htmlparser2: 8.0.2
- selderee: 0.11.0
+ hookified@2.2.0: {}
html-void-elements@3.0.0: {}
- html5parser@2.0.2:
- dependencies:
- tslib: 2.8.1
+ husky@9.1.7: {}
- htmlparser2@10.0.0:
+ iconv-lite@0.6.3:
dependencies:
- domelementtype: 2.3.0
- domhandler: 5.0.3
- domutils: 3.2.2
- entities: 6.0.1
+ safer-buffer: 2.1.2
- htmlparser2@8.0.2:
- dependencies:
- domelementtype: 2.3.0
- domhandler: 5.0.3
- domutils: 3.2.2
- entities: 4.5.0
+ ignore@5.3.2: {}
- http-errors@2.0.0:
- dependencies:
- depd: 2.0.0
- inherits: 2.0.4
- setprototypeof: 1.2.0
- statuses: 2.0.1
- toidentifier: 1.0.1
+ ignore@7.0.10: {}
- http-proxy-agent@7.0.2:
- dependencies:
- agent-base: 7.1.4
- debug: 4.4.1(supports-color@5.5.0)
- transitivePeerDependencies:
- - supports-color
+ import-meta-resolve@4.2.0: {}
- http-proxy-middleware@3.0.5:
- dependencies:
- '@types/http-proxy': 1.17.16
- debug: 4.4.1(supports-color@5.5.0)
- http-proxy: 1.18.1(debug@4.4.1)
- is-glob: 4.0.3
- is-plain-object: 5.0.0
- micromatch: 4.0.8
- transitivePeerDependencies:
- - supports-color
-
- http-proxy@1.18.1(debug@4.4.1):
- dependencies:
- eventemitter3: 4.0.7
- follow-redirects: 1.15.9(debug@4.4.1)
- requires-port: 1.0.0
- transitivePeerDependencies:
- - debug
-
- https-proxy-agent@7.0.6:
- dependencies:
- agent-base: 7.1.4
- debug: 4.4.1(supports-color@5.5.0)
- transitivePeerDependencies:
- - supports-color
-
- human-signals@8.0.1: {}
-
- husky@9.1.7: {}
-
- iconv-lite@0.6.3:
- dependencies:
- safer-buffer: 2.1.2
-
- ignore-by-default@1.0.1: {}
-
- ignore@5.3.2: {}
-
- immutable@5.1.3: {}
-
- import-fresh@3.3.1:
- dependencies:
- parent-module: 1.0.1
- resolve-from: 4.0.0
-
- imurmurhash@0.1.4: {}
-
- inherits@2.0.4: {}
-
- ini@4.1.1: {}
+ imurmurhash@0.1.4: {}
internmap@1.0.1: {}
internmap@2.0.3: {}
- is-binary-path@2.1.0:
- dependencies:
- binary-extensions: 2.3.0
-
- is-buffer@1.1.6: {}
-
- is-docker@3.0.0: {}
-
is-extendable@0.1.1: {}
is-extglob@2.1.1: {}
- is-fullwidth-code-point@3.0.0: {}
-
- is-fullwidth-code-point@4.0.0: {}
-
- is-fullwidth-code-point@5.0.0:
- dependencies:
- get-east-asian-width: 1.3.0
-
is-glob@4.0.3:
dependencies:
is-extglob: 2.1.1
- is-inside-container@1.0.0:
- dependencies:
- is-docker: 3.0.0
-
- is-interactive@2.0.0: {}
-
- is-number@7.0.0: {}
-
- is-plain-obj@4.1.0: {}
-
- is-plain-object@5.0.0: {}
-
- is-potential-custom-element-name@1.0.1: {}
-
- is-stream@4.0.1: {}
-
- is-unicode-supported@1.3.0: {}
-
- is-unicode-supported@2.1.0: {}
-
- is-what@4.1.16: {}
-
- is-wsl@3.1.0:
- dependencies:
- is-inside-container: 1.0.0
-
isexe@2.0.0: {}
- jake@10.9.2:
- dependencies:
- async: 3.2.6
- chalk: 4.1.2
- filelist: 1.0.4
- minimatch: 3.1.2
-
- jiti@2.4.2: {}
-
- js-base64@3.7.7: {}
-
- js-tokens@4.0.0: {}
-
- js-yaml@3.14.1:
+ js-yaml@3.15.2:
dependencies:
argparse: 1.0.10
esprima: 4.0.1
- js-yaml@4.1.0:
- dependencies:
- argparse: 2.0.1
-
- jsdom@26.1.0:
- dependencies:
- cssstyle: 4.6.0
- data-urls: 5.0.0
- decimal.js: 10.6.0
- html-encoding-sniffer: 4.0.0
- http-proxy-agent: 7.0.2
- https-proxy-agent: 7.0.6
- is-potential-custom-element-name: 1.0.1
- nwsapi: 2.2.20
- parse5: 7.3.0
- rrweb-cssom: 0.8.0
- saxes: 6.0.0
- symbol-tree: 3.2.4
- tough-cookie: 5.1.2
- w3c-xmlserializer: 5.0.0
- webidl-conversions: 7.0.0
- whatwg-encoding: 3.1.1
- whatwg-mimetype: 4.0.0
- whatwg-url: 14.2.0
- ws: 8.18.3
- xml-name-validator: 5.0.0
- transitivePeerDependencies:
- - bufferutil
- - supports-color
- - utf-8-validate
-
- jsesc@3.1.0: {}
-
- json-buffer@3.0.1: {}
-
json-schema-traverse@0.4.1: {}
- json-schema-traverse@1.0.0: {}
-
json-stable-stringify-without-jsonify@1.0.1: {}
- json5@2.2.3: {}
-
- jsonc-eslint-parser@2.4.0:
- dependencies:
- acorn: 8.15.0
- eslint-visitor-keys: 3.4.3
- espree: 9.6.1
- semver: 7.7.2
-
- jsonfile@6.1.0:
- dependencies:
- universalify: 2.0.1
- optionalDependencies:
- graceful-fs: 4.2.11
-
- katex@0.16.22:
+ katex@0.16.47:
dependencies:
commander: 8.3.0
- keyv@4.5.4:
+ keyv@5.6.0:
dependencies:
- json-buffer: 3.0.1
+ '@keyv/serialize': 1.1.1
khroma@2.1.0: {}
kind-of@6.0.3: {}
- kolorist@1.8.0: {}
-
- langium@3.3.1:
- dependencies:
- chevrotain: 11.0.3
- chevrotain-allstar: 0.3.1(chevrotain@11.0.3)
- vscode-languageserver: 9.0.1
- vscode-languageserver-textdocument: 1.0.12
- vscode-uri: 3.0.8
-
layout-base@1.0.2: {}
layout-base@2.0.1: {}
- leac@0.6.0: {}
-
levn@0.4.1:
dependencies:
prelude-ls: 1.2.1
type-check: 0.4.0
- lilconfig@3.1.3: {}
-
- linkify-it@5.0.0:
- dependencies:
- uc.micro: 2.1.0
-
- lint-staged@16.1.2:
+ lint-staged@17.6.0:
dependencies:
- chalk: 5.4.1
- commander: 14.0.0
- debug: 4.4.1(supports-color@5.5.0)
- lilconfig: 3.1.3
- listr2: 8.3.3
- micromatch: 4.0.8
- nano-spawn: 1.0.2
- pidtree: 0.6.0
+ picomatch: 4.0.7
string-argv: 0.3.2
- yaml: 2.8.0
- transitivePeerDependencies:
- - supports-color
-
- listr2@8.3.3:
- dependencies:
- cli-truncate: 4.0.0
- colorette: 2.0.20
- eventemitter3: 5.0.1
- log-update: 6.1.0
- rfdc: 1.4.1
- wrap-ansi: 9.0.0
+ tinyexec: 1.3.1
+ optionalDependencies:
+ yaml: 2.9.1
- lit-element@4.2.1:
+ lit-element@4.2.2:
dependencies:
- '@lit-labs/ssr-dom-shim': 1.4.0
- '@lit/reactive-element': 2.1.1
- lit-html: 3.3.1
+ '@lit-labs/ssr-dom-shim': 1.6.0
+ '@lit/reactive-element': 2.1.2
+ lit-html: 3.3.3
- lit-html@3.3.1:
+ lit-html@3.3.3:
dependencies:
'@types/trusted-types': 2.0.7
- lit@3.3.1:
+ lit@3.3.3:
dependencies:
- '@lit/reactive-element': 2.1.1
- lit-element: 4.2.1
- lit-html: 3.3.1
-
- local-pkg@0.5.1:
- dependencies:
- mlly: 1.7.4
- pkg-types: 1.3.1
-
- local-pkg@1.1.1:
- dependencies:
- mlly: 1.7.4
- pkg-types: 2.2.0
- quansync: 0.2.10
-
- locate-path@5.0.0:
- dependencies:
- p-locate: 4.1.0
+ '@lit/reactive-element': 2.1.2
+ lit-element: 4.2.2
+ lit-html: 3.3.3
locate-path@6.0.0:
dependencies:
p-locate: 5.0.0
- lodash-es@4.17.21: {}
-
- lodash.merge@4.6.2: {}
+ lodash-es@4.17.23: {}
- lodash.truncate@4.4.2: {}
+ lodash-es@4.18.1: {}
- log-symbols@6.0.0:
+ magic-string@0.30.21:
dependencies:
- chalk: 5.4.1
- is-unicode-supported: 1.3.0
-
- log-update@6.1.0:
- dependencies:
- ansi-escapes: 7.0.0
- cli-cursor: 5.0.0
- slice-ansi: 7.1.0
- strip-ansi: 7.1.0
- wrap-ansi: 9.0.0
-
- lower-case@2.0.2:
- dependencies:
- tslib: 2.8.1
-
- lru-cache@10.4.3: {}
-
- lru-cache@11.1.0: {}
-
- lru-cache@5.1.1:
- dependencies:
- yallist: 3.1.1
-
- magic-string-ast@1.0.0:
- dependencies:
- magic-string: 0.30.17
-
- magic-string@0.30.17:
- dependencies:
- '@jridgewell/sourcemap-codec': 1.5.4
+ '@jridgewell/sourcemap-codec': 1.6.0
mark.js@8.11.1: {}
- markdown-it-anchor@9.2.0(@types/markdown-it@14.1.2)(markdown-it@14.1.0):
- dependencies:
- '@types/markdown-it': 14.1.2
- markdown-it: 14.1.0
-
- markdown-it-async@2.2.0:
- dependencies:
- '@types/markdown-it': 14.1.2
- markdown-it: 14.1.0
+ marked@16.4.2: {}
- markdown-it-attrs@4.3.1(markdown-it@14.1.0):
+ mdast-util-to-hast@13.2.1:
dependencies:
- markdown-it: 14.1.0
-
- markdown-it-container@4.0.0: {}
-
- markdown-it-emoji@3.0.0: {}
-
- markdown-it-footnote@4.0.0: {}
-
- markdown-it-image-figures@2.1.1(markdown-it@14.1.0):
- dependencies:
- markdown-it: 14.1.0
-
- markdown-it-table-of-contents@0.9.0: {}
-
- markdown-it-task-lists@2.1.1: {}
-
- markdown-it@14.1.0:
- dependencies:
- argparse: 2.0.1
- entities: 4.5.0
- linkify-it: 5.0.0
- mdurl: 2.0.0
- punycode.js: 2.3.1
- uc.micro: 2.1.0
-
- marked@16.1.1: {}
-
- math-intrinsics@1.1.0: {}
-
- md5@2.3.0:
- dependencies:
- charenc: 0.0.2
- crypt: 0.0.2
- is-buffer: 1.1.6
-
- mdast-util-to-hast@13.2.0:
- dependencies:
- '@types/hast': 3.0.4
+ '@types/hast': 3.0.5
'@types/mdast': 4.0.4
- '@ungap/structured-clone': 1.3.0
+ '@ungap/structured-clone': 1.4.0
devlop: 1.1.0
micromark-util-sanitize-uri: 2.0.1
trim-lines: 3.0.1
unist-util-position: 5.0.0
- unist-util-visit: 5.0.0
+ unist-util-visit: 5.1.0
vfile: 6.0.3
- mdn-data@2.12.2: {}
-
- mdurl@2.0.0: {}
-
- media-typer@1.1.0: {}
-
medium-zoom@1.1.0: {}
- merge2@1.4.1: {}
-
- mermaid@11.9.0:
+ mermaid@12.0.0:
dependencies:
- '@braintree/sanitize-url': 7.1.1
- '@iconify/utils': 2.3.0
- '@mermaid-js/parser': 0.6.2
+ '@braintree/sanitize-url': 7.1.2
+ '@iconify/utils': 3.1.7
+ '@mermaid-js/parser': 2.0.0
'@types/d3': 7.4.3
- cytoscape: 3.32.1
- cytoscape-cose-bilkent: 4.1.0(cytoscape@3.32.1)
- cytoscape-fcose: 2.2.0(cytoscape@3.32.1)
+ '@upsetjs/venn.js': 2.0.0
+ chevrotain: 11.1.2
+ cytoscape: 3.34.3
+ cytoscape-cose-bilkent: 4.1.0(cytoscape@3.34.3)
+ cytoscape-fcose: 2.2.0(cytoscape@3.34.3)
d3: 7.9.0
d3-sankey: 0.12.3
- dagre-d3-es: 7.0.11
- dayjs: 1.11.13
- dompurify: 3.2.6
- katex: 0.16.22
+ dagre-d3-es: 7.0.14
+ dayjs: 1.11.23
+ dompurify: 3.4.16
+ elkjs: 0.9.3
+ es-toolkit: 1.52.0
+ katex: 0.16.47
khroma: 2.1.0
- lodash-es: 4.17.21
- marked: 16.1.1
+ marked: 16.4.2
roughjs: 4.6.6
- stylis: 4.3.6
- ts-dedent: 2.2.0
- uuid: 11.1.0
- transitivePeerDependencies:
- - supports-color
-
- micromark-util-character@2.1.1:
- dependencies:
- micromark-util-symbol: 2.0.1
- micromark-util-types: 2.0.2
-
- micromark-util-encode@2.0.1: {}
-
- micromark-util-sanitize-uri@2.0.1:
- dependencies:
- micromark-util-character: 2.1.1
- micromark-util-encode: 2.0.1
- micromark-util-symbol: 2.0.1
-
- micromark-util-symbol@2.0.1: {}
-
- micromark-util-types@2.0.2: {}
-
- micromatch@4.0.8:
- dependencies:
- braces: 3.0.3
- picomatch: 2.3.1
-
- mime-db@1.52.0: {}
-
- mime-db@1.54.0: {}
-
- mime-types@2.1.35:
- dependencies:
- mime-db: 1.52.0
-
- mime-types@3.0.1:
- dependencies:
- mime-db: 1.54.0
-
- mimic-function@5.0.1: {}
-
- minimatch@3.1.2:
- dependencies:
- brace-expansion: 1.1.12
-
- minimatch@5.1.6:
- dependencies:
- brace-expansion: 2.0.2
-
- minimatch@9.0.5:
- dependencies:
- brace-expansion: 2.0.2
-
- minisearch@6.3.0: {}
-
- mitt@3.0.1: {}
-
- mlly@1.7.4:
- dependencies:
- acorn: 8.15.0
- pathe: 2.0.3
- pkg-types: 1.3.1
- ufo: 1.6.1
-
- mrmime@2.0.1: {}
-
- ms@2.1.3: {}
-
- muggle-string@0.4.1: {}
-
- nano-spawn@1.0.2: {}
-
- nanoid@3.3.11: {}
-
- nanoid@5.1.5: {}
-
- natural-compare@1.4.0: {}
-
- no-case@3.0.4:
- dependencies:
- lower-case: 2.0.2
- tslib: 2.8.1
-
- node-addon-api@7.1.1:
- optional: true
-
- node-fetch-native@1.6.6: {}
-
- node-releases@2.0.19: {}
-
- nodemon@3.1.10:
- dependencies:
- chokidar: 3.6.0
- debug: 4.4.1(supports-color@5.5.0)
- ignore-by-default: 1.0.1
- minimatch: 3.1.2
- pstree.remy: 1.1.8
- semver: 7.7.2
- simple-update-notifier: 2.0.0
- supports-color: 5.5.0
- touch: 3.1.1
- undefsafe: 2.0.5
-
- normalize-path@3.0.0: {}
-
- npm-run-path@6.0.0:
- dependencies:
- path-key: 4.0.0
- unicorn-magic: 0.3.0
-
- nprogress@0.2.0: {}
-
- nth-check@2.1.1:
- dependencies:
- boolbase: 1.0.0
-
- nwsapi@2.2.20: {}
-
- object-assign@4.1.1: {}
-
- object-inspect@1.13.4: {}
-
- ofetch@1.4.1:
- dependencies:
- destr: 2.0.5
- node-fetch-native: 1.6.6
- ufo: 1.6.1
-
- ohash@2.0.11: {}
-
- on-finished@2.4.1:
- dependencies:
- ee-first: 1.1.1
-
- onetime@7.0.0:
- dependencies:
- mimic-function: 5.0.1
-
- oniguruma-parser@0.12.1: {}
-
- oniguruma-to-es@2.3.0:
- dependencies:
- emoji-regex-xs: 1.0.0
- regex: 5.1.1
- regex-recursion: 5.1.1
-
- oniguruma-to-es@4.3.3:
- dependencies:
- oniguruma-parser: 0.12.1
- regex: 6.0.1
- regex-recursion: 6.0.2
-
- open@10.1.0:
- dependencies:
- default-browser: 5.2.1
- define-lazy-prop: 3.0.0
- is-inside-container: 1.0.0
- is-wsl: 3.1.0
-
- optionator@0.9.4:
- dependencies:
- deep-is: 0.1.4
- fast-levenshtein: 2.0.6
- levn: 0.4.1
- prelude-ls: 1.2.1
- type-check: 0.4.0
- word-wrap: 1.2.5
-
- ora@8.2.0:
- dependencies:
- chalk: 5.4.1
- cli-cursor: 5.0.0
- cli-spinners: 2.9.2
- is-interactive: 2.0.0
- is-unicode-supported: 2.1.0
- log-symbols: 6.0.0
- stdin-discarder: 0.2.2
- string-width: 7.2.0
- strip-ansi: 7.1.0
-
- p-limit@2.3.0:
- dependencies:
- p-try: 2.2.0
-
- p-limit@3.1.0:
- dependencies:
- yocto-queue: 0.1.0
-
- p-locate@4.1.0:
- dependencies:
- p-limit: 2.3.0
-
- p-locate@5.0.0:
- dependencies:
- p-limit: 3.1.0
-
- p-try@2.2.0: {}
-
- package-manager-detector@1.3.0: {}
-
- param-case@3.0.4:
- dependencies:
- dot-case: 3.0.4
- tslib: 2.8.1
-
- parent-module@1.0.1:
- dependencies:
- callsites: 3.1.0
-
- parse-ms@4.0.0: {}
-
- parse5@7.3.0:
- dependencies:
- entities: 6.0.1
-
- parseley@0.12.1:
- dependencies:
- leac: 0.6.0
- peberminta: 0.9.0
-
- pascal-case@3.1.2:
- dependencies:
- no-case: 3.0.4
- tslib: 2.8.1
-
- pascalcase@2.0.0:
- dependencies:
- camelcase: 6.3.0
-
- path-browserify@1.0.1: {}
-
- path-data-parser@0.1.0: {}
-
- path-exists@4.0.0: {}
-
- path-key@3.1.1: {}
-
- path-key@4.0.0: {}
-
- pathe@1.1.2: {}
-
- pathe@2.0.3: {}
-
- peberminta@0.9.0: {}
-
- perfect-debounce@1.0.0: {}
-
- picocolors@1.1.1: {}
-
- picomatch@2.3.1: {}
-
- picomatch@4.0.3: {}
-
- pidtree@0.6.0: {}
-
- pinia@3.0.3(typescript@5.8.3)(vue@3.5.17(typescript@5.8.3)):
- dependencies:
- '@vue/devtools-api': 7.7.2
- vue: 3.5.17(typescript@5.8.3)
- optionalDependencies:
- typescript: 5.8.3
-
- pkg-types@1.3.1:
- dependencies:
- confbox: 0.1.8
- mlly: 1.7.4
- pathe: 2.0.3
-
- pkg-types@2.2.0:
- dependencies:
- confbox: 0.2.2
- exsolve: 1.0.7
- pathe: 2.0.3
-
- pngjs@5.0.0: {}
-
- points-on-curve@0.2.0: {}
-
- points-on-path@0.2.1:
- dependencies:
- path-data-parser: 0.1.0
- points-on-curve: 0.2.0
-
- postcss-media-query-parser@0.2.3: {}
-
- postcss@8.5.6:
- dependencies:
- nanoid: 3.3.11
- picocolors: 1.1.1
- source-map-js: 1.2.1
-
- preact@10.26.9: {}
-
- prelude-ls@1.2.1: {}
-
- prettier@3.6.2: {}
-
- pretty-ms@9.2.0:
- dependencies:
- parse-ms: 4.0.0
-
- property-information@7.1.0: {}
-
- proxy-from-env@1.1.0: {}
-
- pstree.remy@1.1.8: {}
-
- punycode.js@2.3.1: {}
-
- punycode@2.3.1: {}
-
- qrcode@1.5.4:
- dependencies:
- dijkstrajs: 1.0.3
- pngjs: 5.0.0
- yargs: 15.4.1
-
- qs@6.14.0:
- dependencies:
- side-channel: 1.1.0
-
- quansync@0.2.10: {}
-
- querystring@0.2.0: {}
-
- queue-microtask@1.2.3: {}
-
- raw-body@3.0.0:
- dependencies:
- bytes: 3.1.2
- http-errors: 2.0.0
- iconv-lite: 0.6.3
- unpipe: 1.0.0
-
- readdirp@3.6.0:
- dependencies:
- picomatch: 2.3.1
-
- readdirp@4.1.2: {}
-
- regex-recursion@5.1.1:
- dependencies:
- regex: 5.1.1
- regex-utilities: 2.3.0
-
- regex-recursion@6.0.2:
- dependencies:
- regex-utilities: 2.3.0
-
- regex-utilities@2.3.0: {}
-
- regex@5.1.1:
- dependencies:
- regex-utilities: 2.3.0
-
- regex@6.0.1:
- dependencies:
- regex-utilities: 2.3.0
-
- relateurl@0.2.7: {}
-
- require-directory@2.1.1: {}
-
- require-from-string@2.0.2: {}
-
- require-main-filename@2.0.0: {}
-
- requires-port@1.0.0: {}
-
- resolve-from@4.0.0: {}
-
- resolve-global@2.0.0:
- dependencies:
- global-directory: 4.0.1
-
- restore-cursor@5.1.0:
- dependencies:
- onetime: 7.0.0
- signal-exit: 4.1.0
-
- reusify@1.1.0: {}
-
- rfdc@1.4.1: {}
-
- robust-predicates@3.0.2: {}
-
- rollup@4.45.1:
- dependencies:
- '@types/estree': 1.0.8
- optionalDependencies:
- '@rollup/rollup-android-arm-eabi': 4.45.1
- '@rollup/rollup-android-arm64': 4.45.1
- '@rollup/rollup-darwin-arm64': 4.45.1
- '@rollup/rollup-darwin-x64': 4.45.1
- '@rollup/rollup-freebsd-arm64': 4.45.1
- '@rollup/rollup-freebsd-x64': 4.45.1
- '@rollup/rollup-linux-arm-gnueabihf': 4.45.1
- '@rollup/rollup-linux-arm-musleabihf': 4.45.1
- '@rollup/rollup-linux-arm64-gnu': 4.45.1
- '@rollup/rollup-linux-arm64-musl': 4.45.1
- '@rollup/rollup-linux-loongarch64-gnu': 4.45.1
- '@rollup/rollup-linux-powerpc64le-gnu': 4.45.1
- '@rollup/rollup-linux-riscv64-gnu': 4.45.1
- '@rollup/rollup-linux-riscv64-musl': 4.45.1
- '@rollup/rollup-linux-s390x-gnu': 4.45.1
- '@rollup/rollup-linux-x64-gnu': 4.45.1
- '@rollup/rollup-linux-x64-musl': 4.45.1
- '@rollup/rollup-win32-arm64-msvc': 4.45.1
- '@rollup/rollup-win32-ia32-msvc': 4.45.1
- '@rollup/rollup-win32-x64-msvc': 4.45.1
- fsevents: 2.3.3
-
- roughjs@4.6.6:
- dependencies:
- hachure-fill: 0.5.2
- path-data-parser: 0.1.0
- points-on-curve: 0.2.0
- points-on-path: 0.2.1
-
- rrweb-cssom@0.8.0: {}
-
- run-applescript@7.0.0: {}
-
- run-parallel@1.2.0:
- dependencies:
- queue-microtask: 1.2.3
-
- rw@1.3.3: {}
-
- safer-buffer@2.1.2: {}
-
- sass@1.89.2:
- dependencies:
- chokidar: 4.0.3
- immutable: 5.1.3
- source-map-js: 1.2.1
- optionalDependencies:
- '@parcel/watcher': 2.5.1
-
- sax@1.4.1: {}
-
- saxes@6.0.0:
- dependencies:
- xmlchars: 2.2.0
-
- scule@1.3.0: {}
-
- search-insights@2.17.3: {}
-
- section-matter@1.0.0:
- dependencies:
- extend-shallow: 2.0.1
- kind-of: 6.0.3
-
- selderee@0.11.0:
- dependencies:
- parseley: 0.12.1
-
- semver@6.3.1: {}
-
- semver@7.7.2: {}
-
- set-blocking@2.0.0: {}
-
- setprototypeof@1.2.0: {}
-
- shebang-command@2.0.0:
- dependencies:
- shebang-regex: 3.0.0
-
- shebang-regex@3.0.0: {}
-
- shiki@1.29.2:
- dependencies:
- '@shikijs/core': 1.29.2
- '@shikijs/engine-javascript': 1.29.2
- '@shikijs/engine-oniguruma': 1.29.2
- '@shikijs/langs': 1.29.2
- '@shikijs/themes': 1.29.2
- '@shikijs/types': 1.29.2
- '@shikijs/vscode-textmate': 10.0.2
- '@types/hast': 3.0.4
-
- shiki@3.8.1:
- dependencies:
- '@shikijs/core': 3.8.1
- '@shikijs/engine-javascript': 3.8.1
- '@shikijs/engine-oniguruma': 3.8.1
- '@shikijs/langs': 3.8.1
- '@shikijs/themes': 3.8.1
- '@shikijs/types': 3.8.1
- '@shikijs/vscode-textmate': 10.0.2
- '@types/hast': 3.0.4
-
- side-channel-list@1.0.0:
- dependencies:
- es-errors: 1.3.0
- object-inspect: 1.13.4
-
- side-channel-map@1.0.1:
- dependencies:
- call-bound: 1.0.4
- es-errors: 1.3.0
- get-intrinsic: 1.3.0
- object-inspect: 1.13.4
-
- side-channel-weakmap@1.0.2:
- dependencies:
- call-bound: 1.0.4
- es-errors: 1.3.0
- get-intrinsic: 1.3.0
- object-inspect: 1.13.4
- side-channel-map: 1.0.1
-
- side-channel@1.1.0:
- dependencies:
- es-errors: 1.3.0
- object-inspect: 1.13.4
- side-channel-list: 1.0.0
- side-channel-map: 1.0.1
- side-channel-weakmap: 1.0.2
-
- signal-exit@4.1.0: {}
-
- simple-git@3.28.0:
- dependencies:
- '@kwsites/file-exists': 1.1.1
- '@kwsites/promise-deferred': 1.1.1
- debug: 4.4.1(supports-color@5.5.0)
- transitivePeerDependencies:
- - supports-color
-
- simple-update-notifier@2.0.0:
- dependencies:
- semver: 7.7.2
+ stylis: 4.4.0
+ ts-dedent: 2.3.0
+ uuid: 14.0.2
- sirv@3.0.1:
+ micromark-util-character@2.1.1:
dependencies:
- '@polka/url': 1.0.0-next.29
- mrmime: 2.0.1
- totalist: 3.0.1
-
- sisteransi@1.0.5: {}
+ micromark-util-symbol: 2.0.1
+ micromark-util-types: 2.0.2
- slice-ansi@4.0.0:
- dependencies:
- ansi-styles: 4.3.0
- astral-regex: 2.0.0
- is-fullwidth-code-point: 3.0.0
+ micromark-util-encode@2.0.1: {}
- slice-ansi@5.0.0:
+ micromark-util-sanitize-uri@2.0.1:
dependencies:
- ansi-styles: 6.2.1
- is-fullwidth-code-point: 4.0.0
+ micromark-util-character: 2.1.1
+ micromark-util-encode: 2.0.1
+ micromark-util-symbol: 2.0.1
- slice-ansi@7.1.0:
- dependencies:
- ansi-styles: 6.2.1
- is-fullwidth-code-point: 5.0.0
+ micromark-util-symbol@2.0.1: {}
- source-map-js@1.2.1: {}
+ micromark-util-types@2.0.2: {}
- source-map-support@0.5.21:
+ minimatch@10.2.6:
dependencies:
- buffer-from: 1.1.2
- source-map: 0.6.1
-
- source-map@0.6.1: {}
-
- space-separated-tokens@2.0.2: {}
+ brace-expansion: 5.0.12
- speakingurl@14.0.1: {}
+ minisearch@7.2.0: {}
- sprintf-js@1.0.3: {}
+ mitt@3.0.1: {}
- star-markdown-css@0.5.3: {}
+ ms@2.1.3: {}
- statuses@2.0.1: {}
+ muggle-string@0.4.1: {}
- stdin-discarder@0.2.2: {}
+ nanoid@3.3.19: {}
- string-argv@0.3.2: {}
+ natural-compare@1.4.0: {}
- string-width@4.2.3:
+ nth-check@2.1.1:
dependencies:
- emoji-regex: 8.0.0
- is-fullwidth-code-point: 3.0.0
- strip-ansi: 6.0.1
+ boolbase: 1.0.0
- string-width@7.2.0:
+ oniguruma-to-es@3.1.1:
dependencies:
- emoji-regex: 10.4.0
- get-east-asian-width: 1.3.0
- strip-ansi: 7.1.0
+ emoji-regex-xs: 1.0.0
+ regex: 6.1.0
+ regex-recursion: 6.0.2
- stringify-entities@4.0.4:
+ optionator@0.9.4:
dependencies:
- character-entities-html4: 2.1.0
- character-entities-legacy: 3.0.0
+ deep-is: 0.1.4
+ fast-levenshtein: 2.0.6
+ levn: 0.4.1
+ prelude-ls: 1.2.1
+ type-check: 0.4.0
+ word-wrap: 1.2.5
- strip-ansi@6.0.1:
+ p-limit@3.1.0:
dependencies:
- ansi-regex: 5.0.1
+ yocto-queue: 0.1.0
- strip-ansi@7.1.0:
+ p-locate@5.0.0:
dependencies:
- ansi-regex: 6.1.0
+ p-limit: 3.1.0
- strip-bom-string@1.0.0: {}
+ package-manager-detector@1.8.0: {}
- strip-final-newline@4.0.0: {}
+ path-browserify@1.0.1: {}
- strip-json-comments@3.1.1: {}
+ path-data-parser@0.1.0: {}
- stylis@4.3.6: {}
+ path-exists@4.0.0: {}
- superjson@2.2.2:
- dependencies:
- copy-anything: 3.0.5
+ path-key@3.1.1: {}
- supports-color@5.5.0:
- dependencies:
- has-flag: 3.0.0
+ perfect-debounce@1.0.0: {}
- supports-color@7.2.0:
- dependencies:
- has-flag: 4.0.0
+ picocolors@1.1.1: {}
- symbol-tree@3.2.4: {}
+ picomatch@4.0.7: {}
- tabbable@6.2.0: {}
+ points-on-curve@0.2.0: {}
- table@6.9.0:
+ points-on-path@0.2.1:
dependencies:
- ajv: 8.17.1
- lodash.truncate: 4.4.2
- slice-ansi: 4.0.0
- string-width: 4.2.3
- strip-ansi: 6.0.1
+ path-data-parser: 0.1.0
+ points-on-curve: 0.2.0
- terser@5.43.1:
+ postcss-selector-parser@7.1.6:
dependencies:
- '@jridgewell/source-map': 0.3.10
- acorn: 8.15.0
- commander: 2.20.3
- source-map-support: 0.5.21
+ cssesc: 3.0.0
+ util-deprecate: 1.0.2
- tinyexec@1.0.1: {}
-
- tinyglobby@0.2.14:
+ postcss@8.5.28:
dependencies:
- fdir: 6.4.6(picomatch@4.0.3)
- picomatch: 4.0.3
-
- tldts-core@6.1.86: {}
+ nanoid: 3.3.19
+ picocolors: 1.1.1
+ source-map-js: 1.2.1
- tldts@6.1.86:
- dependencies:
- tldts-core: 6.1.86
+ preact@10.29.8: {}
- to-regex-range@5.0.1:
- dependencies:
- is-number: 7.0.0
+ prelude-ls@1.2.1: {}
- toidentifier@1.0.1: {}
+ prettier@3.9.9: {}
- totalist@3.0.1: {}
+ property-information@7.2.0: {}
- touch@3.1.1: {}
+ punycode@2.3.1: {}
- tough-cookie@5.1.2:
+ qified@0.10.1:
dependencies:
- tldts: 6.1.86
+ hookified: 2.2.0
- tr46@5.1.1:
+ regex-recursion@6.0.2:
dependencies:
- punycode: 2.3.1
+ regex-utilities: 2.3.0
- trim-lines@3.0.1: {}
+ regex-utilities@2.3.0: {}
- ts-api-utils@2.1.0(typescript@5.8.3):
+ regex@6.1.0:
dependencies:
- typescript: 5.8.3
+ regex-utilities: 2.3.0
- ts-dedent@2.2.0: {}
+ rfdc@1.4.1: {}
- tslib@2.8.1: {}
+ robust-predicates@3.0.3: {}
- type-check@0.4.0:
+ rollup@4.63.5:
dependencies:
- prelude-ls: 1.2.1
+ '@types/estree': 1.0.9
+ optionalDependencies:
+ '@napi-rs/lzma-linux-x64-gnu': 1.5.1
+ '@rollup/rollup-android-arm-eabi': 4.63.5
+ '@rollup/rollup-android-arm64': 4.63.5
+ '@rollup/rollup-darwin-arm64': 4.63.5
+ '@rollup/rollup-darwin-x64': 4.63.5
+ '@rollup/rollup-freebsd-arm64': 4.63.5
+ '@rollup/rollup-freebsd-x64': 4.63.5
+ '@rollup/rollup-linux-arm-gnueabihf': 4.63.5
+ '@rollup/rollup-linux-arm-musleabihf': 4.63.5
+ '@rollup/rollup-linux-arm64-gnu': 4.63.5
+ '@rollup/rollup-linux-arm64-musl': 4.63.5
+ '@rollup/rollup-linux-loong64-gnu': 4.63.5
+ '@rollup/rollup-linux-loong64-musl': 4.63.5
+ '@rollup/rollup-linux-ppc64-gnu': 4.63.5
+ '@rollup/rollup-linux-ppc64-musl': 4.63.5
+ '@rollup/rollup-linux-riscv64-gnu': 4.63.5
+ '@rollup/rollup-linux-riscv64-musl': 4.63.5
+ '@rollup/rollup-linux-s390x-gnu': 4.63.5
+ '@rollup/rollup-linux-x64-gnu': 4.63.5
+ '@rollup/rollup-linux-x64-musl': 4.63.5
+ '@rollup/rollup-openbsd-x64': 4.63.5
+ '@rollup/rollup-openharmony-arm64': 4.63.5
+ '@rollup/rollup-win32-arm64-msvc': 4.63.5
+ '@rollup/rollup-win32-ia32-msvc': 4.63.5
+ '@rollup/rollup-win32-x64-gnu': 4.63.5
+ '@rollup/rollup-win32-x64-msvc': 4.63.5
+ fsevents: 2.3.3
- type-is@2.0.1:
+ roughjs@4.6.6:
dependencies:
- content-type: 1.0.5
- media-typer: 1.1.0
- mime-types: 3.0.1
+ hachure-fill: 0.5.2
+ path-data-parser: 0.1.0
+ points-on-curve: 0.2.0
+ points-on-path: 0.2.1
- typescript@5.8.3: {}
+ rw@1.3.3: {}
- uc.micro@2.1.0: {}
+ safer-buffer@2.1.2: {}
- ufo@1.6.1: {}
+ search-insights@2.17.3: {}
- unconfig@7.3.2:
+ section-matter@1.0.0:
dependencies:
- '@quansync/fs': 0.1.3
- defu: 6.1.4
- jiti: 2.4.2
- quansync: 0.2.10
-
- undefsafe@2.0.5: {}
+ extend-shallow: 2.0.1
+ kind-of: 6.0.3
- undici-types@7.8.0: {}
+ semver@7.8.5: {}
- unhead@2.0.12:
+ shebang-command@2.0.0:
dependencies:
- hookable: 5.5.3
-
- unicorn-magic@0.3.0: {}
+ shebang-regex: 3.0.0
- unist-util-is@6.0.0:
- dependencies:
- '@types/unist': 3.0.3
+ shebang-regex@3.0.0: {}
- unist-util-position@5.0.0:
+ shiki@2.5.0:
dependencies:
- '@types/unist': 3.0.3
+ '@shikijs/core': 2.5.0
+ '@shikijs/engine-javascript': 2.5.0
+ '@shikijs/engine-oniguruma': 2.5.0
+ '@shikijs/langs': 2.5.0
+ '@shikijs/themes': 2.5.0
+ '@shikijs/types': 2.5.0
+ '@shikijs/vscode-textmate': 10.0.2
+ '@types/hast': 3.0.5
- unist-util-stringify-position@4.0.0:
- dependencies:
- '@types/unist': 3.0.3
+ source-map-js@1.2.1: {}
- unist-util-visit-parents@6.0.1:
- dependencies:
- '@types/unist': 3.0.3
- unist-util-is: 6.0.0
+ space-separated-tokens@2.0.2: {}
- unist-util-visit@5.0.0:
- dependencies:
- '@types/unist': 3.0.3
- unist-util-is: 6.0.0
- unist-util-visit-parents: 6.0.1
-
- universal-user-agent@7.0.3: {}
-
- universalify@2.0.1: {}
-
- unocss@66.3.3(postcss@8.5.6)(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))(vue@3.5.17(typescript@5.8.3)):
- dependencies:
- '@unocss/astro': 66.3.3(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))(vue@3.5.17(typescript@5.8.3))
- '@unocss/cli': 66.3.3
- '@unocss/core': 66.3.3
- '@unocss/postcss': 66.3.3(postcss@8.5.6)
- '@unocss/preset-attributify': 66.3.3
- '@unocss/preset-icons': 66.3.3
- '@unocss/preset-mini': 66.3.3
- '@unocss/preset-tagify': 66.3.3
- '@unocss/preset-typography': 66.3.3
- '@unocss/preset-uno': 66.3.3
- '@unocss/preset-web-fonts': 66.3.3
- '@unocss/preset-wind': 66.3.3
- '@unocss/preset-wind3': 66.3.3
- '@unocss/preset-wind4': 66.3.3
- '@unocss/transformer-attributify-jsx': 66.3.3
- '@unocss/transformer-compile-class': 66.3.3
- '@unocss/transformer-directives': 66.3.3
- '@unocss/transformer-variant-group': 66.3.3
- '@unocss/vite': 66.3.3(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))(vue@3.5.17(typescript@5.8.3))
- optionalDependencies:
- vite: 7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0)
- transitivePeerDependencies:
- - postcss
- - supports-color
- - vue
+ speakingurl@14.0.1: {}
- unpipe@1.0.0: {}
+ sprintf-js@1.0.3: {}
- unplugin-ast@0.15.1:
- dependencies:
- '@babel/generator': 7.28.0
- ast-kit: 2.1.1
- magic-string-ast: 1.0.0
- unplugin: 2.3.5
+ string-argv@0.3.2: {}
- unplugin-utils@0.2.4:
+ stringify-entities@4.0.4:
dependencies:
- pathe: 2.0.3
- picomatch: 4.0.3
+ character-entities-html4: 2.1.0
+ character-entities-legacy: 3.0.0
- unplugin-vue-components@28.0.0(@babel/parser@7.28.0)(rollup@4.45.1)(vue@3.5.17(typescript@5.8.3)):
- dependencies:
- '@antfu/utils': 0.7.10
- '@rollup/pluginutils': 5.2.0(rollup@4.45.1)
- chokidar: 3.6.0
- debug: 4.4.1(supports-color@5.5.0)
- fast-glob: 3.3.3
- local-pkg: 0.5.1
- magic-string: 0.30.17
- minimatch: 9.0.5
- mlly: 1.7.4
- unplugin: 2.3.5
- vue: 3.5.17(typescript@5.8.3)
- optionalDependencies:
- '@babel/parser': 7.28.0
- transitivePeerDependencies:
- - rollup
- - supports-color
+ strip-bom-string@1.0.0: {}
- unplugin-vue-markdown@29.1.0(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0)):
- dependencies:
- '@mdit-vue/plugin-component': 2.1.4
- '@mdit-vue/plugin-frontmatter': 2.1.4
- '@mdit-vue/types': 2.1.4
- '@types/markdown-it': 14.1.2
- markdown-it: 14.1.0
- markdown-it-async: 2.2.0
- unplugin: 2.3.5
- unplugin-utils: 0.2.4
- vite: 7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0)
-
- unplugin-vue-router@0.14.0(@vue/compiler-sfc@3.5.17)(vue-router@4.5.1(vue@3.5.17(typescript@5.8.3)))(vue@3.5.17(typescript@5.8.3)):
- dependencies:
- '@vue-macros/common': 3.0.0-beta.15(vue@3.5.17(typescript@5.8.3))
- '@vue/compiler-sfc': 3.5.17
- ast-walker-scope: 0.8.1
- chokidar: 4.0.3
- fast-glob: 3.3.3
- json5: 2.2.3
- local-pkg: 1.1.1
- magic-string: 0.30.17
- mlly: 1.7.4
- pathe: 2.0.3
- picomatch: 4.0.3
- scule: 1.3.0
- unplugin: 2.3.5
- unplugin-utils: 0.2.4
- yaml: 2.8.0
- optionalDependencies:
- vue-router: 4.5.1(vue@3.5.17(typescript@5.8.3))
- transitivePeerDependencies:
- - vue
+ stylis@4.4.0: {}
- unplugin@1.16.1:
+ superjson@2.2.6:
dependencies:
- acorn: 8.15.0
- webpack-virtual-modules: 0.6.2
+ copy-anything: 4.1.3
- unplugin@2.3.5:
- dependencies:
- acorn: 8.15.0
- picomatch: 4.0.3
- webpack-virtual-modules: 0.6.2
+ tabbable@6.5.0: {}
- update-browserslist-db@1.1.3(browserslist@4.25.1):
- dependencies:
- browserslist: 4.25.1
- escalade: 3.2.0
- picocolors: 1.1.1
+ tinyexec@1.3.1: {}
- uri-js@4.4.1:
+ tinyglobby@0.2.17:
dependencies:
- punycode: 2.3.1
+ fdir: 6.5.0(picomatch@4.0.7)
+ picomatch: 4.0.7
- uuid@11.1.0: {}
+ trim-lines@3.0.1: {}
- valaxy-addon-algolia@0.2.0(@algolia/client-search@5.34.0)(search-insights@2.17.3)(valaxy@0.25.9(patch_hash=4e8a0c516f0006cdaf6f1333cca04b01a402f6dc55935ae6f485f932da77c611)(@babel/parser@7.28.0)(@types/markdown-it@14.1.2)(@types/node@24.0.15)(@vue/compiler-dom@3.5.17)(@vue/compiler-sfc@3.5.17)(axios@1.10.0)(eslint@9.29.0(jiti@2.4.2))(focus-trap@7.6.5)(postcss@8.5.6)(prettier@3.6.2)(rollup@4.45.1)(terser@5.43.1)(typescript@5.8.3)(yaml@2.8.0)):
+ ts-api-utils@2.5.0(typescript@6.0.3):
dependencies:
- '@docsearch/css': 3.9.0
- '@docsearch/js': 3.9.0(@algolia/client-search@5.34.0)(search-insights@2.17.3)
- valaxy: 0.25.9(patch_hash=4e8a0c516f0006cdaf6f1333cca04b01a402f6dc55935ae6f485f932da77c611)(@babel/parser@7.28.0)(@types/markdown-it@14.1.2)(@types/node@24.0.15)(@vue/compiler-dom@3.5.17)(@vue/compiler-sfc@3.5.17)(axios@1.10.0)(eslint@9.29.0(jiti@2.4.2))(focus-trap@7.6.5)(postcss@8.5.6)(prettier@3.6.2)(rollup@4.45.1)(terser@5.43.1)(typescript@5.8.3)(yaml@2.8.0)
- transitivePeerDependencies:
- - '@algolia/client-search'
- - '@types/react'
- - react
- - react-dom
- - search-insights
+ typescript: 6.0.3
- valaxy-addon-components@0.1.0: {}
+ ts-dedent@2.3.0: {}
- valaxy-addon-git-log@0.3.2(valaxy@0.25.9(patch_hash=4e8a0c516f0006cdaf6f1333cca04b01a402f6dc55935ae6f485f932da77c611)(@babel/parser@7.28.0)(@types/markdown-it@14.1.2)(@types/node@24.0.15)(@vue/compiler-dom@3.5.17)(@vue/compiler-sfc@3.5.17)(axios@1.10.0)(eslint@9.29.0(jiti@2.4.2))(focus-trap@7.6.5)(postcss@8.5.6)(prettier@3.6.2)(rollup@4.45.1)(terser@5.43.1)(typescript@5.8.3)(yaml@2.8.0)):
+ type-check@0.4.0:
dependencies:
- '@octokit/rest': 21.1.1
- fs-extra: 11.3.0
- gravatar: 1.8.2
- md5: 2.3.0
- simple-git: 3.28.0
- valaxy: 0.25.9(patch_hash=4e8a0c516f0006cdaf6f1333cca04b01a402f6dc55935ae6f485f932da77c611)(@babel/parser@7.28.0)(@types/markdown-it@14.1.2)(@types/node@24.0.15)(@vue/compiler-dom@3.5.17)(@vue/compiler-sfc@3.5.17)(axios@1.10.0)(eslint@9.29.0(jiti@2.4.2))(focus-trap@7.6.5)(postcss@8.5.6)(prettier@3.6.2)(rollup@4.45.1)(terser@5.43.1)(typescript@5.8.3)(yaml@2.8.0)
- transitivePeerDependencies:
- - supports-color
+ prelude-ls: 1.2.1
- valaxy-theme-press@0.25.9(patch_hash=a6c7859cddc4d023eca0c3ca0820314f6456487482af67a4b4ba28719d385f3d)(@algolia/client-search@5.34.0)(search-insights@2.17.3):
+ typescript-eslint@8.70.1(eslint@10.11.0)(typescript@6.0.3):
dependencies:
- '@docsearch/css': 3.9.0
- '@docsearch/js': 3.9.0(@algolia/client-search@5.34.0)(search-insights@2.17.3)
- transitivePeerDependencies:
- - '@algolia/client-search'
- - '@types/react'
- - react
- - react-dom
- - search-insights
-
- valaxy@0.25.9(patch_hash=4e8a0c516f0006cdaf6f1333cca04b01a402f6dc55935ae6f485f932da77c611)(@babel/parser@7.28.0)(@types/markdown-it@14.1.2)(@types/node@24.0.15)(@vue/compiler-dom@3.5.17)(@vue/compiler-sfc@3.5.17)(axios@1.10.0)(eslint@9.29.0(jiti@2.4.2))(focus-trap@7.6.5)(postcss@8.5.6)(prettier@3.6.2)(rollup@4.45.1)(terser@5.43.1)(typescript@5.8.3)(yaml@2.8.0):
- dependencies:
- '@antfu/install-pkg': 1.1.0
- '@antfu/utils': 9.2.0
- '@clack/prompts': 0.11.0
- '@iconify-json/ri': 1.2.5
- '@intlify/unplugin-vue-i18n': 6.0.8(@vue/compiler-dom@3.5.17)(eslint@9.29.0(jiti@2.4.2))(rollup@4.45.1)(typescript@5.8.3)(vue-i18n@11.1.10(vue@3.5.17(typescript@5.8.3)))(vue@3.5.17(typescript@5.8.3))
- '@shikijs/transformers': 3.8.1
- '@types/katex': 0.16.7
- '@unhead/addons': 2.0.12(rollup@4.45.1)
- '@unhead/schema-org': 2.0.12(@unhead/vue@2.0.12(vue@3.5.17(typescript@5.8.3)))
- '@unhead/vue': 2.0.12(vue@3.5.17(typescript@5.8.3))
- '@valaxyjs/devtools': 0.25.9(debug@4.4.1)(rollup@4.45.1)(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))
- '@valaxyjs/utils': 0.25.9
- '@vitejs/plugin-vue': 6.0.0(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))(vue@3.5.17(typescript@5.8.3))
- '@vue/devtools-api': 7.7.2
- '@vueuse/core': 13.5.0(vue@3.5.17(typescript@5.8.3))
- '@vueuse/integrations': 13.5.0(axios@1.10.0)(focus-trap@7.6.5)(fuse.js@7.1.0)(nprogress@0.2.0)(qrcode@1.5.4)(vue@3.5.17(typescript@5.8.3))
- beasties: 0.3.5
- consola: 3.4.2
- cross-spawn: 7.0.6
- css-i18n: 0.0.5
- dayjs: 1.11.13
- debug: 4.4.1(supports-color@5.5.0)
- defu: 6.1.4
- ejs: 3.1.10
- escape-html: 1.0.3
- fast-glob: 3.3.3
- feed: 5.1.0
- floating-vue: 5.2.2(vue@3.5.17(typescript@5.8.3))
- fs-extra: 11.3.0
- fuse.js: 7.1.0
- gray-matter: 4.0.3
- hookable: 5.5.3
- html-to-text: 9.0.5
- jiti: 2.4.2
- js-base64: 3.7.7
- js-yaml: 4.1.0
- katex: 0.16.22
- lru-cache: 11.1.0
- markdown-it: 14.1.0
- markdown-it-anchor: 9.2.0(@types/markdown-it@14.1.2)(markdown-it@14.1.0)
- markdown-it-async: 2.2.0
- markdown-it-attrs: 4.3.1(markdown-it@14.1.0)
- markdown-it-container: 4.0.0
- markdown-it-emoji: 3.0.0
- markdown-it-footnote: 4.0.0
- markdown-it-image-figures: 2.1.1(markdown-it@14.1.0)
- markdown-it-table-of-contents: 0.9.0
- markdown-it-task-lists: 2.1.1
- medium-zoom: 1.1.0
- mermaid: 11.9.0
- mlly: 1.7.4
- nprogress: 0.2.0
- open: 10.1.0
- ora: 8.2.0
- pascalcase: 2.0.0
- pathe: 2.0.3
- pinia: 3.0.3(typescript@5.8.3)(vue@3.5.17(typescript@5.8.3))
- qrcode: 1.5.4
- resolve-global: 2.0.0
- sass: 1.89.2
- shiki: 3.8.1
- star-markdown-css: 0.5.3
- table: 6.9.0
- unhead: 2.0.12
- unocss: 66.3.3(postcss@8.5.6)(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))(vue@3.5.17(typescript@5.8.3))
- unplugin-vue-components: 28.0.0(@babel/parser@7.28.0)(rollup@4.45.1)(vue@3.5.17(typescript@5.8.3))
- unplugin-vue-markdown: 29.1.0(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))
- unplugin-vue-router: 0.14.0(@vue/compiler-sfc@3.5.17)(vue-router@4.5.1(vue@3.5.17(typescript@5.8.3)))(vue@3.5.17(typescript@5.8.3))
- vanilla-lazyload: 19.1.3
- vite: 7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0)
- vite-dev-rpc: 1.1.0(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))
- vite-plugin-vue-devtools: 7.7.7(rollup@4.45.1)(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))(vue@3.5.17(typescript@5.8.3))
- vite-plugin-vue-layouts: 0.11.0(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))(vue-router@4.5.1(vue@3.5.17(typescript@5.8.3)))(vue@3.5.17(typescript@5.8.3))
- vite-ssg: 28.0.0(beasties@0.3.5)(prettier@3.6.2)(unhead@2.0.12)(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))(vue-router@4.5.1(vue@3.5.17(typescript@5.8.3)))(vue@3.5.17(typescript@5.8.3))
- vite-ssg-sitemap: 0.9.0
- vitepress-plugin-group-icons: 1.6.1(markdown-it@14.1.0)(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))
- vue: 3.5.17(typescript@5.8.3)
- vue-i18n: 11.1.10(vue@3.5.17(typescript@5.8.3))
- vue-router: 4.5.1(vue@3.5.17(typescript@5.8.3))
- yargs: 18.0.0
+ '@typescript-eslint/eslint-plugin': 8.70.1(@typescript-eslint/parser@8.70.1(eslint@10.11.0)(typescript@6.0.3))(eslint@10.11.0)(typescript@6.0.3)
+ '@typescript-eslint/parser': 8.70.1(eslint@10.11.0)(typescript@6.0.3)
+ '@typescript-eslint/typescript-estree': 8.70.1(typescript@6.0.3)
+ '@typescript-eslint/utils': 8.70.1(eslint@10.11.0)(typescript@6.0.3)
+ eslint: 10.11.0
+ typescript: 6.0.3
transitivePeerDependencies:
- - '@babel/parser'
- - '@nuxt/kit'
- - '@types/markdown-it'
- - '@types/node'
- - '@unhead/react'
- - '@unhead/solid-js'
- - '@unhead/svelte'
- - '@unocss/webpack'
- - '@vue/compiler-dom'
- - '@vue/compiler-sfc'
- - async-validator
- - axios
- - bufferutil
- - canvas
- - change-case
- - drauu
- - eslint
- - focus-trap
- - idb-keyval
- - jwt-decode
- - less
- - lightningcss
- - petite-vue-i18n
- - postcss
- - prettier
- - rollup
- - sass-embedded
- - sortablejs
- - stylus
- - sugarss
- supports-color
- - terser
- - tsx
- - typescript
- - universal-cookie
- - utf-8-validate
- - yaml
- vanilla-lazyload@19.1.3: {}
+ typescript@6.0.3: {}
- vary@1.1.2: {}
+ undici-types@7.24.6: {}
- vfile-message@4.0.2:
+ unist-util-is@6.0.1:
dependencies:
'@types/unist': 3.0.3
- unist-util-stringify-position: 4.0.0
- vfile@6.0.3:
+ unist-util-position@5.0.0:
dependencies:
'@types/unist': 3.0.3
- vfile-message: 4.0.2
- vite-dev-rpc@1.1.0(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0)):
+ unist-util-stringify-position@4.0.0:
dependencies:
- birpc: 2.5.0
- vite: 7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0)
- vite-hot-client: 2.1.0(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))
+ '@types/unist': 3.0.3
- vite-hot-client@2.1.0(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0)):
+ unist-util-visit-parents@6.0.2:
dependencies:
- vite: 7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0)
+ '@types/unist': 3.0.3
+ unist-util-is: 6.0.1
- vite-plugin-inspect@0.8.9(rollup@4.45.1)(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0)):
+ unist-util-visit@5.1.0:
dependencies:
- '@antfu/utils': 0.7.10
- '@rollup/pluginutils': 5.2.0(rollup@4.45.1)
- debug: 4.4.1(supports-color@5.5.0)
- error-stack-parser-es: 0.1.5
- fs-extra: 11.3.0
- open: 10.1.0
- perfect-debounce: 1.0.0
- picocolors: 1.1.1
- sirv: 3.0.1
- vite: 7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0)
- transitivePeerDependencies:
- - rollup
- - supports-color
+ '@types/unist': 3.0.3
+ unist-util-is: 6.0.1
+ unist-util-visit-parents: 6.0.2
- vite-plugin-vue-devtools@7.7.7(rollup@4.45.1)(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))(vue@3.5.17(typescript@5.8.3)):
+ uri-js@4.4.1:
dependencies:
- '@vue/devtools-core': 7.7.7(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))(vue@3.5.17(typescript@5.8.3))
- '@vue/devtools-kit': 7.7.7
- '@vue/devtools-shared': 7.7.7
- execa: 9.6.0
- sirv: 3.0.1
- vite: 7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0)
- vite-plugin-inspect: 0.8.9(rollup@4.45.1)(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))
- vite-plugin-vue-inspector: 5.3.2(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))
- transitivePeerDependencies:
- - '@nuxt/kit'
- - rollup
- - supports-color
- - vue
-
- vite-plugin-vue-inspector@5.3.2(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0)):
- dependencies:
- '@babel/core': 7.28.0
- '@babel/plugin-proposal-decorators': 7.28.0(@babel/core@7.28.0)
- '@babel/plugin-syntax-import-attributes': 7.27.1(@babel/core@7.28.0)
- '@babel/plugin-syntax-import-meta': 7.10.4(@babel/core@7.28.0)
- '@babel/plugin-transform-typescript': 7.28.0(@babel/core@7.28.0)
- '@vue/babel-plugin-jsx': 1.4.0(@babel/core@7.28.0)
- '@vue/compiler-dom': 3.5.17
- kolorist: 1.8.0
- magic-string: 0.30.17
- vite: 7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0)
- transitivePeerDependencies:
- - supports-color
+ punycode: 2.3.1
- vite-plugin-vue-layouts@0.11.0(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))(vue-router@4.5.1(vue@3.5.17(typescript@5.8.3)))(vue@3.5.17(typescript@5.8.3)):
- dependencies:
- debug: 4.4.1(supports-color@5.5.0)
- fast-glob: 3.3.3
- vite: 7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0)
- vue: 3.5.17(typescript@5.8.3)
- vue-router: 4.5.1(vue@3.5.17(typescript@5.8.3))
- transitivePeerDependencies:
- - supports-color
+ util-deprecate@1.0.2: {}
- vite-ssg-sitemap@0.9.0: {}
+ uuid@14.0.2: {}
- vite-ssg@28.0.0(beasties@0.3.5)(prettier@3.6.2)(unhead@2.0.12)(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0))(vue-router@4.5.1(vue@3.5.17(typescript@5.8.3)))(vue@3.5.17(typescript@5.8.3)):
+ vfile-message@4.0.3:
dependencies:
- '@unhead/dom': 2.0.12(unhead@2.0.12)
- '@unhead/vue': 2.0.12(vue@3.5.17(typescript@5.8.3))
- ansis: 4.1.0
- cac: 6.7.14
- html-minifier-terser: 7.2.0
- html5parser: 2.0.2
- jsdom: 26.1.0
- vite: 7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0)
- vue: 3.5.17(typescript@5.8.3)
- optionalDependencies:
- beasties: 0.3.5
- prettier: 3.6.2
- vue-router: 4.5.1(vue@3.5.17(typescript@5.8.3))
- transitivePeerDependencies:
- - bufferutil
- - canvas
- - supports-color
- - unhead
- - utf-8-validate
+ '@types/unist': 3.0.3
+ unist-util-stringify-position: 4.0.0
- vite@5.4.19(@types/node@24.0.15)(sass@1.89.2)(terser@5.43.1):
+ vfile@6.0.3:
dependencies:
- esbuild: 0.21.5
- postcss: 8.5.6
- rollup: 4.45.1
- optionalDependencies:
- '@types/node': 24.0.15
- fsevents: 2.3.3
- sass: 1.89.2
- terser: 5.43.1
+ '@types/unist': 3.0.3
+ vfile-message: 4.0.3
- vite@6.3.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0):
+ vite@5.4.21(@types/node@24.19.0):
dependencies:
- esbuild: 0.25.8
- fdir: 6.4.6(picomatch@4.0.3)
- picomatch: 4.0.3
- postcss: 8.5.6
- rollup: 4.45.1
- tinyglobby: 0.2.14
- optionalDependencies:
- '@types/node': 24.0.15
- fsevents: 2.3.3
- jiti: 2.4.2
- sass: 1.89.2
- terser: 5.43.1
- yaml: 2.8.0
-
- vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0):
- dependencies:
- esbuild: 0.25.8
- fdir: 6.4.6(picomatch@4.0.3)
- picomatch: 4.0.3
- postcss: 8.5.6
- rollup: 4.45.1
- tinyglobby: 0.2.14
+ esbuild: 0.21.5
+ postcss: 8.5.28
+ rollup: 4.63.5
optionalDependencies:
- '@types/node': 24.0.15
+ '@types/node': 24.19.0
fsevents: 2.3.3
- jiti: 2.4.2
- sass: 1.89.2
- terser: 5.43.1
- yaml: 2.8.0
-
- vitepress-plugin-group-icons@1.6.1(markdown-it@14.1.0)(vite@6.3.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0)):
- dependencies:
- '@iconify-json/logos': 1.2.4
- '@iconify-json/vscode-icons': 1.2.23
- '@iconify/utils': 2.3.0
- markdown-it: 14.1.0
- vite: 6.3.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0)
- transitivePeerDependencies:
- - supports-color
- vitepress-plugin-group-icons@1.6.1(markdown-it@14.1.0)(vite@7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0)):
+ vitepress-plugin-group-icons@1.7.6(vite@5.4.21(@types/node@24.19.0)):
dependencies:
- '@iconify-json/logos': 1.2.4
- '@iconify-json/vscode-icons': 1.2.23
- '@iconify/utils': 2.3.0
- markdown-it: 14.1.0
- vite: 7.0.5(@types/node@24.0.15)(jiti@2.4.2)(sass@1.89.2)(terser@5.43.1)(yaml@2.8.0)
- transitivePeerDependencies:
- - supports-color
-
- vitepress@1.1.4(@algolia/client-search@5.34.0)(@types/node@24.0.15)(axios@1.10.0)(fuse.js@7.1.0)(nprogress@0.2.0)(postcss@8.5.6)(qrcode@1.5.4)(sass@1.89.2)(search-insights@2.17.3)(terser@5.43.1)(typescript@5.8.3):
- dependencies:
- '@docsearch/css': 3.9.0
- '@docsearch/js': 3.9.0(@algolia/client-search@5.34.0)(search-insights@2.17.3)
- '@shikijs/core': 1.29.2
- '@shikijs/transformers': 1.29.2
- '@types/markdown-it': 14.1.2
- '@vitejs/plugin-vue': 5.2.4(vite@5.4.19(@types/node@24.0.15)(sass@1.89.2)(terser@5.43.1))(vue@3.5.17(typescript@5.8.3))
- '@vue/devtools-api': 7.7.7
- '@vueuse/core': 10.11.1(vue@3.5.17(typescript@5.8.3))
- '@vueuse/integrations': 10.11.1(axios@1.10.0)(focus-trap@7.6.5)(fuse.js@7.1.0)(nprogress@0.2.0)(qrcode@1.5.4)(vue@3.5.17(typescript@5.8.3))
- focus-trap: 7.6.5
+ '@iconify-json/logos': 1.2.14
+ '@iconify-json/vscode-icons': 1.2.81
+ '@iconify/utils': 3.1.7
+ optionalDependencies:
+ vite: 5.4.21(@types/node@24.19.0)
+
+ vitepress@1.6.4(@algolia/client-search@5.59.0)(@types/node@24.19.0)(postcss@8.5.28)(search-insights@2.17.3)(typescript@6.0.3):
+ dependencies:
+ '@docsearch/css': 3.8.2
+ '@docsearch/js': 3.8.2(@algolia/client-search@5.59.0)(search-insights@2.17.3)
+ '@iconify-json/simple-icons': 1.2.97
+ '@shikijs/core': 2.5.0
+ '@shikijs/transformers': 2.5.0
+ '@shikijs/types': 2.5.0
+ '@types/markdown-it': 14.2.0
+ '@vitejs/plugin-vue': 5.2.4(vite@5.4.21(@types/node@24.19.0))(vue@3.5.43(typescript@6.0.3))
+ '@vue/devtools-api': 7.7.10
+ '@vue/shared': 3.5.43
+ '@vueuse/core': 12.8.2(typescript@6.0.3)
+ '@vueuse/integrations': 12.8.2(focus-trap@7.8.0)(typescript@6.0.3)
+ focus-trap: 7.8.0
mark.js: 8.11.1
- minisearch: 6.3.0
- shiki: 1.29.2
- vite: 5.4.19(@types/node@24.0.15)(sass@1.89.2)(terser@5.43.1)
- vue: 3.5.17(typescript@5.8.3)
+ minisearch: 7.2.0
+ shiki: 2.5.0
+ vite: 5.4.21(@types/node@24.19.0)
+ vue: 3.5.43(typescript@6.0.3)
optionalDependencies:
- postcss: 8.5.6
+ postcss: 8.5.28
transitivePeerDependencies:
- '@algolia/client-search'
- '@types/node'
- '@types/react'
- - '@vue/composition-api'
- async-validator
- axios
- change-case
@@ -8742,6 +3882,7 @@ snapshots:
- less
- lightningcss
- nprogress
+ - preact-render-to-string
- qrcode
- react
- react-dom
@@ -8755,85 +3896,35 @@ snapshots:
- typescript
- universal-cookie
- vscode-jsonrpc@8.2.0: {}
-
- vscode-languageserver-protocol@3.17.5:
- dependencies:
- vscode-jsonrpc: 8.2.0
- vscode-languageserver-types: 3.17.5
-
- vscode-languageserver-textdocument@1.0.12: {}
-
- vscode-languageserver-types@3.17.5: {}
-
- vscode-languageserver@9.0.1:
- dependencies:
- vscode-languageserver-protocol: 3.17.5
-
- vscode-uri@3.0.8: {}
-
- vscode-uri@3.1.0: {}
-
- vue-demi@0.14.10(vue@3.5.17(typescript@5.8.3)):
- dependencies:
- vue: 3.5.17(typescript@5.8.3)
-
- vue-flow-layout@0.1.1(vue@3.5.17(typescript@5.8.3)):
- dependencies:
- vue: 3.5.17(typescript@5.8.3)
-
- vue-i18n@11.1.10(vue@3.5.17(typescript@5.8.3)):
- dependencies:
- '@intlify/core-base': 11.1.10
- '@intlify/shared': 11.1.10
- '@vue/devtools-api': 6.6.4
- vue: 3.5.17(typescript@5.8.3)
-
- vue-resize@2.0.0-alpha.1(vue@3.5.17(typescript@5.8.3)):
- dependencies:
- vue: 3.5.17(typescript@5.8.3)
+ vscode-uri@3.2.0: {}
- vue-router@4.5.1(vue@3.5.17(typescript@5.8.3)):
+ vue-eslint-parser@10.4.1(eslint@10.11.0):
dependencies:
- '@vue/devtools-api': 6.6.4
- vue: 3.5.17(typescript@5.8.3)
+ debug: 4.4.3
+ eslint: 10.11.0
+ eslint-scope: 9.1.2
+ eslint-visitor-keys: 5.0.1
+ espree: 11.2.0
+ esquery: 1.7.0
+ semver: 7.8.5
+ transitivePeerDependencies:
+ - supports-color
- vue-tsc@2.2.12(typescript@5.8.3):
+ vue-tsc@3.3.11(typescript@6.0.3):
dependencies:
- '@volar/typescript': 2.4.15
- '@vue/language-core': 2.2.12(typescript@5.8.3)
- typescript: 5.8.3
+ '@volar/typescript': 2.4.28(typescript@6.0.3)
+ '@vue/language-core': 3.3.11
+ typescript: 6.0.3
- vue@3.5.17(typescript@5.8.3):
+ vue@3.5.43(typescript@6.0.3):
dependencies:
- '@vue/compiler-dom': 3.5.17
- '@vue/compiler-sfc': 3.5.17
- '@vue/runtime-dom': 3.5.17
- '@vue/server-renderer': 3.5.17(vue@3.5.17(typescript@5.8.3))
- '@vue/shared': 3.5.17
+ '@vue/compiler-dom': 3.5.43
+ '@vue/compiler-sfc': 3.5.43
+ '@vue/runtime-dom': 3.5.43
+ '@vue/server-renderer': 3.5.43
+ '@vue/shared': 3.5.43
optionalDependencies:
- typescript: 5.8.3
-
- w3c-xmlserializer@5.0.0:
- dependencies:
- xml-name-validator: 5.0.0
-
- webidl-conversions@7.0.0: {}
-
- webpack-virtual-modules@0.6.2: {}
-
- whatwg-encoding@3.1.1:
- dependencies:
- iconv-lite: 0.6.3
-
- whatwg-mimetype@4.0.0: {}
-
- whatwg-url@14.2.0:
- dependencies:
- tr46: 5.1.1
- webidl-conversions: 7.0.0
-
- which-module@2.0.1: {}
+ typescript: 6.0.3
which@2.0.2:
dependencies:
@@ -8841,73 +3932,11 @@ snapshots:
word-wrap@1.2.5: {}
- wrap-ansi@6.2.0:
- dependencies:
- ansi-styles: 4.3.0
- string-width: 4.2.3
- strip-ansi: 6.0.1
-
- wrap-ansi@9.0.0:
- dependencies:
- ansi-styles: 6.2.1
- string-width: 7.2.0
- strip-ansi: 7.1.0
-
- ws@8.18.3: {}
-
- xml-js@1.6.11:
- dependencies:
- sax: 1.4.1
-
xml-name-validator@5.0.0: {}
- xmlchars@2.2.0: {}
-
- y18n@4.0.3: {}
-
- y18n@5.0.8: {}
-
- yallist@3.1.1: {}
-
- yaml-eslint-parser@1.3.0:
- dependencies:
- eslint-visitor-keys: 3.4.3
- yaml: 2.8.0
-
- yaml@2.8.0: {}
-
- yargs-parser@18.1.3:
- dependencies:
- camelcase: 5.3.1
- decamelize: 1.2.0
-
- yargs-parser@22.0.0: {}
-
- yargs@15.4.1:
- dependencies:
- cliui: 6.0.0
- decamelize: 1.2.0
- find-up: 4.1.0
- get-caller-file: 2.0.5
- require-directory: 2.1.1
- require-main-filename: 2.0.0
- set-blocking: 2.0.0
- string-width: 4.2.3
- which-module: 2.0.1
- y18n: 4.0.3
- yargs-parser: 18.1.3
-
- yargs@18.0.0:
- dependencies:
- cliui: 9.0.1
- escalade: 3.2.0
- get-caller-file: 2.0.5
- string-width: 7.2.0
- y18n: 5.0.8
- yargs-parser: 22.0.0
+ yaml@2.9.1:
+ optional: true
yocto-queue@0.1.0: {}
- yoctocolors@2.1.1: {}
-
zwitch@2.0.4: {}
diff --git a/pnpm-workspace.yaml b/pnpm-workspace.yaml
index be6a22dfa..3eb0fd7ad 100644
--- a/pnpm-workspace.yaml
+++ b/pnpm-workspace.yaml
@@ -1,8 +1,4 @@
-onlyBuiltDependencies:
- - '@parcel/watcher'
- - esbuild
- - vue-demi
-
-patchedDependencies:
- valaxy@0.25.9: patches/valaxy@0.25.9.patch
- valaxy-theme-press@0.25.9: patches/valaxy-theme-press@0.25.9.patch
+allowBuilds:
+ esbuild: true
+minimumReleaseAgeExclude:
+ - lint-staged@17.6.0
diff --git a/public/img/dev-tip/correctcontent-dark.png b/public/img/dev-tip/correctcontent-dark.png
deleted file mode 100644
index 658c7cdd9..000000000
Binary files a/public/img/dev-tip/correctcontent-dark.png and /dev/null differ
diff --git a/public/img/dev-tip/correctcontent-light.png b/public/img/dev-tip/correctcontent-light.png
deleted file mode 100644
index a0b1cc08a..000000000
Binary files a/public/img/dev-tip/correctcontent-light.png and /dev/null differ
diff --git a/public/img/dev-tip/correctendline-dark.png b/public/img/dev-tip/correctendline-dark.png
deleted file mode 100644
index f5f83d037..000000000
Binary files a/public/img/dev-tip/correctendline-dark.png and /dev/null differ
diff --git a/public/img/dev-tip/correctendline-light.png b/public/img/dev-tip/correctendline-light.png
deleted file mode 100644
index 76ba0fdae..000000000
Binary files a/public/img/dev-tip/correctendline-light.png and /dev/null differ
diff --git a/public/img/dev-tip/correcttitle-dark.png b/public/img/dev-tip/correcttitle-dark.png
deleted file mode 100644
index fabca5995..000000000
Binary files a/public/img/dev-tip/correcttitle-dark.png and /dev/null differ
diff --git a/public/img/dev-tip/correcttitle-light.png b/public/img/dev-tip/correcttitle-light.png
deleted file mode 100644
index f92d5723d..000000000
Binary files a/public/img/dev-tip/correcttitle-light.png and /dev/null differ
diff --git a/public/img/dev-tip/correcttranslateendline-dark.png b/public/img/dev-tip/correcttranslateendline-dark.png
deleted file mode 100644
index 0cb9fedce..000000000
Binary files a/public/img/dev-tip/correcttranslateendline-dark.png and /dev/null differ
diff --git a/public/img/dev-tip/correcttranslateendline-light.png b/public/img/dev-tip/correcttranslateendline-light.png
deleted file mode 100644
index 75aea82d3..000000000
Binary files a/public/img/dev-tip/correcttranslateendline-light.png and /dev/null differ
diff --git a/public/img/dev-tip/wrongcontent-dark.png b/public/img/dev-tip/wrongcontent-dark.png
deleted file mode 100644
index 65b9b3c48..000000000
Binary files a/public/img/dev-tip/wrongcontent-dark.png and /dev/null differ
diff --git a/public/img/dev-tip/wrongcontent-light.png b/public/img/dev-tip/wrongcontent-light.png
deleted file mode 100644
index 9ec0a29dc..000000000
Binary files a/public/img/dev-tip/wrongcontent-light.png and /dev/null differ
diff --git a/public/img/dev-tip/wrongendline-dark.png b/public/img/dev-tip/wrongendline-dark.png
deleted file mode 100644
index b7bfa5d5b..000000000
Binary files a/public/img/dev-tip/wrongendline-dark.png and /dev/null differ
diff --git a/public/img/dev-tip/wrongendline-light.png b/public/img/dev-tip/wrongendline-light.png
deleted file mode 100644
index 68e00c421..000000000
Binary files a/public/img/dev-tip/wrongendline-light.png and /dev/null differ
diff --git a/public/img/dev-tip/wrongtitle-dark.png b/public/img/dev-tip/wrongtitle-dark.png
deleted file mode 100644
index ab3251683..000000000
Binary files a/public/img/dev-tip/wrongtitle-dark.png and /dev/null differ
diff --git a/public/img/dev-tip/wrongtitle-light.png b/public/img/dev-tip/wrongtitle-light.png
deleted file mode 100644
index ef23850c7..000000000
Binary files a/public/img/dev-tip/wrongtitle-light.png and /dev/null differ
diff --git a/public/img/dev-tip/wrongtranslateendline-dark.png b/public/img/dev-tip/wrongtranslateendline-dark.png
deleted file mode 100644
index d9a50de48..000000000
Binary files a/public/img/dev-tip/wrongtranslateendline-dark.png and /dev/null differ
diff --git a/public/img/dev-tip/wrongtranslateendline-light.png b/public/img/dev-tip/wrongtranslateendline-light.png
deleted file mode 100644
index 3c7c0c508..000000000
Binary files a/public/img/dev-tip/wrongtranslateendline-light.png and /dev/null differ
diff --git a/public/logo.svg b/public/logo.svg
deleted file mode 100644
index 54a87a1dd..000000000
--- a/public/logo.svg
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
\ No newline at end of file
diff --git a/public/logo.webp b/public/logo.webp
deleted file mode 100644
index c70c25732..000000000
Binary files a/public/logo.webp and /dev/null differ
diff --git a/snippets/snippet-with-region.js b/snippets/snippet-with-region.js
deleted file mode 100644
index 9c7faaebc..000000000
--- a/snippets/snippet-with-region.js
+++ /dev/null
@@ -1,7 +0,0 @@
-// #region snippet
-function foo() {
- // ..
-}
-// #endregion snippet
-
-export default foo
diff --git a/snippets/snippet.js b/snippets/snippet.js
deleted file mode 100644
index 575039d1e..000000000
--- a/snippets/snippet.js
+++ /dev/null
@@ -1,3 +0,0 @@
-export default function () {
- // ..
-}
diff --git a/styles/index.scss b/styles/index.scss
deleted file mode 100644
index 56c202306..000000000
--- a/styles/index.scss
+++ /dev/null
@@ -1,117 +0,0 @@
-@keyframes fly {
- from {
- transform: translateY(0.5em);
- }
-
- to {
- transform: translateY(-0.5em);
- }
-}
-
-.fly-animation {
- animation: fly 0.8s ease-in-out infinite alternate;
-}
-
-// override
-
-// Main Color
-:root {
- --vp-c-brand-1: hsl(196, 55%, 45%);
- --vp-c-brand-2: hsl(196, 59%, 51%);
- --vp-c-brand-3: hsl(196, 54%, 57%);
- --vp-c-brand-soft: hsla(196, 100%, 70%, 0.14);
-
- --va-c-brand: var(--vp-c-brand-1);
- --va-c-brand-1: var(--vp-c-brand-1);
- --va-c-brand-2: var(--vp-c-brand-2);
- --va-c-brand-3: var(--vp-c-brand-3);
- --va-c-brand-soft: var(--vp-c-brand-soft);
-
- --va-c-primary: var(--vp-c-brand-1);
- --va-c-primary-light: var(--vp-c-brand-2);
- --va-c-primary-lighter: var(--vp-c-brand-3);
-}
-
-.dark {
- --vp-c-brand-1: hsl(196, 100%, 83%);
- --vp-c-brand-2: hsl(196, 74%, 63%);
- --vp-c-brand-3: hsl(196, 70%, 55%);
- --vp-c-brand-soft: hsla(196, 100%, 70%, 0.16);
-}
-
-// Background
-html.dark {
- --va-c-bg: hsl(196, 5%, 11%);
- --va-c-bg-light: hsl(196, 10%, 14%);
- --va-c-bg-alt: hsl(196, 4%, 9%);
- --va-c-bg-soft: hsl(196, 10%, 14%);
- --va-c-bg-mute: hsl(0, 0%, 18%);
-}
-
-.dark {
- --vp-c-bg: hsl(196, 7%, 11%);
- --vp-c-bg-alt: hsl(196, 4%, 9%);
- --vp-c-bg-elv: hsl(196, 10%, 14%);
- --vp-c-bg-soft: hsl(196, 10%, 14%);
-}
-
-// Link
-:root {
- --va-c-link: var(--vp-c-brand-1);
-}
-
-html.dark {
- --va-c-link: var(--vp-c-brand-1);
-}
-
-// Theme image
-.theme-image-container {
- position: relative;
- display: inline-block;
- max-width: 100%;
-}
-
-.theme-image-light,
-.theme-image-dark,
-img[src$='#light'],
-img[src$='#dark'] {
- max-width: 100%;
- height: auto;
- transition: opacity 0.3s ease-in-out;
-}
-
-.theme-image-container .theme-image-light {
- display: block;
-}
-
-.theme-image-container .theme-image-dark {
- display: none;
- position: absolute;
- top: 0;
- left: 0;
- width: 100%;
-}
-
-.dark .theme-image-container .theme-image-light {
- display: none;
-}
-
-.dark .theme-image-container .theme-image-dark {
- display: block;
-}
-
-img[src$='#light'] {
- display: block;
-}
-
-img[src$='#dark'] {
- display: none;
-}
-
-.dark img[src$='#light'] {
- display: none;
-}
-
-.dark img[src$='#dark'] {
- display: block;
-}
diff --git a/tsconfig.json b/tsconfig.json
index 744de2730..36ca26037 100644
--- a/tsconfig.json
+++ b/tsconfig.json
@@ -1,22 +1,20 @@
{
"compilerOptions": {
"target": "ESNext",
- "jsx": "preserve",
- "lib": ["DOM", "ESNext"],
- "baseUrl": ".",
"module": "ESNext",
- "moduleResolution": "node",
- "resolveJsonModule": true,
+ "moduleResolution": "Bundler",
+ "lib": ["DOM", "ESNext"],
+ "jsx": "preserve",
"strict": true,
- "strictNullChecks": true,
"noUnusedLocals": true,
+ "resolveJsonModule": true,
"esModuleInterop": true,
"forceConsistentCasingInFileNames": true,
"skipLibCheck": true,
- "allowSyntheticDefaultImports": true,
"allowImportingTsExtensions": true,
"noEmit": true,
- "typeRoots": ["./node_modules/@types"]
+ "types": ["node", "vitepress/client"]
},
- "exclude": ["dist", "node_modules"]
+ "include": [".vitepress/**/*.ts", ".vitepress/**/*.mts", ".vitepress/**/*.vue"],
+ "exclude": ["dist", "node_modules", ".vitepress/cache"]
}
diff --git a/types/image.d.ts b/types/image.d.ts
deleted file mode 100644
index 377d4ff08..000000000
--- a/types/image.d.ts
+++ /dev/null
@@ -1,3 +0,0 @@
-declare module '*.webp'
-declare module '*.png'
-declare module '*.svg'
diff --git a/utils/ensure-full-git.js b/utils/ensure-full-git.js
index 1521822df..75d67da6c 100644
--- a/utils/ensure-full-git.js
+++ b/utils/ensure-full-git.js
@@ -1,6 +1,6 @@
#!/usr/bin/env node
-import { execSync } from 'child_process'
-import { existsSync } from 'fs'
+import { execSync } from 'node:child_process'
+import { existsSync } from 'node:fs'
/**
* Restores complete Git history for shallow clones to fix contributor tracking issues.
@@ -31,7 +31,7 @@ async function checkAndRestoreHistory() {
console.error('❌ Failed to restore Git history:', error.message)
// process.exit(1)
console.warn(
- '! This may result in incomplete contributor information in `valaxy-addon-git-log`. Consider manually running: git fetch --unshallow'
+ '! This may result in incomplete page contributors and last-updated times. Consider manually running: git fetch --unshallow'
)
}
}
diff --git a/utils/languageDetector.ts b/utils/languageDetector.ts
deleted file mode 100644
index 61bb06aa6..000000000
--- a/utils/languageDetector.ts
+++ /dev/null
@@ -1,136 +0,0 @@
-const SUPPORTED_LANGUAGES = ['en', 'zh-CN'] as const
-const DEFAULT_LANGUAGE = 'en'
-
-function detectBrowserLanguage(): string {
- const browserLanguages = navigator.languages || [navigator.language]
-
- if (import.meta.env.DEV) {
- console.log('Browser languages:', browserLanguages)
- console.log('Supported languages:', SUPPORTED_LANGUAGES)
- }
-
- for (const browserLang of browserLanguages) {
- if (SUPPORTED_LANGUAGES.includes(browserLang as any)) {
- if (import.meta.env.DEV) {
- console.log('Exact match found:', browserLang)
- }
- return browserLang
- }
- }
-
- for (const browserLang of browserLanguages) {
- const langCode = browserLang.split('-')[0]
- const matchedLang = SUPPORTED_LANGUAGES.find(lang => lang.startsWith(langCode))
- if (matchedLang) {
- if (import.meta.env.DEV) {
- console.log('Language code match found:', matchedLang, 'for browser lang:', browserLang)
- }
- return matchedLang
- }
- }
-
- if (import.meta.env.DEV) {
- console.log('⚠️ No match found, using default language:', DEFAULT_LANGUAGE)
- }
- return DEFAULT_LANGUAGE
-}
-
-function setLanguage(lang: string, locale?: any) {
- if (locale && locale.value !== lang) {
- if (import.meta.env.DEV) {
- console.log('Setting language from', locale.value, 'to', lang)
- }
-
- locale.value = lang
- }
-
- if (typeof document !== 'undefined') {
- document.documentElement.lang = lang
- }
-
- if (typeof localStorage !== 'undefined') {
- localStorage.setItem('valaxy-lang', lang)
- }
-
- if (import.meta.env.DEV) {
- console.log(`Language switched to: ${lang}`)
- }
-}
-
-export function initLanguageDetection(locale?: any) {
- try {
- let sessionInitialized: string | null = null
- if (typeof sessionStorage !== 'undefined') {
- sessionInitialized = sessionStorage.getItem('valaxy-lang-session-initialized')
- }
-
- if (sessionInitialized === 'true') {
- if (import.meta.env.DEV) {
- console.log('Language already initialized in this session, skipping')
- }
- return
- }
-
- let savedLang: string | null = null
- let hasVisitedBefore: string | null = null
-
- if (typeof localStorage !== 'undefined') {
- savedLang = localStorage.getItem('valaxy-lang')
- hasVisitedBefore = localStorage.getItem('valaxy-lang-initialized')
- }
-
- if (import.meta.env.DEV) {
- console.log('Saved language preference:', savedLang)
- console.log('Has visited before:', hasVisitedBefore)
- }
-
- if (hasVisitedBefore === 'true') {
- if (savedLang && SUPPORTED_LANGUAGES.includes(savedLang as any)) {
- if (import.meta.env.DEV) {
- console.log('Using saved language preference (returning user):', savedLang)
- }
- setLanguage(savedLang, locale)
- } else {
- const currentLang = locale?.value || DEFAULT_LANGUAGE
- if (import.meta.env.DEV) {
- console.log('Using current/default language (returning user):', currentLang)
- }
- setLanguage(currentLang, locale)
- }
- } else {
- const detectedLang = detectBrowserLanguage()
- if (import.meta.env.DEV) {
- console.log('First visit - auto-detected language:', detectedLang)
- }
-
- setLanguage(detectedLang, locale)
-
- if (typeof localStorage !== 'undefined') {
- localStorage.setItem('valaxy-lang-initialized', 'true')
- }
- }
-
- if (typeof sessionStorage !== 'undefined') {
- sessionStorage.setItem('valaxy-lang-session-initialized', 'true')
- }
- } catch (error) {
- console.error('ERROR in language initialization:', error)
- setLanguage(DEFAULT_LANGUAGE, locale)
- if (typeof sessionStorage !== 'undefined') {
- sessionStorage.setItem('valaxy-lang-session-initialized', 'true')
- }
- }
-}
-
-export function setLanguageManually(lang: string, locale?: any) {
- if (SUPPORTED_LANGUAGES.includes(lang as any)) {
- setLanguage(lang, locale)
-
- if (typeof localStorage !== 'undefined') {
- localStorage.setItem('valaxy-lang-initialized', 'true')
- }
- if (typeof sessionStorage !== 'undefined') {
- sessionStorage.setItem('valaxy-lang-session-initialized', 'true')
- }
- }
-}
diff --git a/valaxy.config.ts b/valaxy.config.ts
deleted file mode 100644
index cd0690ea5..000000000
--- a/valaxy.config.ts
+++ /dev/null
@@ -1,201 +0,0 @@
-import type { PressTheme } from 'valaxy-theme-press'
-import process from 'node:process'
-import { $t, defineValaxyConfig } from 'valaxy'
-import { addonAlgolia } from 'valaxy-addon-algolia'
-import { addonComponents } from 'valaxy-addon-components'
-import { addonGitLog } from 'valaxy-addon-git-log'
-
-import { localIconLoader } from 'vitepress-plugin-group-icons'
-import { markdownThemeImagePlugin } from './utils/markdown-theme-image'
-import { fetchOpenListVersion } from './utils/version'
-
-const COMMIT_TAG = process.env.COMMIT_TAG || (await fetchOpenListVersion()) || 'dev'
-const DOCS_COMMIT_SHA = process.env.CF_PAGES_COMMIT_SHA || process.env.DOCS_COMMIT_SHA
-const DOCS_ICP = process.env.DOCS_ICP || ''
-const DOCS_CN = DOCS_ICP !== ''
-const DOCS_BUILT_DATE = new Date().toLocaleString('zh-CN', { hour12: false }).replace('T', ' ')
-// Must have SITE_URL or build fails
-const SITE_URL = process.env.SITE_URL || 'https://doc.oplist.org'
-const VITE_BASE = process.env.VITE_BASE || '/'
-
-const safelist = ['i-ri-home-line', 'i-ri-github-line', 'i-ri-arrow-up-line']
-
-export default defineValaxyConfig({
- siteConfig: {
- title: $t('siteConfig.title'),
- url: SITE_URL,
- description: $t('siteConfig.description'),
-
- author: {
- name: 'OpenList Team',
- link: 'https://github.com/OpenListTeam',
- avatar: `${SITE_URL}/logo.svg`,
- },
-
- comment: {
- enable: DOCS_CN ? false : true,
- },
-
- search: {
- enable: true,
- type: 'algolia',
- },
-
- encrypt: {
- enable: false,
- },
-
- mediumZoom: {
- enable: true,
- },
-
- statistics: {
- enable: true,
- },
-
- license: {
- enabled: false,
- },
- },
-
- addons: [
- // Cannot uncomment this, or build error
- addonAlgolia({
- appId: 'I80ZVXR7H9',
- apiKey: '2a3fe6e1f95a3c8ca60fee55e44c00a1',
- indexName: 'Document Crawler CN',
- }),
- addonComponents(),
- addonGitLog({
- contributor: {
- strategy: 'prebuilt',
- },
- repositoryUrl: 'https://github.com/OpenListTeam/OpenList-Docs',
- }),
- ],
-
- theme: 'press',
- themeConfig: {
- logo: `${VITE_BASE.replace(/\/$/, '')}/logo.svg`,
- sidebar: ['guide', 'configuration', 'faq', 'seeds', 'api', 'migration', 'ecosystem'],
- socialLinks: [{ icon: 'i-ri-github-line', link: 'https://github.com/OpenListTeam/OpenList' }],
- nav: [
- {
- text: 'nav.guide',
- link: '/guide',
- },
- {
- text: 'nav.configuration',
- link: '/configuration',
- },
- {
- text: 'nav.faq',
- link: '/faq',
- },
- {
- text: 'nav.seeds',
- link: '/seeds',
- },
- {
- text: 'nav.ecosystem',
- link: '/ecosystem',
- },
- {
- text: 'nav.community.title',
- items: [
- {
- text: 'nav.community.discussions',
- link: 'https://github.com/OpenListTeam/OpenList/discussions',
- },
- {
- text: 'nav.community.telegram',
- link: 'https://t.me/OpenListTeam',
- },
- {
- text: 'nav.community.telegram_channel',
- link: 'https://t.me/OpenListOfficial',
- },
- ],
- },
- {
- text: COMMIT_TAG,
- items: [
- {
- text: 'Release Notes',
- link: 'https://github.com/OpenListTeam/OpenList/releases',
- },
- ],
- },
- ],
-
- // Why default to be `https://github.com/YunYouJun/valaxy/edit/main/docs/:path`?
- editLink: {
- pattern: 'https://github.com/OpenListTeam/OpenList-Docs/edit/main/:path',
- },
-
- footer: {
- message: DOCS_COMMIT_SHA
- ? `Commit ${DOCS_COMMIT_SHA?.slice(0, 8)} built at ${DOCS_BUILT_DATE}`
- : `Built at ${DOCS_BUILT_DATE}`,
- copyright: `AGPL-3.0 Licensed | © 2022-${new Date().getFullYear()} The OpenList Projects Contributors${DOCS_ICP ? ' | ' + DOCS_ICP + '' : ''}`,
- },
- },
-
- vite: {
- base: VITE_BASE,
- resolve: {
- alias: {
- 'valaxy-theme-press/components/PressNavScreenMenuLink.vue':
- './components/PressNavScreenMenuLink.vue',
- },
- },
- },
- unocss: {
- safelist,
- },
-
- markdown: {
- blocks: {
- tip: {
- icon: 'i-carbon-thumbs-up',
- },
- warning: {
- icon: 'i-carbon-warning-alt',
- },
- danger: {
- icon: 'i-carbon-warning',
- },
- info: {
- icon: 'i-carbon-information',
- },
- },
-
- codeTransformers: [
- // We use `[!!code` in demo to prevent transformation, here we revert it back.
- {
- postprocess(code) {
- return code.replace(/\[!!code/g, '[!code')
- },
- },
- ],
- // theme: 'material-theme-palenight',
- config: md => {
- md.use(markdownThemeImagePlugin)
- },
- },
-
- groupIcons: {
- customIcon: {
- valaxy: localIconLoader(import.meta.url, './public/favicon.svg'),
- docker: 'vscode-icons:file-type-docker',
- nginx: 'vscode-icons:file-type-nginx',
- toml: 'vscode-icons:file-type-toml',
- },
- },
-
- modules: {
- rss: {
- enable: false,
- },
- },
-})
+
+
+
+
+
diff --git a/.vitepress/theme/components/WorkInProgress.vue b/.vitepress/theme/components/WorkInProgress.vue
new file mode 100644
index 000000000..c581edc7c
--- /dev/null
+++ b/.vitepress/theme/components/WorkInProgress.vue
@@ -0,0 +1,40 @@
+
+
+
+
+
+
+
+
+
+
diff --git a/components/openlist_releases_db.json b/.vitepress/theme/components/openlist_releases_db.json
similarity index 100%
rename from components/openlist_releases_db.json
rename to .vitepress/theme/components/openlist_releases_db.json
diff --git a/.vitepress/theme/i18n.ts b/.vitepress/theme/i18n.ts
new file mode 100644
index 000000000..04f843040
--- /dev/null
+++ b/.vitepress/theme/i18n.ts
@@ -0,0 +1,75 @@
+import { useData } from 'vitepress'
+import { computed } from 'vue'
+
+const messages = {
+ en: {
+ wip: 'WIP, please stay tuned',
+ appearance: {
+ title: 'Theme',
+ auto: 'System',
+ light: 'Light',
+ dark: 'Dark',
+ },
+ tooltip: {
+ back_to_top: 'Back to Top',
+ },
+ post: {
+ contributors: 'Contributors',
+ },
+ download: {
+ all: 'All',
+ os: 'Operating System',
+ cpu: 'CPU Architecture',
+ down_source: 'Download Source',
+ download: 'Download',
+ gh_proxy: 'GhProxy',
+ version: 'Version',
+ beta: 'Beta',
+ latest: 'Latest',
+ },
+ },
+ 'zh-CN': {
+ wip: '编写中，敬请期待',
+ appearance: {
+ title: '主题',
+ auto: '跟随系统',
+ light: '浅色',
+ dark: '深色',
+ },
+ tooltip: {
+ back_to_top: '回到顶部',
+ },
+ post: {
+ contributors: '贡献者',
+ },
+ download: {
+ all: '全部',
+ os: '操作系统',
+ cpu: 'CPU 架构',
+ down_source: '下载来源',
+ download: '下载',
+ gh_proxy: '加速下载',
+ version: '版本',
+ beta: '测试版',
+ latest: '最新版',
+ },
+ },
+} as const
+
+type Locale = keyof typeof messages
+
+/** Minimal replacement for vue-i18n's `useI18n`, driven by the VitePress locale. */
+export function useI18n() {
+ const { lang } = useData()
+ const locale = computed🧪
+ {{ t('wip') }}
+
-
-
-
- -
-
-
-
-
-
-
-
-
diff --git a/components/AppLink.vue b/components/AppLink.vue
deleted file mode 100644
index 057f9cbb7..000000000
--- a/components/AppLink.vue
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
-
-
- - - {{ addon.name }} -
- - - -
-
-
- {{ addon.desc }}
-
-
-
-
- {{ addon.desc_zh }}
-
- -
-
-
-
-
-
- #{{ tag }}
-
-
- - - - -
- diff --git a/components/CustomVueDemo.vue b/components/CustomVueDemo.vue deleted file mode 100644 index c25b38265..000000000 --- a/components/CustomVueDemo.vue +++ /dev/null @@ -1,26 +0,0 @@ - - - -
- {{ num }}
-
-
-
-
diff --git a/components/InlineIcon.vue b/components/InlineIcon.vue
deleted file mode 100644
index 97cf31455..000000000
--- a/components/InlineIcon.vue
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
-
-
-
-
diff --git a/components/OpenListContributors.vue b/components/OpenListContributors.vue
deleted file mode 100644
index 5193e38b1..000000000
--- a/components/OpenListContributors.vue
+++ /dev/null
@@ -1,10 +0,0 @@
-
-
-
-
-
-
-
- ![OpenList Logo]()
-
-
-
-
diff --git a/components/PressButton.vue b/components/PressButton.vue
deleted file mode 100644
index bad1a51aa..000000000
--- a/components/PressButton.vue
+++ /dev/null
@@ -1,38 +0,0 @@
-
-
-
-
-
-
-
-
-
- {{ t(text) }}
-
-
-
-
-
-
diff --git a/components/PressHomeHero.vue b/components/PressHomeHero.vue
deleted file mode 100644
index 76b5e6a19..000000000
--- a/components/PressHomeHero.vue
+++ /dev/null
@@ -1,72 +0,0 @@
-
-
-
-
-
-
-
-
- - {{ fm.hero.name }} -
-- {{ t('hero.banner') }} -
- -
-
-
-
-
-
-
-
-
- - diff --git a/components/PressNavBar.vue b/components/PressNavBar.vue deleted file mode 100644 index 426657c1c..000000000 --- a/components/PressNavBar.vue +++ /dev/null @@ -1,109 +0,0 @@ - - - - - -
-
- ![LOGO]()
- {{ t('siteConfig.title') }}
-
-
-
-
-
diff --git a/components/PressNavScreenMenuLink.vue b/components/PressNavScreenMenuLink.vue
deleted file mode 100644
index 2b0ae2a6e..000000000
--- a/components/PressNavScreenMenuLink.vue
+++ /dev/null
@@ -1,43 +0,0 @@
-
-
-
-
-
-
-
-
- ![]()
- ![]()
-
-
-
-
diff --git a/components/WorkInProgress.vue b/components/WorkInProgress.vue
deleted file mode 100644
index 431febf02..000000000
--- a/components/WorkInProgress.vue
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
-
-
-
-
-
diff --git a/components/api/ApiDocsRedirect.vue b/components/api/ApiDocsRedirect.vue
deleted file mode 100644
index 464688b29..000000000
--- a/components/api/ApiDocsRedirect.vue
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- - -
- - {{ t('wip') }} -Redirecting...
-
diff --git a/eslint.config.js b/eslint.config.js
new file mode 100644
index 000000000..27a256dda
--- /dev/null
+++ b/eslint.config.js
@@ -0,0 +1,33 @@
+import js from '@eslint/js'
+import prettier from 'eslint-config-prettier/flat'
+import { defineConfig, globalIgnores } from 'eslint/config'
+import pluginVue from 'eslint-plugin-vue'
+import globals from 'globals'
+import tseslint from 'typescript-eslint'
+
+export default defineConfig(
+ globalIgnores(['dist', '.vitepress/cache']),
+ js.configs.recommended,
+ tseslint.configs.recommended,
+ pluginVue.configs['flat/recommended'],
+ {
+ languageOptions: {
+ globals: { ...globals.browser, ...globals.node },
+ },
+ },
+ {
+ files: ['**/*.vue'],
+ languageOptions: {
+ parserOptions: { parser: tseslint.parser },
+ },
+ },
+ {
+ files: ['.vitepress/theme/**'],
+ rules: {
+ // VitePress's `Layout` and the components used as tags in Markdown keep their single-word names
+ 'vue/multi-word-component-names': 'off',
+ },
+ },
+ // formatting is Prettier's job
+ prettier
+)
diff --git a/layouts/default.vue b/layouts/default.vue
deleted file mode 100644
index bfb6f7a8d..000000000
--- a/layouts/default.vue
+++ /dev/null
@@ -1,95 +0,0 @@
-
-
-
-
-
-
- - - {{ t('post.contributors') }} - -
-
-
-
-
-
-After deployment, please log in to the [EdgeOne Functions console](https://console.tencentcloud.com/edgeone/pages) to modify environment variables. Please refer to the [Variable Description](#variable-description) section.
-
-- EdgeOne Functions China
-
-
-
-
-
-After deployment, please log in to the [EdgeOne Functions console](https://console.cloud.tencent.com/edgeone/pages) to modify environment variables. Please refer to the [Variable Description](#variable-description) section.
-
-- Cloudflare Workers Global
+## APIPages 的部署教程
-
-
+
+
+After deployment, please log in to the [EdgeOne Functions console](https://console.tencentcloud.com/edgeone/pages) to modify environment variables. Please refer to the [Variable Description](#variable-description) section.
+
+- EdgeOne Functions China
+
+
+
+
+
+After deployment, please log in to the [EdgeOne Functions console](https://console.cloud.tencent.com/edgeone/pages) to modify environment variables. Please refer to the [Variable Description](#variable-description) section.
+
+- Cloudflare Workers Global
+
+
+
+
+
+
diff --git a/pages/en/guide/advanced/s3.md b/pages/en/guide/advanced/s3.md
new file mode 100644
index 000000000..bc7eb15ba
--- /dev/null
+++ b/pages/en/guide/advanced/s3.md
@@ -0,0 +1,57 @@
+---
+categories:
+ - guide
+ - advanced
+top: 40
+---
+
+# S3
+
+This function is to map OpenList as the S3 protocol. You can use the [S3 client](#s3-client-recommendation-fill-in-sample), just as OpenList can be mapped to WebDAV.
+
+- It can be the entire OpenList (root directory) or a separate folder
+
+## 1. How to use
+
+1.1 If it is for the first time, first open OpenList Manage to generate `S3 access key id` and `S3 secret access key` to save, then stop OpenList, open the configuration file to enable the `S3` service
+
+- If you update ID and secrets in the future, update and save, and then restart OpenList to take effect
+
+
+
+1.2 Open the [Configuration File](../../configuration/configuration.md#s3), change the `enable` field to` true` to enable S3 service
+
+```json{2}
+ "s3": {
+ "enable": true,
+ "port": 5246,
+ "ssl": false
+ }
+```
+
+1.3 After the first two steps are completed, Start OpenList, open the Manage `s3` configuration page, and choose to store a certain path as an object to store the barrel
+
+- On the left is the name of the storage bucket displayed outside, and the right is the existing list directory path of OpenList. If you want to map the entire root directory, you can choose the `root` path in the list
+ - There may be errors in manual filling. It is recommended to use the `Choose` button on the right side for selection
+ 
+
+## 2. Use instructions
+
+1. For ordinary object downloads, the transfer mode depends on the storage and proxy settings:
+ - If proxying is not required and the storage provides a direct download URL, OpenList may return an HTTP 302 redirect to the storage provider.
+ - If **Web Proxy** is enabled for the target storage, or another driver or proxy rule requires proxying, OpenList serves the response body through the local server.
+2. A direct redirect saves OpenList bandwidth, but the S3 client must follow a cross-host redirect and accept the provider URL's access requirements. Server relay uses OpenList bandwidth and is a safer starting point for clients that cannot use the direct provider redirect. For repository tools such as restic or rustic, enable **Web Proxy** unless direct mode has been verified.
+3. Currently only supports the use of client operations `List`, `get`, `put`, `del`, other operations are not supported yet
+4. Currently only supports the use of the `S3 Client` to operate, Mount S3 to the `OpenList Object Storage` temporarily unavailable
+
+## 3. S3 client recommendation/fill in sample
+
+### 3.1. S3 Browser
+
+S3 Browser：[https://s3browser.com](https://s3browser.com/download.aspx)
+
+
+
+### 3.2. S3Drive
+
+
diff --git a/pages/en/guide/advanced/search.md b/pages/en/guide/advanced/search.md
new file mode 100644
index 000000000..b94d4cebb
--- /dev/null
+++ b/pages/en/guide/advanced/search.md
@@ -0,0 +1,236 @@
+---
+categories:
+ - guide
+ - advanced
+top: 100
+---
+
+# Search
+
+### how to use
+
+::: danger Follow the steps below to enable search:
+
+1. Go to the `indexes` page to select a **Search index** and click `Save`.
+2. After the index is saved, click `Build indexes` to build the index.
+3. Now you can search for files by click the search block on the top right corner of the page or by using the shortcut `Ctrl + K`.
+
+:exclamation: If you do not follow the above prompts, the prompt will be opened: **Search Not available**
+:::
+
+## Difference between different search indexes
+
+- `database`: Search by database, which is using the existing data.db. It will create a new table, record the parent directory, name, and size of every object, but the search does not split words which means that match whether the keywords you enter appear in the name of object. In general, if you don't have a specific search requirement, we recommend you choose it.
+
+- `database (non-full-text search)`: The full-text search mode is used above, but full-text search will have some strange problems when using **MySQL database** as an OpenList database, which has not been resolved yet, so if your OpenList database Change to **MySQL**, and your OpenList version **`≥3.9.1`** It is recommended that you use this to build an index, although it is slower than full-text search and the gap is not very big, but it will not search for strange files , it’s more secure. After the future version is repaired, we will inform you to use the new full-text search to build the index. If you are using **sqlite3**, you can use whichever you like.
+
+- `bleve`: An open source full-text search engine. It will split the words in the name of object and search for the keywords you enter. But its search results may be so strange that you can't get the results you want, and it will take up more resources.
+
+- **sqlite3** is easy to trigger `database is locked` lock library cannot write files
+ - Solution to `database is locked`:
+ - It's because the database is building the index. If you are still in the building process, please wait patiently.
+ - If the index has been completed, it is caused by turning on [Automatically update the index](#automatically-update-the-index). Please turn off [Automatically update the index](#automatically-update-the-index). If the problem still occurs, please close and restart OpenList.
+ - Or switch the database to MySQL
+
+- `meilisearch`: A feature-rich, multilingual, blazing-fast search engine written in Rust. More accurate compared to `bleve`.
+ Requires [self-hosting](https://www.meilisearch.com/docs/learn/self_hosted/getting_started_with_self_hosted_meilisearch) or using a cloud service.
+ `OpenList` uses "http://localhost:7700" as the default meilisearch host,
+ if you host `meilisearch` and `OpenList` together locally with `meilisearch` authentication disabled, `OpenList` will automatically connect it,
+ otherwise you need to modify the **meilisearch** field in the configuration file (host, index UID, API key).
+ When `meilisearch` instance is protected by `api key`, the minimal actions of `api key` required by `OpenList` are `["search","indexes.get","settings.*","documents.*","tasks.*"]`.
+ Storage Space Usage: ~800MiB per 100,000 files (including folders), which may be larger or smaller depending on filename length and folder depth. Please note that the storage space occupied by `meilisearch` will increase as files are continuously added/updated, and space will not be released even if you delete some or all documents from the index, unless you create a refresh instance. Generally, you don't need to worry too much about this situation, as the storage space usage will stabilize at a certain value with use, and will only have a significant impact on space usage when large numbers of files are added.
+ - Download：https://github.com/meilisearch/meilisearch/releases
+ - `meilisearch` Docs：https://www.meilisearch.com/docs/
+ - Reference：https://github.com/AlistGo/alist/discussions/6830
+
+The following table could help you understand the difference between these search indexes quickly:
+
+| | database(full text search) | Database (non-full-text search) | bleve | meilisearch |
+| ----------------------- | ----------------------------------------------- | ------------------------------------------------------------------------ | ----------- | ----------------------------------------- |
+| Search results | Can't search in Chinese | More accurate than full-text search, you can search Chinese | Fuzzy match | Support CJK tokenizers & Chinese variants |
+| Search speed | Fast,see above for advantages and disadvantages | Slower than full-text search, see above for advantages and disadvantages | Fast | Blazing fast |
+| Specify folder search | Yes | Yes | No | Yes |
+| Disk usage | Low | Low | High | High |
+| Auto incremental update | Yes | Yes | No | Yes |
+
+::: warning
+If you are using _MySQL_ as the database, it is recommended to use **`non-full-text search`** (strongly recommended)
+
+**`Non-full-text search`** Although it is not as fast as full-text search, it is not much slower. If you insist on using full-text search, you may have to sacrifice the inability to search Chinese
+
+If you use sqlite as the database, there is no full-text search, you can choose any database~
+
+Full-text search: It will not search in the text of all files, don't get it wrong.
+:::
+
+### Deploy MeiliSearch for indexing using Docker Compose
+
+#### Deploy MeiliSearch using Docker Compose
+
+Feeling confused?
+
+Here's a Compose example to add `meilisearch` to your Openlist Compose. Follow the steps to set up indexing with `meilisearch`.
+
+```yaml
+version: '3.3'
+services:
+ openlist:
+ image: 'openlistteam/openlist:beta-aio'
+ container_name: openlist
+ volumes:
+ - '/tmp/data/Docker/OpenList:/opt/openlist/data'
+ ports:
+ - '5244:5244'
+ environment:
+ - UMASK=022
+ networks:
+ - openlist
+ restart: unless-stopped
+
+ meilisearch:
+ image: getmeili/meilisearch:v1.16
+ container_name: meilisearch
+ ports:
+ - '7700:7700'
+ volumes:
+ - /tmp/data/Docker/meilisearch/meili_data:/meili_data
+ command: meilisearch --schedule-snapshot --snapshot-dir /meili_data/snapshots
+ environment:
+ - MEILI_MASTER_KEY=your_master_key_here
+ tty: true
+ stdin_open: true
+ networks:
+ - openlist
+ restart: unless-stopped
+
+networks:
+ openlist:
+ driver: bridge
+```
+
+Configuration Explanation:
+
+- `UMASK`: Sets file permissions
+- `getmeili/meilisearch:v1.16`: Official recommendation to use a fixed version number (latest version at time of writing is `v1.16`). You may check the latest version yourself via the [official local deployment docs](https://www.meilisearch.com/docs/learn/self_hosted/install_meilisearch_locally).
+- Additional parameters for meilisearch can be modified via the [official local deployment docs](https://www.meilisearch.com/docs/learn/self_hosted/install_meilisearch_locally) or deployed using alternative methods.
+
+::: warning
+The `/tmp/data/Docker` directory here is merely an example; please store your data in an appropriate location.
+
+Additionally, the `MEILI_MASTER_KEY` here should be replaced with a key you generate yourself. You should substitute it with any alphanumeric string of 16 bytes or more. In most cases, one character corresponds to one byte.
+
+PS: This provides only a basic example. Please modify it according to your needs and add other configurations as required.
+:::
+
+#### Setting up meilisearch in openlist
+
+How to configure MeiliSearch in OpenList
+
+First, you need to modify config.json. In this example, it should be located at `/tmp/data/Docker/OpenList/config.json`.
+
+Edit the section below, filling in the IP address and port of your MeiliSearch instance, along with the key you set in `MEILI_MASTER_KEY`.
+
+```json
+ "meilisearch": {
+ "host": "http://meilisearch:7700",
+ "api_key": "your_master_key_here",
+ "index": "openlist"
+ },
+```
+
+Next, open the management panel, click `Indexes`, select `meilisearch`, and click `Refresh` to rebuild the index.
+
+{width=600px}
+
+## Search tips
+
+- If you want to search for a specific folder, you must choose `database` as the search index;
+- If you choose `database` as the search index and the type of your database is `sqlite3`, we suggest that you don't make any changes in the admin page while building the index, as sqlite3 does not support concurrent writes and can cause `database-lock` issues;
+- If you choose `bleve` as the search index, and if you want to search for new files or if you don't want to search for deleted files, the index needs to be completely rebuilt to take effect because `bleve` does not support incremental updates;
+- But for `database`, it supports incremental updates, so you can search for new files or deleted files just by access the modified folder (and click `refresh` icon if cached) without rebuilding the index, which is much more convenient than `bleve`.
+
+### Ignore paths
+
+Paths to be skipped during index building, one path per line, multiple lines can be filled
+
+- Example:
+ - `/aaa network disk`
+ - `/bbb network disk/ccc folder`
+
+If you don't want to configure this, you can turn on the `disable index` option in each driver
+
+## Update index
+
+- (formerly: the path to update the index)
+ After building all the indexes, or a file has a large number of file updates, but it is inconvenient to rebuild, you can use this to update the index
+- Example: - /aaa network disk - /bbb network disk/ccc folder
+
+### Automatically update the index
+
+:warning: **`The default is off, and the index will not be built automatically`**.
+
+For example, you have already built the index, but added a **network disk mount** or **folder update** later.
+
+But you have already built a lot of indexes. According to the previous words, there are two methods.
+
+1. Go in folder by folder before building
+
+2. Or it is cumbersome to refactor all
+
+ But this time, just turn on the **`Automatically build index`** button and enter the **Newly mounted network disk** or **Updated folder**, the indexed files in this directory and The folder automatically builds the index without entering a folder by folder to let him build it automatically
+
+- Advantages: Don't worry, all the indexes in this folder can be automatically built if there is an update into the root directory of the updated folder
+- Cons: always on call ready to build
+
+---
+
+Someone will find out that [**Path to update index**](#Path to update index) can also be updated? Can be updated but the two do not conflict.
+
+- [**Automatically update index**](#automatically-update-the-index): suitable for users who build indexes for all files
+- [**Update Index**](#update-index): Suitable for **not** to build indexes for all files, but there are files that need to be built, manually build indexes to avoid all being indexed
+
+### Maximum index depth
+
+default 20.
+The one shown outside is built manually, and the update index option selects the depth in the update index button.
+Explanation: The directory can enter up to several layers. For example, if you have a folder with a depth of 30 layers, set it to 20, and only build the first 20 layers, and the remaining 10 layers will not be built.
+
+## :warning: Precautions for use
+
+- OpenList **V2** and **v3** types of mounts cannot be built by default
+- If you are using **MySQL** as the database, it is recommended that you use **database (non-full-text search)**, [**Click to view details to see the second item**](#difference-between-different-search-indexes)
+- In the future version (**≥3.9.0 version**), V3 users can choose whether to allow others to mount your network disk and then index it :no_entry:**`Use with caution`**:no_entry:
+ - View details: [allow-indexing](/en/configuration/site#allow-indexing)
+ - Don't ask why V2 is not supported, because the V2 version is no longer maintained, so there is no follow-up
+- Why not directly open V2 V3 index construction: **https://github.com/alist-org/alist/discussions/2529**
+- After building an index, users without permissions can search for hidden file/folder solutions [click to view](meta.md#tips)
+
+## The database file is very large, what should I do if it is still the same after clearing the index?
+
+Normal users do not modify the database options. They use the `sqlite` database to build indexes, which will cause the database file to be particularly large
+
+- Data files, `Data` folders in the same directory in OpenList program,`data.db，data.db-shm，data.db-wal`
+
+After turning on the constructive index, the more the number you build, the larger the files. Finally, you accidentally occupy the machine's hard disk, and then click the clear index button. What should I do if the file is still as big?
+
+- This is caused by the cache of `sqlite`, there are two solutions:
+ 1. We use commands or tools to connect to `sqlite` database, input：**`VACUUM;`**
+
+ ```sql
+ VACUUM;
+ ```
+
+ 2. After using the command to clean up, we replace it with `mysql` database before constructing indexes
+ - Sqlite replaced with mysql database tutorial：**[BV1iV4y1T7kh](https://www.bilibili.com/video/BV1iV4y1T7kh)**
+
+ Comparison after cleaning the command: The picture above shows before cleaning up, and the following figure shows that after cleaning, you can execute several commands several times if there is no effect.
+
+ 
+
+---
+
+`data.db, data.db-shm, data.db-wal` when backup, when backup，`data.db-shm，data.db-wal` Do these two files need backup？
+
+- In the backup, stop the program first, and then backup. You only need to backup the `data.db` database file. The other two do not need to backup
+
+- It may be after you stop the program`data.db-shm，data.db-wal`will automatically disappear, don't worry
diff --git a/pages/en/guide/advanced/sso.md b/pages/en/guide/advanced/sso.md
new file mode 100644
index 000000000..3ff88c5c5
--- /dev/null
+++ b/pages/en/guide/advanced/sso.md
@@ -0,0 +1,164 @@
+---
+categories:
+ - guide
+ - advanced
+top: 60
+---
+
+# Third-party single sign-on
+
+## 1. Single sign-on client id
+
+client ID.
+
+## 2. Single sign-on client secrets
+
+client secrets.
+::: warning matters needing attention
+
+1. Remember to write and save the background parameters of OpenList. After writing and saving, you have to go back to the bottom of the personal data and there will be a button that needs to be bound, otherwise it cannot be used
+2. Only one of the four types of single sign-on can be enabled temporarily. If you used other single sign-on methods before and then changed to a new single Unbind (just one click) and then bind the single sign-on method you want to use now.
+3. If you use **`GitHub,Microsoft,Google,DingTalk`**, you only need to fill in the client ID and secret key, and select the corresponding platform in the options.
+ - If you use **`Casdoor`** the following parameters need to be filled in, just follow the tutorial to fill in
+
+:::
+
+## 3. Registration binding single sign-on
+
+##
+
+##
+
+##
+
+##
+
+##
+
+##
+
+##
+
+## 4. SSO automatically registers as an OpenList account
+
+- **OpenList Version > **v3.22.1** New Features**
+ Before using single sign-on to register as an OpenList account, we need to bind the single sign-on of OpenList first, the binding method is explained above
+- Supports the `five` single sign-on methods mentioned above
+- Do not use the default organization (**app-built-in**) directly, because all users in this organization are global administrator accounts
+- Except `CASDOOR`, you only need to fill in the` Client id` and the `Client secrets`and the newly added single login account registered as OpenList account configuration
+
+### 4.1. SSO Full Fill Demo
+
+Please refer to the detailed description below for how to fill in, the schematic diagram is just a reference for filling in and not suitable for everyone’s user habits
+
+
+
+### 4.2. SSO auto register
+
+If we want SSO single sign-on to be registered as an OpenList account, we need to enable this option before it can be used
+
+### 4.3. SSO default dir
+
+That is to say, the default path used by the registered account is equivalent to the `Base path` in the OpenList user settings.
+
+It can be the root directory `/`, or the path `/path/test/Demo` specified by the user
+
+
+
+### 4.4. SSO default permission
+
+It is equivalent to which permissions are enabled by default for registered users, as shown below
+
+
+
+
+
+The default is 0, no permission is enabled
+
+If we need to enable some permissions during registration, we only need the sum of the numbers of different permissions.
+
+For example：
+
+1. We need to open the user's `WebDav reading` and `WebDav manage ` by default, that is 256+512=768, we just fill in `768` in the options
+2. If we need to open the three permissions of `Make dir or upload`, `Rename` and `Delete` by default when registering, then it is 8+16+128=152, we can fill in `152` in the background
+ I won’t say much about the examples, just add the permissions you need
+
+### 4.5. Precautions and instructions
+
+**4.1-There is already this user in the OpenList user database**
+
+| username | password | base\*path | role | permission | opt_secret | github_id | disabled | sso_id |
+| ------------------ | -------- | ---------- | ---- | ---------- | ---------- | --------- | -------- | ----------- |
+| anyi | FzdDfkmU | /test1 | 0 | 3 | | | 0 | |
+| anyi**\*dc188911** | RUCtgqCw | /test1 | 0 | 3 | | | 0 | **dc18891** |
+
+As shown in the above table, a string of redundant ids is added after the newly registered single sign-on user name
+
+This is because the same user already exists in the OpenList user database, so the sso_id is also added after the user name
+
+If your newly registered single sign-on user name does not exist in the OpenList user database, it will not add the sso_id after the name
+
+**4.2-What should I do if I don’t want the SSO account to be registered as an OpenList account?**
+
+Just turn `SSO auto register` off,This will not affect the use of accounts that have been registered using Sso
+
+**4.3-If I turn off the single sign-on option, what should I do with the account registered with Sso?**
+
+Don't worry, after using single sign-on to register and log in to OpenList, log in in the background, and find `personal information` after logging in
+
+- You can modify **`username`** and **`password`** by yourself, save it after modification, so that you can log in with the OpenList account normally
+- At this time, you can click `Unbind Single Sign-On Platform`, you can unbind or not unbind, and the subsequent [**default path**](#sso-default-dir) and [**default permissions**](#sso-default-permission) of this user can only be modified by the administrator in the OpenList background user
+
+**4.4-Why is this error code displayed when using sso?**
+
+```json{3}
+{
+ "code": 400,
+ "message": "The single sign on platform is not bound to any users: record not found",
+ "data": null
+}
+```
+
+This is because [Single Sign-On Automatic Registration](#sso-auto-register) is not enabled for the OpenList account, and the single sign-on cannot be registered as an OpenList account
+
+- If you are an administrator, you can turn it on
+
+- If you are a user, you can contact the administrator to enable
+
+## 5. Sso compatibility mode
+
+OpenList single -point login is bound to Dingtalk, and then opens OpenList in the **`Dingtalk`** application, When you log in, choose Dingtalk login and jump to your computer browser. After authorization, you find that there is no response, because the browser cannot jump to the Dingtalk application inner browser page
+
+At this time, you need to open the **`sso compatability mode`** again to click on the login to log in successfully
+
+**OpenList applied in Dingtalk and opened as shown in the figure：**
+
+
+
+## 6. How to create the application in Dingtalk workbench
+
+A picture teaches you to create a new application and add it
+
+- LOGO is not modified when the newly -built newly built, you can wait for the newly built and then modify See_Figure_2
+- If you just browse OpenList in the Dingtalk application, you do n’t need a single -point login management, you do n’t need to set up a single -point login configuration, you can just add an application
+ 
+
+### 6.1. Modify the application logo
+
+Open [**DingTalk open platform management**](https://open-dev.dingtalk.com/fe/app#/corp/app) Find your newly built app to modify the logo.
+
+
+
+## 7. redirect url
+
+After turning on **`Sso compatibility mode`** Then you need to log in to the corresponding software to modify the redirect url to change it to the two redirect url below
+
+- `GitHub` only needs to add one：`http(s)://You_Url/api/auth/sso_get_token`
+- `Microsoft` and` Google` both need to be added, you can add multiple Redirect urls, so you only need to add two Redirect URLs.
+
+```
+http(s)://You_Url/api/auth/get_sso_id
+http(s)://You_Url/api/auth/sso_get_token
+```
+
+If you enable the **Sso compatibility mode** if you do not modify it, you will prompt `Invalid Redirect URL` Error
diff --git a/pages/en/guide/advanced/sso/01-GitHub.md b/pages/en/guide/advanced/sso/01-GitHub.md
new file mode 100644
index 000000000..a9506f397
--- /dev/null
+++ b/pages/en/guide/advanced/sso/01-GitHub.md
@@ -0,0 +1,30 @@
+### 3.1. Github
+
+::: warning
+If you want to use GitHub to log in, you first need the machine you built OpenList to be able to connect to GitHub before you can call and use it, otherwise you cannot use it if the link is not connected
+:::
+
+Open **https://github.com/settings/developers** Click **`New OAuth App`**
+
+#### 3.1.1. Register OAuth Instructions
+
+- Application name
+ - Write whatever you want to call it
+- **Homepage URL**
+ - home URL address
+ - Both **http** and **https** can be used
+- Application description
+ - write whatever you want
+- **Authorization callback URL**
+ - Callback URL address
+ - **https://your_domain/api/auth/sso_callback** - Both **http** and **https** can be used
+ Remember to get **Client secrets** after filling it out, and then fill it in the OpenList background.
+ Remember to write and save the background parameters of OpenList. After writing and saving, you have to go back to the bottom of the personal data and there will be a button that needs to be bound, otherwise it cannot be used
+
+#### 3.1.2. Completely fill in the reference schematic
+
+
+
+#### 3.1.3. GitHub login Video Tutorials
+
+
+
+`https://your.openlist.domain/api/auth/sso_callback?method=sso_get_token`
`https://your.openlist.domain/api/auth/sso_get_token`
`https://your.openlist.domain/api/auth/get_sso_id` | + | Valid post logout redirect URIs | Leave blank | + | Web origins | Leave blank | + + ::: + +##### 3.7.1.3. Retrieve JWT public key + +- In the left menu, find `Clients`, select the newly created Client to enter the settings page. +- In the Client settings page, switch to the `Keys` tab. +- Copy the content in the `Public Key` field for later use in OpenList configuration. +- If the public key is not visible, click `Generate RSA Keys` to generate it. + +##### 3.7.1.4. Retrieve Client Secret + +- In the Client settings page, switch to the `Credentials` tab. +- Copy the content in the `Client Secret` field for later use in OpenList configuration. + +#### 3.7.2. OpenList Setup + +Fill in the following parameters in OpenList's SSO configuration: + +- **SSO login enabled:** `yes` +- **SSO login platform:** `OIDC` +- **SSO client id:** Keycloak Client ID (from [Create Client](#_3-7-1-2-create-client) above) +- **SSO client secret:** Keycloak Client Secret (from [Retrieve Client Secret](#_3-7-1-4-retrieve-client-secret) above) +- **SSO oidc username key:** `preferred_username` or as per your Mapper settings +- **SSO organization name:** `master` (from [Create Realm](#_3-7-1-1-create-realm) above) +- **SSO application name:** `OpenList` (from [Create Client](#_3-7-1-2-create-client) above) +- **SSO endpoint name:** `https://your.keycloak.domain/realms/{realm-name}` (where realm-name matches the organization name) +- **SSO jwt public key:** from [Retrieve JWT public key](#_3-7-1-3-retrieve-jwt-public-key) above +- **SSO auto register as OpenList account:** Enable as needed +- **SSO compatibility mode:** `no` (enable if compatibility is required) + +Adjust claims and endpoints based on your specific Keycloak deployment if needed. +For detailed operations, refer to the [Keycloak official OIDC documentation](https://www.keycloak.org/documentation). diff --git a/pages/en/guide/advanced/strm.md b/pages/en/guide/advanced/strm.md new file mode 100644 index 000000000..b8407c602 --- /dev/null +++ b/pages/en/guide/advanced/strm.md @@ -0,0 +1,10 @@ +--- +categories: + - guide + - advanced +top: 10 +--- + +# Generate Strm + + diff --git a/pages/en/guide/advanced/user.md b/pages/en/guide/advanced/user.md new file mode 100644 index 000000000..e3f30e88c --- /dev/null +++ b/pages/en/guide/advanced/user.md @@ -0,0 +1,75 @@ +--- +categories: + - guide + - advanced +top: 140 +--- + +# User + +## Add user + +::: warning Security Notice +Adding a user may expose files and server-side capabilities to another account. Use a strong, unique password, grant only the minimum required permissions, and create accounts only for trusted users. Security incidents resulting from improper user or permission management are the administrator's responsibility. +::: + +## Username + +Username for login. + +## Password + +Password for login. +:::tip +Password is invalid for guest user. + +If you enter an incorrect password 6 times in a row, the current IP will be blocked for 30 minutes and you will not be able to enter your account and password to log in. However, it will not affect other IPs. It will only target IPs that entered 6 incorrect passwords. + +- Restarting will immediately remove the 30-minute ban time + +::: + +## Base path + +The root path that users see when he/she log in. + +Q: **How to allow a user to see multiple folder paths?** + +A: You can create a new [alias](alias.md) storage, add all the paths you need to show the user to the alias, and then point to the newly created alias storage in the user path + +## Permission + +- Can see hides: Can see the hides files and folders +- Access without password: Can access without password +- Add offline download tasks: Add offline download tasks + - ⚠️ Granting a user remote file read/write permissions also grants them the ability to access resources from the server's network context, including internal network addresses. Only grant this permission to fully trusted users. Internal network access resulting from improper permission assignment is not considered a security vulnerability. +- Mkdir or upload: Can make directory or upload files +- Rename: Can rename files and folders +- Move: Can move files and folders +- Copy: Can copy files and folders +- Delete: Can delete files and folders +- Webdav read: Can read files and folders with webdav +- Webdav manage: Can manage files and folders with webdav +- FTP read: Can read files and folders with FTP +- FTP manage: Can manage files and folders with FTP +- Read archives: Read the contents of the file in the compressed package + - After turning on this option, compressed package format files will be previewed by default (as shown in the figure below), which will consume some server traffic, but will not download them all. + - If you want to turn off the preferred preview of the compressed format, **Manage => Setting => Preview by default when opening archives**, this option is turned off, and the preference is the download mode +- Decompress: Decompress compressed package files online +  +  + +## Disabled + +After checking, this user will stop using it and cannot log in. The guest account is disabled by default. If you want to enable the guest account, please close it manually. + +## Tips + +1. Are you worried that visitors can see all files? [**Click to see how to set it up here**](../../faq/why.md#how-do-i-set-it-so-that-visitors-can-only-see-the-content-after-logging-in) +2. **`Guest user is disabled, login please`**: In order to protect your OpenList security, the guest access permission is closed, if you need guest access, open it yourself + - OpenList Manage --> users --> `guest` --> **Disable** uncheck +3. Question about **`Copy/Upload`** + - If you upload (including offline download and upload) large files, or upload a lot of files (hundreds or thousands), it is not recommended to use OpenList to operate, please go to the corresponding network disk official website to operate directly +4. Non-admin users can manage offline download, copy, upload and other operations in the background + - OpenList needs to be upgraded to
+
+ 
+
+
+### Infuse (iOS/macOS)
+
+
+
+### Fileball (iOS)
+
+
+
+### PotPlayer (Windows)
+
+
+
+### Synology NAS (Add via File Station)
+
+
diff --git a/pages/en/guide/drivers/115.md b/pages/en/guide/drivers/115.md
new file mode 100644
index 000000000..eee9c2c17
--- /dev/null
+++ b/pages/en/guide/drivers/115.md
@@ -0,0 +1,384 @@
+---
+top: 697
+categories:
+ - guide
+ - drivers
+---
+
+# 115 Cloud / Share
+
+
+
+::: tip
+[**115 Official Open API**](115_open.md)
+:::
+
+## 115 Cloud
+
+### Root folder ID
+
+Open the official website of 115 Cloud and click the string behind the url when you click into the folder you want to set,
+such as
+
++ +#### 3. Get Cookies Using Python Script + +Expand the detailed description to view the tutorial and script source code + +Source code from：[**https://gist.github.com/ChenyangGao/d26a592a0aeb13465511c885d5c7ad61**](https://gist.github.com/ChenyangGao/d26a592a0aeb13465511c885d5c7ad61) + +::: details View source + +```python +#!/usr/bin/env python3 +"扫码获取 115 cookie" +__author__ = "ChenyangGao
+ +### Offline Download + +**v3.37.0** and above versions support calling `115 Cloud` offline download function in OpenList +Select in the lower right corner and select `115 Cloud` for offline download options + +- Support: `magnet`, `http`, `ed2k` links + Only 115 Cloud is supported for offline download. If it is not 115 Cloud, the following error message will be displayed, Although the offline download prompt was successfully added, an error will be prompted in the background. +- unsupported storage driver for offline download, only 115 Cloud is supported +  +- Some tips for using 115 offline downloads: + 1. Out of sync problems may occur (manual refresh in the lower right corner ) + 2. Currently, when the download is successful, completed tasks in the offline list are deleted. + 3. 115 Task URLs that are already in the offline list cannot be added again. +
+ +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` + +## 115 Share + + + +`Sharing link ID`1 and `Sharing link extraction code`2 How to obtain them respectively is clear at a glance. + +### Root folder ID + +The default is empty and the entire directory file is mounted. + +The folder IDs are the root folder ID and the subfolder ID respectively. The following demonstrates how to obtain the `shared root folder directory ID`1 and `other subfolder directory ID`2 respectively. + +#### 1. shared root folder directory ID + +Open developer mode (F12) and clear all requests first. Before we enter the folder, clear all requests first. + +Let's click on the root folder to enter. There will be a new request on the right, and then select `Load` to see the ID (cid) of our folder. + + + +#### 2. other subfolder directory ID + +Open developer mode (F12) and clear all requests first. Before we enter the folder, clear all requests first. + +There will be a new request on the right, then select `Preview` and expand it to see the IDs (cid) of other subfolders. + + + +### Error Tips + +For example, the 115 sharing link shown in the picture below has expired, but the sharing link can still be opened. + + + +But when adding and saving, the following error code will appear: + +`Failed init storage but storage is already created: failed init storage: failed to get share snap: json: cannot unmarshal number into Go struct field .data.shareinfo.share_state of type string ` + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/115_open.md b/pages/en/guide/drivers/115_open.md new file mode 100644 index 000000000..a2997b375 --- /dev/null +++ b/pages/en/guide/drivers/115_open.md @@ -0,0 +1,171 @@ +--- +top: 698 +categories: + - guide + - drivers +--- + +# 115 Open + +::: tip +Developed with the official [**115 Open Platform API**](https://open.115.com) +::: + + + +## 1. Necessary Conditions + +An **115** account is required. + +::: warning Note +The speed and stability are related to the local network environment, the network environment of the 115 server, and the performance of the machine running OpenList. +::: + +## 2. Preparation for Access + +### 2.1. Register an Application on the Open Platform (optional; no need to create if using the built-in key pair of OpenList/public welfare server/self-built server) + +::: tip +Please register the application according to the requirements of the 115 Open Platform. +::: + +Open Platform address: [115 Open Platform: https://open.115.com](https://open.115.com) + +### 2.2. Obtain Tokens + +1. Visit [api.oplist.org](https://api.oplist.org) **⚠️ If using a public welfare server/self-built server, visit the address of the public welfare server/self-built server**. + +2. Select **115 Network Disk Verification** from the drop-down box. + +  + +  + +3. If you are using the built-in key pair of `OpenList (or public welfare server/self-built server)` (i.e., you do not have application information from the 115 Open Platform), please configure according to `3.1`, `3.2`, and `3.3`: + + 3.1. Check `Use parameters provided by OpenList`. + + 3.2. Leave both `Client ID (ClientID/AppID)` and `Application Secret (AppKey/Secret)` blank. + + 3.3. Click the `Get Token` button. + +  + +  + +4. If you are using your own created OAuth client ID and secret, please configure according to `4.1`, `4.2`, and `4.3`: + + 4.1. Do not check `Use parameters provided by OpenList`. + + 4.2. Enter your `AppId` in `Client ID` and your `AppSecret` in `Application Secret`. + + 4.3. Click the `Get Token` button. + +  + +  + +5. In the pop-up window, log in to your 115 account and authorize OpenList to access your 115 network disk. + +  + +6. After successful authorization, the page will display your `Access Token` and `Refresh Token`. Please copy and save these two tokens. + +  + +  + +## 3. Adding 115 Network Disk to OpenList + +### 3.1. Configuration Instructions + +#### 3.1.1. Root Folder ID + +The default root directory ID is: `0` + +Open the 115 network disk official website, and when clicking to enter the folder to be set, click the number after `cid` in the URL. + +For example,
+
+3. After entering, select SMS login. Once logged in, return to the storage management page. Disable and re-enable the storage to use it normally (you may need to refresh the page).
+
+
+
+## Personal Cloud
+
+### Username
+
+the phone number used to log in
+
+### Password
+
+password for login
+
+### Root folder ID
+
+The string at the end of the official website url, such as:
+
+- https://cloud.189.cn/web/main/file/folder/-11 -> `-11`
+- https://cloud.189.cn/web/main/file/folder/71398114617385472 -> `71398114617385472`
+
+ 
+
+### Family transfer
+
+Give 189 Cloud adds Personal's `Family Transfer option`, which is convenient for users without VIP, and a large number of family cloud spaces upload.
+
+- Note: The old upload interface family cloud will still limit the upload quantity, so `Rapid upload` and ` Old Upload` will not take effect
+
+## Family Cloud
+
+(189 Cloud PC Driver Only) Use a computer browser, open the developer tool (F12), switch the emulation device and select the mobile device
+
+Open https://h5.cloud.189.cn/main.html#/family, enter the folder you want to mount, you can see the request in the network, and then find the required parameters:
+
+
+
+### OpenList fill in examples：
+
+#### 189 Cloud
+
+Fill in the account1and password2,Then click one request in the request, just bring `Cookies`3, click on one at will Then fill in,Cookie expires time is unknown
+
+
+
+#### 189 CloudPC
+
+
+
+Video reference: **https://www.bilibili.com/video/BV16A4y197De**
+
+## suggestion
+
+It is recommended to use the 189 Cloud PC first, [**Notes click to view.**](../../faq/howto.md#when-adding-a-189-cloud-storage-the-device-id-does-not-exist-and-a-secondary-device-verification-is-required)
+
+### The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/alias.md b/pages/en/guide/drivers/alias.md
new file mode 100644
index 000000000..1e1eafee9
--- /dev/null
+++ b/pages/en/guide/drivers/alias.md
@@ -0,0 +1,10 @@
+---
+top: 997
+categories:
+ - guide
+ - drivers
+---
+
+# Alias
+
+
diff --git a/pages/en/guide/drivers/alias_text.md b/pages/en/guide/drivers/alias_text.md
new file mode 100644
index 000000000..abd6a59c8
--- /dev/null
+++ b/pages/en/guide/drivers/alias_text.md
@@ -0,0 +1,282 @@
+**Alias** is a feature that allows multiple different cloud drives or storage paths to be merged into a unified directory. By combining paths, content from different cloud drives or folders can be displayed in the same interface, simplifying access and management.
+
+For example: Cloud Drive Account 1 and Cloud Drive Account 2 both contain a folder named `Movies`, but the contents of these folders may not be identical.
+
+- **Previously (Virtual Path)**:
+
+ You could only mount them to two different paths separately, like:
+ - `CloudDrive1/Movies`, `CloudDrive2/Movies`
+ - `Movies/CloudDrive1`, `Movies/CloudDrive2`
+
+- **Now (Alias)**:
+
+ An aggregated folder (Movies) is provided, which can contain content from both Cloud Drive 1 and Cloud Drive 2 simultaneously.
+
+Folders with the same name will be automatically merged into one. The contents of the folder are the sum of the contents of all folders with the same name. Regarding how this driver handles files with the same name, please refer to the [Path conflict policies](/en/guide/drivers/alias#path-conflict-policies) section later.
+
+For Example:
+
+
+
+In the diagram, we can see that two different folders are merged into one. Files and folders with the same name are also combined, and unique ones are displayed separately.
+
+Example explanations:
+
+- **Example 1**: `riluo.jpg` is unique to Cloud Drive 1, so it is shown separately.
+- **Example 2**: Both folders contain a `video` folder, but the contents of these folders will be merged. Subfolders also follow the **same-name merging** display rule. Both folders contain two videos, but one of them has the same name. After merging according to the **same-name merging** rule, three video files will be displayed in total.
+
+## Paths filling method
+
+There are two ways to fill in:
+
+1. The first one is that you can only fill in the path of the subfolder and the folder with the same name must be used at the end. It is not recommended to use :x:
+ - Paths filling example:
+ ```
+ /file1/locala
+ /file2/localb
+ ```
+2. The second is to directly mount the root folder path, using the `renaming` method, it is strongly recommended to use :heavy_check_mark:
+ - Paths filling example:
+
+ ```
+ #Example 1 Directly write the root folder
+ merge: /file1
+ merge: /file2
+
+ #Example 2 Mount different path folders for merging
+ merge: /file1/localtest233
+ merge: /file2/videos/TV series
+ merge: /file3 2/TV/Domestic TV Series/Station XX
+ ```
+
+According to the second method, we can `merge` and display different folders, which is convenient and quick.
+
+## Path conflict policies
+
+The three configuration items—**Reading conflict policy**, **Writing conflict policy**, and **Putting conflict policy**—determine how the Alias handles files or folders with the same name and identical paths in the backend drivers. Their values and corresponding behaviors are as follows:
+
+### Reading conflict policy
+
+Determines the behavior for handling files with the same name when downloading, copying (as source files), and extracting (as source files) (excluding moving).
+
+- Get the file corresponding to the first conflict path: Select the file from the first available path (from top to bottom in the Paths) where the file exists.
+
+- Load balancing on a per-file basis: Randomly select one file from the available duplicates.
+
+- Load balancing on a per-part basis:
+ - During 302 downloads, copying, or extracting, it falls back to the **Load balancing on a per-file basis** strategy.
+ - When using local proxy downloads, each transmitted chunk is randomly assigned to one of the duplicate files. This requires the backend driver to support Range requests. For details on setting the chunk size, refer to the section [Download concurrency, Download part size](/en/guide/drivers/alias#download-concurrency-download-part-size).
+ - This policy achieves the actual effect as shown in the figure. It is important to note that this diagram is only intended to conveniently demonstrate the operation of this policy. The statement that "participating load-balanced files with the same name have different contents" is **not** a correct usage of this driver. OpenList does not guarantee stable or correct results under such circumstances, nor will it address any issues arising from this usage scenario. Furthermore, the actual minimum size for file splitting is 1 KiB, not 1 byte, so the effect depicted in the diagram will not occur in the stable version.
+
+ 
+
+::: tip
+When a copy operation involves multiple source paths and target paths, the Alias will first attempt to pair source and target paths that belong to the same drive. Only for target paths that cannot be matched in this way will the method specified by the **Reading conflict policy** be used to select a source path.
+
+For example, when copying:
+
+- `DriverA/source/file.txt`
+- `DriverB/source/file.txt`
+
+to:
+
+- `DriverB/target/`
+- `DriverA/target/`
+- `DriverC/target/`
+
+The Alias driver will perform the following operations:
+
+1. Copy `DriverA/source/file.txt` to `DriverA/target/`, since both are located in Driver A.
+2. Copy `DriverB/source/file.txt` to `DriverB/target/`, since both are located in Driver B.
+3. For `DriverC/target/`, which has no matching source in the same driver, select `file.txt` from either Driver A or Driver B according to the **Reading conflict policy**, and copy it to `DriverC/target/` via an upload operation (creating a copy task).
+
+:::
+
+::: tip
+The move operation involves a matching process similar to that of the copy operation. For target paths that cannot be matched with a source path from the same driver, the Alias will randomly select from the still-unmatched source paths to create a pairing (**one-to-one correspondence**). If the number of source paths exceeds the number of target paths, the unmatched source paths will be deleted. If the number of source paths is less than the number of target paths, the move operation will fail. The matching behavior for the move operation is not affected by the **Reading conflict policy**.
+
+For example, in the case described for the copy operation, since there is no source path corresponding to `DriverC/target/`, the move operation will fail.
+
+As another example, when moving:
+
+- `DriverA/source/file.txt`
+- `DriverB/source/file.txt`
+- `DriverD/source/file.txt`
+- `DriverE/source/file.txt`
+- `DriverG/source/file.txt`
+
+to:
+
+- `DriverA/target/`
+- `DriverB/target/`
+- `DriverC/target/`
+- `DriverF/target/`
+
+The Alias will perform the following operations:
+
+1. Move `DriverA/source/file.txt` to `DriverA/target/`.
+2. Move `DriverB/source/file.txt` to `DriverB/target/`.
+3. Randomly select one file from Driver D, E, or G, and move it to `DriverC/target/` (by creating a move task, which is essentially an upload followed by deletion). Let's assume E is selected.
+4. Randomly select one file from the remaining unmatched drivers (D or G), and move it to `DriverF/target/`. Let's assume G is selected.
+5. Delete `DriverD/source/file.txt`.
+
+:::
+
+### Writing conflict policy
+
+Determines the behavior for renaming or deleting files/folders with the same name, as well as creating folders within identically named folders.
+
+- **Disable writing**: Prohibits rename, delete, and folder creation operations.
+- **Write into the first conflict path**: Operates on the driver containing the target path that appears first (top to bottom) in the configured path list.
+- **Allow unique path**: Executes the operation only if the target path is unique (exists in only one backend path). Otherwise, the operation is prohibited.
+- **Allow full conflict paths**: Executes the operation only if the target path exists in **all** configured backend paths, applying the operation across all of them. Otherwise, the operation is prohibited.
+- **Allow unique path and full conflict paths**: Allows the operation when the target path is either unique or exists in all configured backend paths.
+- **Write into all conflict paths**: Forwards the operation to all backend paths where the target path exists.
+
+::: tip
+If the above explanation is unclear, you can refer to the following example.
+
+- In Driver A, the file exists: `file1.txt`
+- In Driver B, the files exist: `file1.txt`, `file2.txt`, `file3.txt`
+- In Driver C, the files exist: `file1.txt`, `file3.txt`
+
+Configured backend paths:
+
+```
+test:DriverA
+test:DriverB
+test:DriverC
+```
+
+Then:
+
+- Since the sub-path `/file1.txt` is valid in all configured paths (`DriverA/`, `DriverB/`, `DriverC/`), `/file1.txt` is referred to as a **full conflict path**.
+- Since the sub-path `/file2.txt` is valid only under the single backend path `DriverB/`, `/file2.txt` is referred to as a **non-conflict path** or **unique path**.
+- Since the sub-path `/file3.txt` exists under both `DriverB/` and `DriverC/`, and the number of backend paths where it exists is neither 1 nor the maximum (3), `/file3.txt` is neither a non-conflict path nor a full conflict path.
+
+When renaming any file to `file4.txt`, the corresponding files in the following drivers will be renamed:
+
+| Writing conflict policy | file1.txt | file2.txt | file3.txt |
+| ----------------------------------------- | ---------------------------- | --------- | ------------------ |
+| Disable writing | Fails | Fails | Fails |
+| Write into the first conflict path | Driver A | Driver B | Driver B |
+| Allow unique path | Fails | Driver B | Fails |
+| Allow full conflict paths | Driver A, Driver B, Driver C | Fails | Fails |
+| Allow unique path and full conflict paths | Driver A, Driver B, Driver C | Driver B | Fails |
+| Write into all conflict paths | Driver A, Driver B, Driver C | Driver B | Driver B, Driver C |
+
+:::
+
+### Putting conflict policy
+
+Determines the behavior for uploading to, copying to, moving to, or extracting to folders with the same name.
+
+- **Disable putting**, **Put into the first conflict path**, **Allow unique path**, **Allow full conflict paths**, **Allow unique path and full conflict paths**, **Put into all conflict paths**: These options function identically to their counterparts in the **Writing conflict policy**.
+- **Random load balancing**: Randomly selects one valid path for the upload.
+- **Weighted random load balancing based on remaining space**: Retrieves the remaining free space of all valid paths, skips paths that fail to report free space or have insufficient space for the file being uploaded, and then randomly selects from the remaining valid paths, weighting the choice by their remaining capacity. If none of the valid paths that successfully reported free space have enough capacity for the file, **a random selection is made from among the valid paths that failed to report capacity**.
+- **Strict weighted random load balancing based on remaining space**: Retrieves the remaining free space of all valid paths, skips paths that fail to report free space or have insufficient space for the file being uploaded, and then randomly selects from the remaining valid paths, weighting the choice by their remaining capacity. If none of the valid paths that successfully reported free space have enough capacity for the file, **an error message is returned directly**.
+
+::: tip
+The load balancing mechanisms within the **Reading conflict policy** and the **Putting conflict policy** are two largely unrelated features. Informally speaking, the load balancing in the **Reading conflict policy** is analogous to RAID 1, while the load balancing in the **Putting conflict policy** is analogous to RAID 0. For specific use cases of each, please refer to [Advanced / Load balancing](/en/guide/advanced/balance).
+
+If you've understood the above, you'll realize that enabling both **Reading Load Balancing** and **Putting Load Balancing** won't make load balancing more balanced. In fact, this configuration produces effects that are hardly any different from enabling only **Putting Load Balancing**.
+
+:::
+
+::: tip
+The legacy version of the Alias used three Boolean configuration items—**Writable**, **Protect same name**, and **Parallel write**—to implement path conflict policy functionality. The correspondence between the legacy configuration and the new configuration is as follows:
+
+- In the legacy configuration, the **Reading conflict policy** was always set to **Get the file corresponding to the first conflict path**.
+- In the legacy configuration, when **Writable** was disabled, both the **Writing conflict policy** and the **Putting conflict policy** were set to **Disabled**.
+- When **Writable** was enabled, the **Writing conflict policy** and the **Putting conflict policy** were both determined as follows:
+ | | Parallel write disabled | Parallel write enabled |
+ | -------------------------- | -------------------------------------- | ----------------------------------------- |
+ | Protect same name enabled | Allow unique path | Allow unique path and full conflict paths |
+ | Protect same name disabled | Write/Put into the first conflict path | Write/Put into all conflict paths |
+
+:::
+
+## File consistency check
+
+When enabled, the driver will filter out paths where the **size or hash value** differs from other copies during the process of collecting valid paths. This is a safety measure, and whether it is enabled has relatively minor impact. It is recommended to enable this option when using the **Load balancing on a per-part basis** reading policy.
+
+Regardless of whether this option is enabled, the Alias does not actively calculate file hashes. Instead, it performs a best-effort match using the hash values returned by the backend drivers.
+
+Different types of hash values returned by backend drivers will not lead to misjudgment. For example, if Driver 1 returns the MD5 of a file and Driver 2 returns the SHA1 of the file, even with this option enabled, the Alias will not consider either path from Driver 1 or Driver 2 invalid simply because the file's MD5 and SHA1 are not equal.
+
+## The download method to use
+
+When adding **`alias`**, `Web Proxy` and `Webdav Policy` are not modified by default. The storage path filled in the Paths path can be `302`, `Local Proxy`, `Download Proxy URL`, three modes Mixed Playback Mixed Playback is possible.
+
+If you checked `Web Proxy`, the storage filled in by the Paths path, if there is a 302 mode playback, it will be played in transit (local proxy mode) at that time, and it will become a proxy mode. If the Webdav policy is also changed, it will also change.
+
+Of course, it is up to you to choose whether to change the mode.
+
+### What if you don’t know how the cloud disks you added are different?
+
+1. You can go to the bottom of the corresponding document to view the document, there is a flow chart description
+ - If there is a 302, the 302 method is used by default. If there are only local proxy and download proxy URLs, the default is to use the local proxy, provided that you have not manually selected
+2. You can check when adding storage, select the corresponding storage to view, for example, let’s check the methods of Alibaba Cloud and 115 respectively
+ - As you can see from the figure below, Alibaba Cloud Disk has the option of `web proxy`, and `webdav policy` defaults to 302. It can be judged that Alibaba Cloud Disk uses the 302 method by default
+ - As you can see from the figure below, the 115 network disk does not have the option of `web proxy`, and the `webdav strategy` defaults to the local proxy. It can be judged that the 115 network disk uses the local proxy mode by default
+ 
+
+## Proxy Range
+
+You need to enable `Web Proxy` or` Webdav Native Proxy` to take effect. Currently only applicable to：`alias`、`139Yun`、`OpenList V3`.
+
+- The `139Yun` driver, when this option is enabled, can resolve issues that occur when a proxy is enabled but the download link does not return the correct HTTP status code, such as problems with video playback or lack of support for resume downloads.
+- The `Alias` driver is added to meet specific use cases, for example, when `139Yun` uses a 302 redirect. By enabling the `Alias` proxy, downloads can use `139Yun` with the 302 redirect, while video playback can use the proxy-enabled `Alias`, reducing unnecessary load.
+- The `OpenList` driver is added to support server-side OpenList mounting with `139Yun` using a 302 redirect. Locally, OpenList can be mounted via the proxy-enabled `OpenList` to access the server's OpenList for video playback, etc., to avoid consuming server bandwidth. This also allows for data-free video streaming on mobile networks.
+
+## Download concurrency, Download part size
+
+**Storage Settings:**
+
+- Alias (Alias) Drive
+- Local Proxy
+- Path: / Cloud Drive Mount Path
+- Download Concurrency: 10
+- Download Chunk Size: 1024
+
+**Effect:**
+
+- Client → OpenList Alias Drive: Uses 1 connection
+- OpenList Alias Drive → Cloud Drive: Supports 10 concurrent connections, with actual concurrency limited by the cloud drive.
+
+```mermaid
+graph LR
+ A[Client] -->|Connection 1| B[OpenList Alias Drive]
+ B -->|Concurrent Connection 1| C[Cloud Drive]
+ B -->|Concurrent Connection 2| C
+ B -->|Concurrent Connection 3| C
+ B -->|Concurrent Connection 4| C
+ B -->|Concurrent Connection 5| C
+ B -->|Concurrent Connection 6| C
+ B -->|Concurrent Connection 7| C
+ B -->|Concurrent Connection 8| C
+ B -->|Concurrent Connection 9| C
+ B -->|Concurrent Connection 10| C
+```
+
+- Single-threaded speed is slower, but it supports concurrency: Using the alias drive allows concurrent downloads, significantly improving speed.
+- Video watching and download acceleration: The experience is enhanced by increasing concurrency.
+- Copying from alias drive to other drives: File transfer is also accelerated in this case.
+
+**Friendly Reminder:** Please do not abuse this feature. Excessive use may cause abnormal activity on the cloud drive account, and you will bear the consequences.
+
+**Configuration Options:**
+
+- max_concurrency: Sets the maximum concurrency for the local proxy. The default is 64, and setting it to 0 means no limit on concurrency.
+
+## Other instructions
+
+If you are using `Windows`, the following situation will occur, and folders with different capitalization will also be regenerated.
+
+For example, Local 1 and Local 2 have a lowercase v for `video` respectively, and the folder OneDrive has an uppercase V `Video` folder.
+
+Then a lowercase video folder will be generated, which contains only `local 1, local 2` files merged by two folders.
+
+At the same time, the uppercase `Video` will gather the files of the three folders.
+
+This is because Windows is case-insensitive, video and Video will be considered as the same folder, you will not have this problem if you switch to Linux or Mac.
diff --git a/pages/en/guide/drivers/alidoc.md b/pages/en/guide/drivers/alidoc.md
new file mode 100644
index 000000000..a8abe5bbf
--- /dev/null
+++ b/pages/en/guide/drivers/alidoc.md
@@ -0,0 +1,78 @@
+---
+top: 677
+categories:
+ - guide
+ - drivers
+---
+
+# AliDoc
+
+::: danger Please read the notes carefully
+This driver is currently not officially maintained by the project team.
+:::
+
+Mount DingTalk Docs web storage in OpenList.
+
+Official website:
+
+- DingTalk Docs:
+
+
+### Web plugin
+
+The advantage of using a browser plug-in to modify is that it can be played directly online, of course, downloading is also possible.
+
+Example 1: If you really don’t know it, you can take a look at an example on the web page: **https://www.bilibili.com/video/BV1UA4y1X7J8**
+
+Example 2: Another plugin method covering 360, Chrome, Edge: **https://youtu.be/PP6b0WSzYMc**
+
+
+
+### Aria2
+
+1. First follow the figure below to set the **`user-agent" `**, and then click the button option in the lower right corner, click ** gear ** (local settings) to configure the parameters well
+
+ 
+
+2. Then open the third button option in the lower right corner (**Open the check box**), and then go to the list to select the file we want to download
+
+3. Select the files we need to download. After selecting, there will be a row of buttons. Select the second option on the right. One is sent to Aria2.
+
+ If you use the webpage to modify the **`user-agent`**, you do not need to configure the `UA` of **Aria2**, and you can download it directly to Aria2
+
+### Motrix
+
+1. First follow the figure below to set the **`user-agent" `**, and then click the button option in the lower right corner, click ** gear ** (local settings) to configure the parameters well
+
+ 
+
+2. Then open the third button option in the lower right corner (**Open the check box**), and then go to the list to select the file we want to download
+
+3. Select the files we need to download. After selecting, there will be a row of buttons. Select the second option on the right. One is sent to Aria2.
+
+ If you use the webpage to modify the **`user-agent`**, you do not need to configure the `UA` of **Motrix**, and you can download it directly to Aria2
+
+- Motrix Download link：[Motrix Official website](https://motrix.app/)，[Motrix-GitHub](https://github.com/agalwood/Motrix)
+
+## Upload Config
+
+Official Documentation: [百度网盘开放平台 - 上传 - 能力说明](https://pan.baidu.com/union/doc/3ksg0s9ye)
+
+> ~~Baidu Netdisk requires that each slice be uploaded within 30 seconds, so excessively high concurrency during file uploads may result in a significant number of failures.~~
+> Currently (November 2025), Baidu Netdisk appears to have significantly relaxed the timeout limit for uploading slices.
+> Tests show that uploading single slice is now allowed to exceed 30 minutes.
+> Therefore, after extending the timeout duration, the failure rate for batch uploading large files should be greatly reduced (even if low upload bandwidth).
+
+- Upload Threads: The number of slices to upload concurrently.
+- Upload API: The domain endpoint used for uploading.
+- Use dynamic upload API: Dynamically fetch upload domain, generally can achieve maximum upload speed. When enabled, the `Upload API` setting will be used as a fallback if failed to get online. This is enabled by default.
+- Custom Upload Slice Size: Allows you to specify the size of each slice. Note that there are limitations, and this feature is available to VIPs only.
+- Low Bandwidth Upload Mode: Attempts to address the frequent `Client.Timeout exceeded while awaiting headers` errors encountered in low upload bandwidth scenarios (e.g., residential broadband). When enabled, it uses the smallest possible slice size.
+
+## The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[local proxy]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[302]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/baidu_photo.md b/pages/en/guide/drivers/baidu_photo.md
new file mode 100644
index 000000000..fc168e3bc
--- /dev/null
+++ b/pages/en/guide/drivers/baidu_photo.md
@@ -0,0 +1,60 @@
+---
+top: 689
+categories:
+ - guide
+ - drivers
+---
+
+# Baidu Photo
+
+
+
+## Cookie
+
+Log in to [Baidu Photo](https://photo.baidu.com), open F12, and find any request containing the `Cookie` value. Copy it.
+
+
+
+## Album ID
+
+**When left blank, all albums in the root directory are displayed by default.**
+
+If you want to mount a single album, fill in the following:
+
+- The **Album ID** should be: {album_id}|{tid}
+ Example: `4021858707431029901|316519298447849660`
+ - **{album_id}**: After entering the album you want to mount, check the top URL for the ID after `/album`. This is the **{album_id}**.
+ - Example: [https://photo.baidu.com/photo/web/album/4021858707431029901](https://photo.baidu.com/photo/web/album/4021858707431029901)
+ - **4021858707431029901** is the **{album_id}**
+
+ - **{tid}**: Access [this link](https://photo.baidu.com/youai/album/v1/list?limit=1000) to obtain the **{tid}**
+ - Once on the page, press `Ctrl+F` and search for the ID above. A few lines below you’ll find the corresponding **{tid}**.
+
+## Display Type
+
+Choose according to your needs.
+
+## Delete Source Files
+
+By default, it only removes the album, not permanently deletes the files. If you enable this option, the files will be permanently deleted after removal. Be cautious when enabling this.
+
+## The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/chaoxing.md b/pages/en/guide/drivers/chaoxing.md
new file mode 100644
index 000000000..0c7d6a18f
--- /dev/null
+++ b/pages/en/guide/drivers/chaoxing.md
@@ -0,0 +1,51 @@
+---
+top: 678
+categories:
+ - guide
+ - drivers
+---
+
+# ChaoxingxingGroupCloud
+
+
+
+chaoxingxing group cloud is also affiliated with chaoxingxing. After logging in to chaoxingxing, you can see a group under the left sidebar.
+
+Official website link：**https://i.chaoxing.com**
+
+### Username Password
+
+chaoxingxing account and password
+
+### Bbsid
+
+Follow the example process below to obtain
+
+
+
+### Root Folder ID
+
+The default is `-1`. For other subfolder ID acquisition methods, see the example below.
+
+- Search the keyword `getResourceList` in the request. For convenience, we can directly search `list` and see it. Then we enter the folder we need to mount. After entering the folder, we can find the `folder id by looking at the request.`
+
+ 
+
+### The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ c1
+ end
+ c1[local proxy]:::someclass==default===>a2[user equipment]
+ classDef someclass fill:#f96
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/chunk.md b/pages/en/guide/drivers/chunk.md
new file mode 100644
index 000000000..19bfcfbb2
--- /dev/null
+++ b/pages/en/guide/drivers/chunk.md
@@ -0,0 +1,113 @@
+---
+top: 995
+categories:
+ - guide
+ - drivers
+---
+
+# Chunk
+
+The Chunk is used to split large files into multiple file chunks. Each chunk is stored as an independent file on the backend driver.
+
+The size of each file chunk can be manually configured by the user. Except for the last chunk of each file—which is smaller than the configured size—all other chunks are always equal to the specified size.
+
+A chunked file is stored as a folder on the backend driver, containing all its chunks.
+
+
+
+## Setup Instructions
+
+- **Remote path:** The real storage path of the chunked files. This path must be the root path or a subpath of another driver.
+- **Part size:** Maximum chunk size / Size of chunks except the last, in bytes.
+- **Chunk large file only:** Whether to only chunk files larger than Part size.
+ - When disabled:
+ 
+ - When enabled:
+ 
+- **Chunk prefix:** The prefix for the names of chunk folders stored on the backend driver, representing a chunked file. This is used to identify whether a folder is a regular folder or a chunked file storing folder, and therefore cannot be empty.
+- **Custom ext:** Custom suffix for chunk names, used to bypass limitations of certain drivers.
+ - When left empty:
+ - When setting to `.jpg`:
+
+::: warning TIP
+Once the driver is created, Custom ext should not be modified again, otherwise previously uploaded chunked files will become unrecognizable.
+
+If modification is necessary, you must manually change the suffix of all chunks on the backend driver afterward.
+:::
+
+- **Store hash:** Whether to store the hashes of chunked files in the chunk folder as well.
+ This feature does not actively compute hashes; it only stores the hashes that the file already carries when uploading.
+- **Num list workers:** When handling `List` requests, if a folder contains chunk folders, it is necessary to further list those chunk folders to retrieve information such as file size and hash value. Using multiple threads can speed up this process. A higher number of threads consumes more CPU and bandwidth resources but also increases speed. It is recommended to be disabled (set to 1) when the backend driver has API rate limiting.
+
+## Use in combination with Crypt
+
+If you need to both chunk and encrypt files, it is recommended to **encrypt first, then chunk**. Specifically, set Remote path of the [Crypt](/en/guide/drivers/crypt) driver to the mount path of the **Chunk** driver, and set Remote path of the **Chunk** driver to the actual storage path of the files.
+
+- Best practice:
+
+```mermaid
+graph LR
+ File[Upload stream] --> Crypt
+ Crypt --> Chunk
+ Chunk -->|chunk1| Backend[Backend driver]
+ Chunk -->|chunk2| Backend
+ Chunk -->|chunk3| Backend
+```
+
+- Bad practice:
+
+```mermaid
+graph LR
+ File[Upload stream] --> Chunk
+ Chunk -->|chunk1| Crypt1[Encryption algorithm]
+ Chunk -->|chunk2| Crypt2[Encryption algorithm]
+ Chunk -->|chunk3| Crypt3[Encryption algorithm]
+ Crypt1 -->|encrypted chunk 1| Backend[Backend driver]
+ Crypt2 -->|encrypted chunk 2| Backend
+ Crypt3 -->|encrypted chunk 3| Backend
+ subgraph Crypt
+ Crypt1
+ Crypt2
+ Crypt3
+ end
+```
+
+**Reason**: The bad practice involves storing a series of encryption metadata in each file chunk, which consumes more space. It also fails to guarantee that the chunks adhere to the user-specified maximum size, thereby undermining the purpose of file chunking.
+
+To perform emergency recovery on an encrypted file chunked according to the best practice, you simply need to concatenate all the chunks in order and then proceed with recovery.
+
+## Use in combination with Alias
+
+If you need to store chunked files across multiple load-balanced drivers, you can combine this with the [Alias](/en/guide/drivers/alias) driver. For details, refer to [Load Balancing / Load balancing by file chunks](/en/guide/advanced/balance#load-balancing-by-file-chunks).
+
+It's important to note that, unlike the approach used with Crypt, when combining with Alias, the process should be **chunk first, then load balance**. This means setting the Remote path of the **Chunk** driver to the mount path of the **Alias** driver, and setting the paths within the **Alias** driver to the actual file storage paths.
+
+- Best Practice:
+
+```mermaid
+graph LR
+ File[Upload Stream] -->|File1| Chunk
+ File -->|File2| Chunk
+ Chunk -->|File1 Block1, File1 Block2, File1 Block3| Alias
+ Chunk -->|File2 Block1, File2 Block2| Alias
+ Alias -->|File1 Block3| D1[Backend Driver 1]
+ Alias -->|File1 Block2| D2[Backend Driver 2]
+ Alias -->|File1 Block1| D3[Backend Driver 3]
+ Alias -->|File2 Block1| D1
+ Alias -->|File2 Block2| D3
+```
+
+- Bad Practice:
+
+```mermaid
+graph LR
+ File[Upload Stream] -->|File1| Alias
+ File -->|File2| Alias
+ Alias -->|File1| Chunk1[Chunk 1]
+ Alias -->|File2| Chunk2[Chunk 2]
+ Chunk1 -->|File1 Block1| D1[Backend Driver 1]
+ Chunk1 -->|File1 Block2| D1
+ Chunk1 -->|File1 Block3| D1
+ Chunk2 -->|File2 Block1| D2[Backend Driver 2]
+ Chunk2 -->|File2 Block2| D2
+```
diff --git a/pages/en/guide/drivers/cloudflare-imgbed.md b/pages/en/guide/drivers/cloudflare-imgbed.md
new file mode 100644
index 000000000..f5a8d92a1
--- /dev/null
+++ b/pages/en/guide/drivers/cloudflare-imgbed.md
@@ -0,0 +1,83 @@
+---
+top: 700
+categories:
+ - guide
+ - drivers
+---
+
+# CloudFlare-ImgBed
+
+
+
+## Disclaimer
+
+::: warning
+This driver only provides an interface to interact with the CloudFlare-ImgBed backend and is not responsible for the availability and stability of the image hosting program itself or its storage channels.
+Users are solely responsible for determining and configuring the storage channels used (e.g., Cloudflare R2, HuggingFace, S3, Telegram) and must strictly comply with the Terms of Service and acceptable use policies of the relevant platforms and service providers. Do not use this driver for any illegal activities, rights infringement, or abuse of platform resources (e.g., excessive consumption of free quotas, illegal storage/distribution of copyrighted content).
+All consequences arising from improper configuration, violation of platform policies, or service abuse (including but not limited to account suspension, data loss, service interruption, etc.) shall be borne by the user. OpenList and its developers shall not be held liable.
+:::
+
+## 1. Preparation
+
+Before configuring this driver, you need to deploy your own CloudFlare-ImgBed backend.
+Project address: [MarSeventh/CloudFlare-ImgBed](https://github.com/MarSeventh/CloudFlare-ImgBed)
+After deployment, log in to the backend dashboard (`https://your-domain/dashboard`), and ensure that at least one storage channel (e.g., HuggingFace, Cloudflare R2, S3, Telegram) is configured in the system settings.
+
+## 2. Add in OpenList
+
+### Mount Path
+
+Enter the path you want to mount to, for example `/imgbed`.
+
+### Root Folder Path
+
+Default is `/`, can be left empty.
+
+### Address
+
+Enter the address of your deployed image hosting service, e.g., `https://img.example.com`. No need to add `/` at the end.
+
+### Token
+
+Enter the API Token generated in the backend system settings.
+
+
+### Small Channel Name
+
+Typically used for uploading files smaller than 20MB. Enter the channel name configured in your backend (e.g., `my cfr2`, `my telegram`).
+
+### Large Channel Name
+
+Used for uploading files larger than 20MB. It is recommended to configure a channel that supports large files (e.g., `huggingface`). If left blank, large files will fall back to the small channel for upload.
+
+### Large Channel Type
+
+Select the corresponding type based on your large file channel:
+
+- `huggingface`: Uses HuggingFace LFS direct upload (supports instant upload and chunking)
+- `telegram` / `cfr2` / `s3` / `discord`: Uses the backend chunked upload API
+
+### Upload Thread
+
+Concurrent thread count for HuggingFace chunked direct upload, default is `3`, max is `32`. Can be increased if network conditions are good.
+
+## The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/cloudreve.md b/pages/en/guide/drivers/cloudreve.md
new file mode 100644
index 000000000..e2efc2db2
--- /dev/null
+++ b/pages/en/guide/drivers/cloudreve.md
@@ -0,0 +1,72 @@
+---
+top: 498
+categories:
+ - guide
+ - drivers
+---
+
+# Cloudreve V3
+
+## Parameters
+
+### Address
+
+The address of the Cloudreve V3 server, such as: `https://www.example.com`. It is better to remove the slash `/` after it.
+
+### Authentication
+
+Cloudreve V3 supports authentication using Cookie. The mounting authentication methods are divided into:
+
+1. `Username` + `Password`: Automatically uses the login interface to obtain Cookie, there might be issues with CAPTCHA.
+2. `Cookie` Only: Can be temporarily used but will expire and cannot be renewed. Parameters can be found from browser requests or Local Storage.
+3. [Reference](../drivers/common.html#Reference): Fill in `ref:/{mount path}` in `Remark`: Reference authentication, tokens, etc., from "Mounted Storage".
+
+::: tip Steps to get cookie:
+Only the string following cloudreve-session= is required.
+:::
+
+
+
+### Root Folder Path
+
+Default is `/`, which can be obtained from the `?path=` in the web link. The obtained parameters may need to be [URL decoded](https://www.google.com/search?q=URL+decode).
+
+### Enable Folder Size
+
+Enable Cloudreve V3 server to calculate the size of each folder and generate thumbnails for each file. Enabling this feature may cause server errors or slow performance, and it is `disabled` by default.
+
+### Custom UA
+
+Used to customize the `User-Agent` header information used in requests. Leaving it blank will use OpenList default settings.
+
+## Upload
+
+The supported storage policies for uploading are as follows:
+
+- Local storage
+- Slave storage
+- OneDrive
+- S3
+
+Upload storage policies can be set within Cloudreve V4 web interface by entering the corresponding folder (requires the server to be Cloudreve Pro).
+
+## The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/cloudreve_v4.md b/pages/en/guide/drivers/cloudreve_v4.md
new file mode 100644
index 000000000..6cac42195
--- /dev/null
+++ b/pages/en/guide/drivers/cloudreve_v4.md
@@ -0,0 +1,116 @@
+---
+top: 497
+categories:
+ - guide
+ - drivers
+---
+
+# Cloudreve V4 / Share
+
+## Parameter Explanation
+
+### Address
+
+The address of the Cloudreve V4 server, such as: `https://www.example.com`. It is better to remove the slash `/` after it.
+
+### Authentication
+
+Cloudreve V4 supports authentication using Token. The mounting authentication methods are divided into:
+
+1. `Username` + `Password`: Automatically uses the login interface to obtain Access Token and Refresh Token, there might be issues with CAPTCHA.
+2. `Refresh Token` Only: Automatically uses the refresh interface to renew Access Token and Refresh Token, parameters can be found from browser requests or Local Storage.
+3. `Access Token` Only: Can be temporarily used but will expire and cannot be renewed.
+4. None: Anonymous user, suitable for public sharing.
+5. [Reference](../drivers/common.html#reference): Fill in `ref:/{mount path}` in `Remark`: Reference authentication, tokens, etc., from "Mounted Storage".
+
+### Steps to get tokens
+
+#### From Local Storage
+
+::: tip
+There may be multiple sessions; please select the one you want to mount.
+:::
+
+
+
+#### From Network
+
+::: tip
+You may need to log in anew to see this request.
+:::
+
+
+
+### Root Folder Path
+
+Cloudreve V4 uses a custom URI as the path, which can be obtained from the `?path=` in the web link. The obtained parameters may need to be [URL decoded](https://www.google.com/search?q=URL+decode).
+
+#### Mounting My Files
+
+Default is `cloudreve://my/`, listing user files.
+
+#### Mounting Share
+
+Supports mounting folder-type shares, the path should be filled as: `cloudreve://{ShareID}@share/`.
+
+- ShareID is the parameter after `/s/` in the share link.
+- Currently, Cloudreve V4 does not support creating password-protected shares. However, if the data is migrated from V3, the previously created sharing password will be retained. The URI of the share link with the password (`/s/{shareID}/{sharePassword}`) is `cloudreve://{shareID}:{sharePassword}@share`.
+
+### Enable Folder Size
+
+Enable Cloudreve V4 server to calculate the size of each folder. Enabling this feature may cause server errors or slow performance, and it is `disabled` by default.
+
+### Enable Thumbnails
+
+Enable Cloudreve V4 server to generate thumbnails for each file. Enabling this feature may cause server errors or slow performance, and it is `disabled` by default.
+
+### Enable Version Upload
+
+Enable overwrite upload and keep the previous version, which consumes extra space. Disabled by default, delete the existing file before overwriting upload.
+
+### Custom UA
+
+Used to customize the `User-Agent` header information used in requests. Leaving it blank will use OpenList default settings.
+
+### Sorting
+
+Supports changing the sorting parameters when requesting lists.
+
+### Hide files currently being uploaded
+
+Filter files with upload sessions (in progress) based on metadata information, size 0, unable to download
+
+## Upload
+
+The supported storage policies for uploading are as follows:
+
+- Local storage
+- Slave storage
+- OneDrive
+- S3
+- KS3
+
+Upload storage policies can be set within Cloudreve V4 web interface by entering the corresponding folder (requires the server to be Cloudreve Pro).
+
+If upload permissions are enabled for shares, uploads are supported. It requires the server to check "Enhance anonymous user permissions" for the user group (requires the server to be Cloudreve Pro).
+
+## The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/cnb_releases.md b/pages/en/guide/drivers/cnb_releases.md
new file mode 100644
index 000000000..78e12ad61
--- /dev/null
+++ b/pages/en/guide/drivers/cnb_releases.md
@@ -0,0 +1,61 @@
+---
+categories:
+ - guide
+ - drivers
+top: 397
+---
+
+# CNB Releases
+
+https://cnb.cool/
+
+## Known issues
+
+CNB releases are not a standard file system and have some unresolved issues. Please do not submit feedback for these.
+
+1. An empty repository needs to be initialized first.
+2. Subdirectories are not supported under Tag / Release directories.
+3. The OpenAPI upload returns `expires_in_sec` as only 10 seconds. Uploading large files may time out; after time out, the upload continues but returns `invalid token`. Therefore, a local timeout mechanism is added to automatically stop uploading when the set time is reached, avoiding failed uploads and wasted bandwidth.
+4. `Move`, `Copy`, and `Rename` operations are not supported.
+5. Only when `UseTagName` is disabled, renaming can be done by modifying the Release name.
+
+## Parameters
+
+### Repo
+
+Only one repository can be specified. To reuse a token, please use the [Reference](common.md#reference) feature.
+
+### Token
+
+Access token. No need to include `Bearer`. Supports the [Reference](common.md#reference) feature.
+
+How to obtain: After logging in, go to `Personal Settings` - [Access Token](https://cnb.cool/profile/token) -> `Add Access Token`.
+
+For listing, grant the `repo-code:r` permission. For modifications, grant the `repo-code:rw` permission.
+
+### UseTagName
+
+Use the original Tag name instead of the Release name.
+
+By default, this is disabled and the Release name is used, which supports renaming. Tag names cannot be changed once created. When creating a new folder for the first time, a Tag with the folder name will be published. Renaming an existing Release will modify the Release name.
+
+## The default download method used
+
+```mermaid
+---
+title: Which download method is used by default?
+---
+flowchart TB
+ style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
+ style a2 fill:#ff7575,stroke:#333,stroke-width:4px
+ subgraph ide1 [ ]
+ a1
+ end
+ a1[302]:::someclass====|default|a2[user equipment]
+ classDef someclass fill:#f96
+ c1[local proxy]-.alternative.->a2[user equipment]
+ b1[Download proxy URL]-.alternative.->a2[user equipment]
+ click a1 "../drivers/common.html#webdav-policy"
+ click b1 "../drivers/common.html#webdav-policy"
+ click c1 "../drivers/common.html#webdav-policy"
+```
diff --git a/pages/en/guide/drivers/common.md b/pages/en/guide/drivers/common.md
new file mode 100644
index 000000000..ce63d7b79
--- /dev/null
+++ b/pages/en/guide/drivers/common.md
@@ -0,0 +1,207 @@
+---
+top: 1000
+categories:
+ - guide
+ - drivers
+---
+
+# Common
+
+## Mount Path
+
+The unique identifier for the mount point, the name displayed externally, and the location where it should be mounted. If you want to mount it to the root directory, please enter `/`.
+
+
+
+
+
+::: danger
+You cannot use duplicate mount path names, otherwise, the following error will occur:
+
+```json
+Failed to create storage in database: UNIQUE constraint failed: x_storages.mount_path
+```
+
+Solution: Use [aliases](./alias.md) to aggregate multiple mount points.
+:::
+
+::: danger
+The mount path name is a required field and cannot be left empty, or the following error will occur:
+
+```json
+Key: 'Storage.MountPath' Error: Field validation for 'MountPath' failed on the 'required' tag
+```
+
+Solution: If you want to mount to the root directory, please enter `/`.
+:::
+
+## Order
+
+When mounting multiple drives, this is used for sorting. The smaller the number, the further to the front. Negative numbers can also be used.
+
+## Remark
+
+You can add notes for easier management.
+
+### Reference
+
+Reference authentication, tokens, etc., from the **"Mounted Storage"** to enable sharing the same token between multiple cloud drives.
+
+Currently, the following cloud drives are supported:
+
+- 139Yun
+- AliyundriveOpen
+- 189CloudPC
+- 123PanShare（ref 123Pan）
+- Cloudreve V3 / V4
+
+**How to use**: In the storage settings, set the first line of **Remark** to: **ref:/mount_path**
+
+**Important**: `ref:/` should be in lowercase letters and symbols.
+
+
+
+## Enable signing
+
+Sign and encrypt files (no password required), only valid for this driver, if other signatures are not enabled and `signature all` and `meta-information encryption` are not set, others will not be signed.
+
+Usage scenario: I don't want to enable all signatures, and I don't want to set metadata encryption. I just want to sign and encrypt a certain driver to prevent it from being scanned.
+
+Scope of influence: `Settings-->Global-->Signature All` > `Metainformation Directory Encryption` > `Single Driver Signature`.
+
+## Disable index
+
+Allow users to disable storage indexing.
+
+- For example, if you enable `Ignore Index` in the index options, you no longer need to configure it after enabling `Disable Index`, which is more convenient.
+
+## Cache Expiration
+
+Cache time of directory structure.
+
+## Custom Cache Policies
+
+Cache time for directory paths (in minutes).
+
+You can customize the cache time for specific file paths using pattern matching. The configuration supports wildcard patterns:
+
+- `*` matches a **single** directory level.
+- `**` matches **multiple** directory levels.
+
+Example configuration:
+
+```txt
+/Series/Completed/*:60
+/Series/Updating/*/**:10
+/Series/Archived/**:30
+```
+
+Explanation:
+
+- `*` matches only a single directory level. Items directly under `/Series/Completed` will be cached for 60 minutes. This does **not** include deeper subdirectories — for example, `/Series/Completed/A/B` will not match this rule.
+- `**` matches multiple directory levels. Therefore, the contents of subdirectories under `/Series/Updating` will be cached for 10 minutes. For example, `/Series/Updating/A/B` and `/Series/Updating/C/D` will match.
+- The pattern `/Series/Updating/*/**` enforces a “single level followed by multi-level” match. As a result, directories directly under `/Series/Updating` will **not** be matched by this rule.
+- All contents under `/Series/Archived` (including any depth of subdirectories) will be cached for 30 minutes.
+
+## Web proxy
+
+Whether the web preview,download and the direct link go through the transfer. If you open this, recommended you set [site_url](../../configuration/configuration.md#site-url) so that OpenList can works fine.
+
+::: tip
+
+- **Web proxy Strategies:** It is a strategy when using the webpage. The default is a local agent. If you fill in the proxy URL and enable the web agent to use the proxy URL
+- **Webdav policy Strategies:** It is an option to use the webdav function
+ - If there are 302 options default to 302, if there is no 302 option default to the local agent, if you want to use the agent URL, please fill in and manually switch to the proxy URL strategy
+
+The two are different configurations.
+
+:::
+
+## Webdav policy
+
+- **302 redirect:** redirect to the real link
+ - Although it does not consume traffic, it is not recommended to share and use it.
+- **use proxy URL:** redirect to proxy URL
+ - It will consume the traffic of the agent URL
+- **native proxy:** return data directly through local transit(best compatibility)
+ - The traffic of the construction of OpenList device will consume
+
+### Description of three modes
+
+```mermaid
+---
+title: 302 redirect, use proxy URL, native proxy
+---
+flowchart LR
+ E(User operation OpenList calls API+ Tutorial on how to modify UA in web page 302 mode +
+
+
+
+
+ Official
+
+
+
+ Crack video (unavailable)
+
+ triggers related API operations Cloud Drive
Cloud Drive receives command and begins execution) + A[(Cloud Drive)] + B(You) + C[Use proxy URL] + D{Native proxy} + E==>A==>E + A==>|Directly transferring from cloud drive to you without any loss
302 downloads as fast as possible|B + A-->|Send the cloud disk to the use proxy URL first|C-->|After being forwarded to you by the proxy URL, your download speed depends on the speed of downloading, forwarding, and forwarding on the other end of the proxy URL|B + A-->|Send the cloud drive to the device running OpenList first|D-->|After being forwarded to you by the device running OpenList, your download speed depends on the speed of downloading, uploading, and forwarding on the end where OpenList is built|B +``` + +## Download proxy URL + +When the proxy is turned on without filling in this field, the local machine will be used for transfer by default. + +### 1. Cloudflare Workers + +Here’s the translation: + +You can use Cloudflare Workers as a proxy. Simply fill in your Cloudflare Workers address here. + +The code to set up Workers can be found at [https://github.com/OpenListTeam/OpenList-Proxy/blob/main/openlist-proxy.js](https://github.com/OpenListTeam/OpenList-Proxy/blob/main/openlist-proxy.js). When using it, you need to replace the following variables: + +- `ADDRESS`: Your OpenList address, which must include the protocol header and should not end with a `/`. For example, `https://pan.example.com`. + +- `TOKEN`: The [Token](../../configuration/other.md#token) of the admin account, which can be found in the “Other Settings” section of the OpenList admin page. + +- `WORKER_ADDRESS`: Your Worker address, which is usually the same as the **Download Proxy URL**. + + :warning: Cloudflare Workers free CDN support is only compatible with **http80** and **https443** ports (whether domestic or international), as tested by group members. + +When filling in the **Download Proxy URL** in the OpenList backend configuration, the link should not end with a `/`. + +Detailed text tutorial:
+For example, if the exported password is `abc123xyz`, it should be entered as `___Obfuscated___abc123xyz` in the Crypt driver. +::: + +Primary encryption key. **Must be remembered** - cannot be recovered if lost. + +#### Salt + +::: warning +Note that salts exported using `rclone config` are obfuscated and cannot be used directly. Please prefix the salt with `___Obfuscated___` before use.
+For example, if the exported salt is `abc123xyz`, it should be entered as `___Obfuscated___abc123xyz` in the Crypt driver. +::: + +Secondary encryption key, acts as an additional password layer. **Must be remembered** - cannot be recovered if lost. + +If you don't know what is salt, treat it as a second password. Optional but recommended + +### Advanced Options + +#### Encrypted Suffix + +**Default:** `.bin` + +Custom suffix for encrypted files (only used when filename encryption is disabled). Must start with a dot (e.g., `.abc`, `.encrypted`). + +#### Filename Encoding + +**Default:** `base64` + +**Warning:** Only modify if you understand the implications. Other encoding options are not thoroughly tested and may cause compatibility issues. + +For rclone compatibility, configure this setting in advanced options. + +## Advanced Usage + +### Rclone Compatibility + +The Crypt driver is fully compatible with [rclone crypt](https://rclone.org/crypt). + +**Important Notes:** + +- OpenList Crypt uses `filename_encoding = base64` by default for better long filename support, configure this setting in advanced options when using with rclone +- Case-insensitive filesystems (e.g., Windows with local storage) may cause issues + +## Troubleshooting + +### Startup Errors + +If Crypt shows errors during OpenList startup, it's likely because Crypt starts before its target path is available. + +**Solution:** Set a higher [order number](./common.md#order) for the Crypt driver to delay its initialization. + +### Data Access Issues + +If you cannot access previously encrypted data: + +1. Verify that the password and salt values are correct +2. Ensure the configuration hasn't been modified +3. Check that the remote path is accessible +4. Confirm the filename encoding setting matches your original configuration + +## The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + c1 + end + c1[local proxy]:::someclass==default===>a2[user equipment] + classDef someclass fill:#f96 + b1[Download proxy URL]-.alternative.->a2[user equipment] + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/degoo.md b/pages/en/guide/drivers/degoo.md new file mode 100644 index 000000000..76b707b06 --- /dev/null +++ b/pages/en/guide/drivers/degoo.md @@ -0,0 +1,55 @@ +--- +categories: + - guide + - drivers +top: 587 +--- + +# Degoo + +https://degoo.com/ + +**Authentication methods**: + +1. Username + Password +2. Refresh Token +3. Access Token + +In normal cases, you can log in with your username + password. If you encounter a 429 error, you can log in using tokens. You can obtain the token from the request body or header in your browser. + +## Username + +Your user's name. + +## Password + +Your user's password. + +## Refresh Token + +Refresh token for automatic token renewal, obtained automatically. + +## Access Token + +Access token for Degoo API, obtained automatically. + +## The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/develop.md b/pages/en/guide/drivers/develop.md new file mode 100644 index 000000000..6ff2c1a8e --- /dev/null +++ b/pages/en/guide/drivers/develop.md @@ -0,0 +1,11 @@ +--- +top: 100 +categories: + - guide + - drivers +--- + +# Contribute new storage driver + +Duplicate `drivers/template` to expand the new storage. Please read [CONTRIBUTING](https://github.com/OpenListTeam/OpenList/blob/main/CONTRIBUTING.md) for details. +The design of the driver part of OpenList is easy to expand, no need to modify other files, just create a new package under the back-end project drivers package and reference this package in the `all.go` file. diff --git a/pages/en/guide/drivers/doubao.md b/pages/en/guide/drivers/doubao.md new file mode 100644 index 000000000..d9b34312b --- /dev/null +++ b/pages/en/guide/drivers/doubao.md @@ -0,0 +1,58 @@ +--- +top: 676 +categories: + - guide + - drivers +--- + +# Doubao Drive + + + +Mount [Doubao Drive](https://www.doubao.com/chat/drive/) cloud storage. + +::: danger Security Risk + +Do not use 302 if the storage is public accessible. +Otherwise, the download link may leak sensitive information such as access token or signature. +Others may use the leaked link to **access all your files**. + +::: + +## Root folder ID + +The root folder ID is the parameter value displayed in the address bar when accessing Doubao Drive via a web page. For example, after accessing [Doubao Drive](https://www.doubao.com/chat/drive/), the address bar shows `https://www.doubao.com/chat/drive/AAAAAAAAAAAAAAAAAAAAAAAAAA?tab=myUpload`, where `AAAAAAAAAAAAAAAAAAAAAAAAAA` is the root folder ID. + + + +## Cookie + +Required. Web cookie. Used to refresh token and extract Authorization/DPoP tokens. + +Open browser developer tools, visit [Doubao Drive](https://www.doubao.com/drive/), log in to your account, check the `Network` tab, search for `biz_auth` and open it, find `Cookie` in the `Header`, copy the complete value and fill it in. + + + +OpenList will automatically extract other attributes from the Cookie. Please ensure that the Cookie contains the following key-value pairs: + +- `LARK_SUITE_DPOP` +- `LARK_SUITE_ACCESS_TOKEN` +- `feishu_dpop_keypair` (used for key generation, optional) + +## App ID + +必填，Doubao's App ID. The App ID may vary for different clients, please refer to the actual value. + +## DPoP Key Secret, Auth Client ID, Auth Scope, Auth SDK Source, Auth SDK Version + +Optional, for Token refresh. Please obtain it yourself, and refer to the actual value. + +## Share Link + +Whether to use share link for download. If enabled, OpenList will create share and request with anonymous user's token to create download link. This can reduce authorization leak. + +Please ensure you have filled all authentication options above before enabling this function. + +## Ignore JWT Check + +Whether to ignore JWT check to prevent time issue diff --git a/pages/en/guide/drivers/dropbox.md b/pages/en/guide/drivers/dropbox.md new file mode 100644 index 000000000..481156524 --- /dev/null +++ b/pages/en/guide/drivers/dropbox.md @@ -0,0 +1,119 @@ +--- +top: 590 +categories: + - guide + - drivers +--- + +# Dropbox + +Dropbox Official：https://www.dropbox.com/ + +## Get refresh token + +- **This drive does not support the online API mode provided by OpenList.** + +- The following tutorial applies when the option is kept disabled as shown below. + +  + +- If you create your own `Client ID` and `Secret`, remember to authorize them. + +The steps are as follows: + +1. First, [click here](https://www.dropbox.com/developers/apps?_tk=pilot_lp&_ad=topbar4&_camp=myapps) to enter the Dropbox app management page and click "Create App". + +  + +2. After entering the app, configure the app type as shown below. + +  + +3. You can get the id and secret in the red box: the upper one is the id, the lower one is the secret. + +  + +4. Configure the callback URL. If you are strict about permissions and do not want to use an external callback address, you can set a local address here, or use the one outside the red box. + +  + +5. Finally, go to the permissions configuration page to set the app's permissions. + +  + +6. [Click here](https://api.oplist.org/) to enter the token acquisition tool. Select Dropbox, fill in your id and secret, and after authorization you can get the refresh token. + +7. In the OpenList configuration page, enter the refresh token, id, and secret to use. Note that the refresh token is about 40-50 characters long. + + + +If you are highly privacy-conscious, Dropbox supports local callback. You can use the following script provided by GPT to quickly implement it, communicating only with Dropbox servers. + +::: warning +Since the callback address is local and you have not set up a real local callback server, please manually copy the authorization code from the browser address bar. + +**Please resolve Python environment issues yourself, or use the callback server provided above.** +::: + +```python +import requests +import webbrowser +# Please replace with your own Dropbox App information +CLIENT_ID = 'your_app_key' +CLIENT_SECRET = 'your_app_secret' +REDIRECT_URI = 'http://localhost:114514' +# Step 1: Get authorization code +auth_url = ( + f"https://www.dropbox.com/oauth2/authorize" + f"?client_id={CLIENT_ID}" + f"&redirect_uri={REDIRECT_URI}" + f"&response_type=code" + f"&token_access_type=offline" # Required: key parameter to get refresh_token +) +print("👉 Please visit the following link to authorize:\n") +print(auth_url) +webbrowser.open(auth_url) +auth_code = input("\n✅ After authorization, paste the code after ?code= in the redirected URL here:\n> ").strip() +# Step 2: Exchange for access_token + refresh_token +token_url = "https://api.dropboxapi.com/oauth2/token" +data = { + 'code': auth_code, + 'grant_type': 'authorization_code', + 'client_id': CLIENT_ID, + 'client_secret': CLIENT_SECRET, + 'redirect_uri': REDIRECT_URI +} +response = requests.post(token_url, data=data) +response.raise_for_status() +tokens = response.json() +# ✅ Only output the refresh token +print("\n🎉 Success! Your Dropbox refresh_token is:\n") +print(tokens.get("refresh_token")) +``` + +## Root folder file_id + +**Empty is the root directory**：display all files +**Single folder ID**：Enter the folder you need to display, copy the top link to fill in `/home` behind + + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/emby.md b/pages/en/guide/drivers/emby.md new file mode 100644 index 000000000..434ac4215 --- /dev/null +++ b/pages/en/guide/drivers/emby.md @@ -0,0 +1,54 @@ +--- +top: 493 +categories: + - guide + - drivers +--- + +# Emby + +Mount media resources from an Emby server. + +## URL + +Emby server address, for example: `http://127.0.0.1:8086`. + +## ApiKey + +Emby API Key. Use together with `UserID` for API authentication. + +## UserID + +Emby user ID. Used with `ApiKey`. + +## Username + +Emby account username. Used with `Password`. + +## Password + +Emby account password. Used with `Username`. + +## LinkMethod + +Choose link method: + +- `stream`: Streaming link (recommended) +- `download`: Direct download link + +Some Emby servers do not grant download permission. In that case, please use `stream`. + +## Authentication Method + +Use **one** of the following login methods: + +1. `ApiKey + UserID` +2. `Username + Password` + +Do not mix both methods at the same time. + +## Example Configuration + +- URL: `http://127.0.0.1:8086` +- LinkMethod: `stream` +- Authentication: choose one method only diff --git a/pages/en/guide/drivers/febbox.md b/pages/en/guide/drivers/febbox.md new file mode 100644 index 000000000..5e725220d --- /dev/null +++ b/pages/en/guide/drivers/febbox.md @@ -0,0 +1,57 @@ +--- +top: 591 +categories: + - guide + - drivers +--- + +# FebBox + +FebBox：https://www.febbox.com + +- The upload function is currently unavailable. + +## Root folder ID + +Root directory ID, default is `0`. + +Other directory IDs can be viewed in the top link address bar after entering the folder. + +- **https://www.febbox.com/console#/files?parent_id=66889900** + + Then the directory ID is `66889900` + +## `Client_id`、`Client_secret` + +Generate address：**https://www.febbox.com/open/clients** + +- The generated client ID and secret key are filled in in the opposite order to the OpenList, so be careful not to fill them in incorrectly. + +  + +## User IP + +**Optional**, the IP address of the user when downloading, quoting the official description + +> IP address, Optional parameter. Supports IPv6 format. After filling in, the best download server suitable for the IP location will be selected. If not filled in, the requested IP will be used. + +## The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/feiji.md b/pages/en/guide/drivers/feiji.md new file mode 100644 index 000000000..63989cb5a --- /dev/null +++ b/pages/en/guide/drivers/feiji.md @@ -0,0 +1,50 @@ +--- +top: 686 +categories: + - guide + - drivers +--- + +# FeiJi Cloud + +**https://feijipan.com/** + + + +::: danger +Feiji Cloud imposes login restrictions on 3rd-party platforms. Attempting to access its service via OpenList may result in your account being banned. Please proceed with caution! +::: + +## Root folder ID + +root folder ID the default is `0`，Other directory ID View the figure below obtaining method + + +## username、password + +Just fill in your own Feiji Cloud Account Password + +## Known issues + +The file size returned by iLanZou is in Kilo Bytes, not Bytes. Therefore, you cannot accurately determine if a file has been modified based on its size. Please pay attention to the configuration of your sync software. + +## The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/ftp.md b/pages/en/guide/drivers/ftp.md new file mode 100644 index 000000000..d4aefa2af --- /dev/null +++ b/pages/en/guide/drivers/ftp.md @@ -0,0 +1,47 @@ +--- +top: 898 +categories: + - guide + - drivers +--- + +# FTP + +### Address + +FTP address, need contains port. + +### Username + +FTP username + +### Password + +FTP password + +### Root folder path + +root folder , default `/`, same as local storage. + +## Enter directory before listing + +Whether to change into the target directory before listing files. Some FTP servers do not support listing files with a path argument directly. Enable this option to first `cd` into the directory and then `ls`, which can resolve such compatibility issues. Default: `false`. + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + c1 + end + c1[local proxy]:::someclass==default===>a2[user equipment] + classDef someclass fill:#f96 + b1[Download proxy URL]-.alternative.->a2[user equipment] + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/github.md b/pages/en/guide/drivers/github.md new file mode 100644 index 000000000..587366ca6 --- /dev/null +++ b/pages/en/guide/drivers/github.md @@ -0,0 +1,125 @@ +--- +top: 399 +categories: + - guide + - drivers +--- + +# GitHub API + +::: tip +GitHub API does not support operating files larger than 100MiB and folders containing more than 100,000 sub-items. + +All `.gitkeep` files will be managed by the driver and will be invisible to the user. + +Operations on submodules are currently not supported. +::: + +## Token + +1. Log in GitHub and visit
+ +## Fill in example: + + +
+ +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + c1 + end + c1[local proxy]:::someclass==default===>a2[user equipment] + classDef someclass fill:#f96 + b1[Download proxy URL]-.alternative.->a2[user equipment] + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/misskey.md b/pages/en/guide/drivers/misskey.md new file mode 100644 index 000000000..9788bcda3 --- /dev/null +++ b/pages/en/guide/drivers/misskey.md @@ -0,0 +1,17 @@ +--- +top: 588 +categories: + - guide + - drivers +--- + +# Misskey Drive + +## Instance URL + +The URL of your Misskey instance, whether self-hosted or in use. +For example, the official instance at `https://misskey.io` + +## Token + +Visit `https://{misskey-instance}/settings/api` to generate an access token. It requires the `read:drive` and `write:drive` permissions. diff --git a/pages/en/guide/drivers/mopan.md b/pages/en/guide/drivers/mopan.md new file mode 100644 index 000000000..dea6db66c --- /dev/null +++ b/pages/en/guide/drivers/mopan.md @@ -0,0 +1,50 @@ +--- +top: 691 +categories: + - guide + - drivers +--- + +# MoPan + + + +MoPan address：**https://mopan.sc.189.cn/mopan/#/downloadPc** + +- There is no web version, only `Android`, `iOS`, `PC-Win64bit`, `iPad`, and `TV`. + +## Sms code + +Enter the option of the mobile phone number and password when the first addition, and then enter the `SMS Code` input `send`, and then click Save to send it to you. + +## Root folder ID + +Do not fill in this option, it will automatically fill into the root directory + +- Due to encrypted requests, an appropriate method for obtaining folder IDs has not yet been found + +### Tips + +1. `root folder ID`,`equipment information`does not need to be filled in, will automatically help you fill +2. If you enter the send in [SMS Code] (#SMS-Code), it is found that it has been saved,Please click Edit to enter the verification code received + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/onedrive.md b/pages/en/guide/drivers/onedrive.md new file mode 100644 index 000000000..e0a92da35 --- /dev/null +++ b/pages/en/guide/drivers/onedrive.md @@ -0,0 +1,146 @@ +--- +top: 599 +categories: + - guide + - drivers +--- + +# OneDrive / Share + +:::tip + +- If you have global administrator permissions for a non-home edition, you can use the [OneDrive APP](onedrive_app.md) driver. +- If your account does not support the API, (for example, the school account has not verified the administrator, or the administrator has disabled the API), then you can also mount it through webdav. For details, see [webdav](webdav.md) + +::: + +## 1. Mounting using Online API's default application + +You do not need to create an application yourself by mounting in this way. + +1. Open
+Then enter https://www.terabox.com in the address bar of this tab to enter the webpage, you can see the reserved request, and then find **`Cookie`** from the reserved request. + +
+ +## Download Api + +**Download api needs to choose `Crack`** ，before you can use +
+ +## Root folder id + +- Root folder id is `/` +- Mount other single subdirectories, put a picture for reference + -
+
+## Download error using Proxy Url link
+
+Using [**Proxy Url**](common.md#download-proxy-url) to download error
+
+```json
+{
+ "error_code": 31211,
+ "error_msg": "access denied"
+}
+```
+
+View specific reasons：**[https://github.com/alist-org/alist/issues/6508](https://github.com/alist-org/alist/issues/6508#issuecomment-2171762705)**
++ +## The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/thunder.md b/pages/en/guide/drivers/thunder.md new file mode 100644 index 000000000..7c81ff4f3 --- /dev/null +++ b/pages/en/guide/drivers/thunder.md @@ -0,0 +1,498 @@ +--- +top: 685 +categories: + - guide + - drivers +--- + +# Thunder Cloud Disk + + + +::: tip +Please use `Thunder` directly instead of `ThunderExpert` if you are not good at it. + +`ThunderExpert` mainly provides more free settings and realizes more login methods + +--- + +`Thunder X` serves overseas users. As of the time of document release, only the Android version is available. Other versions have not yet been released. + +- Thunder X has sufficient speed even without membership. Future changes are unknown. +- Using the APP may require a proxy, but not when mounted on OpenList. + +--- + +`Thunder Browser`：Currently only supports mobile phones (Android, iOS) + +- **https://x.xunlei.com/** +- If you log in to OpenList, the mobile phone will be kicked offline. On the contrary, if you log in to OpenList first and then log in to the mobile phone, OpenList will be kicked offline but there will be no prompt + +::: + +## 1. Thunder + +### Username + +That is, the mobile phone number, email, and username used for login (there is a probability that you cannot log in, you need to try) + +1. Before obtaining the verification code, do not include the `+86` country code when entering the phone number. +2. After obtaining the verification code, the phone number must include the `+86` country code, for example: +8613722223333. + +### Password + +password for login + +
+ +### Credit Key + +After saving for the first time, an error will occur. This is normal. Please go to the storage management interface. + + + +Copy all the content above. + +[Click here to enter](https://i.xunlei.com/xlcaptcha/android.html) + +After entering, open the developer tools (usually by pressing F12), go to the console, and enter `reviewCb()`. **Paste all the previously copied content, including the curly braces,** inside the parentheses, as shown below: + + + +Move the cursor to **after the parentheses** and press Enter. + + + +The webpage will automatically redirect to the mobile number verification page. + +After completing the verification, the page **will not** refresh automatically. Please check the console. The `creditkey` shown below is the required key. + + +Copy it to the storage management, and you can mount it normally. + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + c1 + end + c1[local proxy]:::someclass==default===>a2[user equipment] + classDef someclass fill:#f96 + b1[Download proxy URL]-.alternative.->a2[user equipment] + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` + +## 2. ThunderExpert + +::: tip +If Xunlei needs to download, you must specify UserAgent (same as DownUserAgent below). Or use the proxy function in this program to transfer. +::: + +### Login Type + +1. When selecting User, you only need to fill in the username and password + - User You need to bring the `+86` area code, for example +8613722223333 fill in like this +2. **RefreshToken**: Just fill in RefreshToken when selecting RefreshToken + +### Signature Type + +**Algorithms**：When selecting Algorithms, just fill in the Algorithms (it is difficult to obtain, and needs to be reversed) + +**Captcha sign**: Only fill in CaptchaSign and Timestamp when selecting CaptchaSign + +``` +//signature algorithm +str = ClientID + ClientVersion + PackageName + DeviceID + Timestamp +for (Algorithm in Algorithms) { + str = md5(str + Algorithm) +} +CaptchaSign = "1." + str +``` + +Login type and Sign type recommended options + + + +### DeviceID + +The value calculated by md5 is used to determine the logged in device + +### ClientID, ClientSecret, ClientVersion, PackageName + +It is related to the signature, fill in according to the actual situation + +### UserAgent + +UserAgent used by API requests, may be inaccessible or speed limited if the setting is incorrect + +### DownUserAgent + +The User Agent used for downloading, if the setting is wrong, it will not be downloaded (it will be used when the agent is turned on) Fixed parameters: + +`Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36` + +### Key data acquisition process + +Obtain Xunlei request data through network analysis tools (packet capture tools) --- Please read the following information carefully + +Open Xunlei and log in to your account (the picture below uses the PC client to operate, and the web terminal is also available) + +Included in the request https://xluser-ssl.xunlei.com/v1/shield/captcha/init + +CaptchaSign, Timestamp, DeviceID, ClientID, ClientVersion, PackageName, User-Agent + +**Note**: After obtaining the information of the two pictures, slowly select the data from the two data captured and fill in it + +After logging in to Thunder and opening the packet capture tool, it is possible that the information of **v1/shield/captcha/init** cannot be immediately obtained at this time. + +Do not close the Xunlei PC client and the packet capture tool, just wait, it will refresh automatically after **5 minutes** + +You will see the parameters as shown in the figure below, and you can fill in it according to the acquisition (if you can't see it clearly, you can right-click to copy the picture and link it to the browser to open a new window) + +See **v1/shield/captcha/init** and grab it, please **immediately don't delay for a second** Right-click Xunlei in the taskbar in the lower right corner to exit, exit completely and then reopen to get \* \*Figure II\*\* + + + +Restarting Thunder will refresh the token + +The request to https://xluser-ssl.xunlei.com/v1/auth/token contains RefreshToken (please use the returned value), ClientSecret (does not exist on the web side) + + +Figure 1 contains **7** parameters | Figure 1 contains **2** parameters | a fixed parameter (Down UserAgent), ten parameters and 3 options and a mount path, just write and save, before saving Remember to check~ + +When the `Video URL` option is enabled, it will attempt to replace the original link with the media link returned by the API. Currently, the official platform throttles the download link for **non-members**, but video streaming is not throttled. Therefore, by replacing the link, you can avoid throttling, which applies to both **OpenList** media file downloads and streaming. For regular files, you can also bypass the throttling by renaming the file extension to a media format (e.g., `.mp4`). + +The **Expert Edition** does not enable the `Video URL` option by default, as it is intended for users who configure detailed parameters themselves, and they should be aware of the significance of this option. Hence, it is not enabled by default. For **Xunlei X** users, this option is enabled by default, primarily for the convenience of less experienced users. + +### ThunderExpert complete parameter filling demo: + + + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` + +## 3. Thunder X + +::: danger +At present, the official will ban frequent API calls. Please use with caution and bear the consequences. +::: + +### username、password + +The mailbox and password used for login +
+ +### CaptchaToken + +It will be filled automatically without filling in manually +
+ +### Root folder id + +The default is the full directory of the empty display, If you want to use a subfolder to make the root directory, grab the request to get it + +- In the request in the package`https://api-pan.xunleix.com/drive/v1/files?parent_id=&page_token=&filters=`，you can get the following parameters + - `文件夹ID（id）` + - `文件夹名称（name）` + - `父文件夹ID（parent_id）` +- The `folder ID` obtained in the root directory (for example : `我接收的文件`、`我的云盘`、`高速云下载`), **This will change with different account numbers, there is no the same value, In the request in the package** +  + +### Use video url + +When the `Video URL` option is enabled, it will attempt to replace the original link with the media link returned by the API. Currently, the official platform throttles the download link for **non-members**, but video streaming is not throttled. Therefore, by replacing the link, you can avoid throttling, which applies to both **OpenList** media file downloads and streaming. For regular files, you can also bypass the throttling by renaming the file extension to a media format (e.g., `.mp4`). + +The **Expert Edition** does not enable the `Video URL` option by default, as it is intended for users who configure detailed parameters themselves, and they should be aware of the significance of this option. Hence, it is not enabled by default. For **Xunlei X** users, this option is enabled by default, primarily for the convenience of less experienced users. + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` + +## 4. Thunder X Expert + +::: danger +At present, the official will ban frequent API calls. Please use with caution and bear the consequences. +::: + +### username、password + +The mailbox and password used for login +
+ +### CaptchaToken + +It will be filled automatically without filling in manually +
+ +### Root folder id + +The default is the full directory of the empty display, If you want to use a subfolder to make the root directory, grab the request to get it + +- In the request in the package`https://api-pan.xunleix.com/drive/v1/files?parent_id=&page_token=&filters=`，you can get the following parameters + - `文件夹ID（id）` + - `文件夹名称（name）` + - `父文件夹ID（parent_id）` +- The `folder ID` obtained in the root directory (for example : `我接收的文件`、`我的云盘`、`高速云下载`), **This will change with different account numbers, there is no the same value, In the request in the package** +  + +### Login Type + +- `User`: Only fill in the username and password +- `Refresh token`: Just fill in`RefreshToken` + +### Sign Type + +- `Algorithms`：Choose `Algorithms` Just fill in `Algorithms` (It has been automatically filled. You do n’t have to fill in it yourself. You only need to fill in the username and password.When the algorithm is not invalidated) +- `Captcha sign`: Choose `Captcha sign` Just fill in `Captcha sign` and `Timestamp` + +### Part of parameter Packet Capture description + +- `Captcha token`：No need to fill in +- `Device id`：The value calculated by MD5 is used to judge the login device +- `Client id`, `Client secret`, `Client version`, `Package name`：It related to the signature, fill in according to the actual situation + +--- + +- `User agent`：API requests `User agent`, setting errors may not access or speed limit +- `Download user agent`：When downloading, use the `user agent `,If the setting error cannot be downloaded (the agent will use it) + - `User agent` and `Download user agent`：You can fill it out by yourself. If you don’t know how to fill it out, you can leave it blank and it will be automatically filled in. + +--- + +In the request in the package `https://xluser-ssl.xunleix.com/v1/shield/captcha/init`，you can get the following parameters6 + +- `Client id`、`Device id`、`Captcha sign` +- `Package name`、`Client version`、`Timestamp` + +  + + In the request in the package `https://xluser-ssl.xunleix.com/v1/auth/signin`, you can get the following parameters2 + - `Client id`、`Client secret` +  + +### Use video url + +When the `Video URL` option is enabled, it will attempt to replace the original link with the media link returned by the API. Currently, the official platform throttles the download link for **non-members**, but video streaming is not throttled. Therefore, by replacing the link, you can avoid throttling, which applies to both **OpenList** media file downloads and streaming. For regular files, you can also bypass the throttling by renaming the file extension to a media format (e.g., `.mp4`). + +The **Expert Edition** does not enable the `Video URL` option by default, as it is intended for users who configure detailed parameters themselves, and they should be aware of the significance of this option. Hence, it is not enabled by default. For **Xunlei X** users, this option is enabled by default, primarily for the convenience of less experienced users. + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` + +## 5. Thunder Browser + +### username、password + +Mobile phone number, email, username, and password used to log in + +- When filling in the mobile phone number, please bring the `+86` area code, for example `+8613822334455` + +### CaptchaToken + +It will be filled automatically without filling in manually + +### Root folder id + +The default is the full directory of the empty display, If you want to use a subfolder to make the root directory, grab the request to get it + +- In the request in the package`https://x-api-pan.xunlei.com/drive/v1/files?parent_id&page_token&space=`，you can get the following parameters + - `文件夹ID（id）` + - `文件夹名称（name）` + - `父文件夹ID（parent_id）` +- The `folder ID` obtained in the root directory (for example : `来自分享`、`超级保险箱`), **This will change with different account numbers, there is no the same value, In the request in the package** +  + +### Safe password + +Thunder Browser Safe password + +- Files in Safe password can only be deleted directly and cannot be deleted to the recycle bin, so the [**Deletion method**](#remove-way) below has nothing to do with this configuration. + +### Remove way + +**Trash**：Use OpenList to delete files and then move them to the Recycle Bin. If you delete them accidentally, you can restore them through Thunder Cloud Disk. +**Delete**：Deleting it directly cannot restore it. + +### Use video url + +When the `Video URL` option is enabled, it will attempt to replace the original link with the media link returned by the API. Currently, the official platform throttles the download link for **non-members**, but video streaming is not throttled. Therefore, by replacing the link, you can avoid throttling, which applies to both **OpenList** media file downloads and streaming. For regular files, you can also bypass the throttling by renaming the file extension to a media format (e.g., `.mp4`). + +The **Expert Edition** does not enable the `Video URL` option by default, as it is intended for users who configure detailed parameters themselves, and they should be aware of the significance of this option. Hence, it is not enabled by default. For **Xunlei X** users, this option is enabled by default, primarily for the convenience of less experienced users. + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` + +## 6. Thunder Browser Expert + +### username、password + +Mobile phone number, email, username, and password used to log in + +- When filling in the mobile phone number, please bring the `+86` area code, for example `+8613822334455` + +### CaptchaToken + +It will be filled automatically without filling in manually +
+ +### Root folder id + +The default is the full directory of the empty display, If you want to use a subfolder to make the root directory, grab the request to get it + +- In the request in the package`https://x-api-pan.xunlei.com/drive/v1/files?parent_id&page_token&space=`，you can get the following parameters + - `文件夹ID（id）` + - `文件夹名称（name）` + - `父文件夹ID（parent_id）` +- The `folder ID` obtained in the root directory (for example : `来自分享`、`超级保险箱`), **This will change with different account numbers, there is no the same value, In the request in the package** +  + +### Safe password + +Thunder Browser Safe password + +- Files in Safe password can only be deleted directly and cannot be deleted to the recycle bin, so the [**Deletion method**](#remove-way-1) below has nothing to do with this configuration. + +### Remove way + +**Trash**：Use OpenList to delete files and then move them to the Recycle Bin. If you delete them accidentally, you can restore them through Thunder Cloud +**Delete**：Deleting it directly cannot restore it. + +### Login Type + +- `User`: Only fill in the username and password +- `Refresh token`: Just fill in`RefreshToken` + +### Sign Type + +- `Algorithms`：Choose `Algorithms` Just fill in `Algorithms` (It has been automatically filled. You do n’t have to fill in it yourself. You only need to fill in the username and password.When the algorithm is not invalidated) +- `Captcha sign`: Choose `Captcha sign` Just fill in `Captcha sign` and `Timestamp` + +### Part of parameter Packet Capture description + +- `Captcha token`：No need to fill in +- `Device id`：The value calculated by MD5 is used to judge the login device +- `Client id`, `Client secret`, `Client version`, `Package name`：It related to the signature, fill in according to the actual situation + +--- + +- `User agent`：API requests `User agent`, setting errors may not access or speed limit +- `Download user agent`：When downloading, use the `user agent `,If the setting error cannot be downloaded (the agent will use it) + - `User agent` and `Download user agent`：You can fill it out by yourself. If you don’t know how to fill it out, you can leave it blank and it will be automatically filled in. + +--- + +In the request in the package `https://xluser-ssl.xunlei.com/v1/shield/captcha/init`，you can get the following parameters6 + +- `Client id`、`Device id`、`Captcha sign` +- `Package name`、`Client version`、`Timestamp` +  + + In the request in the package `https://xluser-ssl.xunlei.com/v1/auth/signin/token`, you can get the following parameters3 + - `Client id`、`Client secret`、`Refresh token` + +  + +### Use video url + +When the `Video URL` option is enabled, it will attempt to replace the original link with the media link returned by the API. Currently, the official platform throttles the download link for **non-members**, but video streaming is not throttled. Therefore, by replacing the link, you can avoid throttling, which applies to both **OpenList** media file downloads and streaming. For regular files, you can also bypass the throttling by renaming the file extension to a media format (e.g., `.mp4`). + +The **Expert Edition** does not enable the `Video URL` option by default, as it is intended for users who configure detailed parameters themselves, and they should be aware of the significance of this option. Hence, it is not enabled by default. For **Xunlei X** users, this option is enabled by default, primarily for the convenience of less experienced users. + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/uc.md b/pages/en/guide/drivers/uc.md new file mode 100644 index 000000000..7f6cf7d67 --- /dev/null +++ b/pages/en/guide/drivers/uc.md @@ -0,0 +1,85 @@ +--- +top: 683 +categories: + - guide + - drivers +--- + +# UC / TV + + + +## UC Cloud + +**https://drive.uc.cn/** + +### Cookie + +Press F12 to open "Debug", select "Network", select any request on the left, and find the one with the `Cookie` parameter. + + +### Root Folder ID + +Root Folder ID is `0` + +- After entering the folder, get the directory ID in the top address bar. If the subdirectory is deeper, the directory ID will be at the back of the address bar. Just write the subdirectory ID you want to mount. +  + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + c1 + end + c1[local proxy]:::someclass==default===>a2[user equipment] + classDef someclass fill:#f96 + b1[Download proxy URL]-.alternative.->a2[user equipment] + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` + +## UC TV + +The TV version supports `302`, but only `List` and `Download` operations are supported. Other operations are not supported (the interface does not support it). + +### Add method + +1. Select the `UC TV` driver, fill in the mounting path, and then save +2. Return to the all driver page and use the mobile APP to scan the QR code (If the QR code is not displayed, click on `Table Layout` in the upper right corner of the driver to switch from list mode to table mode) +3. After scanning the QR code to confirm, disable the driver, then enable the `driver` to use it. + - `Refresh token`、`Device id`、`Query token`,It will be filled in automatically, no manual filling is required - Please do not edit manually and modify it +  + +### Root Folder ID + +Root Folder ID is `0` + +- After entering the folder, get the directory ID in the top address bar. If the subdirectory is deeper, the directory ID will be at the back of the address bar. Just write the subdirectory ID you want to mount. +  + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/url_tree.md b/pages/en/guide/drivers/url_tree.md new file mode 100644 index 000000000..d53b55613 --- /dev/null +++ b/pages/en/guide/drivers/url_tree.md @@ -0,0 +1,248 @@ +--- +top: 998 +categories: + - guide + - drivers +--- + +# UrlTree + +:::tip +**`地址树-UrlTree`** 是什么? 是用来挂载单个文件链接的，详情可以查看 **→→→[原需求说明](https://github.com/alist-org/alist/issues/3268)←←←** +::: + +## 可写 + +打开后可以对此驱动进行`新建文件夹`、`移动`、`重命名`、`复制`、`删除`、`PutURL` + +- 当用户在实现该接口的驱动中尝试使用SimpleHttp进行离线下载时，将不会调用离线下载工具。 相反，将调用驱动程序的 `PutURL` 方法。 +- **https://github.com/AlistGo/alist/pull/7779** + +
+ +## 用法 + +具体的用法大概讲解一下，建议将下面不同用法都看看越往后越进阶玩法 + +别看写的看起来很难很啰嗦实际上自己操作一下秒懂。 + +1. 最简单的用法，直接写链接即可 + +**输入** + +``` +http://pic.rmb.bdstatic.com/bjh/aff9c9c8817d943d6857a73188958d45.jpeg +https://raw.githubusercontent.com/OpenListTeam/OpenList/main/README_cn.md +``` + +**输出** + +``` +│ aff9c9c8817d943d6857a73188958d45.jpeg +│ README_cn.md +``` + +2. 有文件的同时，也可以创建文件夹第一个代码示例，也可以创建多个文件夹第二个代码示例 + +**输入** + +``` +http://pic.rmb.bdstatic.com/bjh/aff9c9c8817d943d6857a73188958d45.jpeg +folder: + http://pic.rmb.bdstatic.com/bjh/aff9c9c8817d943d6857a73188958d45.jpeg + https://raw.githubusercontent.com/OpenListTeam/OpenList/main/README_cn.md +``` + +``` +http://pic.rmb.bdstatic.com/bjh/aff9c9c8817d943d6857a73188958d45.jpeg +folder: + http://pic.rmb.bdstatic.com/bjh/aff9c9c8817d943d6857a73188958d45.jpeg + https://raw.githubusercontent.com/OpenListTeam/OpenList/main/README_cn.md +http://pic.rmb.bdstatic.com/bjh/a66923e9bfefd03c2998ee998d3b55e7.jpeg +folder2: + http://pic.rmb.bdstatic.com/bjh/e919290bf3b8396817d369cedf33b8cd.jpeg + https://raw.githubusercontent.com/OpenListTeam/OpenList/main/CONTRIBUTING.md +``` + +**输出** + +``` +│ aff9c9c8817d943d6857a73188958d45.jpeg +└─folder + aff9c9c8817d943d6857a73188958d45.jpeg + README_cn.md +``` + +``` +│ aff9c9c8817d943d6857a73188958d45.jpeg +├─folder +│ aff9c9c8817d943d6857a73188958d45.jpeg +│ README_cn.md +│ +├─ a66923e9bfefd03c2998ee998d3b55e7.jpeg +│ +└─folder2 + CONTRIBUTING.md + e919290bf3b8396817d369cedf33b8cd.jpeg +``` + +开头要空两个空格~ + +3. 可以将文件资源二次命名，实际上下载的还是原来的，并且可以填写文件大小 + +格式：`新命名的名字.后缀:文件大小:链接.后缀` + +``` +新名称.jpeg:1024:http://pic.rmb.bdstatic.com/bjh/aff9c9c8817d943d6857a73188958d45.jpeg +新名称2.md:2048:https://raw.githubusercontent.com/OpenListTeam/OpenList/main/README_cn.md +``` + +文件大小不用写也是可以重新命名的 + +``` +新名称.jpeg:http://pic.rmb.bdstatic.com/bjh/aff9c9c8817d943d6857a73188958d45.jpeg +新名称2.md:https://raw.githubusercontent.com/OpenListTeam/OpenList/main/README_cn.md +``` + +@tab 4 + +4. 多个层级目录套娃玩法 + +- 第一层目录文件夹不需要空格，但是第一层目录里面的文件需要空两个空格 + +``` +folder: + http://pic.rmb.bdstatic.com/bjh/aff9c9c8817d943d6857a73188958d45.jpeg + https://raw.githubusercontent.com/OpenListTeam/OpenList/main/README_cn.md +``` + +- 如果你写好第一层了还想在第一个文件夹里面再套一个那就在这个文件夹下面套一层，写法如下，很简单 + - 目录进行空两格，文件加两个空格就是四个，如果继续想往下套一层继续加2个空格即可 + +``` +folder11: + http://pic.rmb.bdstatic.com/bjh/111.jpeg + folder111: + http://pic.rmb.bdstatic.com/bjh/111.jpeg + folder1111: + http://pic.rmb.bdstatic.com/bjh/111.jpeg + folder222: + http://pic.rmb.bdstatic.com/bjh/222.jpeg + folder2222: + http://pic.rmb.bdstatic.com/bjh/222.jpeg +folder22: + http://pic.rmb.bdstatic.com/bjh/222.jpeg + folder222: + http://pic.rmb.bdstatic.com/bjh/222.jpeg + folder2222: + http://pic.rmb.bdstatic.com/bjh/2223.jpeg +folder33: + http://pic.rmb.bdstatic.com/bjh/333.jpeg + folder333: + http://pic.rmb.bdstatic.com/bjh/333.jpeg + folder3333: + http://pic.rmb.bdstatic.com/bjh/333.jpeg +``` + +- 不建议的写法，像 **`2.jpeg，5.jpeg`** 这样写法，建议想往哪一层文件夹就去哪一层文件夹按照格式增加链接，不要像下面这样写 + +**错误写法** + +``` +folder22: + http://pic.rmb.bdstatic.com/bjh/222.jpeg + folder222: + http://pic.rmb.bdstatic.com/bjh/222.jpeg + folder2222: + http://pic.rmb.bdstatic.com/bjh/2222.jpeg + folder22222: + http://pic.rmb.bdstatic.com/bjh/2222.jpeg + folder222222: + http://pic.rmb.bdstatic.com/bjh/2222.jpeg + http://pic.rmb.bdstatic.com/bjh/2.jpeg + http://pic.rmb.bdstatic.com/bjh/5.jpeg +``` + +**正确写法** + +像 **`2.jpeg，5.jpeg`** 这样文件添加时候，添加到对应的目录里面去，分别对应的是 `folder222 和 folder22222` 两个文件夹 + +``` +folder22: + http://pic.rmb.bdstatic.com/bjh/222.jpeg + folder222: + http://pic.rmb.bdstatic.com/bjh/222.jpeg + http://pic.rmb.bdstatic.com/bjh/2.jpeg + folder2222: + http://pic.rmb.bdstatic.com/bjh/2222.jpeg + folder22222: + http://pic.rmb.bdstatic.com/bjh/2222.jpeg + http://pic.rmb.bdstatic.com/bjh/5.jpeg + folder222222: + http://pic.rmb.bdstatic.com/bjh/2222.jpeg +``` + +5. 全部整合起来的举例用法，有常规的，有分类，有重命名，有标注文件大小 + +``` +https://jsd.example.com/gh/OpenListTeam/OpenList/README.md +文档: + Readme.md:https://pic.rmb.bdstatic.com/bjh/说明.md + Doc: + 文档.doc:https://pic.rmb.bdstatic.com/bjh/测试文档.doc + pdf: + pdf2.pdf:https://pic.rmb.bdstatic.com/bjh/测试.pdf + Excel: + 表格3.xlsx:https://pic.rmb.bdstatic.com/bjh/测试表格.xlsx +视频: + https://pic.rmb.bdstatic.com/bjh/222.jpeg + 电视剧: + https://pic.rmb.bdstatic.com/bjh/222.pm4 + 电影: + https://pic.rmb.bdstatic.com/bjh/222.flv +音乐: + https://pic.rmb.bdstatic.com/bjh/222.jpeg + 古典: + https://pic.rmb.bdstatic.com/bjh/222.mp3 + 轻音乐: + https://pic.rmb.bdstatic.com/bjh/222.flac + https://pic.rmb.bdstatic.com/bjh/222.wav +软件: + https://pic.rmb.bdstatic.com/bjh/222.jpeg + PJ: + xx软件.exe:252525:https://pic.rmb.bdstatic.com/bjh/222.exe + xx安装包.zip:259555:https://pic.rmb.bdstatic.com/bjh/222.zip + IPA: + GPT.ipa:https://pic.rmb.bdstatic.com/bjh/222.ipa + APK: + P图.apk:https://pic.rmb.bdstatic.com/bjh/222.apk +``` + +## 提示 + +1. 如果你点击下载发现没有跳转到下载而是预览，这是因为是根据你原本链接来决定的,例如你原本的链接就是下载他就会跳转到下载 +2. 如果你一个文件夹内有相同的文件，会合并只显示一个，默认使用预览查看下载的是你靠上(前)也就是顶部的文件 + - Tips:请勿同时在一个目录内新建两个同名的文件/夹哦~就像你在资源管理器新建两个一样的文件/夹 都会提醒你不能重复 +3. 如果你在添加时在同级目录下写了两个相同的文件夹名字，会合并成一个文件夹但是合并后靠后(下)的文件夹的文件不会显示，但是可以通过浏览器地址栏访问（参考上一条的提示） +4. 排序默认是按照你填写从上到下依次排序的和 `OpenList-别名`的一样 + +### 默认使用的下载方式 + +```mermaid +--- +title: 默认使用的哪种下载方式？ +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|默认|a2[用户设备] + classDef someclass fill:#f96 + c1[本机代理]-.备选.->a2[用户设备] + b1[代理URL]-.备选.->a2[用户设备] + click a1 "../drivers/common.html#webdav-策略" + click b1 "../drivers/common.html#webdav-策略" + click c1 "../drivers/common.html#webdav-策略" +``` diff --git a/pages/en/guide/drivers/uss.md b/pages/en/guide/drivers/uss.md new file mode 100644 index 000000000..33fc787f6 --- /dev/null +++ b/pages/en/guide/drivers/uss.md @@ -0,0 +1,77 @@ +--- +top: 894 +categories: + - guide + - drivers +--- + +# UPYUN Storage Service + +::: tip +When using the **302 redirect** strategy, the `_upd` and `_upt` parameters are automatically appended to the URL. If **"Parameter Follow"** is enabled in the Upyun console, the CDN nodes will treat these parameters as part of the file path, resulting in a **404 Not Found** error for existing files. + +Solutions: + +- Method 1: In the Upyun console, under **"Cache Control"**, change **"Parameter Follow"** to **"Parameter Not Follow"**. + +- Method 2: Set the WebDAV policy of OpenList to **"Local Proxy"**. This mode avoids appending interfering parameters but will increase the server's data transfer. + ::: + +UPYUN Storage Service，refer to as USS，[**Yupyun USS Official Website**](https://console.upyun.com/services/file/) + +### BucKet + +UPYUN Storage Service Name + +### Endpoint + +Accelerated domain name (default TEST domain or bound domain, not CNAME domain) +If you use http protocol, please add `http://` protocol header. +The test domain name provided by upyun is not accessible in some network and does not support https, so it is recommended to use your own bound domain name. + +### Operator name + +Operator name + +### Operator password + +Operator password + +### Root folder path + +Root path, if not filled, it defaults to the root directory. + +### Sign url expire + +The validity period of the signed download address is 4 hours by default. + +## Example of filling in details + +::: tip +If you want to use the official test domain name, you must manually add http For example: http://xxx.test.upcdn.net +If you want to use HTTPS, of course, you can also add your own domain name, for example: https://you.xxx.com +permission is turned on by itself, and the read permission must be turned on！ +::: + + + +### The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[302]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[local proxy]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/webdav.md b/pages/en/guide/drivers/webdav.md new file mode 100644 index 000000000..ccfa381dd --- /dev/null +++ b/pages/en/guide/drivers/webdav.md @@ -0,0 +1,85 @@ +--- +top: 899 +categories: + - guide + - drivers +--- + +# WebDav + +## Address + +WebDAV root address + +## Username + +username + +## Password + +password + +## Root folder path + +The path of fodler you want to mount, same as join in address + +## Tls insecure skip verify + +Whether to skip SSL certificate verification. If your WebDAV server uses a self-signed certificate, you may need to enable this option. Enabling it will reduce security, please use it with caution. + +## Support 302 redirect + +In general, WebDAV servers return the file content directly. Due to the need for authorization, only proxy downloads are possible. However, some servers redirect to the actual file address, such as OpenList `WebDav Policy`'s `302 Redirect`. + +The `Web Proxy` option in WebDAV storage settings is enabled by default. If disabled, OpenList will attempt to obtain the redirected address and return it to the user device for direct download. + +Prerequisites: + +1. The WebDAV server must support returning 302; if it returns 200, this feature cannot be used, and disabling Web Proxy will make it unusable. +2. The returned 302 address must be publicly accessible and must not require authorization information; otherwise, the user device cannot download it. +3. Disable the `Web Proxy` option in the storage settings. + +## OneDrive/SharePoint + +Select the vendor as sharepoint, and support the international version/21Vianet. + +For OneDrive/SharePoint, you can obtain the WebDAV root address through [this tool](https://tool.example.com/onedrive/webdav). If you want to mount the specified directory, you can join it later. + +The username is the OneDrive account email, and the password is the OneDrive account password. + +## Error message + +- **failed get objs: failed to list objs: PROPFIND/根目录：403** + + Need to log in to [Entra ID](https://entra.microsoft.com/#view/Microsoft_AAD_IAM/TenantOverview.ReactView?Microsoft_AAD_IAM_legacyAADRedirect=true) + + Find 'Manage Security Default' and click to disable it(❗ Note: Closing this option will disable the Authenticator verification for the domain) + +  + + Another situation is that the corresponding OneDrive account has not been used for a long time, which will also prompt this problem. Try to log in to the account again from the OneDrive web page. The system will prompt you to change the password. After updating the password, try again with the changed password. + +- **failed link: failed get link: redirect failed, status: 200** + + This error indicates that the WebDAV server does not support 302 redirects. You need to enable the `Web Proxy` option in the storage settings to use proxy downloads. + +## The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + a1 + end + a1[local proxy]:::someclass====|default|a2[user equipment] + classDef someclass fill:#f96 + c1[302]-.alternative.->a2[user equipment] + b1[Download proxy URL]-.alternative.->a2[user equipment] + click a1 "../drivers/common.html#webdav-policy" + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/weiyun.md b/pages/en/guide/drivers/weiyun.md new file mode 100644 index 000000000..b3db39498 --- /dev/null +++ b/pages/en/guide/drivers/weiyun.md @@ -0,0 +1,60 @@ +--- +top: 682 +categories: + - guide + - drivers +--- + +# Tencent weiyun + + + +Tencent Weiyun official website: **https://www.weiyun.com** + +::: tip Weiyun login validity period reminder + +- QQ: The login can only keep alive for 48 hours at present, and the cookie has to be replaced +- WeChat: no such problem, use token + It is recommended to use WeChat to log in + +::: + +## Root folder file_id + +1. Display the root directory, **`leave blank`**, you don’t need to fill in, the program will automatically fill in +2. If only a single folder ID is displayed, select the folder to be displayed, Copy the ID behind the top address bar + +  + +## Cookie + +After logging in to Weiyun, **Open the developer debugging tool (F12)**, find the request that carries the cookie in any request, copy and fill in it. + +- The token obtained by WeChat login is longer than the cookie field of QQ login +- QQ WeChat fills in the `Cookie` field value, and you can see it by just looking for a request + +  + +## Other notes + +1. The copy function cannot be used +2. **It is recommended not to share Weiyun with the outside world. After all, it is bound to your own QQ number. If you have a major loss to QQ or other things after being blocked/frozen, you will be responsible for the consequences** + +## The default download method used + +```mermaid +--- +title: Which download method is used by default? +--- +flowchart TB + style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff + style a2 fill:#ff7575,stroke:#333,stroke-width:4px + subgraph ide1 [ ] + c1 + end + c1[local proxy]:::someclass==default===>a2[user equipment] + classDef someclass fill:#f96 + b1[Download proxy URL]-.alternative.->a2[user equipment] + click b1 "../drivers/common.html#webdav-policy" + click c1 "../drivers/common.html#webdav-policy" +``` diff --git a/pages/en/guide/drivers/wopan.md b/pages/en/guide/drivers/wopan.md new file mode 100644 index 000000000..018be2240 --- /dev/null +++ b/pages/en/guide/drivers/wopan.md @@ -0,0 +1,78 @@ +--- +top: 693 +categories: + - guide + - drivers +--- + +# WoPan + + + +[https://pan.wo.cn/](https://pan.wo.cn/) + +## GetToken + +::: tip +The difference between the two token acquisition methods: + +- Method 1: **Token valid for seven days** Logging in to the web version of China Unicom Cloud Drive will disconnect and invalidate the mount point on OpenList's side. However, logging in to the mobile version is fine, and thereby you can have both open simultaneously. + +- Method 2: **Token valid for two months** There isn't any problem to log into the Unicom Cloud Drive. However, it will be kicked off if you log in on the mobile side. + +::: + +### Method 1 + +1. Open developer tools +2. Open the official website
-
-
-
-:::
-
-::: zh-CN
+### 使用方法
1. 在列表右键选择需要传输的文件点击复制，然后选择传输到那个文件夹就可以，
2. 如果是多个文件可以选择整个文件夹或者右下角打开复选框多选文件，然后最底部有一排按钮可以点击复制
+
-
-
`https://your.openlist.domain/api/auth/sso_callback?method=sso_get_token`
`https://your.openlist.domain/api/auth/sso_get_token`
`https://your.openlist.domain/api/auth/get_sso_id` - Valid post logout redirect URIs|留空 - Web origins |留空 - ::: - ::: en - ::: details see the details - |Name|Value| - -|---- - Root URL |Leave blank - Home URL |Enter your OpenList access address, e.g.: https://your.openlist.domain - Valid redirect URIs|`https://your.openlist.domain/api/auth/sso_callback?method=get_sso_id`
`https://your.openlist.domain/api/auth/sso_callback?method=sso_get_token`
`https://your.openlist.domain/api/auth/sso_get_token`
`https://your.openlist.domain/api/auth/get_sso_id` - Valid post logout redirect URIs|Leave blank - Web origins |Leave blank + | 配置名 | 配置值 | + | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | + | Root URL | 留空 | + | Home URL | 填入你OpenList的访问地址，如：https://your.openlist.domain | + | Valid redirect URIs | `https://your.openlist.domain/api/auth/sso_callback?method=get_sso_id`
`https://your.openlist.domain/api/auth/sso_callback?method=sso_get_token`
`https://your.openlist.domain/api/auth/sso_get_token`
`https://your.openlist.domain/api/auth/get_sso_id` | + | Valid post logout redirect URIs | 留空 | + | Web origins | 留空 | ::: -##### 3.7.1.3. 获取JWT公钥 { lang="zh-CN" } - -##### 3.7.1.3. Retrieve JWT public key { lang="en" } - -::: zh-CN +##### 3.7.1.3. 获取JWT公钥 - 在左侧找到 `Clients`，选择刚创建的 Client 进入设置页面。 - 在 Client 设置页面，切换到 `Keys` 选项卡。 - 在 `Public Key` 字段中复制公钥内容，稍后在 OpenList 配置中使用。 - 如果没有看到公钥，可以点击 `Generate RSA Keys` 生成 -::: -::: en - -- In the left menu, find `Clients`, select the newly created Client to enter the settings page. -- In the Client settings page, switch to the `Keys` tab. -- Copy the content in the `Public Key` field for later use in OpenList configuration. -- If the public key is not visible, click `Generate RSA Keys` to generate it. - -::: - -##### 3.7.1.4. 获取Client Secret { lang="zh-CN" } - -##### 3.7.1.4. Retrieve Client Secret { lang="en" } - -::: zh-CN +##### 3.7.1.4. 获取Client Secret - 在 Client 设置页面，切换到 `Credentials` 选项卡。 - 在 `Client Secret` 字段中复制客户端密钥内容，稍后在 OpenList 配置中使用。 -::: -::: en - -- In the Client settings page, switch to the `Credentials` tab. -- Copy the content in the `Client Secret` field for later use in OpenList configuration. - -::: +#### 3.7.2. OpenList 设置 -#### 3.7.2. OpenList 设置 { lang="zh-CN" } - -#### 3.7.2. OpenList Setup { lang="en" } - -::: zh-CN 在 OpenList 的单点登录配置填写如下参数： - **启用 SSO 登录**：`是` @@ -176,24 +89,3 @@ After selecting the realm, click `Clients` → `Create Client`. 如有特殊需求，根据实际 Keycloak 部署调整 claims 和端点。 详细操作请参考 [Keycloak 官方 OIDC 文档](https://www.keycloak.org/documentation)。 - -::: - -::: en -Fill in the following parameters in OpenList's SSO configuration: - -- **SSO login enabled:** `yes` -- **SSO login platform:** `OIDC` -- **SSO client id:** Keycloak Client ID (from [Create Client](#_3-7-1-2-create-client) above) -- **SSO client secret:** Keycloak Client Secret (from [Retrieve Client Secret](#_3-7-1-4-retrieve-client-secret) above) -- **SSO oidc username key:** `preferred_username` or as per your Mapper settings -- **SSO organization name:** `master` (from [Create Realm](#_3-7-1-1-create-realm) above) -- **SSO application name:** `OpenList` (from [Create Client](#_3-7-1-2-create-client) above) -- **SSO endpoint name:** `https://your.keycloak.domain/realms/{realm-name}` (where realm-name matches the organization name) -- **SSO jwt public key:** from [Retrieve JWT public key](#_3-7-1-3-retrieve-jwt-public-key) above -- **SSO auto register as OpenList account:** Enable as needed -- **SSO compatibility mode:** `no` (enable if compatibility is required) - -Adjust claims and endpoints based on your specific Keycloak deployment if needed. -For detailed operations, refer to the [Keycloak official OIDC documentation](https://www.keycloak.org/documentation). -::: diff --git a/pages/guide/advanced/strm.md b/pages/guide/advanced/strm.md index 582af8c29..ac54765d9 100644 --- a/pages/guide/advanced/strm.md +++ b/pages/guide/advanced/strm.md @@ -1,11 +1,10 @@ --- -title: - en: Generate Strm - zh-CN: 生成 strm categories: - guide - advanced top: 10 --- +# 生成 strm + diff --git a/pages/guide/advanced/user.md b/pages/guide/advanced/user.md index f4093073b..9b3a99595 100644 --- a/pages/guide/advanced/user.md +++ b/pages/guide/advanced/user.md @@ -1,53 +1,24 @@ --- -title: - en: User - zh-CN: 用户 categories: - guide - advanced top: 140 --- -## Add user { lang="en" } +# 用户 -## 添加用户 { lang="zh-CN" } +## 添加用户 -::: en -::: warning Security Notice -Adding a user may expose files and server-side capabilities to another account. Use a strong, unique password, grant only the minimum required permissions, and create accounts only for trusted users. Security incidents resulting from improper user or permission management are the administrator's responsibility. -::: -::: zh-CN ::: warning 安全提醒 添加用户可能会使其他账户获得文件和服务器侧功能的访问能力。请使用强且唯一的密码，仅授予必要的最小权限，并仅为可信用户创建账户。因用户或权限管理不当而导致的安全事件，由管理员用户承担责任。 ::: -## Username { lang="en" } - -## 用户名 { lang="zh-CN" } +## 用户名 -::: en -Username for login. -::: -::: zh-CN 登录用户名。 -::: - -## Password { lang="en" } - -## 密码 { lang="zh-CN" } - -::: en -Password for login. -:::tip -Password is invalid for guest user. - -If you enter an incorrect password 6 times in a row, the current IP will be blocked for 30 minutes and you will not be able to enter your account and password to log in. However, it will not affect other IPs. It will only target IPs that entered 6 incorrect passwords. -- Restarting will immediately remove the 30-minute ban time +## 密码 -::: - -::: zh-CN 登录密码。 :::tip 密码对游客是无效的。 @@ -58,53 +29,15 @@ If you enter an incorrect password 6 times in a row, the current IP will be bloc ::: -## Base path { lang="en" } - -## 基本路径 { lang="zh-CN" } - -::: en -The root path that users see when he/she log in. +## 基本路径 -Q: **How to allow a user to see multiple folder paths?** - -A: You can create a new [alias](alias.md) storage, add all the paths you need to show the user to the alias, and then point to the newly created alias storage in the user path -::: -::: zh-CN 用户登录时看到的根路径。 Q：**如何否允许一个用户可以看到多个文件夹路径?** A：可以新建一个[别名](alias.md)存储,将你需要给用户展示的路径都添加到别名，然后在用户路径这里指向新建的别名存储。 -::: - -## Permission { lang="en" } - -## 权限 { lang="zh-CN" } - -::: en - -- Can see hides: Can see the hides files and folders -- Access without password: Can access without password -- Add offline download tasks: Add offline download tasks - - ⚠️ Granting a user remote file read/write permissions also grants them the ability to access resources from the server's network context, including internal network addresses. Only grant this permission to fully trusted users. Internal network access resulting from improper permission assignment is not considered a security vulnerability. -- Mkdir or upload: Can make directory or upload files -- Rename: Can rename files and folders -- Move: Can move files and folders -- Copy: Can copy files and folders -- Delete: Can delete files and folders -- Webdav read: Can read files and folders with webdav -- Webdav manage: Can manage files and folders with webdav -- FTP read: Can read files and folders with FTP -- FTP manage: Can manage files and folders with FTP -- Read archives: Read the contents of the file in the compressed package - - After turning on this option, compressed package format files will be previewed by default (as shown in the figure below), which will consume some server traffic, but will not download them all. - - If you want to turn off the preferred preview of the compressed format, **Manage => Setting => Preview by default when opening archives**, this option is turned off, and the preference is the download mode -- Decompress: Decompress compressed package files online -  -  -::: -::: zh-CN +## 权限 - 可以看到隐藏：可以看到隐藏的文件和文件夹 - 无密码访问：无需密码即可访问 @@ -126,37 +59,11 @@ A：可以新建一个[别名](alias.md)存储,将你需要给用户展示的路   -::: - -## Disabled { lang="en" } +## 停用 -## 停用 { lang="zh-CN" } - -::: en -After checking, this user will stop using it and cannot log in. The guest account is disabled by default. If you want to enable the guest account, please close it manually. -::: -::: zh-CN 勾选后将停止使用此用户，无法登陆，游客账户默认停用，如果要启用游客账户请手动关闭停用。 -::: - -## Tips { lang="en" } -## Tips { lang="zh-CN" } - -::: en - -1. Are you worried that visitors can see all files? [**Click to see how to set it up here**](../../faq/why.md#how-do-i-set-it-so-that-visitors-can-only-see-the-content-after-logging-in) -2. **`Guest user is disabled, login please`**: In order to protect your OpenList security, the guest access permission is closed, if you need guest access, open it yourself - - OpenList Manage --> users --> `guest` --> **Disable** uncheck -3. Question about **`Copy/Upload`** - - If you upload (including offline download and upload) large files, or upload a lot of files (hundreds or thousands), it is not recommended to use OpenList to operate, please go to the corresponding network disk official website to operate directly -4. Non-admin users can manage offline download, copy, upload and other operations in the background - - OpenList needs to be upgraded to
@@ -324,8 +143,6 @@ The interfaces of different software vary, but the key is to correctly fill in t
-### Synology NAS (Add via File Station) { lang="en"}
-
-### 群晖 NAS (通过 File Station 添加) { lang="zh-CN" }
+### 群晖 NAS (通过 File Station 添加)
diff --git a/pages/guide/drivers/115.md b/pages/guide/drivers/115.md
index a62ab9c67..eaf61a63f 100644
--- a/pages/guide/drivers/115.md
+++ b/pages/guide/drivers/115.md
@@ -1,35 +1,22 @@
---
-title:
- en: 115 Cloud / Share
- zh-CN: 115 网盘 / 分享
-# This is the icon of the page
-icon: iconfont icon-state
-# This control sidebar order
top: 697
-# A page can have multiple categories
categories:
- guide
- drivers
---
+# 115 网盘 / 分享
+
-::: zh-CN
::: tip
[**115 官方 Open API**](115_open.md)
:::
-::: en
-::: tip
-[**115 Official Open API**](115_open.md)
-:::
-## 115 Cloud { lang="en" }
+## 115 个人网盘
-## 115 个人网盘 { lang="zh-CN" }
+### 视频教程(优先选择文字教程)
-### 视频教程(优先选择文字教程) { lang="zh-CN" }
-
-::: zh-CN
视频教程有可能因为时间关系导致部分视频内功能不可用或产生变化
所以推荐优先选择文字教程，当然如果你看不懂文字教程或者嫌麻烦也可以观看视频教程
@@ -38,48 +25,16 @@ categories:
-#### 3. 使用 Python 脚本获取 Cookie { lang="zh-CN" } - -#### 3. Get Cookies Using Python Script { lang="en" } +#### 3. 使用 Python 脚本获取 Cookie -::: en -Expand the detailed description to view the tutorial and script source code - -Source code from：[**https://gist.github.com/ChenyangGao/d26a592a0aeb13465511c885d5c7ad61**](https://gist.github.com/ChenyangGao/d26a592a0aeb13465511c885d5c7ad61) -::: - -::: zh-CN 展开详细说明进行查看教程和脚本源码 源码来自：[**https://gist.github.com/ChenyangGao/d26a592a0aeb13465511c885d5c7ad61**](https://gist.github.com/ChenyangGao/d26a592a0aeb13465511c885d5c7ad61) -::: ::: details View source @@ -318,32 +240,6 @@ if __name__ == "__main__": ::: -::: en - -1. You need to install [**Python 3.11.x**](https://www.python.org/downloads/) or above -2. If the QR code cannot be displayed properly in the `CMD` and `powershell` terminals, you can use the `-o` parameter to generate an image to scan the code, or you need to install an additional terminal - 1. Use the `-o` parameter to generate the image method and scan the QR code to confirm - - ````python - python main.py wechatmini -o - ``` - The devices that can be obtained are as follows. If you do not fill in the device, the default device on the `Web` side will be used - `Web`，`android`，`ios`，~~`linux`，`mac`，`windows`~~，`tv`，`alipaymini`，`wechatmini`，`qandroid` - ```` - - `alipaymini` and `wechatmini` They are Alipay Mini Program and WeChat Mini Program. - - **Windows、Mac、Linux should not be able to use it anymore. The official client was recently removed from the shelves.** - - It is recommended to use some devices that you do not commonly use, otherwise logging in will crowd out the previous ones. - *** - 2. Additional installation terminal - - Windows Store：**https://apps.microsoft.com/detail/9n0dx20hk701?rtc=1&hl=zh-cn&gl=CN** - - GitHub Download：**https://github.com/microsoft/terminal/releases** - 3. Other ways, solve it yourself - ---- - -Execute the command and obtain the QR code. Scan the QR code on the APP to obtain `Cookie` - -::: zh-CN - 1. 需要安装 [**Python 3.11.x**](https://www.python.org/downloads/) 以上版本 2. 如果二维码在 `CMD` 和 `powershell` 两个终端无法显示正常，可以使用`-o`参数生成图片的方式来扫码，或者需要额外安装一个终端 1. 使用 `-o` 参数，生成图片方式然后扫码确认 @@ -365,11 +261,8 @@ Execute the command and obtain the QR code. Scan the QR code on the APP to obtai --- 执行命令，获取二维码 APP扫码获取 `Cookie` -::: - -##### 3.1. Direct Execution { lang="en" } -##### 3.1.直接执行 { lang="zh-CN" } +##### 3.1.直接执行 ```shell PS C:\Users\233\Desktop\115> python --version @@ -391,16 +284,9 @@ PS C:\Users\233\Desktop\115> python main.py wechatmini ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ ``` -::: en -Execute the command directly. The QR code will appear in the terminal for display. -::: -::: zh-CN 直接执行 二维码会出现在终端中进行显示 -::: - -##### 3.2. Using the -o parameter { lang="en" } -##### 3.2. 使用-o参数 { lang="zh-CN" } +##### 3.2. 使用-o参数 ```bash PS C:\Users\233\Desktop\115> python --version @@ -408,29 +294,9 @@ Python 3.12.2 PS C:\Users\233\Desktop\115> python main.py wechatmini -o ``` -::: en -After using the `-o` parameter, a QR code image will pop up automatically -::: - -::: zh-CN 使用 `-o` 参数后会自动弹出一张二维码图片 -::: - -### 秒传 { lang="zh-CN" } - -### Rapid upload { lang="en" } - -::: en -- **v.3.27.0** version Enhanced Rapid upload: You can directly upload files with `Alibaba Cloud Disk Open` by copying - - The premise is to upload the file from 115 Rapid upload to Alibaba Cloud Disk Open, the file already exists in Alibaba Cloud Disk Open, otherwise it is a normal copy task. - - If you want to transfer 115 cloud disk files to Alibaba Cloud Disk in seconds, you need to turn on the Rapid upload option of Alibaba Cloud Disk, otherwise it will be uploaded in normal mode. - If you want to upload files using Miaochuan, it is recommended to build an OpenList locally on your home computer and add a `local storage` and `115 cloud disk` to copy Miaochuan to save resources. -
- -::: - -::: zh-CN +### 秒传 - **v.3.27.0** 版本 增强秒传：可以直接通过复制方式来和`阿里云盘Open`进行相互秒传文件 - 前提是要从115秒传到阿里云盘Open的文件，阿里云盘Open已经存在，否则就是正常复制任务。 @@ -438,29 +304,8 @@ After using the `-o` parameter, a QR code image will pop up automatically 如果要使用秒传来上传文件建议在自己家用电脑本地搭建一个OpenList添加一个`本地存储`和`115云盘`进行复制秒传这样节省资源。
-::: +### 离线下载 -### 离线下载 { lang="zh-CN" } - -### Offline Download { lang="en" } - -::: en -**v3.37.0** and above versions support calling `115 Cloud` offline download function in OpenList -Select in the lower right corner and select `115 Cloud` for offline download options - -- Support: `magnet`, `http`, `ed2k` links - Only 115 Cloud is supported for offline download. If it is not 115 Cloud, the following error message will be displayed, Although the offline download prompt was successfully added, an error will be prompted in the background. -- unsupported storage driver for offline download, only 115 Cloud is supported -  -- Some tips for using 115 offline downloads: - 1. Out of sync problems may occur (manual refresh in the lower right corner ) - 2. Currently, when the download is successful, completed tasks in the offline list are deleted. - 3. 115 Task URLs that are already in the offline list cannot be added again. -
- -::: - -::: zh-CN **v3.37.0** 及以上版本支持在OpenList调用115离线下载功能 右下角选择 离线下载选项选择`115 Cloud` @@ -474,35 +319,7 @@ Select -::: - -### 默认使用的下载方式 { lang="zh-CN" } - -### The default download method used { lang="en" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -523,86 +340,32 @@ flowchart TB click c1 "../drivers/common.html#webdav-策略" ``` -::: +## 115网盘分享 -## 115 Share { lang="en" } - -## 115网盘分享 { lang="zh-CN" } - -::: zh-CN  `分享链接ID`1 和 `分享链接提取码`2 分别如何获取一目了然 -::: -::: en - - -`Sharing link ID`1 and `Sharing link extraction code`2 How to obtain them respectively is clear at a glance. -::: - -### Root folder ID { lang="en" } - -### 根文件夹ID { lang="zh-CN" } - -::: en -The default is empty and the entire directory file is mounted. - -The folder IDs are the root folder ID and the subfolder ID respectively. The following demonstrates how to obtain the `shared root folder directory ID`1 and `other subfolder directory ID`2 respectively. -::: - -#### 1. shared root folder directory ID { lang="en" } - -#### 1. 分享根文件夹目录ID {lang="zh-CN"} +### 根文件夹ID -::: en -Open developer mode (F12) and clear all requests first. Before we enter the folder, clear all requests first. +#### 1. 分享根文件夹目录ID -Let's click on the root folder to enter. There will be a new request on the right, and then select `Load` to see the ID (cid) of our folder. - - -::: -::: zh-CN 打开开发者模式(F12)先将请求全部清空，我们进入文件夹，先将全部请求清空， 我们再点击根文件夹进入，右侧会有一个新的请求，然后选择`载荷`就能看到我们的这个文件夹的ID (cid)  -::: - -#### 2. other subfolder directory ID { lang="en" } -#### 2. 其它子文件夹目录ID { lang="zh-CN" } +#### 2. 其它子文件夹目录ID -::: zh-CN 打开开发者模式(F12)先将请求全部清空，我们进入文件夹，先将全部请求清空， 右侧会有一个新的请求，然后选择`预览` 然后进行展开查看，就可以看到其它子文件夹的ID (cid)  -::: -::: en -Open developer mode (F12) and clear all requests first. Before we enter the folder, clear all requests first. - -There will be a new request on the right, then select `Preview` and expand it to see the IDs (cid) of other subfolders. - - -::: -### 错误提示 { lang="zh-CN" } +### 错误提示 -### Error Tips { lang="en" } - -::: en -For example, the 115 sharing link shown in the picture below has expired, but the sharing link can still be opened. - - - -But when adding and saving, the following error code will appear: - -`Failed init storage but storage is already created: failed init storage: failed to get share snap: json: cannot unmarshal number into Go struct field .data.shareinfo.share_state of type string ` -::: -::: zh-CN 例如下图所示的115分享链接分享过期，但是分享链接还能打开  @@ -610,36 +373,8 @@ But when adding and saving, the following error code will appear: 但是在添加保存时候会出现如下错误码： `Failed init storage but storage is already created: failed init storage: failed to get share snap: json: cannot unmarshal number into Go struct field .data.shareinfo.share_state of type string ` -::: - -### 默认使用的下载方式 { lang="zh-CN" } -### The default download method used { lang="en" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: - -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -659,5 +394,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/115_open.md b/pages/guide/drivers/115_open.md index b92320c94..bb8a531e7 100644 --- a/pages/guide/drivers/115_open.md +++ b/pages/guide/drivers/115_open.md @@ -1,122 +1,37 @@ --- -title: - en: 115 Open - zh-CN: 115 开放平台 -# This is the icon of the page -icon: iconfont icon-state -# This control sidebar order top: 698 -# A page can have multiple categories categories: - guide - drivers --- -::: en -::: tip -Developed with the official [**115 Open Platform API**](https://open.115.com) -::: -::: zh-CN +# 115 开放平台 + ::: tip 使用官方 [**115开放平台 API**](https://open.115.com) 开发 ::: -## 1. Necessary Conditions { lang="en" } - -## 1. 必要条件 { lang="zh-CN" } +## 1. 必要条件 -::: en -An **115** account is required. -::: -::: en -::: warning Note -The speed and stability are related to the local network environment, the network environment of the 115 server, and the performance of the machine running OpenList. -::: - -::: zh-CN 必须有 **115** 的帐号 -::: -::: zh-CN + ::: warning 注意事项 速度与稳定性与本地网络环境，115 服务器的网络环境以及 OpenList 的运行机器的性能有关 ::: -## 2. Preparation for Access { lang="en" } - -## 2. 准备接入 { lang="zh-CN" } +## 2. 准备接入 -### 2.1. Register an Application on the Open Platform (optional; no need to create if using the built-in key pair of OpenList/public welfare server/self-built server) { lang="en" } +### 2.1. 开放平台注册应用（可选，如果使用OpenList/公益服务器/自建服务器内置的密钥对，则不用创建） -### 2.1. 开放平台注册应用（可选，如果使用OpenList/公益服务器/自建服务器内置的密钥对，则不用创建） { lang="zh-CN" } - -::: en -::: tip -Please register the application according to the requirements of the 115 Open Platform. -::: -::: en -Open Platform address: [115 Open Platform: https://open.115.com](https://open.115.com) -::: -::: zh-CN ::: tip 请根据115 开放平台的要求注册应用 ::: -::: zh-CN -开放平台地址: [115 开放平台:https://open.115.com ](https://open.115.com) -::: - -### 2.2. Obtain Tokens { lang="en" } - -### 2.2. 获取令牌 { lang="zh-CN" } - -::: en - -1. Visit [api.oplist.org](https://api.oplist.org) **⚠️ If using a public welfare server/self-built server, visit the address of the public welfare server/self-built server**. - -2. Select **115 Network Disk Verification** from the drop-down box. - -  - -  - -3. If you are using the built-in key pair of `OpenList (or public welfare server/self-built server)` (i.e., you do not have application information from the 115 Open Platform), please configure according to `3.1`, `3.2`, and `3.3`: - - 3.1. Check `Use parameters provided by OpenList`. - - 3.2. Leave both `Client ID (ClientID/AppID)` and `Application Secret (AppKey/Secret)` blank. - - 3.3. Click the `Get Token` button. - -  -  - -4. If you are using your own created OAuth client ID and secret, please configure according to `4.1`, `4.2`, and `4.3`: - - 4.1. Do not check `Use parameters provided by OpenList`. - - 4.2. Enter your `AppId` in `Client ID` and your `AppSecret` in `Application Secret`. - - 4.3. Click the `Get Token` button. - -  - -  - -5. In the pop-up window, log in to your 115 account and authorize OpenList to access your 115 network disk. - -  - -6. After successful authorization, the page will display your `Access Token` and `Refresh Token`. Please copy and save these two tokens. - -  - -  - -::: +开放平台地址: [115 开放平台:https://open.115.com ](https://open.115.com) -::: zh-CN +### 2.2. 获取令牌 1. 访问[api.oplist.org](https://api.oplist.org) **⚠️如果使用公益服务器/自建服务器，请访问公益服务器/自建服务器的地址** @@ -160,30 +75,12 @@ Open Platform address: [115 Open Platform: https://open.115.com](https://open.11  -::: - -## 3. Adding 115 Network Disk to OpenList { lang="en" } - -## 3. 在OpenList中添加115网盘 { lang="zh-CN" } +## 3. 在OpenList中添加115网盘 -### 3.1. Configuration Instructions { lang="en" } +### 3.1. 配置说明 -### 3.1. 配置说明 { lang="zh-CN" } +#### 3.1.1. 根文件夹 ID -#### 3.1.1. Root Folder ID { lang="en" } - -#### 3.1.1. 根文件夹 ID { lang="zh-CN" } - -::: en -The default root directory ID is: `0` - -Open the 115 network disk official website, and when clicking to enter the folder to be set, click the number after `cid` in the URL. - -For example,
-::: -### 3.2. Start Adding { lang="en" } - -### 3.2. 开始添加 { lang="zh-CN" } - -::: en - -1. Open the management interface of OpenList and click `Storage` in the left menu. - -2. On the storage list page, click the `Add Storage` button in the upper right corner. - -3. Select the driver as `115 Open Platform`. - -  - -  - -4. Enter the mounting path, such as: `115`. - -5. Enter the root folder ID obtained above in `Root Folder ID` (please refer to [3.1.1. Root Folder ID](#_3-1-1-root-folder-id)). - -6. Enter the obtained `Refresh Token` and `Access Token` in the refresh token (if not obtained, please refer to [2. Preparation for Access](#_2-preparation-for-access)). - - 115's token refresh mechanism does not require AppKey and has IP-based rate limiting, so it is implemented using [local logic](https://github.com/OpenListTeam/115-sdk-go). - -7. Click the `Add` button to complete adding the 115 network disk. - -::: -::: zh-CN +### 3.2. 开始添加 1. 打开 OpenList 的管理界面，点击左侧菜单中的`存储`。 @@ -240,24 +110,7 @@ The `root folder ID` of this folder is `249163533602609229`. 7. 点击`添加`按钮，完成115网盘的添加。 -::: - -### 3.3. Method for Refreshing Access Token { lang="en" } - -### 3.3. 当前AccessToken刷新的方式 { lang="zh-CN" } - -::: en - -```mermaid -sequenceDiagram - participant OpenList - participant 115 - OpenList->>115: Post refresh_token - 115->>OpenList: Get new access_token and refresh_token -``` - -::: -::: zh-CN +### 3.3. 当前AccessToken刷新的方式 ```mermaid sequenceDiagram @@ -267,26 +120,8 @@ sequenceDiagram 115服务器->>OpenList: 返回新的访问令牌+刷新令牌 ``` -## 4. Notes { lang="en" } - -## 4. 注意事项 { lang="zh-CN" } - -::: en -::: warning Handling Method for Token Leakage -If the Token is accidentally leaked, you can go to the 115 device login management to解除应用授权 (revoke application authorization). +## 4. 注意事项 -- 115 APP: [iOS, Android] versions need to be ≥ 35.11.0 -- 115 Web端: [https://115.com/?mode=device_manage](https://115.com/?mode=device_manage) - - When it expires, the following content will be prompted: - - ```json - failed get objs: failed to list objs: code: 40140116, message: no auth - ``` - -An account can obtain two `Refresh tokens` in the same application. After the third acquisition, the first obtained `Refresh token` will expire. Using the first `Refresh token` will prompt the above error. -::: -::: zh-CN ::: warning Token 泄漏后处理方法 如果不小心泄漏了 Token，可以前往115设备登录管理解除应用授权 @@ -302,61 +137,19 @@ An account can obtain two `Refresh tokens` in the same application. After the th 一个帐号可以在同一个应用获取两次`Refresh token`，第三次获取后第一次获取到的`Refresh token`就会失效，使用第一个`Refresh token`会提示上面的错误 ::: -## 5. Using Other APP IDs to Obtain Refresh Tokens (Not Yet Implemented) { lang="en" } - -## 5. 使用其他 APP ID 获取刷新令牌（尚未实现） { lang="zh-CN" } - -::: en -::: tip -Under development, the tutorial has not been updated yet. Stay tuned! -::: +## 5. 使用其他 APP ID 获取刷新令牌（尚未实现） -::: zh-CN ::: tip 开发中, 教程暂未更新, 敬请期待! ::: -## 6. Mobile QR Code Authorization PKCE Mode (Not Yet Implemented) { lang="en" } +## 6. 手机扫码授权PKCE模式（尚未实现） -## 6. 手机扫码授权PKCE模式（尚未实现） { lang="zh-CN" } - -::: en -::: tip -Under development, the tutorial has not been updated yet. Stay tuned! -::: - -::: zh-CN ::: tip 开发中, 教程暂未更新, 敬请期待! ::: -## 7. Default Download Method Used { lang="en" } - -## 7. 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +## 7. 默认使用的下载方式 ```mermaid --- @@ -376,5 +169,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/123.md b/pages/guide/drivers/123.md index 8d1a897ab..fe3e8f247 100644 --- a/pages/guide/drivers/123.md +++ b/pages/guide/drivers/123.md @@ -1,27 +1,14 @@ --- -title: - en: 123 Pan / Share / Link - zh-CN: 123 网盘 / 分享 / 直链 -# This is the icon of the page -icon: iconfont icon-state -# This control sidebar order top: 695 -# A page can have multiple categories categories: - guide - drivers --- - - -::: en -::: warning -123 Cloud Disk has implemented anti-leech measures for this **reverse-engineered driver**. To avoid unnecessary disputes, it is recommended that users choose the more standard 123 Open Platform driver. If you continue to use this driver, you need to enable a **local proxy** to prevent anti-leech detection. +# 123 网盘 / 分享 / 直链 -- [123 Open Platform](./123_open.md) + -::: -::: zh-CN ::: warning 123云盘对于该**逆向驱动**已经采取防盗链措施，为了避免不必要的纠纷，建议用户选用更为规范的123开放平台驱动。如果继续使用该驱动，需要开启**本地代理**以防止反盗链检测 @@ -29,32 +16,10 @@ categories: ::: -## Personal { lang="en" } - -## 个人 { lang="zh-CN" } - -::: en -Free user 1G traffic download, unlimited upload, multi-IP sharing is prohibited -::: +## 个人 -::: zh-CN 免费用户 1G 流量下载，上传不限制，禁止多IP共享使用 -::: -::: en -::: warning - -```json -failed get objs: failed to list objs:当前账号存在安全风险，请使用短信验证码或者微信进行登录。 -``` - -solution: - -- This is because the 123 cloud disk officially prohibits the mounting on strange devices, If you are mounted locally, `or` Windows Server server mount `to open the 123 cloud disk web page to log in or modify a password once - -::: - -::: zh-CN ::: warning 挂载提示： @@ -68,113 +33,39 @@ failed get objs: failed to list objs:当前账号存在安全风险，请使用 ::: -::: en -https://www.123pan.com/ - -Just fill in the account password. -::: - -::: zh-CN https://www.123pan.com/ 只需填写账户密码即可。 -::: - -### 用户名 { lang="zh-CN" } - -### Username { lang="en" } +### 用户名 -::: en -The mobile phone number used to log in -::: -::: zh-CN 用于登录的手机号码 -::: - -### 密码 { lang="zh-CN" } -### Password { lang="en" } +### 密码 -::: en -The password used to log in -::: -::: zh-CN 用于登录的密码 -::: -### 根文件夹 ID { lang="zh-CN" } +### 根文件夹 ID -### Root folder file_id { lang="en" } - -::: en -Enter the folder you want to mount, the last string of the official website URL, such as: -::: -::: zh-CN 输入要挂载的文件夹，官网 URL 的最后一串，如： -:::  -### 使用建议 { lang="zh-CN" } - -### Recommendations { lang="en" } - -::: en - -- It seems that the 123 API has a limited number of loads each time, so if you load hundreds of files in a folder at one time, an error may be reported -- It is recommended to A useful approach is not to put too many sub-items in the same folder. - -::: - -::: zh-CN +### 使用建议 - 貌似 123 的 API 每次加载的数量有限，故如果你一个文件夹内一次性加载几百个文件，可能会报错 - 建议不用在每个文件夹内放置太多子文件/文件夹 -::: - -## 直链 { lang="zh-CN" } - -## Link { lang="en" } +## 直链 -::: en -only adapted to the authentication function, the link also needs to be filled in by yourself, like [UrlTree](/guide/drivers/url_tree), fill in the direct link copied in 123 direct link. -::: -::: zh-CN 仅适配了鉴权功能，链接也需要自己填写，像[地址树一样](/guide/drivers/url_tree.md)，把在 123 直链复制的直链填写进去即可 -::: - -::: en -::: danger Please read this reminder carefully -Since 123 Cloud Disk Direct Link is a paid service with a storage quota, if you decide to add more storage, please ensure you set up passwords, metadata, and other protective measures to prevent malicious traffic. - -After configuring these settings, test them in incognito mode to confirm everything is working correctly. If you fail to implement adequate anti-theft measures and experience malicious traffic overload, you will be held responsible for the consequences. -::: - -::: zh-CN ::: danger 请仔细阅读此提醒 由于123云盘直链是付费服务并有限制额度，如果您添加123直链存储，请及时设置密码、元信息等安全措施，以防止恶意刷流量。 设置完成后，请先在无痕模式下进行测试，确保防盗措施已正确设置。如未设置妥当，导致被恶意刷流量，后果自负。 ::: -::: en -First open **`123 Cloud Disk Direct Link Management`**: **https://www.123pan.com/DirectLink** Set an authentication key in the lower right corner, and then turn on the authentication status switch - - - -- Open Settings 123 Cloud Disk Settings: **https://www.123pan.com/Setting** and find the account ID [`1` label in the picture below] -- How to activate direct link? (You need to activate membership to use it) - - Find the folder you want to open, right-click on `Enable Direct Link Space`, and after opening it, you will see a link icon in the folder [Tag `2` in the picture below] -- How to get a direct link to a file? [Tag `3` in the picture below] - - Enter the folder that has 'enabled direct link space', find the file you need to obtain, right-click 'Get direct link', and fill in the OpenList configuration after obtaining it. -  - -::: - -::: zh-CN 首先打开 **`123云盘直链管理`**: **https://www.123pan.com/DirectLink** 右下角自己设置一个鉴权秘钥，然后打开鉴权状态开关  @@ -186,42 +77,7 @@ First open **`123 Cloud Disk Direct Link Management`**: **https://www.123pan.com - 进入已经`启用直链空间`的文件夹，找到需要获取的文件右键`获取直链链接`，获取到后填写到OpenList配置內  -::: - -### 填写示例 { lang="zh-CN" } - -### Fill in example { lang="en" } - -::: en - -- **Origin urls**：Fill in the direct link to the files we copied one by one - - It supports creating different folders like [UrlTree](/guide/drivers/url_tree), and supports filling in the file size and modification time (four options are provided for use, like the UrlTree filling, refer to the second example of the picture below) - - File size unit: `B` bytes. For example, if you want to write a 1MB file, it is 1048567 bytes. You can search for the specific byte conversion in your browser (you can leave it blank). - - File modification time: It is `Unix timestamp`. You can search in the browser for the specific conversion (you can leave it blank). - - Fill in the format: - - ```txt - [FileSize:][Modified:]URL - 127451136:1694101621:https://vip.123pan.cn/1812xxx499/123-link-Test/linuxqq_3.2.0-16736_mips64el.deb - [FileSize:]URL - 134847488:https://vip.123pan.cn/1812xxx499/123-link-Test/linuxqq_3.2.0-16736_loong64.deb - [Modified:]URL - 1694101621:https://vip.123pan.cn/1812xxx499/123-link-Test/linuxqq_3.2.0-16736_arm64.AppImage - URL - https://vip.123pan.cn/1812xxx499/123-link-Test/linuxqq_3.2.0-16736_x86_64.AppImage - ``` - -- **Private key**： - - You can set up the direct link management page yourself and turn it on. Please turn it on. -- **Uid**： - - Account ID in the account settings page -- **Valid duration**： - - The file direct link validity period, in minutes, is filled in by default to 30 minutes - -::: - -::: zh-CN +### 填写示例 - **来源链接**：填写我们一条一条复制的文件直链 - 支持像[地址数](/guide/drivers/url_tree)那样新建不同文件夹，支持填写文件大小和修改时间（提供四种方案可以使用，像地址树填写参考下方图片的图二示例） @@ -248,62 +104,24 @@ First open **`123 Cloud Disk Direct Link Management`**: **https://www.123pan.com - **有效期**： - 文件直链有效期，单位为分钟，默认填充为30分钟 -::: -   -## 分享 { lang="zh-CN" } - -## Share { lang="en" } +## 分享 -::: en -Fill in the driver's **`share key`** and optional **`share password`** (if there is a password, you need to fill in), the root folder ID defaults to `0` to display all files -::: -::: zh-CN 填写驱动的 **`分享key`** 和选填 **`分享密码`** (如果有密码需要填写)，根文件夹ID默认为`0`显示全部文件 -::: - -### 填写示例 { lang="zh-CN" } -### Fill in the example { lang="en" } +### 填写示例 -::: en  -::: -::: zh-CN - -::: - -### Share Password { lang="en" } -### 分享密码 { lang="zh-CN" } +### 分享密码 -::: en -Fill in if you have it, don't if you don't -::: -::: zh-CN 有就填写，没有就不用 -::: - -### Root folder file_id { lang="en" } -### 根文件夹 ID { lang="zh-CN" } +### 根文件夹 ID -::: en -The ID of the root directory of the shared link is `0`, displaying all files - -If you only want to display a certain folder, open the developer mode (F12) to clear all requests (maybe 123 prohibits debug debugging, you need to close this by yourself to continue) - -Find the request on the right side of the picture in the upper-level directory request of the directory you want to display, then click `Response`, find the format button `{}` below and format it, and you can see the relevant directory ID. - -If you are not sure whether the directory ID is correct or not, there is a directory name under the directory ID - - - -::: -::: zh-CN 分享链接根目录ID是`0`，展示全部文件 如果只想展示某个文件夹，打开开发者模式(F12)清空全部请求（可能123禁止debug调试需要自己关闭这个才能继续） @@ -314,36 +132,7 @@ If you are not sure whether the directory ID is correct or not, there is a direc  -::: - -## The default download method used { lang="en" } - -## 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: - -::: zh-CN +## 默认使用的下载方式 ```mermaid --- @@ -363,5 +152,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/123_open.md b/pages/guide/drivers/123_open.md index 68ed98c2e..d94ff33f9 100644 --- a/pages/guide/drivers/123_open.md +++ b/pages/guide/drivers/123_open.md @@ -1,33 +1,18 @@ --- -title: - en: 123 Open - zh-CN: 123 开放平台 -# This is the icon of the page -icon: iconfont icon-state -# This control sidebar order top: 696 -# A page can have multiple categories categories: - guide - drivers --- +# 123 开放平台 + https://www.123pan.com/developer -## 1. Developer Application { lang="en" } - -## 1. 申请开发者 { lang="zh-CN" } - -::: en -::: warning -This driver uses the [developer authorization mode](https://123yunpan.yuque.com/org-wiki-123yunpan-muaork/cr6ced/hpengmyg32blkbg8), which grants direct management access to the cloud drive associated with the provided public/private key pair, , so you **must use your client id and client secret**. - -The acquired token counts as a login device +## 1. 申请开发者 -::: -::: zh-CN ::: warning 该驱动使用的是[开发者授权模式](https://123yunpan.yuque.com/org-wiki-123yunpan-muaork/cr6ced/hpengmyg32blkbg8),将会直接获得该密钥对应网盘的管理权限，所以**必须使用自己的密钥**。 @@ -35,21 +20,6 @@ The acquired token counts as a login device ::: -::: en - -**Application Method**: Visit the [123 Open Platform Official Website](https://www.123pan.com/developer), read the Developer Agreement, fill in the required fields marked with `*`, and apply for the `client_id` and `client_secret`.Typically, after your application is approved the keys will be sent to your email **remember to check your spam folder, and please keep the keys sent by email safe**. - -1. Sign the Developer Agreement - -2. Fill out the application materials - -3. Wait for the review notification - -**Reference Tutorial**: [OpenListTeam/discussions#55](https://github.com/orgs/OpenListTeam/discussions/55) - -::: -::: zh-CN - **申请方式**：访问[123开放平台官网](https://www.123pan.com/developer)，阅读开发者协议，填写对应必填项`*`信息，申请`client_id`和`client_secret`，一般来说申请通过后会发送至邮箱，记得检查邮件的垃圾箱，**请保管好通过邮件发送回来的密钥**。 1. 签署开发者协议 @@ -60,31 +30,7 @@ The acquired token counts as a login device **参考教程**：[OpenListTeam/discussions#55](https://github.com/orgs/OpenListTeam/discussions/55) -::: - -### 2. Get UID { lang="en" } - -### 2. 获取 UID { lang="zh-CN" } - -::: en - -The method to obtain the "Cloud Drive UID" required during the application process is as follows: - -1. **Log in to the 123 Cloud Drive web platform** - - Visit the 123 Cloud Drive official website and log in with your account (phone number). - -2. **Go to the "Settings" page** - - After logging in, click on the profile picture or username at the top right, and select "Settings" (or directly visit:
-:::
-
-## 189CloudTV { lang="en" }
-
-::: en
-Uses the TV interface of 189 Cloud Drive, with the fewest mounting steps.
-
-(Some users have reported throttling issues. If you experience video playback stuttering, black screens, or failure to load, please switch to the 189 Cloud PC client.)
-
-1. When mounting, select 189CloudTV. Leave the login parameters blank. If you are unsure, **just fill in the mount path**.
-
-2. After clicking save, simply return to the storage management page. You can choose to log in by scanning a QR code or click the link to log in (for link login, if you are unsure, it is recommended to **right-click the link and open it in a new window**).
+## 个人云
-
+### 用户名
-3. After entering, select SMS login. Once logged in, return to the storage management page. Disable and re-enable the storage to use it normally (you may need to refresh the page).
-
-
-
-:::
-
-## 个人云 { lang="zh-CN" }
-
-## Personal Cloud { lang="en" }
-
-### Username { lang="en" }
-
-### 用户名 { lang="zh-CN" }
-
-::: en
-the phone number used to log in
-:::
-::: zh-CN
用于登录的电话号码
-:::
-
-### 密码 { lang="zh-CN" }
-### Password { lang="en" }
+### 密码
-::: en
-password for login
-:::
-
-::: zh-CN
登录密码
-:::
-### 根文件夹ID { lang="zh-CN" }
-
-### Root folder ID { lang="en" }
-
-::: en
-The string at the end of the official website url, such as:
-
-- https://cloud.189.cn/web/main/file/folder/-11 -> `-11`
-- https://cloud.189.cn/web/main/file/folder/71398114617385472 -> `71398114617385472`
+### 根文件夹ID
- 
-
-:::
-
-::: zh-CN
官网 URL 末尾的字符串，如：
- https://cloud.189.cn/web/main/file/folder/-11 -> `-11`
@@ -122,113 +50,39 @@ The string at the end of the official website url, such as:
-:::
-
-### 家庭云中转 { lang="zh-CN" }
-
-### Family transfer { lang="en" }
-
-::: en
-Give 189 Cloud adds Personal's `Family Transfer option`, which is convenient for users without VIP, and a large number of family cloud spaces upload.
-
-- Note: The old upload interface family cloud will still limit the upload quantity, so `Rapid upload` and ` Old Upload` will not take effect
+### 家庭云中转
-:::
-::: zh-CN
为天翼云盘增加个人云使用`家庭云中转选项`，方便不开会员且家庭云空间小情况下大量上传。
- 注：旧的上传接口家庭云依然会限制上传量，所以`秒传选项`和`旧的上传方式`不生效
-:::
-
-## 家庭云 { lang="zh-CN" }
-
-## Family Cloud { lang="en" }
-
-::: en
-(189 Cloud PC Driver Only) Use a computer browser, open the developer tool (F12), switch the emulation device and select the mobile device
+## 家庭云
-Open https://h5.cloud.189.cn/main.html#/family, enter the folder you want to mount, you can see the request in the network, and then find the required parameters:
-:::
-
-::: zh-CN
（天翼云盘客户端驱动专用）使用电脑浏览器，打开开发者工具（F12），切换仿真设备选择手机设备
打开https://h5.cloud.189.cn/main.html#/family ，进入你想挂载的文件夹，可在网络中看到请求，然后找到所需参数：
-:::
-### OpenList挂载填写示例： { lang="zh-CN" }
-
-### OpenList fill in examples： { lang="en" }
-
-#### 天翼云盘 { lang="zh-CN" }
+### OpenList挂载填写示例：
-#### 189 Cloud { lang="en" }
+#### 天翼云盘
-::: en
-Fill in the account1and password2,Then click one request in the request, just bring `Cookies`3, click on one at will Then fill in,Cookie expires time is unknown
-:::
-
-::: zh-CN
填写帐号1和密码2，然后在请求中随便点击一个请求随意点击一个携带`Cookie`3的参数复制填写，Cookie有效期未知。
-:::
-#### 天翼云盘客户端 { lang="zh-CN" }
-
-#### 189 CloudPC { lang="en" }
+#### 天翼云盘客户端
-::: en
-Video reference: **https://www.bilibili.com/video/BV16A4y197De**
-:::
-::: zh-CN
视频参考：**https://www.bilibili.com/video/BV16A4y197De**
-:::
-
-## 建议 { lang="zh-CN" }
-## suggestion { lang="en" }
+## 建议
-::: en
-It is recommended to use the 189 Cloud PC first, [**Notes click to view.**](../../faq/howto.md#when-adding-a-189-cloud-storage-the-device-id-does-not-exist-and-a-secondary-device-verification-is-required)
-:::
-::: zh-CN
建议首选使用天翼云盘客户端，[**注意事项点击查看**](../../faq/howto.md#添加-天翼云盘-云存储时-设备-id-不存在-需要二次设备验证)
-:::
-### 默认使用的下载方式 { lang="zh-CN" }
-
-### The default download method used { lang="en" }
-
-::: en
-
-```mermaid
----
-title: Which download method is used by default?
----
-flowchart TB
- style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff
- style a2 fill:#ff7575,stroke:#333,stroke-width:4px
- subgraph ide1 [ ]
- a1
- end
- a1[302]:::someclass====|default|a2[user equipment]
- classDef someclass fill:#f96
- c1[local proxy]-.alternative.->a2[user equipment]
- b1[Download proxy URL]-.alternative.->a2[user equipment]
- click a1 "../drivers/common.html#webdav-policy"
- click b1 "../drivers/common.html#webdav-policy"
- click c1 "../drivers/common.html#webdav-policy"
-```
-
-:::
-
-::: zh-CN
+### 默认使用的下载方式
```mermaid
---
@@ -248,5 +102,3 @@ flowchart TB
click b1 "../drivers/common.html#webdav-策略"
click c1 "../drivers/common.html#webdav-策略"
```
-
-:::
diff --git a/pages/guide/drivers/alias.md b/pages/guide/drivers/alias.md
index 74f94447f..8378c126c 100644
--- a/pages/guide/drivers/alias.md
+++ b/pages/guide/drivers/alias.md
@@ -1,22 +1,10 @@
---
-title:
- en: Alias
- zh-CN: 别名（Alias）
-icon: iconfont icon-state
-# This control sidebar order
top: 997
-# A page can have multiple categories
categories:
- guide
- drivers
-# A page can have multiple tags
-tag:
- - Storage
- - Guide
-# this page is sticky in article list
-sticky: true
-# this page will appear in starred articles
-star: true
---
+# 别名（Alias）
+
diff --git a/pages/guide/drivers/alias_text.md b/pages/guide/drivers/alias_text.md
index 86c6c72da..5a6894cde 100644
--- a/pages/guide/drivers/alias_text.md
+++ b/pages/guide/drivers/alias_text.md
@@ -1,35 +1,3 @@
-::: en
-
-**Alias** is a feature that allows multiple different cloud drives or storage paths to be merged into a unified directory. By combining paths, content from different cloud drives or folders can be displayed in the same interface, simplifying access and management.
-
-For example: Cloud Drive Account 1 and Cloud Drive Account 2 both contain a folder named `Movies`, but the contents of these folders may not be identical.
-
-- **Previously (Virtual Path)**:
-
- You could only mount them to two different paths separately, like:
- - `CloudDrive1/Movies`, `CloudDrive2/Movies`
- - `Movies/CloudDrive1`, `Movies/CloudDrive2`
-
-- **Now (Alias)**:
-
- An aggregated folder (Movies) is provided, which can contain content from both Cloud Drive 1 and Cloud Drive 2 simultaneously.
-
-Folders with the same name will be automatically merged into one. The contents of the folder are the sum of the contents of all folders with the same name. Regarding how this driver handles files with the same name, please refer to the [Path conflict policies](/guide/drivers/alias#path-conflict-policies) section later.
-
-For Example:
-
-
-
-In the diagram, we can see that two different folders are merged into one. Files and folders with the same name are also combined, and unique ones are displayed separately.
-
-Example explanations:
-
-- **Example 1**: `riluo.jpg` is unique to Cloud Drive 1, so it is shown separately.
-- **Example 2**: Both folders contain a `video` folder, but the contents of these folders will be merged. Subfolders also follow the **same-name merging** display rule. Both folders contain two videos, but one of them has the same name. After merging according to the **same-name merging** rule, three video files will be displayed in total.
-
-:::
-::: zh-CN
-
**别名（Alias）** 是一种将多个不同云盘或存储路径合并为一个统一目录的功能。通过路径合并，来自不同云盘或文件夹的内容可以在同一界面中展示，从而简化访问和管理。
例如：云盘账号1和云盘账号2中都包含一个名为`电影`的文件夹，但两者的内容未必完全相同。
@@ -57,39 +25,8 @@ Example explanations:
- **例1**：`riluo.jpg` 仅存在于云盘1中，因此显示为独有文件。
- **例2**：两个文件夹都有一个名为`video`的子文件夹。合并后，两个`video`文件夹的内容会合并展示。若其中有同名文件（例如`movie.mp4`），合并后最终展示3个视频文件。
-:::
-
-## Paths filling method { lang="en" }
+## 路径填写方式
-## 路径填写方式 { lang="zh-CN" }
-
-::: en
-There are two ways to fill in:
-
-1. The first one is that you can only fill in the path of the subfolder and the folder with the same name must be used at the end. It is not recommended to use :x:
- - Paths filling example:
- ```
- /file1/locala
- /file2/localb
- ```
-2. The second is to directly mount the root folder path, using the `renaming` method, it is strongly recommended to use :heavy_check_mark:
- - Paths filling example:
-
- ```
- #Example 1 Directly write the root folder
- merge: /file1
- merge: /file2
-
- #Example 2 Mount different path folders for merging
- merge: /file1/localtest233
- merge: /file2/videos/TV series
- merge: /file3 2/TV/Domestic TV Series/Station XX
- ```
-
-According to the second method, we can `merge` and display different folders, which is convenient and quick.
-:::
-
-::: zh-CN
填写方式有两种：
1. 第一种是只可以填写子文件夹路径并且最后结尾时必须同名文件夹才可以，不推荐使用 :x:
@@ -113,91 +50,13 @@ According to the second method, we can `merge` and display different folders, wh
```
根据第二种这样我们可以将不同的文件夹进行合并显示，方便快捷。
-:::
-
-## Path conflict policies { lang="en" }
-## 路径冲突策略 { lang="zh-CN" }
+## 路径冲突策略
-::: en
-The three configuration items—**Reading conflict policy**, **Writing conflict policy**, and **Putting conflict policy**—determine how the Alias handles files or folders with the same name and identical paths in the backend drivers. Their values and corresponding behaviors are as follows:
-
-:::
-::: zh-CN
**读取冲突策略**、**写入冲突策略**和**上传冲突策略**三个配置项确定了别名驱动如何处理后端驱动中路径相同的同名文件或文件夹，其值与对应的行为如下：
-:::
-
-### Reading conflict policy { lang="en" }
-
-### 读取冲突策略 { lang="zh-CN" }
-
-::: en
-Determines the behavior for handling files with the same name when downloading, copying (as source files), and extracting (as source files) (excluding moving).
-
-- Get the file corresponding to the first conflict path: Select the file from the first available path (from top to bottom in the Paths) where the file exists.
-
-- Load balancing on a per-file basis: Randomly select one file from the available duplicates.
+### 读取冲突策略
-- Load balancing on a per-part basis:
- - During 302 downloads, copying, or extracting, it falls back to the **Load balancing on a per-file basis** strategy.
- - When using local proxy downloads, each transmitted chunk is randomly assigned to one of the duplicate files. This requires the backend driver to support Range requests. For details on setting the chunk size, refer to the section [Download concurrency, Download part size](/guide/drivers/alias#download-concurrency-download-part-size).
- - This policy achieves the actual effect as shown in the figure. It is important to note that this diagram is only intended to conveniently demonstrate the operation of this policy. The statement that "participating load-balanced files with the same name have different contents" is **not** a correct usage of this driver. OpenList does not guarantee stable or correct results under such circumstances, nor will it address any issues arising from this usage scenario. Furthermore, the actual minimum size for file splitting is 1 KiB, not 1 byte, so the effect depicted in the diagram will not occur in the stable version.
-
- 
-
-::: tip
-When a copy operation involves multiple source paths and target paths, the Alias will first attempt to pair source and target paths that belong to the same drive. Only for target paths that cannot be matched in this way will the method specified by the **Reading conflict policy** be used to select a source path.
-
-For example, when copying:
-
-- `DriverA/source/file.txt`
-- `DriverB/source/file.txt`
-
-to:
-
-- `DriverB/target/`
-- `DriverA/target/`
-- `DriverC/target/`
-
-The Alias driver will perform the following operations:
-
-1. Copy `DriverA/source/file.txt` to `DriverA/target/`, since both are located in Driver A.
-2. Copy `DriverB/source/file.txt` to `DriverB/target/`, since both are located in Driver B.
-3. For `DriverC/target/`, which has no matching source in the same driver, select `file.txt` from either Driver A or Driver B according to the **Reading conflict policy**, and copy it to `DriverC/target/` via an upload operation (creating a copy task).
-
-:::
-::: en
-::: tip
-The move operation involves a matching process similar to that of the copy operation. For target paths that cannot be matched with a source path from the same driver, the Alias will randomly select from the still-unmatched source paths to create a pairing (**one-to-one correspondence**). If the number of source paths exceeds the number of target paths, the unmatched source paths will be deleted. If the number of source paths is less than the number of target paths, the move operation will fail. The matching behavior for the move operation is not affected by the **Reading conflict policy**.
-
-For example, in the case described for the copy operation, since there is no source path corresponding to `DriverC/target/`, the move operation will fail.
-
-As another example, when moving:
-
-- `DriverA/source/file.txt`
-- `DriverB/source/file.txt`
-- `DriverD/source/file.txt`
-- `DriverE/source/file.txt`
-- `DriverG/source/file.txt`
-
-to:
-
-- `DriverA/target/`
-- `DriverB/target/`
-- `DriverC/target/`
-- `DriverF/target/`
-
-The Alias will perform the following operations:
-
-1. Move `DriverA/source/file.txt` to `DriverA/target/`.
-2. Move `DriverB/source/file.txt` to `DriverB/target/`.
-3. Randomly select one file from Driver D, E, or G, and move it to `DriverC/target/` (by creating a move task, which is essentially an upload followed by deletion). Let's assume E is selected.
-4. Randomly select one file from the remaining unmatched drivers (D or G), and move it to `DriverF/target/`. Let's assume G is selected.
-5. Delete `DriverD/source/file.txt`.
-
-:::
-::: zh-CN
影响下载、复制（作为源文件）、解压（作为源文件）（没有移动）同名文件的方式。
- 读取首个有效路径：选择填写的所有路径中从上到下第一个存在该文件的路径中的同名文件。
@@ -230,7 +89,7 @@ The Alias will perform the following operations:
3. 按照**读取冲突策略**给出的方案选择驱动 A 或 B 中的`file.txt`，通过上传的方式（创建复制任务）复制到`驱动C/target/`。
:::
-::: zh-CN
+
::: tip
移动操作存在与复制操作类似的匹配过程，对于未获得匹配的目标路径，随机选择同样未被匹配的源路径进行匹配（**一一对应**），源路径数量超过目标路径时，未得到匹配的源路径会被删除，源路径数量少于目标路径时，移动操作会失败。移动操作的匹配行为不会受到**读取冲突策略**的影响。
@@ -261,54 +120,8 @@ The Alias will perform the following operations:
:::
-### Writing conflict policy { lang="en" }
-
-### 写入冲突策略 { lang="zh-CN" }
-
-::: en
-Determines the behavior for renaming or deleting files/folders with the same name, as well as creating folders within identically named folders.
-
-- **Disable writing**: Prohibits rename, delete, and folder creation operations.
-- **Write into the first conflict path**: Operates on the driver containing the target path that appears first (top to bottom) in the configured path list.
-- **Allow unique path**: Executes the operation only if the target path is unique (exists in only one backend path). Otherwise, the operation is prohibited.
-- **Allow full conflict paths**: Executes the operation only if the target path exists in **all** configured backend paths, applying the operation across all of them. Otherwise, the operation is prohibited.
-- **Allow unique path and full conflict paths**: Allows the operation when the target path is either unique or exists in all configured backend paths.
-- **Write into all conflict paths**: Forwards the operation to all backend paths where the target path exists.
-
-::: tip
-If the above explanation is unclear, you can refer to the following example.
-
-- In Driver A, the file exists: `file1.txt`
-- In Driver B, the files exist: `file1.txt`, `file2.txt`, `file3.txt`
-- In Driver C, the files exist: `file1.txt`, `file3.txt`
-
-Configured backend paths:
-
-```
-test:DriverA
-test:DriverB
-test:DriverC
-```
-
-Then:
-
-- Since the sub-path `/file1.txt` is valid in all configured paths (`DriverA/`, `DriverB/`, `DriverC/`), `/file1.txt` is referred to as a **full conflict path**.
-- Since the sub-path `/file2.txt` is valid only under the single backend path `DriverB/`, `/file2.txt` is referred to as a **non-conflict path** or **unique path**.
-- Since the sub-path `/file3.txt` exists under both `DriverB/` and `DriverC/`, and the number of backend paths where it exists is neither 1 nor the maximum (3), `/file3.txt` is neither a non-conflict path nor a full conflict path.
+### 写入冲突策略
-When renaming any file to `file4.txt`, the corresponding files in the following drivers will be renamed:
-
-| Writing conflict policy | file1.txt | file2.txt | file3.txt |
-| ----------------------------------------- | ---------------------------- | --------- | ------------------ |
-| Disable writing | Fails | Fails | Fails |
-| Write into the first conflict path | Driver A | Driver B | Driver B |
-| Allow unique path | Fails | Driver B | Fails |
-| Allow full conflict paths | Driver A, Driver B, Driver C | Fails | Fails |
-| Allow unique path and full conflict paths | Driver A, Driver B, Driver C | Driver B | Fails |
-| Write into all conflict paths | Driver A, Driver B, Driver C | Driver B | Driver B, Driver C |
-
-:::
-::: zh-CN
影响重命名、删除同名文件或文件夹，在同名文件夹下创建文件夹的方式。
- 禁用：禁止重命名、删除和创建文件夹操作。
@@ -340,49 +153,20 @@ test:驱动C
- 由于子路径`/file3.txt`在`驱动B/`和`驱动C/`下存在，存在的后端路径数量既不为 1，也不为最大（3），因此`/file3.txt`既不是不冲突路径，也不是全冲突路径。
重命名任意文件为`file4.txt`时，以下驱动中的对应文件会被重命名：
-| 写入冲突策略 | file1.txt | file2.txt | file3.txt |
-| -- | -- | -- | -- |
-| 禁用 | 操作失败 | 操作失败 | 操作失败 |
-| 写入首个有效路径 | 驱动A | 驱动B | 驱动B |
-| 仅允许不冲突路径 | 操作失败 | 驱动B | 操作失败 |
-| 仅允许全冲突路径 | 驱动A、驱动B、驱动C | 操作失败 | 操作失败 |
-| 允许不冲突路径和全冲突路径 | 驱动A、驱动B、驱动C | 驱动B | 操作失败 |
-| 写入所有有效路径 | 驱动A、驱动B、驱动C | 驱动B | 驱动B、驱动C |
-
-:::
-
-### Putting conflict policy { lang="en" }
-
-### 上传冲突策略 { lang="zh-CN" }
-
-::: en
-Determines the behavior for uploading to, copying to, moving to, or extracting to folders with the same name.
-
-- **Disable putting**, **Put into the first conflict path**, **Allow unique path**, **Allow full conflict paths**, **Allow unique path and full conflict paths**, **Put into all conflict paths**: These options function identically to their counterparts in the **Writing conflict policy**.
-- **Random load balancing**: Randomly selects one valid path for the upload.
-- **Weighted random load balancing based on remaining space**: Retrieves the remaining free space of all valid paths, skips paths that fail to report free space or have insufficient space for the file being uploaded, and then randomly selects from the remaining valid paths, weighting the choice by their remaining capacity. If none of the valid paths that successfully reported free space have enough capacity for the file, **a random selection is made from among the valid paths that failed to report capacity**.
-- **Strict weighted random load balancing based on remaining space**: Retrieves the remaining free space of all valid paths, skips paths that fail to report free space or have insufficient space for the file being uploaded, and then randomly selects from the remaining valid paths, weighting the choice by their remaining capacity. If none of the valid paths that successfully reported free space have enough capacity for the file, **an error message is returned directly**.
-::: tip
-The load balancing mechanisms within the **Reading conflict policy** and the **Putting conflict policy** are two largely unrelated features. Informally speaking, the load balancing in the **Reading conflict policy** is analogous to RAID 1, while the load balancing in the **Putting conflict policy** is analogous to RAID 0. For specific use cases of each, please refer to [Advanced / Load balancing](/guide/advanced/balance).
-
-If you've understood the above, you'll realize that enabling both **Reading Load Balancing** and **Putting Load Balancing** won't make load balancing more balanced. In fact, this configuration produces effects that are hardly any different from enabling only **Putting Load Balancing**.
+| 写入冲突策略 | file1.txt | file2.txt | file3.txt |
+| -------------------------- | ------------------- | --------- | ------------ |
+| 禁用 | 操作失败 | 操作失败 | 操作失败 |
+| 写入首个有效路径 | 驱动A | 驱动B | 驱动B |
+| 仅允许不冲突路径 | 操作失败 | 驱动B | 操作失败 |
+| 仅允许全冲突路径 | 驱动A、驱动B、驱动C | 操作失败 | 操作失败 |
+| 允许不冲突路径和全冲突路径 | 驱动A、驱动B、驱动C | 驱动B | 操作失败 |
+| 写入所有有效路径 | 驱动A、驱动B、驱动C | 驱动B | 驱动B、驱动C |
:::
-::: en
-::: tip
-The legacy version of the Alias used three Boolean configuration items—**Writable**, **Protect same name**, and **Parallel write**—to implement path conflict policy functionality. The correspondence between the legacy configuration and the new configuration is as follows:
-- In the legacy configuration, the **Reading conflict policy** was always set to **Get the file corresponding to the first conflict path**.
-- In the legacy configuration, when **Writable** was disabled, both the **Writing conflict policy** and the **Putting conflict policy** were set to **Disabled**.
-- When **Writable** was enabled, the **Writing conflict policy** and the **Putting conflict policy** were both determined as follows:
- | | Parallel write disabled | Parallel write enabled |
- | -- | -- | -- |
- | Protect same name enabled | Allow unique path | Allow unique path and full conflict paths |
- | Protect same name disabled | Write/Put into the first conflict path | Write/Put into all conflict paths |
+### 上传冲突策略
-:::
-::: zh-CN
影响上传到、复制到、移动到、解压到同名文件夹的方式。
- 禁用、上传到首个有效路径、只允许不冲突路径、只允许全冲突路径、允许不冲突路径和全冲突路径、上传到所有有效路径：与**写入冲突策略**中的对应选项相同。
@@ -396,76 +180,37 @@ The legacy version of the Alias used three Boolean configuration items—**Writa
一旦理解了上述原理，你就会明白同时开启**读取负载均衡**和**上传负载均衡**并不能让你负载得均均又衡衡，这种配置产生的效果和仅开启**上传负载均衡**没有什么太大的区别。
:::
-::: zh-CN
+
::: tip
旧版别名驱动使用**可写**、**保护同名**和**并行写入**三个布尔配置项实现路径冲突策略功能，旧版配置与新版配置的对应关系如下：
- 在旧版配置中，**读取冲突策略**总为**读取首个有效路径**。
- 在旧版配置中，当**可写**关闭时，**写入冲突策略**与**上传冲突策略**均为**禁用**。
- 当**可写**开启时，**写入冲突策略**与**上传冲突策略**均为
- | | 关闭并行写入 | 开启并行写入 |
- | -- | -- | -- |
- | 开启保护同名 | 仅允许不冲突路径 | 允许不冲突路径和全冲突路径 |
- | 关闭保护同名 | 写入/上传到首个有效路径 | 写入/上传到所有有效路径 |
+ | | 关闭并行写入 | 开启并行写入 |
+ | ------------ | ----------------------- | -------------------------- |
+ | 开启保护同名 | 仅允许不冲突路径 | 允许不冲突路径和全冲突路径 |
+ | 关闭保护同名 | 写入/上传到首个有效路径 | 写入/上传到所有有效路径 |
:::
-## File consistency check { lang="en" }
-
-## 文件一致性校验 { lang="zh-CN" }
-
-::: en
-When enabled, the driver will filter out paths where the **size or hash value** differs from other copies during the process of collecting valid paths. This is a safety measure, and whether it is enabled has relatively minor impact. It is recommended to enable this option when using the **Load balancing on a per-part basis** reading policy.
-
-Regardless of whether this option is enabled, the Alias does not actively calculate file hashes. Instead, it performs a best-effort match using the hash values returned by the backend drivers.
-
-Different types of hash values returned by backend drivers will not lead to misjudgment. For example, if Driver 1 returns the MD5 of a file and Driver 2 returns the SHA1 of the file, even with this option enabled, the Alias will not consider either path from Driver 1 or Driver 2 invalid simply because the file's MD5 and SHA1 are not equal.
+## 文件一致性校验
-:::
-::: zh-CN
开启时，驱动在收集有效路径的过程中，会过滤掉那些**大小或哈希值**与其它副本不同的路径，是一种安全措施，开启与否影响不太大，推荐使用**按分片负载均衡**读取策略时打开。
无论是否启用该选项，别名都不会主动计算文件的哈希值，而是使用后端驱动返回的哈希值做尽力而为的匹配。
后端驱动返回不同种类的哈希值不会导致误判。例如驱动 1 返回了文件的 MD5，驱动 2 返回了文件的 SHA1，即便开启本选项，别名也不会因为文件的 MD5 与 SHA1 不相等而判定驱动 1 或 2 中的任何一个路径无效。
-:::
-
-## The download method to use { lang="en" }
-
-## 使用的下载方式 { lang="zh-CN" }
-
-::: en
-When adding **`alias`**, `Web Proxy` and `Webdav Policy` are not modified by default. The storage path filled in the Paths path can be `302`, `Local Proxy`, `Download Proxy URL`, three modes Mixed Playback Mixed Playback is possible.
+## 使用的下载方式
-If you checked `Web Proxy`, the storage filled in by the Paths path, if there is a 302 mode playback, it will be played in transit (local proxy mode) at that time, and it will become a proxy mode. If the Webdav policy is also changed, it will also change.
-
-Of course, it is up to you to choose whether to change the mode.
-:::
-::: zh-CN
添加 **`别名-alias`** 时 `Web代理` 和 `Webdav策略` 默认不修改的情况下 Paths路径填写的存储路径可以 `302`，`本地代理`，`下载代理URL`，三种模式混合播放可以进行混合播放。
如果你勾选了`Web代理` ，Paths路径填写的存储 如果有302模式播放的 到时候都会进行中转(本地代理模式)播放，变成代理模式，Webdav策略如果也进行了改动也会进行变化。
当然，是否选择更换模式您自己进选择。
-:::
-
-### What if you don’t know how the cloud disks you added are different? { lang="en" }
-### 如果你不知道你添加的云盘是什么方式怎么办? { lang="zh-CN" }
-
-::: en
-
-1. You can go to the bottom of the corresponding document to view the document, there is a flow chart description
- - If there is a 302, the 302 method is used by default. If there are only local proxy and download proxy URLs, the default is to use the local proxy, provided that you have not manually selected
-2. You can check when adding storage, select the corresponding storage to view, for example, let’s check the methods of Alibaba Cloud and 115 respectively
- - As you can see from the figure below, Alibaba Cloud Disk has the option of `web proxy`, and `webdav policy` defaults to 302. It can be judged that Alibaba Cloud Disk uses the 302 method by default
- - As you can see from the figure below, the 115 network disk does not have the option of `web proxy`, and the `webdav strategy` defaults to the local proxy. It can be judged that the 115 network disk uses the local proxy mode by default
- 
-
-:::
-
-::: zh-CN
+### 如果你不知道你添加的云盘是什么方式怎么办?
1. 可以前往文档的相对应的文档最底部查看，有一份流程图说明
- 如果有302的就是默认使用302方式，如果只有本地代理和下载代理URL默认的就是使用本地代理，前提是你没有进行手动选择
@@ -474,75 +219,16 @@ Of course, it is up to you to choose whether to change the mode.
- 从下图中看到，115网盘没有 `web代理`选择，`webdav策略`默认是本地代理，可以判断出115网盘默认使用的是本地代理方式
-:::
-
-## Proxy Range { lang="en" }
+## 代理 Range
-## 代理 Range { lang="zh-CN" }
-
-::: en
-You need to enable `Web Proxy` or` Webdav Native Proxy` to take effect. Currently only applicable to：`alias`、`139Yun`、`OpenList V3`.
-
-- The `139Yun` driver, when this option is enabled, can resolve issues that occur when a proxy is enabled but the download link does not return the correct HTTP status code, such as problems with video playback or lack of support for resume downloads.
-- The `Alias` driver is added to meet specific use cases, for example, when `139Yun` uses a 302 redirect. By enabling the `Alias` proxy, downloads can use `139Yun` with the 302 redirect, while video playback can use the proxy-enabled `Alias`, reducing unnecessary load.
-- The `OpenList` driver is added to support server-side OpenList mounting with `139Yun` using a 302 redirect. Locally, OpenList can be mounted via the proxy-enabled `OpenList` to access the server's OpenList for video playback, etc., to avoid consuming server bandwidth. This also allows for data-free video streaming on mobile networks.
-
-:::
-
-::: zh-CN
需要先启用 `Web代理` 或者 `Webdav本地代理` 才会生效。目前仅适用于：`别名`、`中国移动云盘`、`OpenList V3`。
- `139Yun` 驱动开启这个选项后，可解决即使开启代理但下载链接没有返回正确的http状态码导致的一些问题，例如视频无法播放、不支持断点续传等
- `Alias` 驱动添加是为了满足某些场景，例如 `139Yun` 走302， 然后通过 开启代理的 `Alias` 后，下载用 `139Yun` 走302，播放视频用 开启代理的 `Alias`，减少不必要的负载
- `OpenList` 驱动添加是为了 服务器的 OpenList 挂载 `139Yun` 走302，然后本地的 OpenList 通过 开启代理的 `OpenList` 挂载 服务器的 OpenList 播放视频等，达到不消化服务器流量的目的，移动卡还能免流
-:::
-
-## Download concurrency, Download part size { lang="en" }
-
-## 下载并发、下载分片大小 { lang="zh-CN" }
-
-::: en
-**Storage Settings:**
-
-- Alias (Alias) Drive
-- Local Proxy
-- Path: / Cloud Drive Mount Path
-- Download Concurrency: 10
-- Download Chunk Size: 1024
-
-**Effect:**
-
-- Client → OpenList Alias Drive: Uses 1 connection
-- OpenList Alias Drive → Cloud Drive: Supports 10 concurrent connections, with actual concurrency limited by the cloud drive.
-
-```mermaid
-graph LR
- A[Client] -->|Connection 1| B[OpenList Alias Drive]
- B -->|Concurrent Connection 1| C[Cloud Drive]
- B -->|Concurrent Connection 2| C
- B -->|Concurrent Connection 3| C
- B -->|Concurrent Connection 4| C
- B -->|Concurrent Connection 5| C
- B -->|Concurrent Connection 6| C
- B -->|Concurrent Connection 7| C
- B -->|Concurrent Connection 8| C
- B -->|Concurrent Connection 9| C
- B -->|Concurrent Connection 10| C
-```
-
-- Single-threaded speed is slower, but it supports concurrency: Using the alias drive allows concurrent downloads, significantly improving speed.
-- Video watching and download acceleration: The experience is enhanced by increasing concurrency.
-- Copying from alias drive to other drives: File transfer is also accelerated in this case.
+## 下载并发、下载分片大小
-**Friendly Reminder:** Please do not abuse this feature. Excessive use may cause abnormal activity on the cloud drive account, and you will bear the consequences.
-
-**Configuration Options:**
-
-- max_concurrency: Sets the maximum concurrency for the local proxy. The default is 64, and setting it to 0 means no limit on concurrency.
-
-:::
-::: zh-CN
**存储设置：**
- 别名 (Alias) 驱动
@@ -581,27 +267,8 @@ graph LR
- `max_concurrency`：设置本地代理的最大并发数，默认为 64，设置为 0 表示不限制并发数。
-:::
-
-## Other instructions { lang="en" }
-
-## 其他说明 { lang="zh-CN" }
-
-::: en
-
-If you are using `Windows`, the following situation will occur, and folders with different capitalization will also be regenerated.
+## 其他说明
-For example, Local 1 and Local 2 have a lowercase v for `video` respectively, and the folder OneDrive has an uppercase V `Video` folder.
-
-Then a lowercase video folder will be generated, which contains only `local 1, local 2` files merged by two folders.
-
-At the same time, the uppercase `Video` will gather the files of the three folders.
-
-This is because Windows is case-insensitive, video and Video will be considered as the same folder, you will not have this problem if you switch to Linux or Mac.
-
-:::
-
-::: zh-CN
如果你是使用的`Windows`，会出现如下情况，有大小写不同的文件夹也会进行二次生成。
例如本地1，本地2 分别有 `video` 小写的v ，文件夹 OneDrive 有一个大写的 V `Video` 文件夹。
@@ -611,5 +278,3 @@ This is because Windows is case-insensitive, video and Video will be considered
同时大写的 `Video` 里面 会集合三个文件夹的文件
这是因为 Windows 大小写不敏感，video和Video会被认为是同一个文件夹，你换成 Linux 或者 Mac 就不会有这个问题了
-
-:::
diff --git a/pages/guide/drivers/alidoc.md b/pages/guide/drivers/alidoc.md
index e7e10c989..e67bb28f6 100644
--- a/pages/guide/drivers/alidoc.md
+++ b/pages/guide/drivers/alidoc.md
@@ -1,34 +1,16 @@
---
-title:
- en: AliDoc
- zh-CN: 钉钉文档
top: 677
categories:
- guide
- drivers
---
-::: en
-::: danger Please read the notes carefully
-This driver is currently not officially maintained by the project team.
-:::
+# 钉钉文档
-::: zh-CN
::: danger 请仔细阅读注意事项
本接口目前非项目组官方维护
:::
-::: en
-Mount DingTalk Docs web storage in OpenList.
-
-Official website:
-
-- DingTalk Docs:
-
-
-:::
-
-::: zh-CN
-
- Tutorial on how to modify UA in web page 302 mode -
-
-
-
-
- Official
-
-
-
- Crack video (unavailable)
-
- 网页302模式修改UA教程 @@ -437,23 +194,7 @@ If you don’t change **`"User-Agent"`**, you can enable=Web Agent, the disadvan
triggers related API operations Cloud Drive
Cloud Drive receives command and begins execution) - A[(Cloud Drive)] - B(You) - C[Use proxy URL] - D{Native proxy} - E==>A==>E - A==>|Directly transferring from cloud drive to you without any loss
302 downloads as fast as possible|B - A-->|Send the cloud disk to the use proxy URL first|C-->|After being forwarded to you by the proxy URL, your download speed depends on the speed of downloading, forwarding, and forwarding on the other end of the proxy URL|B - A-->|Send the cloud drive to the device running OpenList first|D-->|After being forwarded to you by the device running OpenList, your download speed depends on the speed of downloading, uploading, and forwarding on the end where OpenList is built|B -``` - -::: - -::: zh-CN +### 三种模式说明 ```mermaid --- @@ -343,45 +144,12 @@ flowchart LR A-->|云盘先发送给搭建OpenList的设备|D-->|由搭建OpenList的设备转发给你
转发给你之后,你下载速度
取决于搭建OpenList那一端下载然后上传转发的速度|B ``` -::: - -## Download proxy URL { lang="en" } +## 下载代理 URL -## 下载代理 URL { lang="zh-CN" } - -::: en -When the proxy is turned on without filling in this field, the local machine will be used for transfer by default. -::: - -::: zh-CN 开启代理时不填写此字段，默认使用本机进行传输。 -::: - -### 1. Cloudflare Workers { lang="en" } - -### 1. Cloudflare Workers { lang="zh-CN" } - -::: en -Here’s the translation: - -You can use Cloudflare Workers as a proxy. Simply fill in your Cloudflare Workers address here. - -The code to set up Workers can be found at [https://github.com/OpenListTeam/OpenList-Proxy/blob/main/openlist-proxy.js](https://github.com/OpenListTeam/OpenList-Proxy/blob/main/openlist-proxy.js). When using it, you need to replace the following variables: -- `ADDRESS`: Your OpenList address, which must include the protocol header and should not end with a `/`. For example, `https://pan.example.com`. +### 1. Cloudflare Workers -- `TOKEN`: The [Token](../../configuration/other.md#token) of the admin account, which can be found in the “Other Settings” section of the OpenList admin page. - -- `WORKER_ADDRESS`: Your Worker address, which is usually the same as the **Download Proxy URL**. - - :warning: Cloudflare Workers free CDN support is only compatible with **http80** and **https443** ports (whether domestic or international), as tested by group members. - -When filling in the **Download Proxy URL** in the OpenList backend configuration, the link should not end with a `/`. - -Detailed text tutorial:
-For example, if the exported password is `abc123xyz`, it should be entered as `___Obfuscated___abc123xyz` in the Crypt driver. -::: - -::: zh-CN ::: warning 请注意，使用rclone config导出的配置中，密码是混淆后的，无法直接使用，请在密码的前缀中添加 `___Obfuscated___` 后再使用。
例如导出的密码是 `abc123xyz`，则在 Crypt 驱动中应填写 `___Obfuscated___abc123xyz`。 ::: -::: en -Primary encryption key. **Must be remembered** - cannot be recovered if lost. -::: -::: zh-CN 主要加密密钥。**必须牢记** - 丢失后无法恢复。 -::: -#### Salt { lang="en" } +#### 盐值 -#### 盐值 { lang="zh-CN" } - -::: en -::: warning -Note that salts exported using `rclone config` are obfuscated and cannot be used directly. Please prefix the salt with `___Obfuscated___` before use.
-For example, if the exported salt is `abc123xyz`, it should be entered as `___Obfuscated___abc123xyz` in the Crypt driver. -::: - -::: zh-CN ::: warning 请注意，rclone config 导出的配置中，盐值(即password2)是混淆后的，无法直接使用，请在盐值的前缀中添加 `___Obfuscated___` 后再使用。
例如导出的盐值是 `abc123xyz`，则在 Crypt 驱动中应填写 `___Obfuscated___abc123xyz`。 ::: -::: en -Secondary encryption key, acts as an additional password layer. **Must be remembered** - cannot be recovered if lost. - -If you don't know what is salt, treat it as a second password. Optional but recommended - -::: -::: zh-CN 辅助加密密钥，相当于第二层密码保护。**必须牢记** - 丢失后无法恢复。 如果您不知道什么是加盐，可以视为第二个密码。可选，推荐。 -::: - -### Advanced Options { lang="en" } -### 高级选项 { lang="zh-CN" } +### 高级选项 -#### Encrypted Suffix { lang="en" } +#### 加密后缀 -#### 加密后缀 { lang="zh-CN" } - -::: en -**Default:** `.bin` - -Custom suffix for encrypted files (only used when filename encryption is disabled). Must start with a dot (e.g., `.abc`, `.encrypted`). -::: - -::: zh-CN **默认值：** `.bin` 加密文件的自定义后缀（仅在文件名加密禁用时使用）。必须以点开头（例如：`.abc`、`.encrypted`）。 -::: -#### Filename Encoding { lang="en" } +#### 文件名编码 -#### 文件名编码 { lang="zh-CN" } - -::: en -**Default:** `base64` - -**Warning:** Only modify if you understand the implications. Other encoding options are not thoroughly tested and may cause compatibility issues. - -For rclone compatibility, configure this setting in advanced options. -::: - -::: zh-CN **默认值：** `base64` **警告：** 仅在了解其影响时才修改此设置。其他编码选项未经充分测试，可能导致兼容性问题。 为了与 rclone 兼容，请在高级选项中配置此设置。 -::: - -## Advanced Usage { lang="en" } - -## 高级用法 { lang="zh-CN" } -### Rclone Compatibility { lang="en" } +## 高级用法 -### Rclone 兼容性 { lang="zh-CN" } +### Rclone 兼容性 -::: en -The Crypt driver is fully compatible with [rclone crypt](https://rclone.org/crypt). - -**Important Notes:** - -- OpenList Crypt uses `filename_encoding = base64` by default for better long filename support, configure this setting in advanced options when using with rclone -- Case-insensitive filesystems (e.g., Windows with local storage) may cause issues - -::: - -::: zh-CN Crypt 驱动与 [rclone crypt](https://rclone.org/crypt) 目前完全兼容。 **重要说明：** @@ -431,43 +185,16 @@ Crypt 驱动与 [rclone crypt](https://rclone.org/crypt) 目前完全兼容。 - OpenList Crypt 默认使用 `filename_encoding = base64` 以更好地支持长文件名，与 rclone 一起使用时请在高级选项中配置此设置 - 大小写不敏感的文件系统（如 Windows 本地存储）可能会出现问题 -::: - -## Troubleshooting { lang="en" } - -## 故障排除 { lang="zh-CN" } - -### Startup Errors { lang="en" } +## 故障排除 -### 启动错误 { lang="zh-CN" } +### 启动错误 -::: en -If Crypt shows errors during OpenList startup, it's likely because Crypt starts before its target path is available. - -**Solution:** Set a higher [order number](./common.md#order) for the Crypt driver to delay its initialization. -::: - -::: zh-CN 如果 Crypt 在 OpenList 启动时显示错误，可能是因为 Crypt 在其目标路径可用之前就启动了。 **解决方案：** 为 Crypt 驱动设置更高的[序号](./common.md#序号)以延迟其初始化。 -::: -### Data Access Issues { lang="en" } +### 数据访问问题 -### 数据访问问题 { lang="zh-CN" } - -::: en -If you cannot access previously encrypted data: - -1. Verify that the password and salt values are correct -2. Ensure the configuration hasn't been modified -3. Check that the remote path is accessible -4. Confirm the filename encoding setting matches your original configuration - -::: - -::: zh-CN 如果无法访问之前加密的数据： 1. 验证密码和盐值是否正确 @@ -475,33 +202,7 @@ If you cannot access previously encrypted data: 3. 检查远程路径是否可访问 4. 确认文件名编码设置与原始配置匹配 -::: - -## The default download method used { lang="en" } - -## 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - c1 - end - c1[local proxy]:::someclass==default===>a2[user equipment] - classDef someclass fill:#f96 - b1[Download proxy URL]-.alternative.->a2[user equipment] - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +## 默认使用的下载方式 ```mermaid --- @@ -519,5 +220,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/degoo.md b/pages/guide/drivers/degoo.md index 3bce42b64..4b03b83c3 100644 --- a/pages/guide/drivers/degoo.md +++ b/pages/guide/drivers/degoo.md @@ -1,25 +1,14 @@ --- -title: - en: Degoo - zh-CN: Degoo categories: - guide - drivers top: 587 --- -https://degoo.com/ - -::: en -**Authentication methods**: +# Degoo -1. Username + Password -2. Refresh Token -3. Access Token +https://degoo.com/ -In normal cases, you can log in with your username + password. If you encounter a 429 error, you can log in using tokens. You can obtain the token from the request body or header in your browser. -::: -::: zh-CN **鉴权方式**： 1. 用户名 + 密码 @@ -27,79 +16,24 @@ In normal cases, you can log in with your username + password. If you encounter 3. 访问令牌 正常情况下，可以使用用户名 + 密码进行登录。如果您遇到了429错误，可以使用令牌登录。您可以从浏览器的请求内容或头部中获取访问令牌。 -::: -## Username { lang="en" } +## 用户名 -## 用户名 { lang="zh-CN" } - -::: en -Your user's name. -::: -::: zh-CN 您的用户名。 -::: - -## Password { lang="en" } -## 密码 { lang="zh-CN" } +## 密码 -::: en -Your user's password. -::: -::: zh-CN 您用户的密码。 -::: - -## Refresh Token { lang="en" } -## 刷新令牌 { lang="zh-CN" } +## 刷新令牌 -::: en -Refresh token for automatic token renewal, obtained automatically. -::: -::: zh-CN 用于自动更新令牌的刷新令牌，自动获取。 -::: -## Access Token { lang="en" } +## 访问令牌 -## 访问令牌 { lang="zh-CN" } - -::: en -Access token for Degoo API, obtained automatically. -::: -::: zh-CN Degoo API 访问令牌，自动获取。 -::: - -## The default download method used { lang="en" } - -## 默认使用的下载方式 { lang="zh-CN" } -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +## 默认使用的下载方式 ```mermaid --- @@ -119,5 +53,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/develop.md b/pages/guide/drivers/develop.md index 9d920a5ff..0edceb634 100644 --- a/pages/guide/drivers/develop.md +++ b/pages/guide/drivers/develop.md @@ -1,30 +1,11 @@ --- -title: - en: Contribute new storage driver - zh-CN: 贡献新存储驱动 -icon: iconfont icon-code -# This control sidebar order top: 100 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - Develop -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- -::: en -Duplicate `drivers/template` to expand the new storage. Please read [CONTRIBUTING](https://github.com/OpenListTeam/OpenList/blob/main/CONTRIBUTING.md) for details. -The design of the driver part of OpenList is easy to expand, no need to modify other files, just create a new package under the back-end project drivers package and reference this package in the `all.go` file. -::: -::: zh-CN +# 贡献新存储驱动 + 复制 `drivers/template` 以扩展新存储。 请阅读 [CONTRIBUTING](https://github.com/OpenListTeam/OpenList/blob/main/CONTRIBUTING.md) 了解详情。 OpenList 的驱动部分的设计很容易扩展，不需要修改其他文件，只需在后端项目驱动包下新建一个包，在 `all.go` 文件中引用这个包即可。 -::: diff --git a/pages/guide/drivers/doubao.md b/pages/guide/drivers/doubao.md index 1d0e67431..f8fc67d4b 100644 --- a/pages/guide/drivers/doubao.md +++ b/pages/guide/drivers/doubao.md @@ -1,36 +1,16 @@ --- -title: - en: Doubao Drive - zh-CN: 豆包云盘 -icon: iconfont icon-state -# This control sidebar order top: 676 -# A page can have multiple categories categories: - guide - drivers --- - +# 豆包云盘 -::: en -Mount [Doubao Drive](https://www.doubao.com/chat/drive/) cloud storage. + -::: -::: zh-CN 挂载 [豆包云盘](https://www.doubao.com/chat/drive/) 云存储。 -::: - -::: en -::: danger Security Risk - -Do not use 302 if the storage is public accessible. -Otherwise, the download link may leak sensitive information such as access token or signature. -Others may use the leaked link to **access all your files**. - -::: -::: zh-CN ::: danger 安全风险 若存储可公开访问，则请勿使用302重定向。 @@ -39,41 +19,14 @@ Others may use the leaked link to **access all your files**. ::: -## Root folder ID { lang="en" } - -## 根文件夹ID { lang="zh-CN" } +## 根文件夹ID -::: en -The root folder ID is the parameter value displayed in the address bar when accessing Doubao Drive via a web page. For example, after accessing [Doubao Drive](https://www.doubao.com/chat/drive/), the address bar shows `https://www.doubao.com/chat/drive/AAAAAAAAAAAAAAAAAAAAAAAAAA?tab=myUpload`, where `AAAAAAAAAAAAAAAAAAAAAAAAAA` is the root folder ID. - - -::: - -::: zh-CN 根文件夹ID即为网页访问豆包云盘时地址栏中的参数值，例如访问[豆包云盘](https://www.doubao.com/chat/drive/)后，地址栏显示为`https://www.doubao.com/chat/drive/AAAAAAAAAAAAAAAAAAAAAAAAAA?tab=myUpload`，其中`AAAAAAAAAAAAAAAAAAAAAAAAAA`即为根文件夹ID。  -::: - -## Cookie { lang="zh-CN" } - -## Cookie { lang="en" } - -::: en -Required. Web cookie. Used to refresh token and extract Authorization/DPoP tokens. -Open browser developer tools, visit [Doubao Drive](https://www.doubao.com/drive/), log in to your account, check the `Network` tab, search for `biz_auth` and open it, find `Cookie` in the `Header`, copy the complete value and fill it in. - - - -OpenList will automatically extract other attributes from the Cookie. Please ensure that the Cookie contains the following key-value pairs: - -- `LARK_SUITE_DPOP` -- `LARK_SUITE_ACCESS_TOKEN` -- `feishu_dpop_keypair` (used for key generation, optional) +## Cookie -::: -::: zh-CN 必填，网页 Cookie。用于刷新 Token 和提取 Authorization/DPoP Token。 打开浏览器开发者工具，访问 [豆包云盘](https://www.doubao.com/drive/)，登录账号后，查看`Network`（网络）Tab，搜索 `biz_auth` 并打开它，在 `Header`（标头）中找到 `Cookie`，复制其完整值填入即可。 @@ -86,56 +39,20 @@ OpenList 会自动从 Cookie 中提取其他属性。请确保 Cookie 中包含 - `LARK_SUITE_ACCESS_TOKEN` - `feishu_dpop_keypair` （用于密钥生成，可选） -::: - -## App ID { lang="en" } - -## App ID { lang="zh-CN" } - -::: en -必填，Doubao's App ID. The App ID may vary for different clients, please refer to the actual value. -::: +## App ID -::: zh-CN 必填，豆包的App ID。不同客户端的App ID可能不相同，请以实际为准。 -::: - -## DPoP Key Secret, Auth Client ID, Auth Scope, Auth SDK Source, Auth SDK Version { lang="en" } -## DPoP 密钥、认证客户端ID、认证区域、认证SDK来源、认证SDK版本 { lang="zh-CN" } - -::: en -Optional, for Token refresh. Please obtain it yourself, and refer to the actual value. -::: +## DPoP 密钥、认证客户端ID、认证区域、认证SDK来源、认证SDK版本 -::: zh-CN 可选，用于刷新 Token。请自行获取，以实际为准。 -::: - -## Share Link { lang="en" } - -## 分享链接 { lang="zh-CN" } -::: en -Whether to use share link for download. If enabled, OpenList will create share and request with anonymous user's token to create download link. This can reduce authorization leak. - -Please ensure you have filled all authentication options above before enabling this function. -::: +## 分享链接 -::: zh-CN 是否使用分享链接下载。启用后，OpenList 将创建分享然后使用匿名用户Token请求创建下载链接以减少授权泄露。 请确保您在启用此功能前已经填写了上面的所有认证参数。 -::: - -## Ignore JWT Check { lang="en" } -## 忽略 JWT 检查 { lang="zh-CN" } +## 忽略 JWT 检查 -::: en -Whether to ignore JWT check to prevent time issue -::: - -::: zh-CN 是否忽略 JWT 检查以避免时间问题。 -::: diff --git a/pages/guide/drivers/dropbox.md b/pages/guide/drivers/dropbox.md index dca3db801..7b8adec66 100644 --- a/pages/guide/drivers/dropbox.md +++ b/pages/guide/drivers/dropbox.md @@ -1,77 +1,15 @@ --- -title: - en: Dropbox - zh-CN: Dropbox -icon: iconfont icon-state -# This control sidebar order top: 590 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - '302' -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- -::: en -Dropbox Official：https://www.dropbox.com/ -::: -::: zh-CN -Dropbox官网：https://www.dropbox.com/ -::: - -## Get refresh token { lang="en" } - -## 获取刷新令牌 { lang="zh-CN" } - -::: en - -- **This drive does not support the online API mode provided by OpenList.** - -- The following tutorial applies when the option is kept disabled as shown below. - -  - -- If you create your own `Client ID` and `Secret`, remember to authorize them. - -The steps are as follows: - -1. First, [click here](https://www.dropbox.com/developers/apps?_tk=pilot_lp&_ad=topbar4&_camp=myapps) to enter the Dropbox app management page and click "Create App". - -  - -2. After entering the app, configure the app type as shown below. - -  - -3. You can get the id and secret in the red box: the upper one is the id, the lower one is the secret. - -  - -4. Configure the callback URL. If you are strict about permissions and do not want to use an external callback address, you can set a local address here, or use the one outside the red box. - -  - -5. Finally, go to the permissions configuration page to set the app's permissions. - -  - -6. [Click here](https://api.oplist.org/) to enter the token acquisition tool. Select Dropbox, fill in your id and secret, and after authorization you can get the refresh token. - -7. In the OpenList configuration page, enter the refresh token, id, and secret to use. Note that the refresh token is about 40-50 characters long. +# Dropbox - - -::: +Dropbox官网：https://www.dropbox.com/ -::: zh-CN +## 获取刷新令牌 - **该驱动并不支持由 OpenList 提供的 online api 模式！** @@ -109,18 +47,6 @@ The steps are as follows:  -::: - -::: en -If you are highly privacy-conscious, Dropbox supports local callback. You can use the following script provided by GPT to quickly implement it, communicating only with Dropbox servers. - -::: warning -Since the callback address is local and you have not set up a real local callback server, please manually copy the authorization code from the browser address bar. - -**Please resolve Python environment issues yourself, or use the callback server provided above.** -::: - -::: zh-CN 如果你有强烈的隐私意识，dropbox支持本地回调，可以使用以下全程由GPT提供的脚本快速实现，只和dropbox的服务器进行通信。 ::: warning @@ -129,48 +55,6 @@ Since the callback address is local and you have not set up a real local callbac **请自行解决py运行的环境问题，或者使用上面搭建好的回调服务器** ::: -::: en - -```python -import requests -import webbrowser -# Please replace with your own Dropbox App information -CLIENT_ID = 'your_app_key' -CLIENT_SECRET = 'your_app_secret' -REDIRECT_URI = 'http://localhost:114514' -# Step 1: Get authorization code -auth_url = ( - f"https://www.dropbox.com/oauth2/authorize" - f"?client_id={CLIENT_ID}" - f"&redirect_uri={REDIRECT_URI}" - f"&response_type=code" - f"&token_access_type=offline" # Required: key parameter to get refresh_token -) -print("👉 Please visit the following link to authorize:\n") -print(auth_url) -webbrowser.open(auth_url) -auth_code = input("\n✅ After authorization, paste the code after ?code= in the redirected URL here:\n> ").strip() -# Step 2: Exchange for access_token + refresh_token -token_url = "https://api.dropboxapi.com/oauth2/token" -data = { - 'code': auth_code, - 'grant_type': 'authorization_code', - 'client_id': CLIENT_ID, - 'client_secret': CLIENT_SECRET, - 'redirect_uri': REDIRECT_URI -} -response = requests.post(token_url, data=data) -response.raise_for_status() -tokens = response.json() -# ✅ Only output the refresh token -print("\n🎉 Success! Your Dropbox refresh_token is:\n") -print(tokens.get("refresh_token")) -``` - -::: - -::: zh-CN - ```python import requests import webbrowser @@ -207,50 +91,13 @@ print("\n🎉 获取成功！你的 Dropbox refresh_token 是：\n") print(tokens.get("refresh_token")) ``` -::: - -## Root folder file_id { lang="en" } +## 根文件夹ID -## 根文件夹ID { lang="zh-CN" } - -::: en -**Empty is the root directory**：display all files -**Single folder ID**：Enter the folder you need to display, copy the top link to fill in `/home` behind - -::: -::: zh-CN 空为根目录：挂载全部文件 单文件夹ID：进入你需要挂载的文件夹复制顶部链接将`/home`后面的填写进去即可  -::: - -### The default download method used { lang="en" } - -### 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` -::: -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -270,5 +117,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/emby.md b/pages/guide/drivers/emby.md index 684ea3477..f29071a3d 100644 --- a/pages/guide/drivers/emby.md +++ b/pages/guide/drivers/emby.md @@ -1,136 +1,54 @@ --- -title: - en: Emby - zh-CN: Emby -icon: iconfont icon-state -# This control sidebar order top: 493 -# A page can have multiple categories categories: - guide - drivers --- -::: en -Mount media resources from an Emby server. -::: -::: zh-CN -挂载 Emby 服务器中的媒体资源。 -::: +# Emby -## URL { lang="en" } +挂载 Emby 服务器中的媒体资源。 -## URL 服务器地址 { lang="zh-CN" } +## URL 服务器地址 -::: en -Emby server address, for example: `http://127.0.0.1:8086`. -::: -::: zh-CN Emby 服务器地址，例如：`http://127.0.0.1:8086`。 -::: - -## ApiKey { lang="en" } -## ApiKey { lang="zh-CN" } +## ApiKey -::: en -Emby API Key. Use together with `UserID` for API authentication. -::: -::: zh-CN Emby API Key。与 `UserID` 搭配使用进行 API 认证。 -::: -## UserID { lang="en" } +## UserID -## UserID { lang="zh-CN" } - -::: en -Emby user ID. Used with `ApiKey`. -::: -::: zh-CN Emby 用户 ID。与 `ApiKey` 搭配使用。 -::: - -## Username { lang="en" } -## 用户名 { lang="zh-CN" } +## 用户名 -::: en -Emby account username. Used with `Password`. -::: -::: zh-CN Emby 账号用户名。与 `Password` 搭配使用。 -::: -## Password { lang="en" } +## 密码 -## 密码 { lang="zh-CN" } - -::: en -Emby account password. Used with `Username`. -::: -::: zh-CN Emby 账号密码。与 `Username` 搭配使用。 -::: - -## LinkMethod { lang="en" } - -## 链接方式 LinkMethod { lang="zh-CN" } -::: en -Choose link method: +## 链接方式 LinkMethod -- `stream`: Streaming link (recommended) -- `download`: Direct download link - -Some Emby servers do not grant download permission. In that case, please use `stream`. -::: -::: zh-CN 选择链接方式： - `stream`：串流链接（推荐） - `download`：下载链接 有些 Emby 服务器未开放下载权限，此时请使用 `stream`。 -::: - -## Authentication Method { lang="en" } -## 认证方式 { lang="zh-CN" } +## 认证方式 -::: en -Use **one** of the following login methods: - -1. `ApiKey + UserID` -2. `Username + Password` - -Do not mix both methods at the same time. -::: -::: zh-CN 登录方式二选一： 1. `ApiKey + UserID` 2. `Username + Password` 请不要同时混用两种方式。 -::: - -## Example Configuration { lang="en" } -## 配置示例 { lang="zh-CN" } - -::: en - -- URL: `http://127.0.0.1:8086` -- LinkMethod: `stream` -- Authentication: choose one method only - -::: - -::: zh-CN +## 配置示例 - URL：`http://127.0.0.1:8086` - LinkMethod：`stream` - 认证方式：仅选择其中一种 - -::: diff --git a/pages/guide/drivers/febbox.md b/pages/guide/drivers/febbox.md index f1b4994a5..8a8affa4a 100644 --- a/pages/guide/drivers/febbox.md +++ b/pages/guide/drivers/febbox.md @@ -1,54 +1,19 @@ --- -title: - en: FebBox - zh-CN: FebBox -icon: iconfont icon-state -# This control sidebar order top: 591 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - '302' -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- -::: en -FebBox：https://www.febbox.com - -- The upload function is currently unavailable. +# FebBox -::: -::: zh-CN FebBox：https://www.febbox.com - 需要代理，直连似乎无法访问？ - 目前上传功能不可用 -::: - -## Root folder ID { lang="en" } - -## 根文件夹ID { lang="zh-CN" } - -::: en -Root directory ID, default is `0`. +## 根文件夹ID -Other directory IDs can be viewed in the top link address bar after entering the folder. - -- **https://www.febbox.com/console#/files?parent_id=66889900** - - Then the directory ID is `66889900` - -::: -::: zh-CN 根目录ID，默认为`0`。 其它目录 ID 查看进入文件夹后看顶部链接地址栏。 @@ -57,74 +22,21 @@ Other directory IDs can be viewed in the top link address bar after entering the 那这个目录 ID 就是 `66889900` -::: - -## `Client_id`、`Client_secret` { lang="en" } +## 客户端 ID 和 秘钥 -## 客户端 ID 和 秘钥 { lang="zh-CN" } - -::: en -Generate address：**https://www.febbox.com/open/clients** - -- The generated client ID and secret key are filled in in the opposite order to the OpenList, so be careful not to fill them in incorrectly. - -  - -::: -::: zh-CN 生成地址：**https://www.febbox.com/open/clients** - 生成的客户端 ID 和秘钥和 OpenList 填写的顺序是相反的，注意别填错  -::: - -## User IP { lang="en" } - -## 用户 IP { lang="zh-CN" } - -::: en -**Optional**, the IP address of the user when downloading, quoting the official description - -> IP address, Optional parameter. Supports IPv6 format. After filling in, the best download server suitable for the IP location will be selected. If not filled in, the requested IP will be used. +## 用户 IP -::: - -::: zh-CN **可选** ，用户下载时的 IP，引用官方说明 > IP 地址，可选参数。支持 IPv6 格式。填写后，将选择适合 IP 位置的最佳下载服务器。如果未填写，将使用请求的 IP。 -::: - -## The default download method used { lang="en" } - -## 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +## 默认使用的下载方式 ```mermaid --- @@ -144,5 +56,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/feiji.md b/pages/guide/drivers/feiji.md index 317bd54df..646fdc622 100644 --- a/pages/guide/drivers/feiji.md +++ b/pages/guide/drivers/feiji.md @@ -1,101 +1,34 @@ --- -title: - en: FeiJi Cloud - zh-CN: 小飞机网盘 -icon: iconfont icon-state -# This control sidebar order top: 686 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - '302' -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- +# 小飞机网盘 + **https://feijipan.com/** -::: en -::: danger -Feiji Cloud imposes login restrictions on 3rd-party platforms. Attempting to access its service via OpenList may result in your account being banned. Please proceed with caution! -::: - -::: zh-CN ::: danger 小飞机网盘对第三方平台有登录限制，尝试登录极易封号，请谨慎使用！ ::: -## Root folder ID { lang="en" } +## 根文件夹ID -## 根文件夹ID { lang="zh-CN" } - -::: en -root folder ID the default is `0`，Other directory ID View the figure below obtaining method - -::: -::: zh-CN 根目录ID，默认为`0`，其它目录ID查看下图获取方式  -::: -## username、password { lang="en" } +## 账户、密码 -## 账户、密码 { lang="zh-CN" } - -::: en -Just fill in your own Feiji Cloud Account Password -::: -::: zh-CN 填写自己的小飞机网盘帐号密码 -::: - -## Known issues { lang="en" } -## 已知问题 { lang="zh-CN" } +## 已知问题 -::: en -The file size returned by iLanZou is in Kilo Bytes, not Bytes. Therefore, you cannot accurately determine if a file has been modified based on its size. Please pay attention to the configuration of your sync software. -::: -::: zh-CN 蓝奏云优享版返回的文件大小非 Bytes，而是 Kilo Bytes，因此无法使用文件大小准确判断一个文件是否被修改，需要注意同步软件的配置。 -::: - -## The default download method used { lang="en" } - -## 默认使用的下载方式 { lang="zh-CN" } -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +## 默认使用的下载方式 ```mermaid --- @@ -115,5 +48,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/ftp.md b/pages/guide/drivers/ftp.md index 3a12fb35f..f511964b9 100644 --- a/pages/guide/drivers/ftp.md +++ b/pages/guide/drivers/ftp.md @@ -1,106 +1,33 @@ --- -title: - en: FTP - zh-CN: FTP -icon: iconfont icon-state -# This control sidebar order top: 898 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - '本地代理' -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- -### Address { lang="en" } +# FTP -## 地址 { lang="zh-CN" } +## 地址 -::: en -FTP address, need contains port. -::: -::: zh-CN FTP 地址，需要包含端口。 -::: -### Username { lang="en" } +## 用户名 -## 用户名 { lang="zh-CN" } - -::: en -FTP username -::: -::: zh-CN FTP 用户名 -::: - -### Password { lang="en" } -## 密码 { lang="zh-CN" } +## 密码 -::: en -FTP password -::: -::: zh-CN FTP 密码 -::: - -### Root folder path { lang="en" } -## 根文件夹ID { lang="zh-CN" } +## 根文件夹ID -::: en -root folder , default `/`, same as local storage. -::: -::: zh-CN 根文件夹，默认 `/`，同本地存储。 -::: -## Enter directory before listing { lang="en" } +## 列出前先进入目录 -## 列出前先进入目录 { lang="zh-CN" } - -::: en -Whether to change into the target directory before listing files. Some FTP servers do not support listing files with a path argument directly. Enable this option to first `cd` into the directory and then `ls`, which can resolve such compatibility issues. Default: `false`. -::: - -::: zh-CN 是否在列出文件前先进入目标目录。部分 FTP 服务器不支持直接带路径参数列出文件，开启此选项后会先 `cd` 进入目录再 `ls`，可以解决此类兼容性问题。默认: `false`。 -::: - -### The default download method used { lang="en" } -### 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - c1 - end - c1[local proxy]:::someclass==default===>a2[user equipment] - classDef someclass fill:#f96 - b1[Download proxy URL]-.alternative.->a2[user equipment] - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -118,5 +45,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/github.md b/pages/guide/drivers/github.md index 99a78fedf..a2a38ac38 100644 --- a/pages/guide/drivers/github.md +++ b/pages/guide/drivers/github.md @@ -1,36 +1,12 @@ --- -title: - en: GitHub API - zh-CN: GitHub API -icon: iconfont icon-state -# This control sidebar order top: 399 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - '302' - - '官方' -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- -::: en -::: tip -GitHub API does not support operating files larger than 100MiB and folders containing more than 100,000 sub-items. - -All `.gitkeep` files will be managed by the driver and will be invisible to the user. - -Operations on submodules are currently not supported. -::: +# GitHub API -::: zh-CN ::: tip GitHub API 不支持操作 100M 或更大的文件，不支持操作含有超过 100,000 个子文件（夹）的文件夹。 @@ -39,28 +15,7 @@ GitHub API 不支持操作 100M 或更大的文件，不支持操作含有超过 本驱动暂不支持操作子模块。 ::: -## Token { lang="en" } - -## Token { lang="zh-CN" } - -::: en - -1. Log in GitHub and visit
-::: - -## 2FA { lang="en" } -## 两步验证 { lang="zh-CN" } +## 两步验证 -::: en -Non -filling options,If you open 2FA, you need to fill in it,If you don’t use 2FA, you don’t need to fill in it -::: -::: zh-CN 非必填选项，如果开启了需要填写，没开启的不需要填写 -::: - -### Two fa secret { lang="en" } -### 两步验证秘钥 { lang="zh-CN" } +### 两步验证秘钥 -::: en -**https://mega.nz/fm/account/security/two-factor-authentication** -Click to enable `Enable two-factor authentication (2FA)` and then see a QR code, there is a string of letters below the QR code, This is `Two fa secret`, please record before scanning the code and do not lose it, Should the `Two-factor authentication (2FA) secret` be lost, you can unbinding and then retrieve a new 2FA QR code for setup. - -::: -::: zh-CN **https://mega.nz/fm/account/security/two-factor-authentication** 点击启用 `启用双重验证（2FA）`然后会看到一个二维码，二维码下方有一串字母，这个就是`2FA验证秘钥`，请在扫码绑定前记录一下切勿丢失，`2FA验证秘钥`如果丢失可以解绑重新获取一个新的  -::: - -### Two fa code { lang="en" } -### 两步验证代码 { lang="zh-CN" } +### 两步验证代码 -::: en -To enable 2-factor authentication, you need to install a app that support 2FA (such as [Google Authenticator](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2), [Microsoft Authenticator](https://support.microsoft.com/en-us/account-billing/download-and-install-the-microsoft-authenticator-app-351498fc-850a-45da-b7b6-27e523b8702a)), on your phone. -Then login to OpenList manage and goto `Profile` page, click `Enable 2FA` button, scan the QR code with your 2FA app, and enter the code generated by your 2FA app. -Scan the QR appearing on the screen. At the same time, this QR code is also [two-fa-secret](#two-fa-secret) - -
-::: -::: zh-CN 要启用双因素身份验证，需要在手机上安装支持 TOTP 的验证器，例如 [Google Authenticator](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2)，[Microsoft Authenticator](https://support.microsoft.com/zh-cn/account-billing/%E4%B8%8B%E8%BD%BD%E5%B9%B6%E5%AE%89%E8%A3%85microsoft-authenticator%E5%BA%94%E7%94%A8-351498fc-850a-45da-b7b6-27e523b8702a) 扫描屏幕出现的二维码就可以，同时这个二维码也是[两步验证秘钥](#两步验证秘钥) 
-::: -## Fill in example: { lang="en" } +## 填写示例 -## 填写示例 { lang="zh-CN" } - -::: en - -
-::: -::: zh-CN 
-::: - -### The default download method used { lang="en" } -### 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - c1 - end - c1[local proxy]:::someclass==default===>a2[user equipment] - classDef someclass fill:#f96 - b1[Download proxy URL]-.alternative.->a2[user equipment] - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -159,5 +62,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/misskey.md b/pages/guide/drivers/misskey.md index 8b7d28775..2fa23981d 100644 --- a/pages/guide/drivers/misskey.md +++ b/pages/guide/drivers/misskey.md @@ -1,45 +1,17 @@ --- -title: - en: Misskey Drive - zh-CN: Misskey Drive -icon: iconfont icon-state -# This control sidebar order top: 588 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - '302' -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- -## Instance URL { lang="en" } +# Misskey Drive -## 实例地址 { lang="zh-CN" } +## 实例地址 -::: en -The URL of your Misskey instance, whether self-hosted or in use. -For example, the official instance at `https://misskey.io` -::: -::: zh-CN 自行部署的或正在使用的Misskey实例地址 例如官方实例`https://misskey.io` -::: -## Token { lang="en" } +## Token -## Token { lang="zh-CN" } - -::: en -Visit `https://{misskey-instance}/settings/api` to generate an access token. It requires the `read:drive` and `write:drive` permissions. -::: -::: zh-CN 前往`https://{misskey-instance}/settings/api`生成访问token，需要`read:drive`及`write:drive`权限。 -::: diff --git a/pages/guide/drivers/mopan.md b/pages/guide/drivers/mopan.md index 3814f25e8..00e006d12 100644 --- a/pages/guide/drivers/mopan.md +++ b/pages/guide/drivers/mopan.md @@ -1,114 +1,34 @@ --- -title: - en: MoPan - zh-CN: 四川电信魔盘 -icon: iconfont icon-state -# This control sidebar order top: 691 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - '302' -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- - - -::: en -MoPan address：**https://mopan.sc.189.cn/mopan/#/downloadPc** +# 四川电信魔盘 -- There is no web version, only `Android`, `iOS`, `PC-Win64bit`, `iPad`, and `TV`. - -::: + -::: zh-CN 四川电信魔盘官网链接：**https://mopan.sc.189.cn/mopan/#/downloadPc** - 没有网页端，只有`Android`,`IOS`,`PC-Win64位`,`iPad`,`TV` -::: +## Sms code -## Sms code { lang="en" } - -## Sms code { lang="zh-CN" } - -::: en -Enter the option of the mobile phone number and password when the first addition, and then enter the `SMS Code` input `send`, and then click Save to send it to you. -::: -::: zh-CN 第一次添加时先输入 手机号和密码的选项，然后在`Sms Code`输入 `send`，再点击保存会给你进行发短信，然后将验证码重新输入就可以添加 -::: - -## Root folder ID { lang="en" } - -## 根文件夹ID { lang="zh-CN" } -::: en -Do not fill in this option, it will automatically fill into the root directory +## 根文件夹ID -- Due to encrypted requests, an appropriate method for obtaining folder IDs has not yet been found - -::: -::: zh-CN 留空会自动填充为根目录 - 由于请求加密，暂时未想到合适的获取文件夹 ID 的方法 -::: - -### Tips { lang="en" } - -## 提示 { lang="zh-CN" } - -::: en - -1. `root folder ID`,`equipment information`does not need to be filled in, will automatically help you fill -2. If you enter the send in [SMS Code] (#SMS-Code), it is found that it has been saved,Please click Edit to enter the verification code received - -::: - -::: zh-CN +## 提示 1. `根文件夹ID`、`设备信息`不用填写,会自动帮你填充 2. 如果在[Sms Code](#sms-code)输入验证码后已经保存了，请进入编辑输入收到的验证码 -::: - -### The default download method used { lang="en" } - -### 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -128,5 +48,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/onedrive.md b/pages/guide/drivers/onedrive.md index 345279756..0dd38fa35 100644 --- a/pages/guide/drivers/onedrive.md +++ b/pages/guide/drivers/onedrive.md @@ -1,25 +1,12 @@ --- -title: - en: OneDrive / Share - zh-CN: OneDrive / 分享 -icon: iconfont icon-state -# This control sidebar order top: 599 -# A page can have multiple categories categories: - guide - drivers --- -:::en -:::tip - -- If you have global administrator permissions for a non-home edition, you can use the [OneDrive APP](onedrive_app.md) driver. -- If your account does not support the API, (for example, the school account has not verified the administrator, or the administrator has disabled the API), then you can also mount it through webdav. For details, see [webdav](webdav.md) - -::: +# OneDrive / 分享 -:::zh-CN :::tip - 如果你拥有非家庭版的全局管理员权限，可使用 [OneDrive APP](onedrive_app.md) 驱动 @@ -27,25 +14,8 @@ categories: ::: -## 1. Mounting using Online API's default application { lang="en" } - -## 1. 使用在线 API 的默认应用挂载 { lang="zh-CN" } - -::: en -You do not need to create an application yourself by mounting in this way. - -1. Open
-Then enter https://www.terabox.com in the address bar of this tab to enter the webpage, you can see the reserved request, and then find **`Cookie`** from the reserved request. - -
-::: -::: zh-CN ~~[**点此登录**](https://www.terabox.com/)进行获取刷新令牌，随意找一个请求即可找到 **`Cookie`**~~ 由于目前网页端已经禁用了F12，我们可以先在别的页面打开F12将 `网络` → `保留日志` 选项打开
然后在从这个标签页地址栏输入 https://www.terabox.com 进入网页，就能看到保留的请求，再从保留的请求找找到 **`Cookie`** 
-::: -## Download Api { lang="en" } +## 下载接口 -## 下载接口 { lang="zh-CN" } - -::: en -**Download api needs to choose `Crack`** ，before you can use -
-::: -::: zh-CN **下载接口需要选择 `非官方`** ，才可以使用
-::: - -## Root folder id { lang="en" } - -## 根文件夹ID { lang="zh-CN" } - -::: en -- Root folder id is `/` -- Mount other single subdirectories, put a picture for reference - -
-
-:::
-
-::: zh-CN
+## 根文件夹ID
- 根目录为 `/`
- 挂载其他单个子目录，放一张图参考一下吧
-
-:::
-
-## Download error using Proxy Url link { lang="en" }
-
-## 使用Proxy Url链接下载错误 { lang="zh-CN" }
-
-::: en
-Using [**Proxy Url**](common.md#download-proxy-url) to download error
-
-```json
-{
- "error_code": 31211,
- "error_msg": "access denied"
-}
-```
+## 使用Proxy Url链接下载错误
-View specific reasons：**[https://github.com/alist-org/alist/issues/6508](https://github.com/alist-org/alist/issues/6508#issuecomment-2171762705)**
--::: -::: zh-CN 使用了[**Proxy Url**](common.md#下载代理-url)进行下载报错 ```json @@ -107,35 +44,8 @@ View specific reasons：**[https://github.com/alist-org/alist/issues/6508](https 具体原因查看：**[https://github.com/alist-org/alist/issues/6508](https://github.com/alist-org/alist/issues/6508#issuecomment-2171762705)**
-::: - -## The default download method used { lang="en" } - -## 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` -::: -::: zh-CN +## 默认使用的下载方式 ```mermaid --- @@ -155,5 +65,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/thunder.md b/pages/guide/drivers/thunder.md index 970a3274d..cfc931003 100644 --- a/pages/guide/drivers/thunder.md +++ b/pages/guide/drivers/thunder.md @@ -1,41 +1,14 @@ --- -title: - en: Thunder Cloud Disk - zh-CN: 迅雷云盘 / X / 浏览器 -icon: iconfont icon-state -# This control sidebar order top: 685 -# A page can have multiple categories categories: - guide - drivers --- - - -::: en -::: tip -Please use `Thunder` directly instead of `ThunderExpert` if you are not good at it. - -`ThunderExpert` mainly provides more free settings and realizes more login methods - ---- - -`Thunder X` serves overseas users. As of the time of document release, only the Android version is available. Other versions have not yet been released. - -- Thunder X has sufficient speed even without membership. Future changes are unknown. -- Using the APP may require a proxy, but not when mounted on OpenList. - ---- - -`Thunder Browser`：Currently only supports mobile phones (Android, iOS) - -- **https://x.xunlei.com/** -- If you log in to OpenList, the mobile phone will be kicked offline. On the contrary, if you log in to OpenList first and then log in to the mobile phone, OpenList will be kicked offline but there will be no prompt +# 迅雷云盘 / X / 浏览器 -::: + -::: zh-CN ::: tip `迅雷` 前两个是服务**国内用户** @@ -59,72 +32,23 @@ Please use `Thunder` directly instead of `ThunderExpert` if you are not good at ::: -## 1. Thunder { lang="en" } - -## 1. 迅雷 { lang="zh-CN" } - -### Username { lang="en" } +## 1. 迅雷 -### 用户名 { lang="zh-CN" } +### 用户名 -::: en -That is, the mobile phone number, email, and username used for login (there is a probability that you cannot log in, you need to try) - -1. Before obtaining the verification code, do not include the `+86` country code when entering the phone number. -2. After obtaining the verification code, the phone number must include the `+86` country code, for example: +8613722223333. - -::: - -::: zh-CN 即用于登陆的手机号,邮箱,用户名(有概率无法登录,需要尝试) 1. 在获取验证码之前填写手机号先不要携带 `+86` 区号 2. 获取验证码后填写需要携带 `+86` 区号，例如 +8613722223333 这样填写 -::: - -### Password { lang="en" } +### 密码 -### 密码 { lang="zh-CN" } - -::: en -password for login -::: -::: zh-CN 即用于登陆的密码 -::: -
- -### Credit Key { lang="en" } - -### 信用密钥 { lang="zh-CN" } - -::: en -After saving for the first time, an error will occur. This is normal. Please go to the storage management interface. - - - -Copy all the content above. - -[Click here to enter](https://i.xunlei.com/xlcaptcha/android.html) -After entering, open the developer tools (usually by pressing F12), go to the console, and enter `reviewCb()`. **Paste all the previously copied content, including the curly braces,** inside the parentheses, as shown below: - - - -Move the cursor to **after the parentheses** and press Enter. - - - -The webpage will automatically redirect to the mobile number verification page. - -After completing the verification, the page **will not** refresh automatically. Please check the console. The `creditkey` shown below is the required key. - +
-Copy it to the storage management, and you can mount it normally. +### 信用密钥 -::: -::: zh-CN 在第一次保存后会产生报错，这是正常的，请返回存储管理界面  @@ -149,34 +73,7 @@ Copy it to the storage management, and you can mount it normally. 将其复制到存储管理后即可正常挂载 -::: - -### 默认使用的下载方式 { lang="zh-CN" } - -### The default download method used { lang="en" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - c1 - end - c1[local proxy]:::someclass==default===>a2[user equipment] - classDef someclass fill:#f96 - b1[Download proxy URL]-.alternative.->a2[user equipment] - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: - -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -195,65 +92,20 @@ flowchart TB click c1 "../drivers/common.html#webdav-策略" ``` -::: - -## 2. 迅雷专家版 { lang="zh-CN" } +## 2. 迅雷专家版 -## 2. ThunderExpert { lang="en" } - -::: en -::: tip -If Xunlei needs to download, you must specify UserAgent (same as DownUserAgent below). Or use the proxy function in this program to transfer. -::: -::: zh-CN ::: tip 迅雷如果需要下载必须指定 UserAgent(同下 DownUserAgent)，或使用本程序中的代理功能进行中转。 ::: -### 登录类型 { lang="zh-CN" } - -### Login Type { lang="en" } - -::: en - -1. When selecting User, you only need to fill in the username and password - - User You need to bring the `+86` area code, for example +8613722223333 fill in like this -2. **RefreshToken**: Just fill in RefreshToken when selecting RefreshToken - -::: - -::: zh-CN +### 登录类型 1. 选择 `用户名` 时填用户名和密码 - 用户名需要携带 `+86` 区号，例如 +8613722223333 这样填写 2. 选择 `刷新令牌` 时只需填写 `刷新令牌` -::: +### 签名类型 -### 签名类型 { lang="zh-CN" } - -### Signature Type { lang="en" } - -::: en -**Algorithms**：When selecting Algorithms, just fill in the Algorithms (it is difficult to obtain, and needs to be reversed) - -**Captcha sign**: Only fill in CaptchaSign and Timestamp when selecting CaptchaSign - -``` -//signature algorithm -str = ClientID + ClientVersion + PackageName + DeviceID + Timestamp -for (Algorithm in Algorithms) { - str = md5(str + Algorithm) -} -CaptchaSign = "1." + str -``` - -Login type and Sign type recommended options - - - -::: -::: zh-CN 选择 `算法` 时需填写 `算法`(比较难获取,需要逆向) 选择 `验证码签名` 时只需填写 `验证码签名` 和 `时间戳` @@ -271,90 +123,25 @@ CaptchaSign = "1." + str  -::: - -### 设备ID { lang="zh-CN" } - -### DeviceID { lang="en" } +### 设备ID -::: en -The value calculated by md5 is used to determine the logged in device -::: - -::: zh-CN 通过 MD5 计算的值，用于判断登录的设备 -::: -### 客户端ID, 客户端秘钥, 客户端版本, 包名 { lang="zh-CN" } +### 客户端ID, 客户端秘钥, 客户端版本, 包名 -### ClientID, ClientSecret, ClientVersion, PackageName { lang="en" } - -::: en -It is related to the signature, fill in according to the actual situation -::: -::: zh-CN 与签名有关，根据实际情况填写 -::: -### 用户代理 { lang="zh-CN" } +### 用户代理 -### UserAgent { lang="en" } - -::: en -UserAgent used by API requests, may be inaccessible or speed limited if the setting is incorrect -::: -::: zh-CN API 请求使用的 UserAgent，设置错误可能无法访问或限速 -::: -### 下载用户代理 { lang="zh-CN" } +### 下载用户代理 -### DownUserAgent { lang="en" } - -::: en -The User Agent used for downloading, if the setting is wrong, it will not be downloaded (it will be used when the agent is turned on) Fixed parameters: - -`Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36` -::: -::: zh-CN 下载时用到的 User Agent，如果设置错误会无法下载(开启代理会使用) 固定参数： `Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36` -::: - -### 关键数据获取流程 { lang="zh-CN" } - -### Key data acquisition process { lang="en" } - -::: en -Obtain Xunlei request data through network analysis tools (packet capture tools) --- Please read the following information carefully - -Open Xunlei and log in to your account (the picture below uses the PC client to operate, and the web terminal is also available) - -Included in the request https://xluser-ssl.xunlei.com/v1/shield/captcha/init - -CaptchaSign, Timestamp, DeviceID, ClientID, ClientVersion, PackageName, User-Agent - -**Note**: After obtaining the information of the two pictures, slowly select the data from the two data captured and fill in it - -After logging in to Thunder and opening the packet capture tool, it is possible that the information of **v1/shield/captcha/init** cannot be immediately obtained at this time. - -Do not close the Xunlei PC client and the packet capture tool, just wait, it will refresh automatically after **5 minutes** - -You will see the parameters as shown in the figure below, and you can fill in it according to the acquisition (if you can't see it clearly, you can right-click to copy the picture and link it to the browser to open a new window) - -See **v1/shield/captcha/init** and grab it, please **immediately don't delay for a second** Right-click Xunlei in the taskbar in the lower right corner to exit, exit completely and then reopen to get \* \*Figure II\*\* - - -Restarting Thunder will refresh the token - -The request to https://xluser-ssl.xunlei.com/v1/auth/token contains RefreshToken (please use the returned value), ClientSecret (does not exist on the web side) - - -Figure 1 contains **7** parameters | Figure 1 contains **2** parameters | a fixed parameter (Down UserAgent), ten parameters and 3 options and a mount path, just write and save, before saving Remember to check~ -::: -::: zh-CN +### 关键数据获取流程 通过网络分析工具(抓包工具)获取迅雷请求数据 @@ -383,60 +170,18 @@ CaptchaSign、Timestamp、DeviceID、ClientID、ClientVersion、PackageName、Us  图一包含 **7 条** 参数 | 图一包含 \*\*2 条\*\* 参数 | 一条固定参数(Down UserAgent) ，十条参数 和 3 个选项 以及一个挂载路径，写好保存即可，保存前记得检查喔~~ -::: -### 使用视频URL { lang="zh-CN" } +### 使用视频URL -::: en -When the `Video URL` option is enabled, it will attempt to replace the original link with the media link returned by the API. Currently, the official platform throttles the download link for **non-members**, but video streaming is not throttled. Therefore, by replacing the link, you can avoid throttling, which applies to both **OpenList** media file downloads and streaming. For regular files, you can also bypass the throttling by renaming the file extension to a media format (e.g., `.mp4`). - -The **Expert Edition** does not enable the `Video URL` option by default, as it is intended for users who configure detailed parameters themselves, and they should be aware of the significance of this option. Hence, it is not enabled by default. For **Xunlei X** users, this option is enabled by default, primarily for the convenience of less experienced users. -::: - -::: zh-CN `视频URL` 开启后，会尝试使用接口返回的媒体链接进行替换原本的链接。目前官方对 `非会员` 情况下，下载链接进行了限速，但视频播放是不限速的。因此可以通过替换链接的方式来避免限速，这一点对于 `OpenList` 媒体文件下载和在线播放均生效。对于普通文件，也可以采取重命名文件后缀为媒体格式（例如：`.mp4` ）的方式绕过限速。 专家版没默认开启 `视频URL`选项，目的是针对于自行配置详细参数的人群来说，应当知晓该选项的意义，因此默认不启用。对于 `迅雷X` 驱动默认启用该选项，更多的是为了小白用户考虑。 -::: - -### 迅雷专家版 完整的参数填演示图 { lang="zh-CN" } -### ThunderExpert complete parameter filling demo: { lang="en" } +### 迅雷专家版 完整的参数填演示图 -::: en  -::: -::: zh-CN - -::: - -### 默认使用的下载方式 { lang="zh-CN" } - -### The default download method used { lang="en" } -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -457,61 +202,24 @@ flowchart TB click c1 "../drivers/common.html#webdav-策略" ``` -## 3. Thunder X { lang="en" } - -## 3. 迅雷 X { lang="zh-CN" } +## 3. 迅雷 X -::: zh-CN ::: danger 目前官方对于频繁调用接口行为会进行封号处理，请谨慎使用，后果自负。 ::: -::: en -::: danger -At present, the official will ban frequent API calls. Please use with caution and bear the consequences. -::: - -### 用户名、密码 { lang="zh-CN" } -### username、password { lang="en" } +### 用户名、密码 -::: en -The mailbox and password used for login -
-::: -::: zh-CN 即用于登陆的邮箱和密码
-::: -### 验证码 { lang="zh-CN" } +### 验证码 -### CaptchaToken { lang="en" } - -::: en -It will be filled automatically without filling in manually -
-::: -::: zh-CN 会自动填充，不用自己填写
-::: -### 根文件夹ID { lang="zh-CN" } +### 根文件夹ID -### Root folder id { lang="en" } - -::: en -The default is the full directory of the empty display, If you want to use a subfolder to make the root directory, grab the request to get it - -- In the request in the package`https://api-pan.xunleix.com/drive/v1/files?parent_id=&page_token=&filters=`，you can get the following parameters - - `文件夹ID（id）` - - `文件夹名称（name）` - - `父文件夹ID（parent_id）` -- The `folder ID` obtained in the root directory (for example : `我接收的文件`、`我的云盘`、`高速云下载`), **This will change with different account numbers, there is no the same value, In the request in the package** -  - -::: -::: zh-CN 默认为空展示全部目录，如果想用子文件夹做根目录请抓包获取 - 抓包请求中的`https://api-pan.xunleix.com/drive/v1/files?parent_id=&page_token=&filters=`，可以得到下面参数 @@ -521,51 +229,13 @@ The default is the full directory of the empty display, If you want to use a sub - 根目录下获取的`文件夹ID（Folder id）`（例如：`我接收的文件`、`我的云盘`、`高速云下载`），**这个会随着账号不同而变动，没有通用的值，自己抓包获取**  -::: - -### 使用视频URL { lang="zh-CN" } - -### Use video url { lang="en" } +### 使用视频URL -::: en -When the `Video URL` option is enabled, it will attempt to replace the original link with the media link returned by the API. Currently, the official platform throttles the download link for **non-members**, but video streaming is not throttled. Therefore, by replacing the link, you can avoid throttling, which applies to both **OpenList** media file downloads and streaming. For regular files, you can also bypass the throttling by renaming the file extension to a media format (e.g., `.mp4`). - -The **Expert Edition** does not enable the `Video URL` option by default, as it is intended for users who configure detailed parameters themselves, and they should be aware of the significance of this option. Hence, it is not enabled by default. For **Xunlei X** users, this option is enabled by default, primarily for the convenience of less experienced users. -::: - -::: zh-CN `视频URL` 开启后，会尝试使用接口返回的媒体链接进行替换原本的链接。目前官方对 `非会员` 情况下，下载链接进行了限速，但视频播放是不限速的。因此可以通过替换链接的方式来避免限速，这一点对于 `OpenList` 媒体文件下载和在线播放均生效。对于普通文件，也可以采取重命名文件后缀为媒体格式（例如：`.mp4` ）的方式绕过限速。 专家版没默认开启 `视频URL`选项，目的是针对于自行配置详细参数的人群来说，应当知晓该选项的意义，因此默认不启用。对于 `迅雷X` 驱动默认启用该选项，更多的是为了小白用户考虑。 -::: - -### 默认使用的下载方式 { lang="zh-CN" } -### The default download method used { lang="en" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -586,63 +256,24 @@ flowchart TB click c1 "../drivers/common.html#webdav-策略" ``` -::: - -## 4. 迅雷 X 专家版 { lang="zh-CN" } - -## 4. Thunder X Expert { lang="en" } +## 4. 迅雷 X 专家版 -::: en -::: danger -At present, the official will ban frequent API calls. Please use with caution and bear the consequences. -::: -::: zh-CN ::: danger 目前官方对于频繁调用接口行为会进行封号处理，请谨慎使用，后果自负。 ::: -### 用户名、密码 { lang="zh-CN" } - -### username、password { lang="en" } +### 用户名、密码 -::: en -The mailbox and password used for login -
-::: -::: zh-CN 即用于登陆的邮箱和密码
-::: - -### 验证码 { lang="zh-CN" } -### CaptchaToken { lang="en" } +### 验证码 -::: en -It will be filled automatically without filling in manually -
-::: -::: zh-CN 会自动填充，不用自己填写
-::: -### 根文件夹ID { lang="zh-CN" } +### 根文件夹ID -### Root folder id { lang="en" } - -::: en -The default is the full directory of the empty display, If you want to use a subfolder to make the root directory, grab the request to get it - -- In the request in the package`https://api-pan.xunleix.com/drive/v1/files?parent_id=&page_token=&filters=`，you can get the following parameters - - `文件夹ID（id）` - - `文件夹名称（name）` - - `父文件夹ID（parent_id）` -- The `folder ID` obtained in the root directory (for example : `我接收的文件`、`我的云盘`、`高速云下载`), **This will change with different account numbers, there is no the same value, In the request in the package** -  - -::: -::: zh-CN 默认为空展示全部目录，如果想用子文件夹做根目录请抓包获取 - 抓包请求中的`https://api-pan.xunleix.com/drive/v1/files?parent_id=&page_token=&filters=`，可以得到下面参数 @@ -652,75 +283,17 @@ The default is the full directory of the empty display, If you want to use a sub - 根目录下获取的`文件夹ID（Folder id）`（例如：`我接收的文件`、`我的云盘`、`高速云下载`），**这个会随着账号不同而变动，没有固定一样的值，自己抓包获取**  -::: - -### 登录类型 { lang="zh-CN" } - -### Login Type { lang="en" } - -::: en - -- `User`: Only fill in the username and password -- `Refresh token`: Just fill in`RefreshToken` - -::: -::: zh-CN +### 登录类型 - `用户`：选择 `用户`时填`用户名和密码` - `刷新令牌`：选择 `刷新令牌` 时只需填写 `刷新令牌` -::: - -### 签名类型 { lang="zh-CN" } - -### Sign Type { lang="en" } - -::: en - -- `Algorithms`：Choose `Algorithms` Just fill in `Algorithms` (It has been automatically filled. You do n’t have to fill in it yourself. You only need to fill in the username and password.When the algorithm is not invalidated) -- `Captcha sign`: Choose `Captcha sign` Just fill in `Captcha sign` and `Timestamp` - -::: - -::: zh-CN +### 签名类型 - `算法`：选择 `算法（Algorithms）` 时需填写 `算法（Algorithms）` - `验证码签名`：选择 `验证码签名（Captcha sign）` 时只需填写 `验证码签名（Captcha sign）` 和 `时间戳（Timestamp）` -::: - -### 部分参数抓包说明 { lang="zh-CN" } - -### Part of parameter Packet Capture description { lang="en" } - -::: en - -- `Captcha token`：No need to fill in -- `Device id`：The value calculated by MD5 is used to judge the login device -- `Client id`, `Client secret`, `Client version`, `Package name`：It related to the signature, fill in according to the actual situation - ---- - -- `User agent`：API requests `User agent`, setting errors may not access or speed limit -- `Download user agent`：When downloading, use the `user agent `,If the setting error cannot be downloaded (the agent will use it) - - `User agent` and `Download user agent`：You can fill it out by yourself. If you don’t know how to fill it out, you can leave it blank and it will be automatically filled in. - ---- - -In the request in the package `https://xluser-ssl.xunleix.com/v1/shield/captcha/init`，you can get the following parameters6 - -- `Client id`、`Device id`、`Captcha sign` -- `Package name`、`Client version`、`Timestamp` - -  - - In the request in the package `https://xluser-ssl.xunleix.com/v1/auth/signin`, you can get the following parameters2 - - `Client id`、`Client secret` -  - -::: - -::: zh-CN +### 部分参数抓包说明 - `验证码`：无需填写 - `设备id`：通过 MD5 计算的值，用于判断登录的设备 @@ -746,51 +319,13 @@ In the request in the package `https://xluser-ssl.xunleix.com/v1/shield/captcha/ - `客户端ID（Client id）`、`客户端密钥（Client secret）`  -::: +### 使用视频URL -### 使用视频URL { lang="zh-CN" } - -### Use video url { lang="en" } - -::: en -When the `Video URL` option is enabled, it will attempt to replace the original link with the media link returned by the API. Currently, the official platform throttles the download link for **non-members**, but video streaming is not throttled. Therefore, by replacing the link, you can avoid throttling, which applies to both **OpenList** media file downloads and streaming. For regular files, you can also bypass the throttling by renaming the file extension to a media format (e.g., `.mp4`). - -The **Expert Edition** does not enable the `Video URL` option by default, as it is intended for users who configure detailed parameters themselves, and they should be aware of the significance of this option. Hence, it is not enabled by default. For **Xunlei X** users, this option is enabled by default, primarily for the convenience of less experienced users. -::: - -::: zh-CN `视频URL` 开启后，会尝试使用接口返回的媒体链接进行替换原本的链接。目前官方对 `非会员` 情况下，下载链接进行了限速，但视频播放是不限速的。因此可以通过替换链接的方式来避免限速，这一点对于 `OpenList` 媒体文件下载和在线播放均生效。对于普通文件，也可以采取重命名文件后缀为媒体格式（例如：`.mp4` ）的方式绕过限速。 专家版没默认开启 `视频URL`选项，目的是针对于自行配置详细参数的人群来说，应当知晓该选项的意义，因此默认不启用。对于 `迅雷X` 驱动默认启用该选项，更多的是为了小白用户考虑。 -::: - -### 默认使用的下载方式 { lang="zh-CN" } - -### The default download method used { lang="en" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` -::: -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -811,56 +346,20 @@ flowchart TB click c1 "../drivers/common.html#webdav-策略" ``` -::: - -## 5.迅雷浏览器 { lang="zh-CN" } - -## 5. Thunder Browser { lang="en" } +## 5.迅雷浏览器 -### 用户名、密码 { lang="zh-CN" } +### 用户名、密码 -### username、password { lang="en" } - -::: en -Mobile phone number, email, username, and password used to log in - -- When filling in the mobile phone number, please bring the `+86` area code, for example `+8613822334455` - -::: -::: zh-CN 即用于登陆的手机号,邮箱,用户名，以及密码 - 填写手机号要携带 `+86` 区号，例如 `+8613822334455` -::: - -### 验证码 { lang="zh-CN" } - -### CaptchaToken { lang="en" } +### 验证码 -::: en -It will be filled automatically without filling in manually -::: -::: zh-CN 会自动填充，不用自己填写 -::: - -### 根文件夹ID { lang="zh-CN" } -### Root folder id { lang="en" } +### 根文件夹ID -::: en -The default is the full directory of the empty display, If you want to use a subfolder to make the root directory, grab the request to get it - -- In the request in the package`https://x-api-pan.xunlei.com/drive/v1/files?parent_id&page_token&space=`，you can get the following parameters - - `文件夹ID（id）` - - `文件夹名称（name）` - - `父文件夹ID（parent_id）` -- The `folder ID` obtained in the root directory (for example : `来自分享`、`超级保险箱`), **This will change with different account numbers, there is no the same value, In the request in the package** -  - -::: -::: zh-CN 默认为空展示全部目录，如果想用子文件夹做根目录请抓包获取 - 抓包请求中的`https://x-api-pan.xunlei.com/drive/v1/files?parent_id&page_token&space=`，可以得到下面参数 @@ -870,82 +369,24 @@ The default is the full directory of the empty display, If you want to use a sub - 根目录下获取的`文件夹ID（Folder id）`（例如：`来自分享`、`超级保险箱`），**这个会随着账号不同而变动，没有固定一样的值，自己抓包获取**  -::: - -### 保险箱密码 { lang="zh-CN" } - -### Safe password { lang="en" } +### 保险箱密码 -::: en -Thunder Browser Safe password - -- Files in Safe password can only be deleted directly and cannot be deleted to the recycle bin, so the [**Deletion method**](#remove-way) below has nothing to do with this configuration. - -::: -::: zh-CN 迅雷浏览器云盘的保险箱密码 - 超级保险箱內文件只能直接删除 无法删除到回收站，所以下方[**删除方式**](#删除方式)与此配置无关 -::: - -### 删除方式 { lang="zh-CN" } - -### Remove way { lang="en" } +### 删除方式 -::: en -**Trash**：Use OpenList to delete files and then move them to the Recycle Bin. If you delete them accidentally, you can restore them through Thunder Cloud Disk. -**Delete**：Deleting it directly cannot restore it. -::: - -::: zh-CN **回收站**：在OpenList删除后移除到回收站，如果有误删可以通过迅雷云盘恢复 **删除**：直接删除不可以恢复找回 -::: - -### 使用视频URL { lang="zh-CN" } - -### Use video url { lang="en" } - -::: en -When the `Video URL` option is enabled, it will attempt to replace the original link with the media link returned by the API. Currently, the official platform throttles the download link for **non-members**, but video streaming is not throttled. Therefore, by replacing the link, you can avoid throttling, which applies to both **OpenList** media file downloads and streaming. For regular files, you can also bypass the throttling by renaming the file extension to a media format (e.g., `.mp4`). -The **Expert Edition** does not enable the `Video URL` option by default, as it is intended for users who configure detailed parameters themselves, and they should be aware of the significance of this option. Hence, it is not enabled by default. For **Xunlei X** users, this option is enabled by default, primarily for the convenience of less experienced users. -::: +### 使用视频URL -::: zh-CN `视频URL` 开启后，会尝试使用接口返回的媒体链接进行替换原本的链接。目前官方对 `非会员` 情况下，下载链接进行了限速，但视频播放是不限速的。因此可以通过替换链接的方式来避免限速，这一点对于 `OpenList` 媒体文件下载和在线播放均生效。对于普通文件，也可以采取重命名文件后缀为媒体格式（例如：`.mp4` ）的方式绕过限速。 专家版没默认开启 `视频URL`选项，目的是针对于自行配置详细参数的人群来说，应当知晓该选项的意义，因此默认不启用。对于 `迅雷X` 驱动默认启用该选项，更多的是为了小白用户考虑。 -::: - -### 默认使用的下载方式 { lang="zh-CN" } -### The default download method used { lang="en" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -966,59 +407,21 @@ flowchart TB click c1 "../drivers/common.html#webdav-策略" ``` -::: - -## 6. 迅雷浏览器专家版 { lang="zh-CN" } - -## 6. Thunder Browser Expert { lang="en" } - -### 用户名、密码 { lang="zh-CN" } - -### username、password { lang="en" } +## 6. 迅雷浏览器专家版 -::: en -Mobile phone number, email, username, and password used to log in +### 用户名、密码 -- When filling in the mobile phone number, please bring the `+86` area code, for example `+8613822334455` - -::: -::: zh-CN 即用于登陆的手机号,邮箱,用户名，以及密码 - 填写手机号要携带 `+86` 区号，例如 `+8613822334455` -::: +### 验证码 -### 验证码 { lang="zh-CN" } - -### CaptchaToken { lang="en" } - -::: en -It will be filled automatically without filling in manually -
-::: -::: zh-CN 会自动填充，不用自己填写
-::: - -### 根文件夹ID { lang="zh-CN" } -### Root folder id { lang="en" } +### 根文件夹ID -::: en -The default is the full directory of the empty display, If you want to use a subfolder to make the root directory, grab the request to get it - -- In the request in the package`https://x-api-pan.xunlei.com/drive/v1/files?parent_id&page_token&space=`，you can get the following parameters - - `文件夹ID（id）` - - `文件夹名称（name）` - - `父文件夹ID（parent_id）` -- The `folder ID` obtained in the root directory (for example : `来自分享`、`超级保险箱`), **This will change with different account numbers, there is no the same value, In the request in the package** -  - -::: - -::: zh-CN 默认为空展示全部目录，如果想用子文件夹做根目录请抓包获取 - 抓包请求中的`https://x-api-pan.xunlei.com/drive/v1/files?parent_id&page_token&space=`，可以得到下面参数 @@ -1028,104 +431,28 @@ The default is the full directory of the empty display, If you want to use a sub - 根目录下获取的`文件夹ID（Folder id）`（例如：`来自分享`、`超级保险箱`），**这个会随着账号不同而变动，没有固定一样的值，自己抓包获取**  -::: - -### 保险箱密码 { lang="zh-CN" } - -### Safe password { lang="en" } - -::: en -Thunder Browser Safe password - -- Files in Safe password can only be deleted directly and cannot be deleted to the recycle bin, so the [**Deletion method**](#remove-way-1) below has nothing to do with this configuration. +### 保险箱密码 -::: -::: zh-CN 迅雷浏览器云盘的保险箱密码 - 超级保险箱內文件只能直接删除 无法删除到回收站，所以下方[**删除方式**](#删除方式-1)与此配置无关 -::: - -### 删除方式 { lang="zh-CN" } +### 删除方式 -### Remove way { lang="en" } - -::: en -**Trash**：Use OpenList to delete files and then move them to the Recycle Bin. If you delete them accidentally, you can restore them through Thunder Cloud -**Delete**：Deleting it directly cannot restore it. -::: -::: zh-CN **回收站**：在OpenList删除后移除到回收站，如果有误删可以通过迅雷云盘恢复 **删除**：直接删除不可以恢复找回 -::: -### 登录类型 { lang="zh-CN" } - -### Login Type { lang="en" } - -::: en - -- `User`: Only fill in the username and password -- `Refresh token`: Just fill in`RefreshToken` - -::: -::: zh-CN +### 登录类型 - `用户`：选择 `用户`时填`用户名和密码` - `刷新令牌`：选择 `刷新令牌` 时只需填写 `刷新令牌` -::: - -### 签名类型 { lang="zh-CN" } - -### Sign Type { lang="en" } - -::: en - -- `Algorithms`：Choose `Algorithms` Just fill in `Algorithms` (It has been automatically filled. You do n’t have to fill in it yourself. You only need to fill in the username and password.When the algorithm is not invalidated) -- `Captcha sign`: Choose `Captcha sign` Just fill in `Captcha sign` and `Timestamp` - -::: -::: zh-CN +### 签名类型 - `算法`：选择 `算法（Algorithms）` 时需填写 `算法（Algorithms）` - `验证码签名`：选择 `验证码签名（Captcha sign）` 时只需填写 `验证码签名（Captcha sign）` 和 `时间戳（Timestamp）` -::: - -### 部分参数抓包说明 { lang="zh-CN" } - -### Part of parameter Packet Capture description { lang="en" } - -::: en - -- `Captcha token`：No need to fill in -- `Device id`：The value calculated by MD5 is used to judge the login device -- `Client id`, `Client secret`, `Client version`, `Package name`：It related to the signature, fill in according to the actual situation - ---- - -- `User agent`：API requests `User agent`, setting errors may not access or speed limit -- `Download user agent`：When downloading, use the `user agent `,If the setting error cannot be downloaded (the agent will use it) - - `User agent` and `Download user agent`：You can fill it out by yourself. If you don’t know how to fill it out, you can leave it blank and it will be automatically filled in. - ---- - -In the request in the package `https://xluser-ssl.xunlei.com/v1/shield/captcha/init`，you can get the following parameters6 - -- `Client id`、`Device id`、`Captcha sign` -- `Package name`、`Client version`、`Timestamp` -  - - In the request in the package `https://xluser-ssl.xunlei.com/v1/auth/signin/token`, you can get the following parameters3 - - `Client id`、`Client secret`、`Refresh token` - -  - -::: - -::: zh-CN +### 部分参数抓包说明 - `验证码`：无需填写 - `设备id`：通过 MD5 计算的值，用于判断登录的设备 @@ -1150,29 +477,13 @@ In the request in the package `https://xluser-ssl.xunlei.com/v1/shield/captcha/i - `客户端ID（Client id）`、`客户端密钥（Client secret）`、`刷新令牌（Refresh token）`  -::: - -### 使用视频URL { lang="zh-CN" } - -### Use video url { lang="en" } +### 使用视频URL -::: en -When the `Video URL` option is enabled, it will attempt to replace the original link with the media link returned by the API. Currently, the official platform throttles the download link for **non-members**, but video streaming is not throttled. Therefore, by replacing the link, you can avoid throttling, which applies to both **OpenList** media file downloads and streaming. For regular files, you can also bypass the throttling by renaming the file extension to a media format (e.g., `.mp4`). - -The **Expert Edition** does not enable the `Video URL` option by default, as it is intended for users who configure detailed parameters themselves, and they should be aware of the significance of this option. Hence, it is not enabled by default. For **Xunlei X** users, this option is enabled by default, primarily for the convenience of less experienced users. -::: - -::: zh-CN `视频URL` 开启后，会尝试使用接口返回的媒体链接进行替换原本的链接。目前官方对 `非会员` 情况下，下载链接进行了限速，但视频播放是不限速的。因此可以通过替换链接的方式来避免限速，这一点对于 `OpenList` 媒体文件下载和在线播放均生效。对于普通文件，也可以采取重命名文件后缀为媒体格式（例如：`.mp4` ）的方式绕过限速。 专家版没默认开启 `视频URL`选项，目的是针对于自行配置详细参数的人群来说，应当知晓该选项的意义，因此默认不启用。对于 `迅雷X` 驱动默认启用该选项，更多的是为了小白用户考虑。 -::: - -### The default download method used { lang="en" } -### 默认使用的下载方式 { lang="zh-CN" } - -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -1192,28 +503,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: diff --git a/pages/guide/drivers/uc.md b/pages/guide/drivers/uc.md index 33d3d3eca..123306d58 100644 --- a/pages/guide/drivers/uc.md +++ b/pages/guide/drivers/uc.md @@ -1,91 +1,31 @@ --- -title: - en: UC / TV - zh-CN: UC / TV -icon: iconfont icon-state -# This control sidebar order top: 683 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - '本地代理' - - '302' -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- - +# UC / TV -## UC Cloud { lang="en" } + -## UC 网盘 { lang="zh-CN" } +## UC 网盘 **https://drive.uc.cn/** -### Cookie { lang="en" } +### Cookie -### Cookie { lang="zh-CN" } - -::: en -Press F12 to open "Debug", select "Network", select any request on the left, and find the one with the `Cookie` parameter. - -::: -::: zh-CN 在 `F12`任意请求中找到携带 `Cookie` 的值  -::: - -### Root Folder ID { lang="en" } - -### 根文件夹ID { lang="zh-CN" } - -::: en -Root Folder ID is `0` -- After entering the folder, get the directory ID in the top address bar. If the subdirectory is deeper, the directory ID will be at the back of the address bar. Just write the subdirectory ID you want to mount. -  +### 根文件夹ID -::: -::: zh-CN 根目录ID为 `0` - 子文件夹ID进入文件夹后顶部地址栏获取目录ID，如果子目录越深目录ID在地址栏越靠后，想挂载哪个子目录就写那个子目录ID就可以  -::: - -### The default download method used { lang="en" } - -### 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - c1 - end - c1[local proxy]:::someclass==default===>a2[user equipment] - classDef someclass fill:#f96 - b1[Download proxy URL]-.alternative.->a2[user equipment] - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -104,34 +44,11 @@ flowchart TB click c1 "../drivers/common.html#webdav-策略" ``` -::: +## UC TV -## UC TV { lang="en" } - -## UC TV { lang="zh-CN" } - -::: en -The TV version supports `302`, but only `List` and `Download` operations are supported. Other operations are not supported (the interface does not support it). -::: -::: zh-CN TV 版支持 `302`，但是只能 `访问` 和 `下载` 两个操作，其它操作不支持(接口不支持) -::: - -### Add method { lang="en" } -### 添加方式 { lang="zh-CN" } - -::: en - -1. Select the `UC TV` driver, fill in the mounting path, and then save -2. Return to the all driver page and use the mobile APP to scan the QR code (If the QR code is not displayed, click on `Table Layout` in the upper right corner of the driver to switch from list mode to table mode) -3. After scanning the QR code to confirm, disable the driver, then enable the `driver` to use it. - - `Refresh token`、`Device id`、`Query token`,It will be filled in automatically, no manual filling is required - Please do not edit manually and modify it -  - -::: - -::: zh-CN +### 添加方式 1. 选择 `UCTV` 驱动，填写挂载路径，然后保存 2. 返回全部驱动页面，使用手机APP扫描二维码（如果不显示二维码，驱动右上角点击点击`表格布局` 从列表模式切换成表格模式） @@ -139,54 +56,14 @@ TV 版支持 `302`，但是只能 `访问` 和 `下载` 两个操作，其它操 - `Refresh token 刷新令牌`、`Device id 设备ID `、`Query token` 会自动填充，不需要人工填写 - 请不要进行编辑手动修改  -::: - -### Root Folder ID { lang="en" } - -### 根文件夹ID { lang="zh-CN" } +### 根文件夹ID -::: en -Root Folder ID is `0` - -- After entering the folder, get the directory ID in the top address bar. If the subdirectory is deeper, the directory ID will be at the back of the address bar. Just write the subdirectory ID you want to mount. -  - -::: -::: zh-CN 要挂载的根文件夹，默认为`0` - 子文件夹ID进入文件夹后顶部地址栏获取目录ID，如果子目录越深目录ID在地址栏越靠后  -::: - -### The default download method used { lang="en" } - -### 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -206,5 +83,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/url_tree.md b/pages/guide/drivers/url_tree.md index 587103642..b471cb280 100644 --- a/pages/guide/drivers/url_tree.md +++ b/pages/guide/drivers/url_tree.md @@ -1,25 +1,12 @@ --- -title: - en: UrlTree - zh-CN: 地址树 -icon: iconfont icon-state -# This control sidebar order top: 998 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - '302' -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- +# 地址树 + :::tip **`地址树-UrlTree`** 是什么? 是用来挂载单个文件链接的，详情可以查看 **→→→[原需求说明](https://github.com/alist-org/alist/issues/3268)←←←** ::: diff --git a/pages/guide/drivers/uss.md b/pages/guide/drivers/uss.md index 12c45e965..3e14a9d4d 100644 --- a/pages/guide/drivers/uss.md +++ b/pages/guide/drivers/uss.md @@ -1,38 +1,12 @@ --- -title: - en: UPYUN Storage Service - zh-CN: 又拍云存储 -icon: iconfont icon-state -# This control sidebar order top: 894 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - '302' - - '官方' -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- -::: en -::: tip -When using the **302 redirect** strategy, the `_upd` and `_upt` parameters are automatically appended to the URL. If **"Parameter Follow"** is enabled in the Upyun console, the CDN nodes will treat these parameters as part of the file path, resulting in a **404 Not Found** error for existing files. - -Solutions: +# 又拍云存储 -- Method 1: In the Upyun console, under **"Cache Control"**, change **"Parameter Follow"** to **"Parameter Not Follow"**. - -- Method 2: Set the WebDAV policy of OpenList to **"Local Proxy"**. This mode avoids appending interfering parameters but will increase the server's data transfer. -::: - -::: zh-CN ::: tip 在使用 **302 重定向** 策略时，会自动在 URL 后拼接 `_upd` 与 `_upt` 参数，若又拍云控制台开启了 **“参数跟随”**，CDN 节点会将这些参数视为文件路径的一部分进行匹配，从而导致原本存在的文件返回 **404 Not Found**。 @@ -44,134 +18,45 @@ Solutions: ::: -::: en -UPYUN Storage Service，refer to as USS，[**Yupyun USS Official Website**](https://console.upyun.com/services/file/) -::: -::: zh-CN UPYUN 存储服务，简称 USS，[**又拍云USS官网**](https://console.upyun.com/services/file/) -::: -### BucKet { lang="en" } +## 存储桶 -## 存储桶 { lang="zh-CN" } - -::: en -UPYUN Storage Service Name -::: -::: zh-CN **UPYUN 存储桶服务名称** -::: -### Endpoint { lang="en" } +## Endpoint -## Endpoint { lang="zh-CN" } - -::: en -Accelerated domain name (default TEST domain or bound domain, not CNAME domain) -If you use http protocol, please add `http://` protocol header. -The test domain name provided by upyun is not accessible in some network and does not support https, so it is recommended to use your own bound domain name. -::: -::: zh-CN 加速域名（默认的测试域名或已绑定域名，不是CNAME域名） 如果使用http协议，请自行添加`http://`协议头 又拍云提供的默认测试域名在部分网络环境下无法访问，且不支持https，建议使用自行绑定的域名 -::: -### Operator name { lang="en" } +## 操作员名称 -## 操作员名称 { lang="zh-CN" } - -::: en -Operator name -::: -::: zh-CN 操作员名称 -::: - -### Operator password { lang="en" } -## 操作员密码 { lang="zh-CN" } +## 操作员密码 -::: en -Operator password -::: -::: zh-CN 操作员密码 -::: - -### Root folder path { lang="en" } -## 根文件夹 ID { lang="zh-CN" } +## 根文件夹 ID -::: en -Root path, if not filled, it defaults to the root directory. -::: -::: zh-CN 根路径，不填则默认为根目录。 -::: - -### Sign url expire { lang="en" } -## 签名链接有效期 { lang="zh-CN" } +## 签名链接有效期 -::: en -The validity period of the signed download address is 4 hours by default. -::: -::: zh-CN 签名下载地址的有效期默认为 4 小时。 -::: - -## Example of filling in details { lang="en" } -## 详情填写示意图 { lang="zh-CN" } +## 详情填写示意图 -::: en -::: tip -If you want to use the official test domain name, you must manually add http For example: http://xxx.test.upcdn.net -If you want to use HTTPS, of course, you can also add your own domain name, for example: https://you.xxx.com -permission is turned on by itself, and the read permission must be turned on！ -::: -::: en - -::: - -::: zh-CN ::: tip 如果你要用官方提供的的测试域名那必须要手动加http 例如： http://xxx.test.upcdn.net 如果想用HTTPS，当然也可以添加自己的域名就可以使用例如：https://you.xxx.com 操作员的权限自己需要哪个开启哪个，读取权限必须得开！ ::: -::: zh-CN - -::: -### The default download method used { lang="en" } - -### 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[302]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[local proxy]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` + -::: -::: zh-CN +### 默认使用的下载方式 ```mermaid --- @@ -191,5 +76,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/webdav.md b/pages/guide/drivers/webdav.md index 75c08c730..cdb514c5a 100644 --- a/pages/guide/drivers/webdav.md +++ b/pages/guide/drivers/webdav.md @@ -1,95 +1,33 @@ --- -title: - en: WebDav - zh-CN: WebDAV -icon: iconfont icon-state -# This control sidebar order top: 899 -# A page can have multiple categories categories: - guide - drivers --- -## Address { lang="en" } +# WebDAV -## 地址 { lang="zh-CN" } +## 地址 -::: en -WebDAV root address -::: - -::: zh-CN WebDAV 根地址 -::: - -## Username { lang="en" } -## 用户名 { lang="zh-CN" } +## 用户名 -::: en -username -::: - -::: zh-CN 用户名 -::: - -## Password { lang="en" } -## 密码 { lang="zh-CN" } +## 密码 -::: en -password -::: - -::: zh-CN 密码 -::: - -## Root folder path { lang="en" } - -## 根文件夹ID { lang="zh-CN" } -::: en -The path of fodler you want to mount, same as join in address -::: +## 根文件夹ID -::: zh-CN 要挂载的文件夹路径，与加入地址相同 -::: -## Tls insecure skip verify { lang="en" } +## 跳过 SSL 证书验证 -## 跳过 SSL 证书验证 { lang="zh-CN" } - -::: en -Whether to skip SSL certificate verification. If your WebDAV server uses a self-signed certificate, you may need to enable this option. Enabling it will reduce security, please use it with caution. -::: - -::: zh-CN 是否跳过 SSL 证书验证。如果你的 WebDAV 服务器使用自签名证书，可能需要启用此选项。启用后会降低安全性，请谨慎使用。 -::: - -## Support 302 redirect { lang="en" } - -## 支持 302 重定向 { lang="zh-CN" } - -::: en - -In general, WebDAV servers return the file content directly. Due to the need for authorization, only proxy downloads are possible. However, some servers redirect to the actual file address, such as OpenList `WebDav Policy`'s `302 Redirect`. - -The `Web Proxy` option in WebDAV storage settings is enabled by default. If disabled, OpenList will attempt to obtain the redirected address and return it to the user device for direct download. -Prerequisites: - -1. The WebDAV server must support returning 302; if it returns 200, this feature cannot be used, and disabling Web Proxy will make it unusable. -2. The returned 302 address must be publicly accessible and must not require authorization information; otherwise, the user device cannot download it. -3. Disable the `Web Proxy` option in the storage settings. - -::: - -::: zh-CN +## 支持 302 重定向 通常情况下，WebDAV 服务器会直接返回文件内容，由于需要授权，只能代理下载。但一些服务器会重定向到实际的文件地址，如 OpenList `WebDav 策略` 的 `302 重定向`。 @@ -101,51 +39,15 @@ WebDAV 存储设置的 `Web 代理` 选项默认为开启状态，如果关闭 2. 返回的 302 地址必须是公开可访问的地址，不得需要授权信息，否则用户设备无法下载。 3. 在存储设置中关闭 `Web 代理` 选项。 -::: - -## OneDrive/SharePoint { lang="en" } - -## OneDrive/SharePoint { lang="zh-CN" } - -::: en -Select the vendor as sharepoint, and support the international version/21Vianet. - -For OneDrive/SharePoint, you can obtain the WebDAV root address through [this tool](https://tool.example.com/onedrive/webdav). If you want to mount the specified directory, you can join it later. +## OneDrive/SharePoint -The username is the OneDrive account email, and the password is the OneDrive account password. -::: - -::: zh-CN 选择 vendor 为 sharepoint，支持国际版/世纪互联。 你可以通过[这个工具](https://alist.example.com/tool/onedrive/webdav.html)获取 WebDAV 根地址，如果要挂载指定的目录，在后面拼接即可。 用户名为 OneDrive 账号邮箱，密码即为 OneDrive 账号密码。 -::: - -## Error message { lang="en" } - -## 错误提示 { lang="zh-CN" } - -::: en - -- **failed get objs: failed to list objs: PROPFIND/根目录：403** - Need to log in to [Entra ID](https://entra.microsoft.com/#view/Microsoft_AAD_IAM/TenantOverview.ReactView?Microsoft_AAD_IAM_legacyAADRedirect=true) - - Find 'Manage Security Default' and click to disable it(❗ Note: Closing this option will disable the Authenticator verification for the domain) - -  - - Another situation is that the corresponding OneDrive account has not been used for a long time, which will also prompt this problem. Try to log in to the account again from the OneDrive web page. The system will prompt you to change the password. After updating the password, try again with the changed password. - -- **failed link: failed get link: redirect failed, status: 200** - - This error indicates that the WebDAV server does not support 302 redirects. You need to enable the `Web Proxy` option in the storage settings to use proxy downloads. - -::: - -::: zh-CN +## 错误提示 - **failed get objs: failed to list objs: PROPFIND/根目录：403** @@ -161,36 +63,7 @@ The username is the OneDrive account email, and the password is the OneDrive acc 此错误表示 WebDAV 服务器不支持 302 重定向，需要在存储设置中启用 `Web 代理` 选项以使用代理下载。 -::: - -## The default download method used { lang="en" } - -## 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style a1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - a1 - end - a1[local proxy]:::someclass====|default|a2[user equipment] - classDef someclass fill:#f96 - c1[302]-.alternative.->a2[user equipment] - b1[Download proxy URL]-.alternative.->a2[user equipment] - click a1 "../drivers/common.html#webdav-policy" - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: - -::: zh-CN +## 默认使用的下载方式 ```mermaid --- @@ -210,5 +83,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/weiyun.md b/pages/guide/drivers/weiyun.md index a500b46c5..ce6209d7a 100644 --- a/pages/guide/drivers/weiyun.md +++ b/pages/guide/drivers/weiyun.md @@ -1,43 +1,16 @@ --- -title: - en: Tencent weiyun - zh-CN: 腾讯微云 -icon: iconfont icon-state -# This control sidebar order top: 682 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - '本地代理' -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- - - -::: en -Tencent Weiyun official website: **https://www.weiyun.com** -::: -::: en -::: tip Weiyun login validity period reminder - -- QQ: The login can only keep alive for 48 hours at present, and the cookie has to be replaced -- WeChat: no such problem, use token - It is recommended to use WeChat to log in +# 腾讯微云 -::: + -::: zh-CN 腾讯微云官网：**https://www.weiyun.com** -::: -::: zh-CN + ::: tip 微云登录有效期提示 - QQ：登录目前只能保活48小时就得更换cookie @@ -46,42 +19,15 @@ Tencent Weiyun official website: **https://www.weiyun.com** ::: -## Root folder file_id { lang="en" } - -## 根文件夹ID { lang="zh-CN" } - -::: en - -1. Display the root directory, **`leave blank`**, you don’t need to fill in, the program will automatically fill in -2. If only a single folder ID is displayed, select the folder to be displayed, Copy the ID behind the top address bar - -  - -::: - -::: zh-CN +## 根文件夹ID 1. 展示根目录，**`留空`** 就可以不用填写，程序会自动填充 2. 如果只展示其中单个文件夹ID，进入想展示的文件夹內然后复制顶部地址栏后面的ID  -::: - -## Cookie { lang="en" } - -## Cookie { lang="zh-CN" } - -::: en -After logging in to Weiyun, **Open the developer debugging tool (F12)**, find the request that carries the cookie in any request, copy and fill in it. +## Cookie -- The token obtained by WeChat login is longer than the cookie field of QQ login -- QQ WeChat fills in the `Cookie` field value, and you can see it by just looking for a request - -  - -::: -::: zh-CN 登录微云后，**打开开发者调试工具(F12)**，在任意请求中找到携带cookie的请求复制填写就可以。 - 微信登录获取的token比QQ登录的cookie字段要长 @@ -89,51 +35,12 @@ After logging in to Weiyun, **Open the developer debugging tool (F12)**, find th  -::: - -## Other notes { lang="en" } - -## 其他说明 { lang="zh-CN" } - -::: en - -1. The copy function cannot be used -2. **It is recommended not to share Weiyun with the outside world. After all, it is bound to your own QQ number. If you have a major loss to QQ or other things after being blocked/frozen, you will be responsible for the consequences** - -::: - -::: zh-CN +## 其他说明 1. 复制功能无法使用 2. **建议不要将微云对外共享，毕竟是绑定的自己QQ号码，如果被封/冻结之后对QQ或者其它产生了重大损失后果自负** -::: - -## The default download method used { lang="en" } - -## 默认使用的下载方式 { lang="zh-CN" } - -::: en - -```mermaid ---- -title: Which download method is used by default? ---- -flowchart TB - style c1 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff - style a2 fill:#ff7575,stroke:#333,stroke-width:4px - subgraph ide1 [ ] - c1 - end - c1[local proxy]:::someclass==default===>a2[user equipment] - classDef someclass fill:#f96 - b1[Download proxy URL]-.alternative.->a2[user equipment] - click b1 "../drivers/common.html#webdav-policy" - click c1 "../drivers/common.html#webdav-policy" -``` - -::: -::: zh-CN +## 默认使用的下载方式 ```mermaid --- @@ -151,5 +58,3 @@ flowchart TB click b1 "../drivers/common.html#webdav-策略" click c1 "../drivers/common.html#webdav-策略" ``` - -::: diff --git a/pages/guide/drivers/wopan.md b/pages/guide/drivers/wopan.md index b17debdf8..8acdc555d 100644 --- a/pages/guide/drivers/wopan.md +++ b/pages/guide/drivers/wopan.md @@ -1,44 +1,18 @@ --- -title: - en: WoPan - zh-CN: 中国联通云盘 -icon: iconfont icon-state -# This control sidebar order top: 693 -# A page can have multiple categories categories: - guide - drivers -# A page can have multiple tags -tag: - - Storage - - Guide - - '302' -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- +# 中国联通云盘 + [https://pan.wo.cn/](https://pan.wo.cn/) -## GetToken { lang="en" } - -## 获取令牌 { lang="zh-CN" } - -::: en -::: tip -The difference between the two token acquisition methods: - -- Method 1: **Token valid for seven days** Logging in to the web version of China Unicom Cloud Drive will disconnect and invalidate the mount point on OpenList's side. However, logging in to the mobile version is fine, and thereby you can have both open simultaneously. - -- Method 2: **Token valid for two months** There isn't any problem to log into the Unicom Cloud Drive. However, it will be kicked off if you log in on the mobile side. - -::: +## 获取令牌 -::: zh-CN ::: tip 两个令牌获取方法的区别： @@ -48,21 +22,7 @@ The difference between the two token acquisition methods: ::: -### Method 1 { lang="en" } - -### 方法一 { lang="zh-CN" } - -::: en - -1. Open developer tools -2. Open the official website
::: -::: en -::: warning -Versions above v3.25.0 change the password to an encrypted hash value, and the password cannot be calculated directly. If the password is forgotten, it can only be re-**`randomly generated`** or **`manually set`**. -::: - -::: zh-CN ::: warning v3.25.0以上版本将密码改成加密方式存储的hash值，无法直接反算出密码，如果忘记了密码只能通过重新 **`随机生成`** 或者 **`手动设置`**。 ::: -::: en -The `xxxx` refers to the names corresponding to different systems/architectures, generally Linux-x86/64 is openlist-linux-amd64. -::: - -::: zh-CN `xxxx` 指的是不同系统/架构对应的名称，一般 Linux-x86/64 为 openlist-linux-amd64。 -::: ### Linux @@ -538,18 +278,11 @@ Expand-Archive .\openlist-xxxx.zip .\openlist.exe admin set NEW_PASSWORD ``` -## Daemon { lang="en" } - -## 守护进程 { lang="zh-CN" } +## 守护进程 ### Linux -::: en -`vim /usr/lib/systemd/system/openlist.service` add the following content, where `path_openlist` is the path where openlist is located: -::: -::: zh-CN 使用任意方式编辑 `/usr/lib/systemd/system/openlist.service` 并添加如下内容，其中 `path_openlist` 为 OpenList 所在的路径： -::: ```ini [Unit] @@ -564,21 +297,6 @@ Restart=on-failure WantedBy=multi-user.target ``` -::: en -Then `systemctl daemon-reload`, now you can use these commands to manage the program: - -- Start: `systemctl start openlist` -- Shut down: `systemctl stop openlist` -- Self-start: `systemctl enable openlist` -- Cancel Self-start: `systemctl disable openlist` -- Status: `systemctl status openlist` -- Restart: `systemctl restart openlist` - -Can't configure daemon? [**Video Tutorial**](https://www.bilibili.com/video/BV1rF41197Qv?t=187.0) - -::: - -::: zh-CN 然后，执行 `systemctl daemon-reload` 重载配置，现在你可以使用这些命令来管理程序： - 启动: `systemctl start openlist` @@ -590,17 +308,9 @@ Can't configure daemon? [**Video Tutorial**](https://www.bilibili.com/video/BV1r 守护进程不会配置? [**视频教程**](https://www.bilibili.com/video/BV1rF41197Qv?t=187.0) -::: - ### macOS -::: en -Edit `~/Library/LaunchAgents/org.openlist.plist` in any way and add the following content, modify `path_openlist` to be the path where OpenList is located, and `path/to/working/dir` to be the working path of OpenList: -::: - -::: zh-CN 使用任意方式编辑 `~/Library/LaunchAgents/org.openlist.plist` 并添加如下内容，修改 `path_openlist` 为 OpenList 所在的路径，`path/to/working/dir` 为 OpenList的工作路径: -::: ```xml @@ -626,45 +336,15 @@ Edit `~/Library/LaunchAgents/org.openlist.plist` in any way and add the followin ``` -::: en -Then, execute `launchctl load ~/Library/LaunchAgents/org.openlist.plist` to load the configuration, now you can use these commands to manage the program: - -- Start: `launchctl start ~/Library/LaunchAgents/org.openlist.plist` -- Close: `launchctl stop ~/Library/LaunchAgents/org.openlist.plist` -- Unload configuration: `launchctl unload ~/Library/LaunchAgents/org.openlist.plist` - -::: - -::: zh-CN 然后，执行 `launchctl load ~/Library/LaunchAgents/org.openlist.plist` 加载配置，现在你可以使用这些命令来管理程序： - 开启: `launchctl start ~/Library/LaunchAgents/org.openlist.plist` - 关闭: `launchctl stop ~/Library/LaunchAgents/org.openlist.plist` - 卸载配置: `launchctl unload ~/Library/LaunchAgents/org.openlist.plist` -::: - ### Windows -#### Method One { lang="en" } - -#### 方法1 { lang="zh-CN" } - -::: en - -1. Download the newest `nssm` from https://nssm.cc/download. -2. Unzip the archive and go to the diretory of `nssm.exe`. -3. Hold Shift and right click on the blank space, then release and press S or select "powershell here", you should now see a blue window named "Windows PowerShell". -4. Type `.\nssm.exe install openlist`. -5. Select the path of `openlist.exe` for "Path", e.g. `D:\openlist\openlist.exe`; type `server` for "Argument". -6. You can custom "Display Name", "Description" and "Startup Type" in "Details" tab. -7. Go to "I/O" tab and select a file for both "Output (stdout)" and "Output (stderr)", e.g. `D:\openlist\stdout.log`. The file itself (`stdout.log`) may not exist, but the folder (`D:\openlist`) must exist. -8. Click on "Install Service". - You can now start the service from services.msc or task manager. - -::: - -::: zh-CN +#### 方法1 1. 在 https://nssm.cc/download 下载最新版本的 `nssm`； 2. 在解压后的文件夹内按住 Shift 并右击空白处，选择“在此处打开 Powershell 窗口”； @@ -675,49 +355,11 @@ Then, execute `launchctl load ~/Library/LaunchAgents/org.openlist.plist` to load 7. 点击“Install Service”即可。 此后可以直接在服务中启动 `openlist`。 -::: - -#### Method Two { lang="en" } +#### 方法2 -#### 方法2 { lang="zh-CN" } - -::: zh-CN 用 **`.VBS`** 脚本启动和停止，分别创建两个脚本 分别是 `启动.vbs` 和 `停止.vbs`。 直接在和 OpenList 启动程序同级文件夹里面双击启动即可，不用担心没有反应 直接去 浏览器访问即可。 -::: - -::: en -Use **`.VBS`** script to start and stop, create two scripts respectively `start.vbs` and `stop.vbs`. -Just double-click to start it in the folder at the same level as the OpenList startup program, don't worry about no response, just go to the browser to access it. -::: - -::: en -::: info Two startup scripts -**start.vbs** - -```bash title="vbscript" -Dim ws -Set ws = Wscript.CreateObject("Wscript.Shell") -ws.run "openlist.exe server",vbhide -Wscript.quit -``` -**stop.vbs** - -```bash title="vbscript" -Dim ws -Set ws = Wscript.CreateObject("Wscript.Shell") -ws.run "taskkill /f /im openlist.exe",0 -Wscript.quit -``` - -1. If the script will not be created, you can download it yourself: [**Script Download**](https://www.alipan.com/s/DHPMhRtKUzY/folder/63e0961eae317bd4d4d945cda69dbb00f9837fb7) -2. If the script will not be used, you can watch the video: [**reference video**](https://www.bilibili.com/video/BV1wWYTzdE4B) - How to realize Windows startup automatically, you can refer to the script mentioned above to use the video (second). - -::: - -::: zh-CN ::: info 两个启动脚本 **启动.vbs** @@ -743,19 +385,6 @@ Wscript.quit ::: -::: en -::: info -For all platform, you can use follow command to silent start, stop and restart. (v3.4.0 and later) - -```bash -openlist start -openlist stop -openlist restart -``` - -::: - -::: zh-CN ::: info 对于所有平台，您可以使用以下命令来静默启动、停止和重新启动。 （v3.4.0 及更高版本） @@ -767,14 +396,6 @@ openlist restart ::: -## How to update { lang="en" } - -## 如何更新 { lang="zh-CN" } +## 如何更新 -::: en -Download the new version of OpenList and replace the previous one. -::: - -::: zh-CN 下载新版 OpenList，把之前的替换了即可。 -::: diff --git a/pages/guide/installation/paas.md b/pages/guide/installation/paas.md index cc32decf4..b6598f064 100644 --- a/pages/guide/installation/paas.md +++ b/pages/guide/installation/paas.md @@ -1,157 +1,73 @@ --- -# This is the title of the article -# title: One-click Script -title: - en: PaaS - zh-CN: PaaS -icon: iconfont icon-module -# This control sidebar order top: 30 -# A page can have multiple categories categories: - guide - installation -# A page can have multiple tags --- -::: zh-CN +# PaaS + ::: tip 文档可能更新不及时，请根据关键信息结合平台当前部署界面进行调整 ::: -::: en -::: tip -The documentation may not be updated in a timely manner. Please make adjustments based on the key information and the current deployment interface of the platform. -::: - -## ClawCloud { lang="en" } - -## 爪云 { lang="zh-CN" } -### One-click deployment { lang="en" } +## 爪云 -### 一键部署 { lang="zh-CN" } +### 一键部署 -::: en -::: danger -Due to the removal of `PUID`/`PGID` environment variable support for better container specifications in [OpenList v4.1.1](https://github.com/OpenListTeam/OpenList/releases/tag/v4.1.1), ClawCloud platform will not be able to function properly due to lack of permission to write data (including using images or app in App Store). - -As of October 20 2025, ClawCloud has not yet merged our Deployment Template. One-click deployment is temporarily unavailable. If you want to deploy on ClawCloud, please refer to [#1209 (comment)](https://github.com/OpenListTeam/OpenList/issues/1209#issuecomment-3243803024). -::: -::: zh-CN ::: danger 由于在[OpenList v4.1.1](https://github.com/OpenListTeam/OpenList/releases/tag/v4.1.1)中为容器规范移除了`PUID`/`PGID`环境变量支持，故在 ClawCloud 平台将由于无权限写入数据而无法正常使用（包括使用镜像和App Store内应用） 截止 2025年10月20日， ClawCloud 官方暂未合并我们的修复部署模板，一键部署暂不可用。如需部署至ClawCloud，请参阅 [#1209 (comment)](https://github.com/OpenListTeam/OpenList/issues/1209#issuecomment-3243803024)。 ::: -::: en -Click the button below to [deploy to Claw Cloud](https://template.run.claw.cloud/?openapp=system-fastdeploy%3FtemplateName%3Dopenlist). It can also be found in App Launchpad. -::: - -::: zh-CN 点击下方按钮[部署到 Claw Cloud](https://template.run.claw.cloud/?openapp=system-fastdeploy%3FtemplateName%3Dopenlist)。亦可在 App Launchpad 中找到。 -::: [](https://template.run.claw.cloud/?openapp=system-fastdeploy%3FtemplateName%3Dopenlist) -### Manual deployment { lang="en" } - -### 手动部署 { lang="zh-CN" } - -#### 关键信息 { lang="zh-CN" } +### 手动部署 -#### Key Information { lang="en" } - -::: en -Name|Value|Description -:--|:--|:--- -Application Name|openlist|Application name -Image|openlistteam/openlist:latest-lite|Image, please make sure to use the one with **lite**, otherwise the error `Pod ephemeral local storage usage exceeds the total limit of containers 100Mi.` may occur -Replicas|1|Number of replicas, set to 1 -CPU|0.2|Number of CPU cores, set according to your own needs -Memory|256M|Memory size, set according to your own needs -Container Port|5244|Mapped port, which is `5244` if you have not modified the startup command or configuration -Public Access|Y|Enable external access -Custom Domain|-|If you have your own domain name, set it according to the prompts; if not, keep the default. Please make sure to use **https** for the protocol -Local Storage|-|Persistent volume --- Capacity|1|Capacity --- Mount Path|/opt/openlist/data|Configured mapped directory, which is `/opt/openlist/data` if you have not modified the startup command or configuration -::: -::: zh-CN -名称|值|说明 -:--|:--|:--- -Application Name|openlist|应用名 -Image|openlistteam/openlist:latest-lite|镜像，请务必使用带有**lite**的镜像，否则可能出现`Pod ephemeral local storage usage exceeds the total limit of containers 100Mi.` -Replicas|1|副本数，设置为1 -CPU|0.2|CPU核心数，请根据自身需求设置 -Memory|256M|内存大小，请根据自身需求设置 -Container Port|5244|映射端口，如果你没有修改启动命令或者配置，则为`5244` -Public Access|Y|打开外部访问 -Custom Domain|-|如果你有自身的域名，请根据提示进行设置，如果没有，保持默认，协议请务必使用**https** -Local Storage|-|持久卷 --- Capacity|1|容量 --- Mount Path|/opt/openlist/data|配置映射的目录，如果你没有修改启动命令或者配置，则为`/opt/openlist/data` -::: +#### 关键信息 -#### 参考图示 { lang="zh-CN" } +| 名称 | 值 | 说明 | +| :--------------- | :-------------------------------- | :------------------------------------------------------------------------------------------------------------------------------- | +| Application Name | openlist | 应用名 | +| Image | openlistteam/openlist:latest-lite | 镜像，请务必使用带有**lite**的镜像，否则可能出现`Pod ephemeral local storage usage exceeds the total limit of containers 100Mi.` | +| Replicas | 1 | 副本数，设置为1 | +| CPU | 0.2 | CPU核心数，请根据自身需求设置 | +| Memory | 256M | 内存大小，请根据自身需求设置 | +| Container Port | 5244 | 映射端口，如果你没有修改启动命令或者配置，则为`5244` | +| Public Access | Y | 打开外部访问 | +| Custom Domain | - | 如果你有自身的域名，请根据提示进行设置，如果没有，保持默认，协议请务必使用**https** | +| Local Storage | - | 持久卷 | +| -- Capacity | 1 | 容量 | +| -- Mount Path | /opt/openlist/data | 配置映射的目录，如果你没有修改启动命令或者配置，则为`/opt/openlist/data` | -#### Reference Diagram { lang="en" } +#### 参考图示  diff --git a/pages/guide/installation/reverse-proxy.md b/pages/guide/installation/reverse-proxy.md index 9b017b223..b9b52b7be 100644 --- a/pages/guide/installation/reverse-proxy.md +++ b/pages/guide/installation/reverse-proxy.md @@ -1,40 +1,11 @@ --- -# This is the title of the article -# title: One-click Script -title: - en: Reverse proxy - zh-CN: 反向代理 -icon: iconfont icon-page -# This control sidebar order top: 10 -# A page can have multiple categories categories: - guide - installation -# A page can have multiple tags -tag: - - Install - - Guide -# this page is sticky in article list -sticky: true -# this page will appear in starred articles -star: true --- -::: en -OpenList listens to port 5244 by default. If modified, please also update the port number in the configuration below. - -If you are using **reverse proxy**, please ensure that the correct `Host` header is passed, as OpenList will generate the URL based on this information. - -If the `Host` header is unavailable, you can use the higher-priority `X-Forwarded-Host` header (non-standard header). If the issue persists, configure the [site_url](../../configuration/configuration.md#site-url). - -If you want to use a **sub folder**, you should configure the [site_url](../../configuration/configuration.md#site-url). Refer to [reverse proxy with sub folder](../../faq/howto.md#how-to-reverse-proxy-with-sub-directory). - -:::warning -If you need to proxy to a non-standard port, make sure to pass the `domain:port` information through the `Host` or `X-Forwarded-Host` header, otherwise the port will be lost in URLs! -::: - -::: zh-CN +# 反向代理 OpenList 默认监听 5244 端口。如有修改，请一并修改下列配置中的端口号。 @@ -52,12 +23,7 @@ OpenList 默认监听 5244 端口。如有修改，请一并修改下列配置 https://nginx.org/en/docs/http/ngx_http_proxy_module.html -::: en -Add in the `server` field of the website configuration file: -::: -::: zh-CN 在网站配置文件的 `server` 字段中添加： -::: ```nginx location / { @@ -75,26 +41,6 @@ location / { } ``` -::: en -::: warning -If you use the aaPanel, be sure to delete the following default configuration: - -```nginx -location ~ ^/(\.user.ini|\.htaccess|\.git|\.svn|\.project|LICENSE|README.md -location ~ .\*\.(gif|jpg|jpeg|png|bmp|swf)$ -location ~ .\*\.(js|css)?$ -``` - -Disable Nginx caching in `/www/server/nginx/conf/proxy.conf` or the corresponding website configuration file. Otherwise, with the default configuration, when accessing large files, Nginx will attempt to cache the remote file locally first, resulting in playback failures. - -```nginx -proxy_cache cache_one; # Remove this line -proxy_max_temp_file_size 0; # Add this line -``` - -::: - -::: zh-CN ::: warning 如果使用宝塔面板，请务必删除以下默认配置： @@ -113,20 +59,6 @@ proxy_max_temp_file_size 0; #加上这一行 ::: -::: en - -::: note Nginx Host Variables Differences - -| Variable | Description | Includes Port | Notes | -| -------------------- | ------------------------------------------------ | ------------- | ---------------------------------------------------------------------------------------------------- | -| `$http_host` | The original `Host` request header | Yes | If the `Host` request header is missing, the value will be empty; not recommended for best practices | -| `$host` | Server name from the `Host` request header field | No | Defaults to the server's `server_name` if `Host` field is missing | -| `$host:$server_port` | Server name + port | Yes | Use this combination when you need to use a non-default port (other than 80 or 443) | - -::: - -::: zh-CN - ::: tip Nginx 主机变量区别 | 变量 | 内容 | 是否包含端口号 | 备注 | @@ -137,18 +69,6 @@ proxy_max_temp_file_size 0; #加上这一行 ::: -::: en -If HTTP/3 is needed, the corresponding `Host` line should be modified to: - -```nginx -proxy_set_header Host $host:$server_port; -``` - -This modified configuration will be compatible with requests using HTTP/2 or lower versions. - -::: - -::: zh-CN 如果需要使用 HTTP/3，需要将对应 `Host` 行修改为： ```nginx @@ -157,27 +77,8 @@ proxy_set_header Host $host:$server_port; 这样修改后的配置同时也可以兼容 HTTP/2 及更低版本的请求。 -::: - ## Apache -::: en -Add the anti-generation configuration item `ProxyPass` under the `VirtualHost` field, such as: - -```xml -