chore: initial import — heicode manager + website
This commit is contained in:
@@ -0,0 +1,33 @@
|
||||
# 渠道而外设置说明
|
||||
|
||||
该配置用于设置一些额外的渠道参数，可以通过 JSON 对象进行配置。主要包含以下两个设置项：
|
||||
|
||||
1. force_format
|
||||
- 用于标识是否对数据进行强制格式化为 OpenAI 格式
|
||||
- 类型为布尔值，设置为 true 时启用强制格式化
|
||||
|
||||
2. proxy
|
||||
- 用于配置网络代理
|
||||
- 类型为字符串，填写代理地址（例如 socks5 协议的代理地址）
|
||||
|
||||
3. thinking_to_content
|
||||
- 用于标识是否将思考内容`reasoning_content`转换为`<think>`标签拼接到内容中返回
|
||||
- 类型为布尔值，设置为 true 时启用思考内容转换
|
||||
|
||||
--------------------------------------------------------------
|
||||
|
||||
## JSON 格式示例
|
||||
|
||||
以下是一个示例配置，启用强制格式化并设置了代理地址：
|
||||
|
||||
```json
|
||||
{
|
||||
"force_format": true,
|
||||
"thinking_to_content": true,
|
||||
"proxy": "socks5://xxxxxxx"
|
||||
}
|
||||
```
|
||||
|
||||
--------------------------------------------------------------
|
||||
|
||||
通过调整上述 JSON 配置中的值，可以灵活控制渠道的额外行为，比如是否进行格式化以及使用特定的网络代理。
|
||||
@@ -0,0 +1,184 @@
|
||||
# NewAPI / Heicode Manager Rebuild and Deploy Runbook
|
||||
|
||||
Date: 2026-05-03
|
||||
Scope: rebuild and deploy the `heicode` Manager service on an Azure VM while keeping NewAPI as an independent model gateway.
|
||||
Security rule: never put real passwords, tokens, SSH keys, Redis keys, PostgreSQL DSNs, NewAPI keys, or cloud credentials in Git, Markdown, shell history, tickets, or logs. Use environment variables, `.env` on the VM, Secret Store references, or `REDACTED` placeholders only.
|
||||
|
||||
## 1. Current repo deployment surfaces
|
||||
|
||||
| Surface | Purpose | Notes |
|
||||
|---|---|---|
|
||||
| `heicode/Dockerfile` | Production image build | Builds default and classic web assets, then compiles the Go binary. |
|
||||
| `heicode/docker-compose.azure-vm.yml` | Azure VM Manager service | Runs only `heicode`; PostgreSQL and Redis are expected to be managed Azure services. |
|
||||
| `heicode/docker-compose.override.yml` | Local-source image override | Builds `heicode-manager:local` from the checked-out repo. Keep it in the compose file list when deploying this repo state. |
|
||||
| `heicode/bin/azure_vm_deploy.sh` | SSH deployment helper | Uses env vars only; can fast-forward a remote branch, performs remote compose up, health gate, and rollback pointer capture. |
|
||||
| `heicode/bin/acceptance_agnet_local.sh` | Local Agnet control-plane smoke/acceptance probe | Requires an admin session cookie supplied via env; does not store credentials. |
|
||||
| `heicode/.env.example` | Env-var reference | Placeholder-only reference; production `.env` must stay on the VM and out of Git. |
|
||||
|
||||
## 2. Required VM inputs
|
||||
|
||||
Prepare these values outside the repo, for example in a secret manager, CI secret store, or an uncommitted VM-local `.env`:
|
||||
|
||||
```text
|
||||
VM_HOST=<azure-vm-host-or-ip>
|
||||
VM_USER=<ssh-user>
|
||||
REMOTE_DIR=/opt/heicode/heicode
|
||||
GIT_REF=main
|
||||
HEICODE_DATA_ROOT=/var/lib/heicode/heicode
|
||||
SQL_DSN=postgresql://<user>:REDACTED@<azure-postgres-host>:5432/heicode?sslmode=require
|
||||
REDIS_CONN_STRING=rediss://:REDACTED@<azure-redis-host>:6380
|
||||
SESSION_SECRET=REDACTED
|
||||
HEICODE_AUTH_BASE_URL=https://apimtaiji.azure-api.net/api/mcp
|
||||
HEICODE_ROOT_EMAILS=<comma-separated-admin-emails-if-needed>
|
||||
HEICODE_ADMIN_EMAILS=<comma-separated-admin-emails-if-needed>
|
||||
```
|
||||
|
||||
Do not paste real values into this document, commits, chat, or terminal transcripts that will be saved.
|
||||
|
||||
## 3. Pre-deploy checklist
|
||||
|
||||
Run locally from the repo root unless stated otherwise:
|
||||
|
||||
1. Confirm mainline docs boundary:
|
||||
- `docs/heicode.md`
|
||||
- `docs/plan.md`
|
||||
- `docs/README.md`
|
||||
2. Confirm worktree state:
|
||||
- `git status --short`
|
||||
3. Validate compose syntax without exposing secrets:
|
||||
- `cd heicode`
|
||||
- `cat > /tmp/heicode.deploy.env <<'EOF_ENV'`
|
||||
- `HEICODE_DATA_ROOT=/tmp/heicode-data`
|
||||
- `SQL_DSN=REDACTED`
|
||||
- `REDIS_CONN_STRING=REDACTED`
|
||||
- `SESSION_SECRET=REDACTED`
|
||||
- `EOF_ENV`
|
||||
- `ENV_FILE=/tmp/heicode.deploy.env IMAGE_TAG=heicode-manager:local docker compose -f docker-compose.azure-vm.yml -f docker-compose.override.yml --env-file /tmp/heicode.deploy.env config --quiet`
|
||||
- `rm -f /tmp/heicode.deploy.env`
|
||||
4. Build verification options:
|
||||
- Preferred full image check: `cd heicode && docker compose -f docker-compose.azure-vm.yml -f docker-compose.override.yml build heicode`
|
||||
- Backend slice check when full image build is too slow: `cd heicode && go test -count=1 ./controller ./model ./router`
|
||||
5. Confirm no secrets are staged:
|
||||
- `git diff --cached -- . ':!*.jpg' ':!*.png'`
|
||||
- Search for known real secret fragments only locally; never copy matches into reports.
|
||||
|
||||
## 4. VM preparation checklist
|
||||
|
||||
Run on the Azure VM:
|
||||
|
||||
```bash
|
||||
export HEICODE_DATA_ROOT=/var/lib/heicode/heicode
|
||||
sudo mkdir -p "$HEICODE_DATA_ROOT"/data "$HEICODE_DATA_ROOT"/logs
|
||||
sudo chown -R "$USER":"$USER" "$HEICODE_DATA_ROOT"
|
||||
cd /opt/heicode/heicode
|
||||
```
|
||||
|
||||
Create or update VM-local `.env` in `REMOTE_DIR`; keep it untracked:
|
||||
|
||||
```bash
|
||||
cat > .env <<'EOF_ENV'
|
||||
HEICODE_DATA_ROOT=/var/lib/heicode/heicode
|
||||
SQL_DSN=postgresql://<user>:REDACTED@<azure-postgres-host>:5432/heicode?sslmode=require
|
||||
REDIS_CONN_STRING=rediss://:REDACTED@<azure-redis-host>:6380
|
||||
SESSION_SECRET=REDACTED
|
||||
HEICODE_AUTH_BASE_URL=https://apimtaiji.azure-api.net/api/mcp
|
||||
HEICODE_ROOT_EMAILS=
|
||||
HEICODE_ADMIN_EMAILS=
|
||||
EOF_ENV
|
||||
chmod 600 .env
|
||||
```
|
||||
|
||||
Replace `REDACTED` placeholders through a secure VM-local editor or secret injection mechanism only.
|
||||
|
||||
## 5. Rebuild and deploy procedure
|
||||
|
||||
From the local control machine, after the VM repo has the intended commit:
|
||||
|
||||
```bash
|
||||
cd heicode
|
||||
VM_HOST=<azure-vm-host-or-ip> \
|
||||
VM_USER=<ssh-user> \
|
||||
REMOTE_DIR=/opt/heicode/heicode \
|
||||
GIT_REF=main \
|
||||
HEALTH_URL=http://127.0.0.1:3000/api/status \
|
||||
./bin/azure_vm_deploy.sh
|
||||
```
|
||||
|
||||
The script will:
|
||||
|
||||
1. SSH to the VM.
|
||||
2. Verify the remote repo, compose CLI, compose file, and VM-local env file exist.
|
||||
3. If `GIT_REF` is set, fast-forward the remote checkout from `origin/<GIT_REF>`.
|
||||
4. Record the currently running container image in `.last_success_image` when available.
|
||||
5. Run `ENV_FILE=.env docker compose -f docker-compose.azure-vm.yml -f docker-compose.override.yml --env-file .env up -d --build --force-recreate heicode`.
|
||||
6. Poll `/api/status` through the VM-local health URL.
|
||||
7. Update `.last_success_image` only after the health gate passes.
|
||||
|
||||
## 5.1 Agnet operator handoff
|
||||
|
||||
When Agnet is the executor, Manager should create a high-risk `newapi-rebuild-deploy` deployment using `docs/integration/agnet-platform-request-contract.md` and pass only references:
|
||||
|
||||
| Field | Required reference |
|
||||
|---|---|
|
||||
| `resource_grants[].secret_ref` | Secret Store reference for SSH access and runtime env access; never plaintext. |
|
||||
| `resource_grants[].metadata.host_ref` | `env://NEWAPI_VM_HOST` or equivalent platform secret/env ref. |
|
||||
| `resource_grants[].constraints.rollback_command_ref` | `runbook://newapi/rollback` or this runbook section. |
|
||||
| `orchestration_plan.constraints.healthcheck_url_ref` | `env://NEWAPI_HEALTHCHECK_URL`, expected to resolve to the VM-local `/api/status` probe. |
|
||||
| `orchestration_plan.metadata.commit` | Intended Git commit or branch to deploy, such as `origin/main` after push. |
|
||||
|
||||
Minimum evidence Agnet must return before Manager marks the operation deployed:
|
||||
|
||||
1. Remote commit after fetch/pull.
|
||||
2. `docker compose ... ps` status for `heicode`.
|
||||
3. Health check response proving `"success":true`.
|
||||
4. Redacted log tail or log digest.
|
||||
5. Rollback pointer (`.last_success_image`) update or explicit note that no previous image existed.
|
||||
|
||||
If any item is missing, Manager must keep the deployment in `running`, `failed`, or `pending_operator_review`; it must not report production deployment as completed.
|
||||
|
||||
## 6. Post-deploy verification checklist
|
||||
|
||||
Run on the VM or through secure operator access:
|
||||
|
||||
```bash
|
||||
cd /opt/heicode/heicode
|
||||
ENV_FILE=.env docker compose -f docker-compose.azure-vm.yml -f docker-compose.override.yml --env-file .env ps
|
||||
ENV_FILE=.env docker compose -f docker-compose.azure-vm.yml -f docker-compose.override.yml --env-file .env logs --tail=100 heicode
|
||||
curl -fsS http://127.0.0.1:3000/api/status
|
||||
```
|
||||
|
||||
Expected health response includes `"success":true`.
|
||||
|
||||
Optional Manager / Agnet smoke probe after obtaining a safe admin session cookie without logging it:
|
||||
|
||||
```bash
|
||||
AUTH_COOKIE='REDACTED_SESSION_COOKIE' \
|
||||
BASE_URL='http://127.0.0.1:3000' \
|
||||
TENANT_ID='tenant_smoke' \
|
||||
PROJECT_ID='project_smoke' \
|
||||
./bin/acceptance_agnet_local.sh
|
||||
```
|
||||
|
||||
Do not commit or report the real cookie.
|
||||
|
||||
## 7. Rollback checklist
|
||||
|
||||
If the health gate fails or post-deploy checks fail:
|
||||
|
||||
1. Keep the failed container logs for local VM inspection only; redact before sharing.
|
||||
2. Inspect `.last_success_image` on the VM.
|
||||
3. Re-run compose with the last known good image or revert the repo commit, then:
|
||||
|
||||
```bash
|
||||
ENV_FILE=.env docker compose -f docker-compose.azure-vm.yml --env-file .env up -d --force-recreate heicode
|
||||
curl -fsS http://127.0.0.1:3000/api/status
|
||||
```
|
||||
|
||||
4. If database migrations were applied by the app, do not manually mutate production data without an explicit backup and approval.
|
||||
|
||||
## 8. Known risks / open items
|
||||
|
||||
- `go test ./...` can be blocked by missing embedded frontend build artifacts or pre-existing relay tests; use focused checks for the changed slice and a full Docker image build before production.
|
||||
- Production PostgreSQL and Redis are external managed services; the compose file intentionally does not start local database/cache containers for Azure VM deployment.
|
||||
- NewAPI remains an independent model gateway and should not be exposed as a normal SaaS user backend.
|
||||
- Long-lived secrets must move toward Secret Store / Secret Broker; current VM `.env` usage is an operational bridge, not the final P2 target.
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 7.1 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 5.0 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 11 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 2.0 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 12 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 11 KiB |
@@ -0,0 +1,151 @@
|
||||
# 宝塔面板部署教程
|
||||
|
||||
本文档提供使用宝塔面板 Docker 功能部署 New API 的图文教程。
|
||||
|
||||
> 📖 官方文档：[宝塔面板部署](https://docs.newapi.pro/zh/docs/installation/deployment-methods/bt-docker-installation)
|
||||
|
||||
***
|
||||
|
||||
## 前置要求
|
||||
|
||||
| 项目 | 要求 |
|
||||
| ----- | ---------------------------------- |
|
||||
| 宝塔面板 | ≥ 9.2.0 版本 |
|
||||
| 推荐系统 | CentOS 7+、Ubuntu 18.04+、Debian 10+ |
|
||||
| 服务器配置 | 至少 1 核 2G 内存 |
|
||||
|
||||
***
|
||||
|
||||
## 步骤一：安装宝塔面板
|
||||
|
||||
1. 前往 [宝塔面板官网](https://www.bt.cn/new/download.html) 下载适合您系统的安装脚本
|
||||
2. 运行安装脚本安装宝塔面板
|
||||
3. 安装完成后，使用提供的地址、用户名和密码登录宝塔面板
|
||||
|
||||
***
|
||||
|
||||
## 步骤二：安装 Docker
|
||||
|
||||
1. 登录宝塔面板后，在左侧菜单栏找到并点击 **Docker**
|
||||
2. 首次进入会提示安装 Docker 服务，点击 **立即安装**
|
||||
3. 按照提示完成 Docker 服务的安装
|
||||
|
||||
***
|
||||
|
||||
## 步骤三：安装 New API
|
||||
|
||||
### 方法一：使用宝塔应用商店（推荐）
|
||||
|
||||
1. 在宝塔面板 Docker 功能中，点击 **应用商店**
|
||||
2. 搜索并找到 **New-API**
|
||||
3. 点击 **安装**
|
||||
4. 配置以下基本选项：
|
||||
- **容器名称**：可自定义，默认为 `heicode`
|
||||
- **端口映射**：默认为 `3000:3000`
|
||||
- **环境变量**：
|
||||
- `SESSION_SECRET`：会话密钥（**必填**，多机部署时必须一致）
|
||||
- `CRYPTO_SECRET`：加密密钥（使用 Redis 时必填）
|
||||
5. 点击 **确认** 开始安装
|
||||
6. 等待安装完成后，访问 `http://您的服务器IP:3000` 即可使用
|
||||
|
||||
### 方法二：使用 Docker Compose
|
||||
|
||||
1. 在宝塔面板中创建网站目录，如 `/www/wwwroot/heicode`
|
||||
2. 创建 `docker-compose.yml` 文件：
|
||||
|
||||
```yaml
|
||||
version: '3'
|
||||
services:
|
||||
heicode:
|
||||
image: calciumion/heicode:latest
|
||||
container_name: heicode
|
||||
restart: always
|
||||
ports:
|
||||
- "3000:3000"
|
||||
volumes:
|
||||
- ./data:/data
|
||||
environment:
|
||||
- SESSION_SECRET=your_session_secret_here # 请修改为随机字符串
|
||||
- TZ=Asia/Shanghai
|
||||
```
|
||||
|
||||
1. 在终端中进入目录并启动：
|
||||
|
||||
```bash
|
||||
cd /www/wwwroot/heicode
|
||||
docker-compose up -d
|
||||
```
|
||||
|
||||
***
|
||||
|
||||
## 配置说明
|
||||
|
||||
### 必要环境变量
|
||||
|
||||
| 变量名 | 说明 | 是否必填 |
|
||||
| ------------------- | ------------------ | ------ |
|
||||
| `SESSION_SECRET` | 会话密钥，多机部署必须一致 | **必填** |
|
||||
| `CRYPTO_SECRET` | 加密密钥，使用 Redis 时必填 | 条件必填 |
|
||||
| `SQL_DSN` | 数据库连接字符串（使用外部数据库时） | 可选 |
|
||||
| `REDIS_CONN_STRING` | Redis 连接字符串 | 可选 |
|
||||
|
||||
### 生成随机密钥
|
||||
|
||||
```bash
|
||||
# 生成 SESSION_SECRET
|
||||
openssl rand -hex 16
|
||||
|
||||
# 或使用 Linux 命令
|
||||
head -c 16 /dev/urandom | xxd -p
|
||||
```
|
||||
|
||||
***
|
||||
|
||||
## 常见问题
|
||||
|
||||
### Q1：无法访问 3000 端口？
|
||||
|
||||
1. 检查服务器防火墙是否开放 3000 端口
|
||||
2. 在宝塔面板 **安全** 中放行 3000 端口
|
||||
3. 检查云服务器安全组是否开放端口
|
||||
|
||||
### Q2：登录后提示会话失效？
|
||||
|
||||
确保设置了 `SESSION_SECRET` 环境变量，且值不为空。
|
||||
|
||||
### Q3：数据如何持久化？
|
||||
|
||||
使用 Docker 卷映射数据目录：
|
||||
|
||||
```yaml
|
||||
volumes:
|
||||
- ./data:/data
|
||||
```
|
||||
|
||||
### Q4：如何更新版本？
|
||||
|
||||
```bash
|
||||
# 拉取最新镜像
|
||||
docker pull calciumion/heicode:latest
|
||||
|
||||
# 重启容器
|
||||
docker-compose down && docker-compose up -d
|
||||
```
|
||||
|
||||
***
|
||||
|
||||
## 相关链接
|
||||
|
||||
- [官方文档](https://docs.newapi.pro/zh/docs/installation)
|
||||
- [环境变量配置](https://docs.newapi.pro/zh/docs/installation/config-maintenance/environment-variables)
|
||||
- [常见问题](https://docs.newapi.pro/zh/docs/support/faq)
|
||||
- [GitHub 仓库](https://github.com/QuantumNous/heicode)
|
||||
|
||||
***
|
||||
|
||||
## 截图示例
|
||||
|
||||
|
||||
|
||||
> ⚠️ 注意：密钥为环境变量 `SESSION_SECRET`，请务必设置！
|
||||
|
||||
@@ -0,0 +1,7 @@
|
||||
Request URL
|
||||
https://api.io.solutions/v1/io-cloud/clusters/654fc0a9-0d4a-4db4-9b95-3f56189348a2/update-name
|
||||
Request Method
|
||||
PUT
|
||||
|
||||
{"status":"succeeded","message":"Cluster name updated successfully"}
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@@ -0,0 +1,107 @@
|
||||
# Glossaire Français (French Glossary)
|
||||
|
||||
Ce document fournit des traductions standards françaises pour la terminologie clé du projet afin d'assurer la cohérence et la précision des traductions.
|
||||
|
||||
This document provides standard French translations for key project terminology to ensure consistency and accuracy in translations.
|
||||
|
||||
## Concepts de Base (Core Concepts)
|
||||
|
||||
- L'utilisation d'émojis dans les traductions est autorisée s'ils sont présents dans l'original
|
||||
- L'utilisation de termes purement techniques est autorisée s'ils sont présents dans l'original
|
||||
- L'utilisation de termes techniques en anglais est autorisée s'ils sont largement utilisés dans l'environnement technique francophone (par exemple, API)
|
||||
|
||||
| Chinois | Français | Anglais | Description |
|
||||
|---------|----------|---------|-------------|
|
||||
| 倍率 | Ratio | Ratio/Multiplier | Multiplicateur utilisé pour le calcul des prix. **Important :** Dans le contexte des calculs de prix, toujours utiliser "Ratio" plutôt que "Multiplicateur" pour assurer la cohérence terminologique |
|
||||
| 令牌 | Jeton | Token | Identifiants d'accès API ou unités de texte traitées par les modèles |
|
||||
| 渠道 | Canal | Channel | Canal d'accès aux fournisseurs d'API |
|
||||
| 分组 | Groupe | Group | Classification des utilisateurs ou des jetons |
|
||||
| 额度 | Quota | Quota | Quota de services disponible pour l'utilisateur |
|
||||
|
||||
## Modèles (Model Related)
|
||||
|
||||
| Chinois | Français | Anglais | Description |
|
||||
|---------|----------|---------|-------------|
|
||||
| 提示 | Invite | Prompt | Contenu d'entrée du modèle |
|
||||
| 补全 | Complétion | Completion | Contenu de sortie du modèle. **Important :** Ne pas utiliser "Achèvement" ou "Finalisation" - uniquement "Complétion" pour correspondre à la terminologie technique |
|
||||
| 输入 | Entrée | Input/Prompt | Contenu envoyé au modèle |
|
||||
| 输出 | Sortie | Output/Completion | Contenu retourné par le modèle |
|
||||
| 模型倍率 | Ratio du modèle | Model Ratio | Ratio de tarification pour différents modèles |
|
||||
| 补全倍率 | Ratio de complétion | Completion Ratio | Ratio de tarification supplémentaire pour la sortie |
|
||||
| 固定价格 | Prix fixe | Price per call | Prix par appel |
|
||||
| 按量计费 | Paiement à l'utilisation | Pay-as-you-go | Tarification basée sur l'utilisation |
|
||||
| 按次计费 | Paiement par appel | Pay-per-view | Prix fixe par appel |
|
||||
|
||||
## Gestion des Utilisateurs (User Management)
|
||||
|
||||
| Chinois | Français | Anglais | Description |
|
||||
|---------|----------|---------|-------------|
|
||||
| 超级管理员 | Super-administrateur | Root User | Administrateur avec les privilèges les plus élevés |
|
||||
| 管理员 | Administrateur | Admin User | Administrateur système |
|
||||
| 普通用户 | Utilisateur normal | Normal User | Utilisateur avec privilèges standards |
|
||||
|
||||
## Recharge et Échange (Recharge & Redemption)
|
||||
|
||||
| Chinois | Français | Anglais | Description |
|
||||
|---------|----------|---------|-------------|
|
||||
| 充值 | Recharge | Top Up | Ajout de quota au compte |
|
||||
| 兑换码 | Code d'échange | Redemption Code | Code qui peut être échangé contre du quota |
|
||||
|
||||
## Gestion des Canaux (Channel Management)
|
||||
|
||||
| Chinois | Français | Anglais | Description |
|
||||
|---------|----------|---------|-------------|
|
||||
| 渠道 | Canal | Channel | Canal du fournisseur d'API |
|
||||
| API密钥 | Clé API | API Key | Clé d'accès API. **Important :** Utiliser "Clé API" au lieu de "Jeton API" pour plus de précision et conformément à la terminologie technique francophone établie. Le terme "Clé" reflète mieux la fonctionnalité d'accès aux ressources, tandis que "Jeton" est plus souvent associé aux unités de texte dans le contexte du traitement des modèles linguistiques. |
|
||||
| 优先级 | Priorité | Priority | Priorité de sélection du canal |
|
||||
| 权重 | Poids | Weight | Poids d'équilibrage de charge |
|
||||
| 代理 | Proxy | Proxy | Adresse du serveur proxy |
|
||||
| 模型重定向 | Redirection de modèle | Model Mapping | Remplacement du nom du modèle dans le corps de la requête |
|
||||
| 供应商 | Fournisseur | Provider/Vendor | Fournisseur de services ou d'API |
|
||||
|
||||
## Sécurité (Security Related)
|
||||
|
||||
| Chinois | Français | Anglais | Description |
|
||||
|---------|----------|---------|-------------|
|
||||
| 两步验证 | Authentification à deux facteurs | Two-Factor Authentication | Méthode de vérification de sécurité supplémentaire pour les comptes |
|
||||
| 2FA | 2FA | Two-Factor Authentication | Abréviation de l'authentification à deux facteurs |
|
||||
|
||||
## Recommandations de Traduction (Translation Guidelines)
|
||||
|
||||
### Variantes Contextuelles de Traduction
|
||||
|
||||
**Invite/Entrée (Prompt/Input)**
|
||||
|
||||
- **Invite** : Lors de l'interaction avec les LLM, dans l'interface utilisateur, lors de la description de l'interaction avec le modèle
|
||||
- **Entrée** : Dans la tarification, la documentation technique, la description du processus de traitement des données
|
||||
- **Règle** : S'il s'agit de l'expérience utilisateur et de l'interaction avec l'IA → "Invite", s'il s'agit du processus technique ou des calculs → "Entrée"
|
||||
|
||||
**Jeton (Token)**
|
||||
|
||||
- Jeton d'accès API (API Token)
|
||||
- Unité de texte traitée par le modèle (Text Token)
|
||||
- Jeton d'accès système (Access Token)
|
||||
|
||||
**Quota (Quota)**
|
||||
|
||||
- Quota de services disponible pour l'utilisateur
|
||||
- Parfois traduit comme "Crédit"
|
||||
|
||||
### Particularités de la Langue Française
|
||||
|
||||
- **Formes plurielles** : Nécessite une implémentation correcte des formes plurielles (_one, _other)
|
||||
- **Accords grammaticaux** : Attention aux accords grammaticaux dans les termes techniques
|
||||
- **Genre grammatical** : Accord du genre des termes techniques (par exemple, "modèle" - masculin, "canal" - masculin)
|
||||
|
||||
### Termes Standardisés
|
||||
|
||||
- **Complétion (Completion)** : Contenu de sortie du modèle
|
||||
- **Ratio (Ratio)** : Multiplicateur pour le calcul des prix
|
||||
- **Code d'échange (Redemption Code)** : Utilisé au lieu de "Code d'échange" pour plus de précision
|
||||
- **Fournisseur (Provider/Vendor)** : Organisation ou service fournissant des API ou des modèles d'IA
|
||||
|
||||
---
|
||||
|
||||
**Note pour les contributeurs :** Si vous trouvez des incohérences dans les traductions de terminologie ou si vous avez de meilleures suggestions de traduction pour le français, n'hésitez pas à créer une Issue ou une Pull Request.
|
||||
|
||||
**Contribution Note for French:** If you find any inconsistencies in terminology translations or have better translation suggestions for French, please feel free to submit an Issue or Pull Request.
|
||||
@@ -0,0 +1,86 @@
|
||||
# 翻译术语表 (Translation Glossary)
|
||||
|
||||
本文档为翻译贡献者提供项目中关键术语的标准翻译参考，以确保翻译的一致性和准确性。
|
||||
|
||||
This document provides standard translation references for key terminology in the project to ensure consistency and accuracy for translation contributors.
|
||||
|
||||
## 核心概念 (Core Concepts)
|
||||
|
||||
| 中文 | English | 说明 | Description |
|
||||
|------|---------|------|-------------|
|
||||
| 倍率 | Ratio | 用于计算价格的乘数因子 | Multiplier factor used for price calculation |
|
||||
| 令牌 | Token | API访问凭证，也指模型处理的文本单元 | API access credentials or text units processed by models |
|
||||
| 渠道 | Channel | API服务提供商的接入通道 | Access channel for API service providers |
|
||||
| 分组 | Group | 用户或令牌的分类，影响价格倍率 | Classification of users or tokens, affecting price ratios |
|
||||
| 额度 | Quota | 用户可用的服务额度 | Available service quota for users |
|
||||
|
||||
## 模型相关 (Model Related)
|
||||
|
||||
| 中文 | English | 说明 | Description |
|
||||
|------|---------|------|-------------|
|
||||
| 提示 | Prompt | 模型输入内容 | Model input content |
|
||||
| 补全 | Completion | 模型输出内容 | Model output content |
|
||||
| 输入 | Input/Prompt | 发送给模型的内容 | Content sent to the model |
|
||||
| 输出 | Output/Completion | 模型返回的内容 | Content returned by the model |
|
||||
| 模型倍率 | Model Ratio | 不同模型的计费倍率 | Billing ratio for different models |
|
||||
| 补全倍率 | Completion Ratio | 输出内容的额外计费倍率 | Additional billing ratio for output content |
|
||||
| 固定价格 | Price per call | 按次计费的价格 | Fixed price per call |
|
||||
| 按量计费 | Pay-as-you-go | 根据使用量计费 | Billing based on usage |
|
||||
| 按次计费 | Pay-per-view | 每次调用固定价格 | Fixed price per invocation |
|
||||
|
||||
## 用户管理 (User Management)
|
||||
|
||||
| 中文 | English | 说明 | Description |
|
||||
|------|---------|------|-------------|
|
||||
| 超级管理员 | Root User | 最高权限管理员 | Administrator with highest privileges |
|
||||
| 管理员 | Admin User | 系统管理员 | System administrator |
|
||||
| 普通用户 | Normal User | 普通权限用户 | Regular user with standard privileges |
|
||||
|
||||
## 充值与兑换 (Recharge & Redemption)
|
||||
|
||||
| 中文 | English | 说明 | Description |
|
||||
|------|---------|------|-------------|
|
||||
| 充值 | Top Up | 为账户增加额度 | Add quota to account |
|
||||
| 兑换码 | Redemption Code | 可兑换额度的代码 | Code that can be redeemed for quota |
|
||||
|
||||
## 渠道管理 (Channel Management)
|
||||
|
||||
| 中文 | English | 说明 | Description |
|
||||
|------|---------|------|-------------|
|
||||
| 渠道 | Channel | API服务提供通道 | API service provider channel |
|
||||
| 密钥 | Key | API访问密钥 | API access key |
|
||||
| 优先级 | Priority | 渠道选择优先级 | Channel selection priority |
|
||||
| 权重 | Weight | 负载均衡权重 | Load balancing weight |
|
||||
| 代理 | Proxy | 代理服务器地址 | Proxy server address |
|
||||
| 模型重定向 | Model Mapping | 请求体中模型名称替换 | Model name replacement in request body |
|
||||
|
||||
## 安全相关 (Security Related)
|
||||
|
||||
| 中文 | English | 说明 | Description |
|
||||
|------|---------|------|-------------|
|
||||
| 两步验证 | Two-Factor Authentication | 为账户提供额外安全保护的验证方式 | Additional security verification method for accounts |
|
||||
| 2FA | Two-Factor Authentication | 两步验证的缩写 | Abbreviation for Two-Factor Authentication |
|
||||
|
||||
## 计费相关 (Billing Related)
|
||||
|
||||
| 中文 | English | 说明 | Description |
|
||||
|------|---------|------|-------------|
|
||||
| 倍率 | Ratio | 价格计算的乘数因子 | Multiplier factor used for price calculation |
|
||||
| 倍率 | Multiplier | 价格计算的乘数因子（同义词） | Multiplier factor used for price calculation (synonym) |
|
||||
|
||||
## 翻译注意事项 (Translation Guidelines)
|
||||
|
||||
- **提示 (Prompt)** = 模型输入内容 / Model input content
|
||||
- **补全 (Completion)** = 模型输出内容 / Model output content
|
||||
- **倍率 (Ratio)** = 价格计算的乘数因子 / Multiplier factor for price calculation
|
||||
- **额度 (Quota)** = 可用的用户服务额度，有时也翻译为 Credit / Available service quota for users, sometimes also translated as Credit
|
||||
- **Token** = 根据上下文可能指 / Depending on context, may refer to:
|
||||
- API访问令牌 (API Token)
|
||||
- 模型处理的文本单元 (Text Token)
|
||||
- 系统访问令牌 (Access Token)
|
||||
|
||||
---
|
||||
|
||||
**贡献说明**: 如发现术语翻译不一致或有更好的翻译建议，欢迎提交 Issue 或 Pull Request。
|
||||
|
||||
**Contribution Note**: If you find any inconsistencies in terminology translations or have better translation suggestions, please feel free to submit an Issue or Pull Request.
|
||||
@@ -0,0 +1,107 @@
|
||||
# Русский глоссарий (Russian Glossary)
|
||||
|
||||
Данный раздел предоставляет стандартные переводы ключевой терминологии проекта на русский язык для обеспечения согласованности и точности переводов.
|
||||
|
||||
This section provides standard Russian translations for key project terminology to ensure consistency and accuracy in translations.
|
||||
|
||||
## Основные концепции (Core Concepts)
|
||||
|
||||
- Допускается использовать символы Emoji в переводе, если они были в оригинале.
|
||||
- Допускается использование сугубо технических терминов, если они были в оригинале.
|
||||
- Допускается использование технических терминов на английском языке, если они широко используются в русскоязычной технической среде (например, API).
|
||||
|
||||
| Китайский | Русский | Английский | Описание |
|
||||
|-----------|--------|-----------|----------|
|
||||
| 倍率 | Коэффициент | Ratio/Multiplier | Множитель для расчета цены. **Важно:** В контексте расчетов цен всегда использовать "Коэффициент", а не "Множитель" для обеспечения консистентности терминологии |
|
||||
| 令牌 | Токен | Token | Учетные данные API или текстовые единицы |
|
||||
| 渠道 | Канал | Channel | Канал доступа к поставщику API |
|
||||
| 分组 | Группа | Group | Классификация пользователей или токенов |
|
||||
| 额度 | Квота | Quota | Доступная квота услуг для пользователя |
|
||||
|
||||
## Модели (Model Related)
|
||||
|
||||
| Китайский | Русский | Английский | Описание |
|
||||
|-----------|--------|-----------|----------|
|
||||
| 提示 | Промпт/Ввод | Prompt | Содержимое ввода в модель |
|
||||
| 补全 | Вывод | Completion | Содержимое вывода модели. **Важно:** Не использовать "Дополнение" или "Завершение" - только "Вывод" для соответствия технической терминологии |
|
||||
| 输入 | Ввод | Input/Prompt | Содержимое, отправляемое в модель |
|
||||
| 输出 | Вывод | Output/Completion | Содержимое, возвращаемое моделью |
|
||||
| 模型倍率 | Коэффициент модели | Model Ratio | Коэффициент тарификации для разных моделей |
|
||||
| 补全倍率 | Коэффициент вывода | Completion Ratio | Дополнительный коэффициент тарификации для вывода |
|
||||
| 固定价格 | Цена за запрос | Price per call | Цена за один вызов |
|
||||
| 按量计费 | Оплата по объему | Pay-as-you-go | Тарификация на основе использования |
|
||||
| 按次计费 | Оплата за запрос | Pay-per-view | Фиксированная цена за вызов |
|
||||
|
||||
## Управление пользователями (User Management)
|
||||
|
||||
| Китайский | Русский | Английский | Описание |
|
||||
|-----------|--------|-----------|----------|
|
||||
| 超级管理员 | Суперадминистратор | Root User | Администратор с наивысшими привилегиями |
|
||||
| 管理员 | Администратор | Admin User | Системный администратор |
|
||||
| 普通用户 | Обычный пользователь | Normal User | Пользователь со стандартными привилегиями |
|
||||
|
||||
## Пополнение и обмен (Recharge & Redemption)
|
||||
|
||||
| Китайский | Русский | Английский | Описание |
|
||||
|-----------|--------|-----------|----------|
|
||||
| 充值 | Пополнение | Top Up | Добавление квоты на аккаунт |
|
||||
| 兑换码 | Код купона | Redemption Code | Код, который можно обменять на квоту |
|
||||
|
||||
## Управление каналами (Channel Management)
|
||||
|
||||
| Китайский | Русский | Английский | Описание |
|
||||
|-----------|--------|-----------|----------|
|
||||
| 渠道 | Канал | Channel | Канал поставщика API |
|
||||
| API密钥 | API ключ | API Key | Ключ доступа к API. **Важно:** Использовать "API ключ" вместо "API токен" для большей точности и соответствия общепринятой русскоязычной технической терминологии. Термин "ключ" более точно отражает функционал доступа к ресурсам, в то время как "токен" чаще ассоциируется с текстовыми единицами в контексте обработки языковых моделей. |
|
||||
| 优先级 | Приоритет | Priority | Приоритет выбора канала |
|
||||
| 权重 | Вес | Weight | Вес балансировки нагрузки |
|
||||
| 代理 | Прокси | Proxy | Адрес прокси-сервера |
|
||||
| 模型重定向 | Перенаправление модели | Model Mapping | Замена имени модели в теле запроса |
|
||||
| 供应商 | Поставщик | Provider/Vendor | Поставщик услуг или API |
|
||||
|
||||
## Безопасность (Security Related)
|
||||
|
||||
| Китайский | Русский | Английский | Описание |
|
||||
|-----------|--------|-----------|----------|
|
||||
| 两步验证 | Двухфакторная аутентификация | Two-Factor Authentication | Дополнительный метод проверки безопасности для аккаунтов |
|
||||
| 2FA | 2FA | Two-Factor Authentication | Аббревиатура двухфакторной аутентификации |
|
||||
|
||||
## Рекомендации по переводу (Translation Guidelines)
|
||||
|
||||
### Контекстуальные варианты перевода
|
||||
|
||||
**Промпт/Ввод (Prompt/Input)**
|
||||
|
||||
- **Промпт**: При общении с LLM, в пользовательском интерфейсе, при описании взаимодействия с моделью
|
||||
- **Ввод**: При тарификации, технической документации, описании процесса обработки данных
|
||||
- **Правило**: Если речь о пользовательском опыте и взаимодействии с AI → "Промпт", если о техническом процессе или расчетах → "Ввод"
|
||||
|
||||
**Token**
|
||||
|
||||
- API токен доступа (API Token)
|
||||
- Текстовая единица, обрабатываемая моделью (Text Token)
|
||||
- Токен доступа к системе (Access Token)
|
||||
|
||||
**Квота (Quota)**
|
||||
|
||||
- Доступная квота услуг пользователя
|
||||
- Иногда переводится как "Кредит"
|
||||
|
||||
### Особенности русского языка
|
||||
|
||||
- **Множественные формы**: Требуется правильная реализация множественных форм (_one,_few, _many,_other)
|
||||
- **Падежные окончания**: Внимательное отношение к падежным окончаниям в технических терминах
|
||||
- **Грамматический род**: Согласование рода технических терминов (например, "модель" - женский род, "канал" - мужской род)
|
||||
|
||||
### Стандартизированные термины
|
||||
|
||||
- **Вывод (Completion)**: Содержимое вывода модели
|
||||
- **Коэффициент (Ratio)**: Множитель для расчета цены
|
||||
- **Код купона (Redemption Code)**: Используется вместо "Код обмена" для большей точности
|
||||
- **Поставщик (Provider/Vendor)**: Организация или сервис, предоставляющий API или AI-модели
|
||||
|
||||
---
|
||||
|
||||
**Примечание для участников:** При обнаружении несогласованности в переводах терминологии или наличии лучших предложений по переводу, не стесняйтесь создавать Issue или Pull Request.
|
||||
|
||||
**Contribution Note for Russian:** If you find any inconsistencies in terminology translations or have better translation suggestions for Russian, please feel free to submit an Issue or Pull Request.
|
||||
Reference in New Issue
Block a user