Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
67 changes: 67 additions & 0 deletions .github/workflows/docker.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,67 @@
name: Build and Publish Docker

on:
push:
branches: [ "main" ]
# Publish semver tags as releases.
tags: [ 'v*.*.*' ]
workflow_dispatch:

env:
REGISTRY: ghcr.io
# github.repository as <account>/<repo>
IMAGE_NAME: ${{ github.repository }}

jobs:
build:
runs-on: ubuntu-latest
permissions:
contents: read
packages: write
# This is used to complete the identity challenge
# with sigstore/fulcio when running outside of PRs.
id-token: write

steps:
- name: Checkout repository
uses: actions/checkout@v3

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

actions/checkout@v3 is deprecated — upgrade to v4.

v3 uses Node 16 which is EOL on GitHub Actions. This is also flagged by actionlint.

Proposed fix
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
uses: actions/checkout@v3
uses: actions/checkout@v4
🧰 Tools
🪛 actionlint (1.7.10)

[error] 27-27: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

🤖 Prompt for AI Agents
In @.github/workflows/docker.yml at line 27, Update the workflow step that
references actions/checkout@v3 to use actions/checkout@v4 to address
deprecation/Node16 EOL and satisfy actionlint; locate the line containing "uses:
actions/checkout@v3" and replace the version tag with "@v4", then run your
workflow linter and CI to verify there are no further compatibility issues.


# Install the cosign tool except on PR
# https://github.com/sigstore/cosign-installer
- name: Install cosign
if: github.event_name != 'pull_request'
uses: sigstore/cosign-installer@v3.5.0
with:
cosign-release: 'v2.2.4'
Comment on lines +29 to +35

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Cosign is installed but never used to sign the image.

The workflow installs cosign but there is no subsequent step that actually signs the built image digest. Either add a signing step after the build-and-push step, or remove the cosign installation to avoid unnecessary complexity and workflow time.

🤖 Prompt for AI Agents
In @.github/workflows/docker.yml around lines 29 - 35, The workflow installs
cosign in the "Install cosign" step but never uses it to sign the image; either
remove that step or add a post-build signing step: after the job step that
builds and pushes the image (the build-and-push step) add a step that runs
cosign sign --key or cosign sign --keyless against the pushed image digest (use
the same image name/digest output from the build step), or alternatively delete
the "Install cosign" step to avoid unnecessary installation; ensure the new step
references the image digest variable produced by the build-and-push step and
runs only when not a pull_request (same if condition as the Install cosign
step).


- name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3

- name: Log into registry ${{ env.REGISTRY }}
if: github.event_name != 'pull_request'
uses: docker/login-action@v3
with:
registry: ${{ env.REGISTRY }}
username: ${{ github.actor }}
password: ${{ secrets.GITHUB_TOKEN }}

- name: Extract Docker metadata
id: meta
uses: docker/metadata-action@v5
with:
images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
tags: |
type=raw,value=latest,enable={{is_default_branch}}
type=ref,event=branch
type=semver,pattern={{version}}

- name: Build and push Docker image
id: build-and-push
uses: docker/build-push-action@v5
with:
context: .
push: ${{ github.event_name != 'pull_request' }}
tags: ${{ steps.meta.outputs.tags }}
labels: ${{ steps.meta.outputs.labels }}
cache-from: type=gha
cache-to: type=gha,mode=max
43 changes: 43 additions & 0 deletions .github/workflows/sync.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
name: Sync Upstream

permissions:
contents: write

on:
schedule:
# Run once a day at midnight
- cron: "0 0 * * *"
workflow_dispatch:
Comment on lines +1 to +10

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

This workflow appears unrelated to the zh_TW localization PR.

A fork-sync workflow doesn't belong in a PR that adds Traditional Chinese support. Consider splitting this into a separate PR to keep changes focused and reviewable.

🤖 Prompt for AI Agents
In @.github/workflows/sync.yml around lines 1 - 10, This PR adds an unrelated CI
workflow called "Sync Upstream" (the sync.yml workflow with the schedule/cron
and workflow_dispatch entries); remove this workflow from the current changeset
and either revert the sync.yml addition or move it into a separate branch/PR
dedicated to fork-sync updates so the zh_TW localization PR only contains
localization files and related changes.


jobs:
sync_latest_from_upstream:
runs-on: ubuntu-latest
name: Sync latest commits from upstream repo

steps:
- name: Checkout target repo
uses: actions/checkout@v3

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Update actions/checkout to v4.

actions/checkout@v3 uses a deprecated Node.js runtime. Upgrade to v4 to avoid warnings and ensure continued compatibility with GitHub Actions runners.

Proposed fix
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
uses: actions/checkout@v3
uses: actions/checkout@v4
🧰 Tools
🪛 actionlint (1.7.10)

[error] 19-19: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

🤖 Prompt for AI Agents
In @.github/workflows/sync.yml at line 19, Update the GitHub Actions checkout
action reference from actions/checkout@v3 to actions/checkout@v4 to remove the
deprecated Node.js runtime warning; find the uses: actions/checkout@v3 entry in
the workflow (the checkout step) and change the version tag to `@v4` so the
workflow uses the v4 runner-compatible release.

with:
ref: main
fetch-depth: 0

- name: Sync upstream changes
id: sync
uses: aormsby/Fork-Sync-With-Upstream-action@v3.4
with:
upstream_sync_repo: QuantumNous/new-api
upstream_sync_branch: main
target_sync_branch: main
target_repo_token: ${{ secrets.GITHUB_TOKEN }}
upstream_pull_args: '--allow-unrelated-histories'
Comment on lines +26 to +32

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

aormsby Fork-Sync-With-Upstream-action GitHub latest version releases 2025

💡 Result:

  • Latest release (as of Feb 11, 2026): v3.4.1 (released Mar 9, 2024) for aormsby/Fork-Sync-With-Upstream-action. [1][2]
  • 2025 releases: None (the repo’s newest tag/release shown is still v3.4.1 from 2024). [1][3]

Use in workflow: uses: aormsby/Fork-Sync-With-Upstream-action@v3.4.1 [2]

Sources: [1] https://github.com/aormsby/Fork-Sync-With-Upstream-action/releases, [2] https://github.com/marketplace/actions/upstream-sync, [3] https://github.com/aormsby/Fork-Sync-With-Upstream-action/tags


🏁 Script executed:

# Search for the action repository and check if it's still maintained
cd /tmp && git clone --depth 1 https://github.com/aormsby/Fork-Sync-With-Upstream-action.git 2>/dev/null || echo "Clone check attempted"
# Check GitHub releases via web if available
curl -s "https://api.github.com/repos/aormsby/Fork-Sync-With-Upstream-action/releases" 2>/dev/null | jq -r '.[0:5] | .[] | "\(.tag_name) - \(.published_at)"' | head -10

Repository: QuantumNous/new-api

Length of output: 206


Update action to v3.4.1 (or pin to commit SHA) and remove --allow-unrelated-histories flag.

  1. The workflow uses v3.4 from October 2022; the latest version is v3.4.1 (March 2024). Update to at least v3.4.1, or follow best practice by pinning the action to a specific commit SHA rather than a mutable tag to mitigate supply-chain risks.
  2. --allow-unrelated-histories bypasses git's ancestry checks and can introduce unexpected merge artifacts. For a fork sync, this should not be necessary unless the repositories genuinely have divergent history that requires explicit acknowledgment. Remove it unless there is a documented reason.
Proposed fix
-        uses: aormsby/Fork-Sync-With-Upstream-action@v3.4
+        uses: aormsby/Fork-Sync-With-Upstream-action@v3.4.1
         with:
           upstream_sync_repo: QuantumNous/new-api
           upstream_sync_branch: main
           target_sync_branch: main
           target_repo_token: ${{ secrets.GITHUB_TOKEN }}
-          upstream_pull_args: '--allow-unrelated-histories'
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
uses: aormsby/Fork-Sync-With-Upstream-action@v3.4
with:
upstream_sync_repo: QuantumNous/new-api
upstream_sync_branch: main
target_sync_branch: main
target_repo_token: ${{ secrets.GITHUB_TOKEN }}
upstream_pull_args: '--allow-unrelated-histories'
uses: aormsby/Fork-Sync-With-Upstream-action@v3.4.1
with:
upstream_sync_repo: QuantumNous/new-api
upstream_sync_branch: main
target_sync_branch: main
target_repo_token: ${{ secrets.GITHUB_TOKEN }}
🤖 Prompt for AI Agents
In @.github/workflows/sync.yml around lines 26 - 32, Update the GitHub Action
reference and remove the unnecessary git flag: change the action reference
aormsby/Fork-Sync-With-Upstream-action@v3.4 to at least v3.4.1 or, preferably,
pin to a specific commit SHA, and delete the upstream_pull_args:
'--allow-unrelated-histories' line (remove use of upstream_pull_args entirely
unless there is a documented need for unrelated history merges).


- name: New commits found
if: steps.sync.outputs.has_new_commits == 'true'
run: echo "New commits were found to sync."

- name: No new commits
if: steps.sync.outputs.has_new_commits == 'false'
run: echo "There were no new commits."

- name: Show value of 'has_new_commits'
run: echo ${{ steps.sync.outputs.has_new_commits }}
Comment on lines +42 to +43

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Quote the expression to prevent shell injection.

Unquoted ${{ }} expressions in run: are a script injection vector. Always wrap them in quotes.

Proposed fix
-        run: echo ${{ steps.sync.outputs.has_new_commits }}
+        run: echo "${{ steps.sync.outputs.has_new_commits }}"
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- name: Show value of 'has_new_commits'
run: echo ${{ steps.sync.outputs.has_new_commits }}
- name: Show value of 'has_new_commits'
run: echo "${{ steps.sync.outputs.has_new_commits }}"
🤖 Prompt for AI Agents
In @.github/workflows/sync.yml around lines 42 - 43, The workflow step that
prints the has_new_commits output is using an unquoted GitHub Actions expression
which is a shell injection risk; update the step named "Show value of
'has_new_commits'" so the run command wraps the expression in quotes (i.e.,
quote the ${{ steps.sync.outputs.has_new_commits }} expression used in the run
line) to ensure the value is treated as a single string and prevent injection.

15 changes: 8 additions & 7 deletions README.fr.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,10 @@
🍥 **Passerelle de modèles étendus de nouvelle génération et système de gestion d'actifs d'IA**

<p align="center">
<a href="./README.zh.md">中文</a> |
<a href="./README.md">English</a> |
<strong>Français</strong> |
<a href="./README.zh_CN.md">简体中文</a> |
<a href="./README.zh_TW.md">繁體中文</a> |
<a href="./README.md">English</a> |
<strong>Français</strong> |
<a href="./README.ja.md">日本語</a>
</p>

Expand Down Expand Up @@ -56,10 +57,10 @@

## 📝 Description du projet

> [!NOTE]
> [!NOTE]
> Il s'agit d'un projet open-source développé sur la base de [One API](https://github.com/songquanpeng/one-api)

> [!IMPORTANT]
> [!IMPORTANT]
> - Ce projet est uniquement destiné à des fins d'apprentissage personnel, sans garantie de stabilité ni de support technique.
> - Les utilisateurs doivent se conformer aux [Conditions d'utilisation](https://openai.com/policies/terms-of-use) d'OpenAI et aux **lois et réglementations applicables**, et ne doivent pas l'utiliser à des fins illégales.
> - Conformément aux [《Mesures provisoires pour la gestion des services d'intelligence artificielle générative》](http://www.cac.gov.cn/2023-07/13/c_1690898327029107.htm), veuillez ne fournir aucun service d'IA générative non enregistré au public en Chine.
Expand Down Expand Up @@ -186,7 +187,7 @@ docker run --name new-api -d --restart always \
| Fonctionnalité | Description |
|------|------|
| 🎨 Nouvelle interface utilisateur | Conception d'interface utilisateur moderne |
| 🌍 Multilingue | Prend en charge le chinois, l'anglais, le français, le japonais |
| 🌍 Multilingue | Prend en charge le chinois simplifié, le chinois traditionnel, l'anglais, le français et le japonais |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Incomplete language list in the multilingual feature row.

The feature description lists Chinese (Simplified and Traditional), English, French, and Japanese, but omits Russian and Vietnamese which are also supported.

📝 Suggested fix
-| 🌍 Multilingue | Prend en charge le chinois simplifié, le chinois traditionnel, l'anglais, le français et le japonais |
+| 🌍 Multilingue | Prend en charge le chinois simplifié, le chinois traditionnel, l'anglais, le français, le russe, le japonais et le vietnamien |

Based on learnings: Frontend i18n supports zh_CN, zh_TW, en, fr, ru, ja, vi.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
| 🌍 Multilingue | Prend en charge le chinois simplifié, le chinois traditionnel, l'anglais, le français et le japonais |
| 🌍 Multilingue | Prend en charge le chinois simplifié, le chinois traditionnel, l'anglais, le français, le russe, le japonais et le vietnamien |
🤖 Prompt for AI Agents
In `@README.fr.md` at line 190, Update the Multilingue feature row string ("| 🌍
Multilingue | Prend en charge le chinois simplifié, le chinois traditionnel,
l'anglais, le français et le japonais |") to include Russian and Vietnamese as
supported languages (matching frontend i18n: zh_CN, zh_TW, en, fr, ru, ja, vi)
so the README accurately reflects all supported languages.

| 🔄 Compatibilité des données | Complètement compatible avec la base de données originale de One API |
| 📈 Tableau de bord des données | Console visuelle et analyse statistique |
| 🔒 Gestion des permissions | Regroupement de jetons, restrictions de modèles, gestion des utilisateurs |
Expand Down Expand Up @@ -372,7 +373,7 @@ docker run --name new-api -d --restart always \
calciumion/new-api:latest
```

> **💡 Explication du chemin:**
> **💡 Explication du chemin:**
> - `./data:/data` - Chemin relatif, données sauvegardées dans le dossier data du répertoire actuel
> - Vous pouvez également utiliser un chemin absolu, par exemple : `/your/custom/path:/data`

Expand Down
15 changes: 8 additions & 7 deletions README.ja.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,10 @@
🍥 **次世代大規模モデルゲートウェイとAI資産管理システム**

<p align="center">
<a href="./README.zh.md">中文</a> |
<a href="./README.md">English</a> |
<a href="./README.fr.md">Français</a> |
<a href="./README.zh_CN.md">简体中文</a> |
<a href="./README.zh_TW.md">繁體中文</a> |
<a href="./README.md">English</a> |
<a href="./README.fr.md">Français</a> |
<strong>日本語</strong>
</p>

Expand Down Expand Up @@ -56,10 +57,10 @@

## 📝 プロジェクト説明

> [!NOTE]
> [!NOTE]
> 本プロジェクトは、[One API](https://github.com/songquanpeng/one-api)をベースに二次開発されたオープンソースプロジェクトです

> [!IMPORTANT]
> [!IMPORTANT]
> - 本プロジェクトは個人学習用のみであり、安定性の保証や技術サポートは提供しません。
> - ユーザーは、OpenAIの[利用規約](https://openai.com/policies/terms-of-use)および**法律法規**を遵守する必要があり、違法な目的で使用してはいけません。
> - [《生成式人工智能服务管理暂行办法》](http://www.cac.gov.cn/2023-07/13/c_1690898327029107.htm)の要求に従い、中国地域の公衆に未登録の生成式AI サービスを提供しないでください。
Expand Down Expand Up @@ -186,7 +187,7 @@ docker run --name new-api -d --restart always \
| 機能 | 説明 |
|------|------|
| 🎨 新しいUI | モダンなユーザーインターフェースデザイン |
| 🌍 多言語 | 中国語、英語、フランス語、日本語をサポート |
| 🌍 多言語 | 簡体字中国語、繁体字中国語、英語、フランス語、日本語をサポート |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Incomplete language list in the multilingual feature row.

The feature lists Simplified Chinese, Traditional Chinese, English, French, and Japanese, but omits Russian and Vietnamese which are also supported by the frontend.

📝 Suggested fix
-| 🌍 多言語 | 簡体字中国語、繁体字中国語、英語、フランス語、日本語をサポート |
+| 🌍 多言語 | 簡体字中国語、繁体字中国語、英語、フランス語、ロシア語、日本語、ベトナム語をサポート |

Based on learnings: Frontend i18n supports zh_CN, zh_TW, en, fr, ru, ja, vi.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
| 🌍 多言語 | 簡体字中国語、繁体字中国語、英語、フランス語、日本語をサポート |
| 🌍 多言語 | 簡体字中国語、繁体字中国語、英語、フランス語、ロシア語、日本語、ベトナム語をサポート |
🤖 Prompt for AI Agents
In `@README.ja.md` at line 190, Update the multilingual feature row string that
currently reads "| 🌍 多言語 | 簡体字中国語、繁体字中国語、英語、フランス語、日本語をサポート |" to include
Russian and Vietnamese (e.g., add "ロシア語、ベトナム語") so it reflects frontend i18n
support for zh_CN, zh_TW, en, fr, ru, ja, vi; edit the README.ja.md table cell
with the "🌍 多言語" row to list all supported languages.

| 🔄 データ互換性 | オリジナルのOne APIデータベースと完全に互換性あり |
| 📈 データダッシュボード | ビジュアルコンソールと統計分析 |
| 🔒 権限管理 | トークングループ化、モデル制限、ユーザー管理 |
Expand Down Expand Up @@ -374,7 +375,7 @@ docker run --name new-api -d --restart always \
calciumion/new-api:latest
```

> **💡 パス説明:**
> **💡 パス説明:**
> - `./data:/data` - 相対パス、データは現在のディレクトリのdataフォルダに保存されます
> - 絶対パスを使用することもできます:`/your/custom/path:/data`

Expand Down
15 changes: 8 additions & 7 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,10 @@
🍥 **Next-Generation LLM Gateway and AI Asset Management System**

<p align="center">
<a href="./README.zh.md">中文</a> |
<strong>English</strong> |
<a href="./README.fr.md">Français</a> |
<a href="./README.zh_CN.md">简体中文</a> |
<a href="./README.zh_TW.md">繁體中文</a> |
<strong>English</strong> |
<a href="./README.fr.md">Français</a> |
<a href="./README.ja.md">日本語</a>
</p>

Expand Down Expand Up @@ -56,10 +57,10 @@

## 📝 Project Description

> [!NOTE]
> [!NOTE]
> This is an open-source project developed based on [One API](https://github.com/songquanpeng/one-api)

> [!IMPORTANT]
> [!IMPORTANT]
> - This project is for personal learning purposes only, with no guarantee of stability or technical support
> - Users must comply with OpenAI's [Terms of Use](https://openai.com/policies/terms-of-use) and **applicable laws and regulations**, and must not use it for illegal purposes
> - According to the [《Interim Measures for the Management of Generative Artificial Intelligence Services》](http://www.cac.gov.cn/2023-07/13/c_1690898327029107.htm), please do not provide any unregistered generative AI services to the public in China.
Expand Down Expand Up @@ -186,7 +187,7 @@ docker run --name new-api -d --restart always \
| Feature | Description |
|------|------|
| 🎨 New UI | Modern user interface design |
| 🌍 Multi-language | Supports Chinese, English, French, Japanese |
| 🌍 Multi-language | Supports Simplified Chinese, Traditional Chinese, English, French, Japanese |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Incomplete language list in the multilingual feature row.

The feature description mentions Simplified Chinese, Traditional Chinese, English, French, and Japanese, but omits Russian and Vietnamese which are also supported.

📝 Suggested fix
-| 🌍 Multi-language | Supports Simplified Chinese, Traditional Chinese, English, French, Japanese |
+| 🌍 Multi-language | Supports Simplified Chinese, Traditional Chinese, English, French, Russian, Japanese, Vietnamese |

Based on learnings: Frontend i18n supports zh_CN, zh_TW, en, fr, ru, ja, vi.

🤖 Prompt for AI Agents
In `@README.md` at line 190, Update the "🌍 Multi-language" table row in README.md
to include the missing languages Russian and Vietnamese; locate the row that
currently reads "Supports Simplified Chinese, Traditional Chinese, English,
French, Japanese" and expand it to list all supported locales (e.g., Simplified
Chinese, Traditional Chinese, English, French, Russian, Japanese, Vietnamese or
corresponding locale codes zh_CN, zh_TW, en, fr, ru, ja, vi) so the README
accurately reflects frontend i18n support.

| 🔄 Data Compatibility | Fully compatible with the original One API database |
| 📈 Data Dashboard | Visual console and statistical analysis |
| 🔒 Permission Management | Token grouping, model restrictions, user management |
Expand Down Expand Up @@ -372,7 +373,7 @@ docker run --name new-api -d --restart always \
calciumion/new-api:latest
```

> **💡 Path explanation:**
> **💡 Path explanation:**
> - `./data:/data` - Relative path, data saved in the data folder of the current directory
> - You can also use absolute path, e.g.: `/your/custom/path:/data`

Expand Down
13 changes: 7 additions & 6 deletions README.zh.md → README.zh_CN.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,10 @@
🍥 **新一代大模型网关与AI资产管理系统**

<p align="center">
<strong>中文</strong> |
<a href="./README.md">English</a> |
<a href="./README.fr.md">Français</a> |
简体中文 |
<a href="./README.zh_TW.md">繁體中文</a> |
<a href="./README.md">English</a> |
<a href="./README.fr.md">Français</a> |
<a href="./README.ja.md">日本語</a>
</p>

Expand Down Expand Up @@ -56,10 +57,10 @@

## 📝 项目说明

> [!NOTE]
> [!NOTE]
> 本项目为开源项目,在 [One API](https://github.com/songquanpeng/one-api) 的基础上进行二次开发

> [!IMPORTANT]
> [!IMPORTANT]
> - 本项目仅供个人学习使用,不保证稳定性,且不提供任何技术支持
> - 使用者必须在遵循 OpenAI 的 [使用条款](https://openai.com/policies/terms-of-use) 以及**法律法规**的情况下使用,不得用于非法用途
> - 根据 [《生成式人工智能服务管理暂行办法》](http://www.cac.gov.cn/2023-07/13/c_1690898327029107.htm) 的要求,请勿对中国地区公众提供一切未经备案的生成式人工智能服务
Expand Down Expand Up @@ -372,7 +373,7 @@ docker run --name new-api -d --restart always \
calciumion/new-api:latest
```

> **💡 路径说明:**
> **💡 路径说明:**
> - `./data:/data` - 相对路径,数据保存在当前目录的 data 文件夹
> - 也可使用绝对路径,如:`/your/custom/path:/data`

Expand Down
Loading