Two small, independent file-sharing services for handing files to friends in mainland China from a Shenzhen ECS box — a browsable folder, and expiring links with an admin UI. Each is its own Docker Compose service with no shared database or cloud dependency.
Deliberately reachable by bare IP, not a domain — mainland China requires ICP filing for anything served at a domain name, and a bare IP sidesteps that entirely.
| App | Port | What it's for | Source |
|---|---|---|---|
fileshare/ |
8080 | Browsable directory listing + password-gated management page (upload / rename / delete / copy-link) | Custom Python (stdlib only) |
gokapi/ |
9001 | Expiring links with a real admin UI, encrypted at rest | Gokapi |
fileshare replaced Filebrowser, then Alist — Filebrowser archives 2026-09-01 with no further releases, and Alist ended up being more than this needed. gokapi was added afterward to cover one-off private links with real expiry, a role a since-removed companion app (quickshare-sz) used to fill.
Each app directory is self-contained:
cd fileshare # or gokapi
cp .env.example .env # fileshare only — edit in real values
docker compose up -d --buildgokapi doesn't use .env — its admin account is created on first boot via its own /setup wizard in the browser, not environment variables. Its default docker-compose.yml pulls the upstream f0rc3/gokapi image directly; if that registry is blocked on your network (see below), use docker-compose.china.yml instead.
Official images (python:3.12-alpine, alpine:latest) pull fine through China-side Docker registry mirrors. Third-party namespaced images — like f0rc3/gokapi — get a 403 from the docker.m.daocloud.io mirror, and the once-common hub-mirror.c.163.com mirror is dead (its hostname doesn't even resolve anymore). GitHub's release-asset CDN (release-assets.githubusercontent.com) is also unreachable directly from mainland China.
The workaround, wired up as gokapi/docker-compose.china.yml:
- On a machine with normal internet access — not the target server — run
gokapi/fetch-binary.shto download the Gokapi release binary. scpthe resultinggokapi/bin/directory to the server.docker compose -f docker-compose.china.yml up -d --build— this builds a thin local image wrapping the binary instead of pulling a prebuilt one.
The Shenzhen deployment serves a mainland Chinese audience, so its public download/password pages are translated to Simplified Chinese via gokapi/custom/public.js — Gokapi's supported no-rebuild customization hook (it auto-loads any custom/public.js it finds, mounted at /app/custom in docker-compose.china.yml). Its PublicName config value is also set to 深圳文件快传 instead of an English name. This is scoped to that one deployment on purpose — other boxes running this repo keep the English UI unless you copy custom/public.js over and mount it the same way.
Gokapi caches custom/public.js for 2 days, so after editing it on the server, bump custom/version.txt (a plain integer, e.g. echo 2 > version.txt) and restart the container — this changes the script's URL and forces every client to fetch the new version instead of a stale cached copy.
Four reference pages, published as standalone HTML (also mirrored in docs/ here — English only, regardless of which repo language section you're reading):
- File Share Cheat Sheet — the original quick-reference for fileshare
- IP Change Checklist — what to do within a minute of the server's IP changing
- Where Your Files Live — storage paths, add/remove commands, and retention per app
- New Box, Same Stack — replicating both apps onto a fresh Ubuntu box
- Every credential in this repo's compose files is a placeholder read from a gitignored
.env— real values live only on the deployed server, never in git history. gokapi's data directory is encrypted at rest (Level 1 — local key, so the container still restarts unattended after a crash or reboot without manual intervention).filesharestores files unencrypted, as plain filesystem paths — access control is entirely "does the link/password, whichever the app uses."
两个独立的小型文件共享服务，用于从深圳 ECS 向国内朋友分享文件——可浏览目录，以及带管理界面的到期链接。每个都是独立的 Docker Compose 服务，没有共享数据库或云端依赖。
刻意通过裸 IP 访问，而非域名——中国大陆要求任何通过域名对外提供服务的站点完成 ICP 备案，裸 IP 完全绕开了这项要求。
| 应用 | 端口 | 用途 | 源码 |
|---|---|---|---|
fileshare/ |
8080 | 可浏览目录列表 + 密码保护的管理页面（上传 / 改名 / 删除 / 复制链接） | 自定义 Python（仅标准库） |
gokapi/ |
9001 | 带真正管理界面、静态加密的到期链接 | Gokapi |
fileshare 先后替代了 Filebrowser 和 Alist——Filebrowser 将于 2026-09-01 归档、不再有后续发布，而 Alist 的功能则超出了实际需求。gokapi 是之后加入的，用来覆盖一次性私密链接、带真正到期机制的场景——这个角色以前由已下线的伴生应用 quickshare-sz 承担。
每个应用目录都是自包含的：
cd fileshare # 或 gokapi
cp .env.example .env # 仅 fileshare 需要——填入真实值
docker compose up -d --buildgokapi 不使用 .env——它的管理员账号是首次启动时通过浏览器里的 /setup 向导创建的，而不是环境变量。它默认的 docker-compose.yml 直接拉取上游 f0rc3/gokapi 镜像；如果你的网络屏蔽了该镜像仓库（见下文），改用 docker-compose.china.yml。
官方镜像（python:3.12-alpine、alpine:latest）通过国内 Docker 镜像源都能正常拉取。但第三方命名空间的镜像——比如 f0rc3/gokapi——会被 docker.m.daocloud.io 镜像源返回 403，而曾经常用的 hub-mirror.c.163.com 镜像源已经失效（连域名都解析不出来）。GitHub 的发布资源 CDN（release-assets.githubusercontent.com）在中国大陆也无法直接访问。
对应的解决方案，已经写成了 gokapi/docker-compose.china.yml：
- 在一台能正常访问互联网的机器上——不是目标服务器——运行
gokapi/fetch-binary.sh下载 Gokapi 的发布二进制文件。 - 把生成的
gokapi/bin/目录通过scp传到服务器上。 - 执行
docker compose -f docker-compose.china.yml up -d --build——这会基于该二进制文件在本地构建一个精简镜像，而不是拉取预先构建好的镜像。
深圳部署面向中国大陆用户，因此其公开下载页 / 密码验证页通过 gokapi/custom/public.js 翻译成简体中文——这是 Gokapi 官方支持的免重新构建自定义方式（只要在 /app/custom 下挂载一个 custom/public.js，Gokapi 会自动加载它，docker-compose.china.yml 里已经配好了这个挂载）。同时把 PublicName 配置项改成了「深圳文件快传」而不是英文名称。这个改动只作用于这一台服务器——用本仓库部署的其他服务器默认仍是英文界面，除非你把 custom/public.js 复制过去并按同样方式挂载。
Gokapi 会把 custom/public.js 缓存 2 天，所以在服务器上改完这个文件后，需要把 custom/version.txt（一个纯数字，比如执行 echo 2 > version.txt）加一并重启容器——这会让脚本的 URL 发生变化，逼所有客户端重新拉取新版本，而不是继续用缓存里的旧版本。
四份参考文档，已发布为独立 HTML 页面（同时也镜像在本仓库的 docs/ 目录下——文档内容均为英文，与你正在阅读的语言区块无关）：
- File Share Cheat Sheet —— fileshare 最初的速查文档
- IP Change Checklist —— 服务器 IP 变更后一分钟内该做的事
- Where Your Files Live —— 每个应用的存储路径、增删命令与保留策略
- New Box, Same Stack —— 如何把两个应用迁移到一台全新的 Ubuntu 主机上
- 本仓库 compose 文件中的所有凭据都只是占位符，真实值从被 gitignore 排除在外的
.env文件中读取——真实值只存在于已部署的服务器上，从未进入 git 历史记录。 gokapi的数据目录是静态加密的（Level 1——密钥保存在本地，因此容器在崩溃或重启后仍能无人值守自动恢复）。fileshare未加密存储文件，直接以明文文件系统路径存放——访问控制完全依赖链接和密码。