Skip to content

AI-native knowledge base & Evernote/Obsidian alternative with instant sync & native MCP. Free on Cloudflare or self-hosted via Docker.

docs: align self-hosting storage documentation

tianma-if3245bbec0518
diff --git a/README.md b/README.md
index 83fcc3dc..75f143cc 100644
--- a/README.md
+++ b/README.md
@@ -214,7 +214,7 @@ If you want to migrate notes from other platforms to EdgeEver, please refer to t
## Docker Deployment Roadmap
-> 🐳 Docker-based self-hosting for VPS, NAS, and home servers is planned but is not yet available in current releases. The API now reserves a storage adapter boundary so a future SQLite + local/S3-compatible deployment can reuse the existing routes, REST API, MCP endpoint, schema, and migration history. See [Self-hosting and Docker architecture](docs/self-hosting-architecture.md).
+> 🐳 Docker-based self-hosting for VPS, NAS, and home servers is planned but is not yet a supported release. An experimental Bun runtime is already available for adapter development, with SQLite + local files or S3-compatible storage; PostgreSQL remains reserved at the contract level. See [Self-hosting and Docker architecture](docs/self-hosting-architecture.md).
## Acknowledgements
diff --git a/README.zh-CN.md b/README.zh-CN.md
index 76eba66e..85575883 100644
--- a/README.zh-CN.md
+++ b/README.zh-CN.md
@@ -228,7 +228,7 @@ Cloudflare Worker 侧执行图片处理会消耗计算/图片处理额度,因
## Docker 部署规划
-> 🐳 面向 VPS、NAS 和家庭服务器的 Docker 私有化部署已纳入规划,但当前版本尚不支持。API 已预留存储适配器边界,未来可在复用现有路由、REST API、MCP 接口、数据库结构和迁移历史的前提下接入 SQLite + 本地文件/S3 兼容存储。详见[自托管与 Docker 架构预留](docs/self-hosting-architecture.zh-CN.md)。
+> 🐳 面向 VPS、NAS 和家庭服务器的 Docker 私有化部署已纳入规划,但当前还不是正式支持的发行方式。现在已经提供用于适配器开发的实验性 Bun 运行入口,支持 SQLite + 本地文件或 S3 兼容存储;PostgreSQL 目前仍只预留契约。详见[自托管与 Docker 架构预留](docs/self-hosting-architecture.zh-CN.md)。
## 致谢
diff --git a/docs/self-hosting-architecture.md b/docs/self-hosting-architecture.md
index f9896d09..4dca0650 100644
--- a/docs/self-hosting-architecture.md
+++ b/docs/self-hosting-architecture.md
@@ -38,10 +38,10 @@ EdgeEver container
└── attachment store -> /data/resources
```
-The initial self-hosted adapter should preserve the existing SQLite schema and
-`migrations/*.sql` files. Attachments should be addressed by the same opaque
-object keys currently stored in `resources.object_key`; the implementation may
-use a local filesystem first and add an S3-compatible backend later.
+The initial self-hosted adapter preserves the existing SQLite schema and
+`migrations/*.sql` files. Attachments are addressed by the same opaque object
+keys currently stored in `resources.object_key`; the experimental runtime
+already supports both a local filesystem backend and an S3-compatible backend.
When PostgreSQL is implemented, it must introduce an explicit SQL dialect and
migration set for PostgreSQL-specific full-text search and transaction
diff --git a/docs/self-hosting-architecture.zh-CN.md b/docs/self-hosting-architecture.zh-CN.md
index 141a3289..1b505a70 100644
--- a/docs/self-hosting-architecture.zh-CN.md
+++ b/docs/self-hosting-architecture.zh-CN.md
@@ -34,9 +34,9 @@ EdgeEver 容器
└── 附件存储 -> /data/resources
```
-自托管适配器应继续复用现有 SQLite 结构和 `migrations/*.sql`;附件继续使用
-`resources.object_key` 中保存的不透明对象键,初版可以使用本地文件系统,
-后续再增加 S3 兼容存储。
+自托管适配器继续复用现有 SQLite 结构和 `migrations/*.sql`;附件继续使用
+`resources.object_key` 中保存的不透明对象键。目前的实验性运行入口已经支持
+本地文件系统和 S3 兼容对象存储两种后端。
未来实现 PostgreSQL 时,必须明确处理 SQL 方言以及 PostgreSQL 专用的全文搜索
和事务行为,并提供独立迁移策略,不能让现有 SQLite/D1 migration 文件产生歧义。