文档：明确本项目不提供 Docker 镜像与预编译二进制

Author: Open-Pixel-AI

README.md

@@ -95,9 +95,37 @@ PixelAPI 把 AI 订阅账号（Claude、Codex/OpenAI、Gemini、Antigravity、Gr
 
 ## 部署
 
-> **注意**：`deploy/install.sh` 与 `deploy/docker-compose*.yml` 中的下载地址和镜像
-> （`Wei-Shaw/sub2api` releases、`weishaw/sub2api` 镜像）指向的是**上游发布物**，
-> 用它们装到的是上游 Sub2API，不是本分支。本分支目前请从源码构建。
+### ⚠️ 本项目不提供 Docker 镜像和预编译二进制
+
+**这一点请务必先看清楚，否则你装到的会是另一个项目。**
+
+本仓库**没有**发布任何 Docker 镜像，Docker Hub 上不存在 PixelAPI 的镜像；本仓库的 Releases
+也只提供源码，**不附带预编译二进制**。
+
+而 `deploy/` 目录下的部署文件是从上游继承下来的，里面写死的地址**全部指向上游 Sub2API**：
+
+| 文件 | 里面写的东西 | 实际会装到什么 |
+| --- | --- | --- |
+| `deploy/docker-compose.yml`<br>`deploy/docker-compose.local.yml` | `image: weishaw/sub2api:latest` | **上游 Sub2API 的官方镜像**，不是本项目 |
+| `deploy/install.sh` | `GITHUB_REPO="Wei-Shaw/sub2api"` | 从**上游 Releases** 下载的二进制，不是本项目 |
+
+也就是说，直接 `docker compose up -d` 或者跑那条一键安装脚本，起来的是上游 Sub2API，
+本分支的账号广场、共享结算、Grok 接入等功能一个都不会有。
+
+**唯一受支持的方式是[从源码构建](#从源码构建)。**
+
+如果你确实需要容器化部署，得自己构建镜像——仓库根目录的 `Dockerfile` 是完整的多阶段构建
+（前端 + 内嵌前端的 Go 二进制），可以直接用：
+
+```bash
+# 自行构建镜像
+docker build -t pixelapi:local .
+
+# 然后把 compose 文件里的 image 换成自己构建的 tag
+#   image: weishaw/sub2api:latest   ->   image: pixelapi:local
+```
+
+同理，`deploy/install.sh` 若要复用，需要自行把 `GITHUB_REPO` 和产物下载逻辑改成你自己的发布源。
 
 ### 从源码构建
 

README_EN.md

@@ -99,9 +99,39 @@ by room or group, and the platform handles routing, metering, revenue split and
 
 ## Deployment
 
-> **Note**: `deploy/install.sh` and `deploy/docker-compose*.yml` still point at **upstream artifacts**
-> (`Wei-Shaw/sub2api` releases, the `weishaw/sub2api` image). Using them installs upstream Sub2API, not
-> this fork. Build from source for now.
+### ⚠️ No Docker Image or Prebuilt Binary Is Published
+
+**Read this first, or you will end up installing a different project.**
+
+This repository publishes **no Docker image** — there is no PixelAPI image on Docker Hub — and its
+Releases contain **source code only, with no prebuilt binaries attached**.
+
+The files under `deploy/` are inherited from upstream, and every address hardcoded in them points at
+**upstream Sub2API**:
+
+| File | What it references | What you actually get |
+| --- | --- | --- |
+| `deploy/docker-compose.yml`<br>`deploy/docker-compose.local.yml` | `image: weishaw/sub2api:latest` | **Upstream Sub2API's official image**, not this project |
+| `deploy/install.sh` | `GITHUB_REPO="Wei-Shaw/sub2api"` | A binary from **upstream Releases**, not this project |
+
+In other words, running `docker compose up -d` or that one-liner install script gives you upstream
+Sub2API — with none of this fork's account marketplace, shared-revenue settlement or Grok support.
+
+**Building [from source](#build-from-source) is the only supported path.**
+
+If you do need containerized deployment, build the image yourself. The `Dockerfile` at the repository
+root is a complete multi-stage build (frontend plus a Go binary with the frontend embedded):
+
+```bash
+# Build your own image
+docker build -t pixelapi:local .
+
+# Then replace the image in the compose files with your own tag
+#   image: weishaw/sub2api:latest   ->   image: pixelapi:local
+```
+
+Likewise, to reuse `deploy/install.sh` you must repoint `GITHUB_REPO` and its download logic at your
+own release source.
 
 ### Build From Source